Hello,
thanks for your feedback.
In fact I didn't realize that the RAM disk image was not found. I guess
it was due to the fact that the board was not able to reach the
Workstation using TFTP for any reason, anyhow this is the fconfig -l
output you asked for:
******************************************Redboot Boot
Script************************************
fconfig -l
Run script at boot: true
Boot script:
.. fis load vmlinux
.. load -r -b 0x00600000 -h 10.0.0.34 ts7260-sdcard-initrd-1.02.gz
.. exec -r 0x00600000 -s 448760 -b 0x00218000 -l 0x000C0000 -c
"console=ttyAM0,115200 root=/dev/ram0 init=/linuxrc rw"
Boot script timeout (100ms resolution): 1
Use BOOTP for network configuration: false
Gateway IP address: 10.0.0.101
Local IP address: 10.0.0.33
Local IP address mask: 255.0.0.0
Default server IP address: 10.0.0.101
Network hardware address [MAC]: 0x00:0xD0:0x69:0x40:0x6A:0x44
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
****************************************End of the boot
script***********************************************
but a new problem occurred when the board was able to boot for twice, I
have deleted the first reboot because it was already pasted in the first
post:
****************************************BOOT OUTPUT
MESSAGE*******************************************
/dev/sdcard0/disc0/part3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdcard0/disc0/part3: ***** REBOOT LINUX *****
/dev/sdcard0/disc0/part3: 15330/60000 files (3.0% non-contiguous),
232625/239104 blocks
fsck corrected errors on the root partition, but requested that
the system be rebooted (exit code 3).
Automatic reboot in 5 seconds.
Restarting system.
>> TS-NANDBOOT, Rev 1.00 - built 10:14:31, Mar 7 2005
>> Copyright (C) 2004, Technologic Systems
>> TS-BOOTROM, Rev 1.08 - built 16:18:21, Jun 5 2006
>> Copyright (C) 2006, Technologic Systems
>> TS-7260: Rev E1 CPU, Rev E PLD, 32MB SDRAM, options ( SDCARD )
>> TS-5620: detected, battery OK, time ( 18:24:27, May 3 2010 )
+Ethernet eth0: MAC address 00:d0:69:40:6a:44
IP: 10.0.0.33/255.0.0.0, Gateway: 10.0.0.101
Default server: 10.0.0.101
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version current-TS_5 - built 10:49:48, Jun 19
2006
RAM: 0x00000000-0x02000000, [0x00052ab0-0x01ff9000] available
FLASH: 0x60000000 - 0x62000000, 2048 blocks of 0x00004000 bytes each.
== Executing boot script in 0.100 seconds - enter ^C to abort
RedBoot> fis load vmlinux
RedBoot> load -r -b 0x00600000 -h 10.0.0.34 ts7260-sdcard-initrd-1.02.gz
Using default protocol (TFTP)
Raw file loaded 0x00600000-0x0066d8f7, assumed entry at 0x00600000
RedBoot> exec -r 0x00600000 -s 448760 -b 0x00218000 -l 0x000C0000 -c
"console=ttyAM0,115200 root=/dev/ram0 init=/linuxrc rw"
Linux version 2.4.26-ts11 (gcc version 3.3.4) #22 Tue
Jun 6 12:23:09 MST 2006
********I HAVE CUT SOME MESSAGES HERE IN ORDER TO SHORTEN THE
MESSAGE*************************
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 438K
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
Freeing init memory: 72K
Using sdcard.o
sdcard0: Technologic Systems SD card controller, address 0x13000000
sdcard0: card size 498176 sectors
Partition check:
sdcard0a: p1 p2 p3
INIT: version 2.86 booting
Creating extra device nodes...done.
Started device management daemon v1.3.25 for /dev
Checking root file system...
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
/dev/sdcard0/disc0/part3: clean, 15330/60000 files, 232625/239104 blocks
Cleaning up ifupdown...done.
Loading modules: af_packet usb-ohci usb.c: registered new driver
usbdevfs
usb.c: registered new driver hub
usb-ohci-ep93xx usb-ohci.c: USB OHCI at membase 0xe0020000, IRQ 56
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 3 ports detected
Checking all file systems...
fsck 1.37 (21-Mar-2005)
... done.
hub.c: new USB device not_pci-3, assigned address 2
usb.c: USB device 2 (vend/prod 0x90c/0x1000) is not claimed by any
active driver.
Setting up networking...done.
Starting hotplug subsystem: usb isapnp ide scsi.
Setting up IP spoofing protection: rp_filter.
Enabling packet forwarding...done.
Configuring network interfaces...Unable to handle kernel NULL pointer
dereference at virtual address 00000084
pgd = c05dc000
[00000084] *pgd=0179f001, *pmd = 0179f001, *pte = 00000000, *ppte =
00000000
Internal error: Oops: 7
CPU: 0
pc : [<c02f2368>] lr : [<c02f2368>] Not tainted
sp : c05ede40 ip : c05ede18 fp : c066fa40
r10: 00000008 r9 : c05edec0 r8 : c057b160
r7 : 00000000 r6 : 00000148 r5 : c56dc070 r4 : 00000000
r3 : a0000093 r2 : 00000001 r1 : 00000001 r0 : 0000002f
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment user
Control: C000317F Table: 005DC000 DAC: 00000015
Process pump (pid: 338, stack limit = 0xc05ec368)
Stack: (0xc05ede40 to 0xc05ee000)
de40: c06ac1c0 c037195c c60279a4 00000000 00000148 c05edee8 ffffffea
00000800
de60: 2aac0000 00000000 c057b160 00000000 c05ede88 00000148 00000014
c05ededc
de80: 00000000 c02e1608 00000152 00000000 00000000 00000000 00000000
c057b160
dea0: 00000000 7ffef388 7ffeddfc 00000148 c02e2364 7ffeddfc 00000148
00000000
dec0: c05ededc 00000014 c05edeb4 00000001 00000000 00000000 00000000
00080000
dee0: 00000002 06000000 ffffffff 0000ffff c179ff00 c0362fd4 00000001
2abc0000
df00: c0248784 2aac0000 c05dcaa8 c05dcaa8 2aac1000 00000000 c0229720
2aac1000
********************************END OF THE
REBOOT**********************************************
As you can see some weird output is appearing for ever and ever
till I have to reset the board. What I'm not sure is if it has to do
with the kernel or whit the SD Card.
Other test I've done is trying to mount the SD Card when the
board boots using the same kernel, but with the rootfs that the board
has in flash and I'm able to mount the SD Card and see its contents:
mount -t ext2 /dev/sdcard0/disc0/part3 /mnt/cf
$ cd /mnt/cf
$ ls -l
drwxr-xr-x 2 root root 2048 May 2 2006 bin
drwxr-xr-x 2 root root 1024 May 2 2006 boot
drwxr-xr-x 3 root root 17408 May 2 2006 dev
drwxr-xr-x 64 root root 3072 May 3 18:25 etc
drwxr-xr-x 2 root root 1024 May 2 2006 home
drwxr-xr-x 2 root root 1024 Oct 20 2006 include
drwxr-xr-x 7 root root 3072 May 2 2006 lib
drwx------ 2 root root 1024 May 2 2006 lost+found
drwxr-xr-x 6 root root 1024 May 2 2006 mnt
drwxr-xr-x 2 root root 1024 May 2 2006 nfsroot
drwxr-xr-x 2 root root 1024 May 2 2006 opt
dr-xr-xr-x 2 root root 1024 May 2 2006 proc
drwxr-xr-x 3 root root 1024 May 2 2006 root
drwxr-xr-x 2 root root 2048 May 2 2006 sbin
drwxr-xr-x 2 root root 1024 May 2 2006 sys
drwxr-xr-x 3 root root 1024 May 1 16:41 tmp
drwxr-xr-x 12 root root 1024 May 2 2006 usr
drwxr-xr-x 15 root root 1024 May 2 2006 var
$ cd /
$ umount /mnt/cf
Thank you again everybody for your comments.
Kind regards.
Jose.
--- In "j.chitte" <> wrote:
>
>
>
>
>
> --- In "jgarciallamas" jgarciallamas@ wrote:
> >
> >
> > Hi there,
> >
> > this is my first post in this forum so hi everybody. I have been
reading your posts since years so thanks everybody for your
contributions.
> >
> > I'm facing a problem regarding the boot process using the SD card,
I know that I have not been the only one. I guess I have read all the
posts regarding this issue and I have also tried different things but
the question is that I am still on the same point, this is without being
able to boot from the SD card.
> >
> > As I mentioned I'm using the TS7260. Following the instruccions on
wiki what I have done till now is:
> >
> > 1. Using the kernel the board takes by default, this is:
> >
> > Linux version 2.4.26-ts11 (gcc version 3.3.4) #22
Tue Jun 6 12:23:09 MST 2006
> >
> > 2. Using the initrd I have found in the repositories:
> >
> > ts7260-sdcard-initrd-1.03.gz
> >
> > In order to load the initrd file I'm using a TFTP server.
> >
> > 3. The SD card I'm using is the default one, 256Mb, so that Debian
is preinstalled on partition 3.
> >
> > 4. I have modified Redboot boot script so these are the
instruccions:
> >
> > RedBoot> fis load vmlinux
> > RedBoot> load -r -b 0x00600000 -h 10.0.0.34
ts7260-sdcard-initrd-1.03.gz
> > Using default protocol (TFTP)
> > Raw file loaded 0x00600000-0x0066d81d, assumed entry at 0x00600000
> > RedBoot> exec -r 0x00600000 -s 447849 -b 0x00218000 -l 0x000C0000 -c
"console=ttyAM0,115200 root=/dev/ram0 init=/linuxrc rw"
> >
> >
> > From this point on the board boots for the first time, where some
kind of checking is done in the sdcard. Afterwards, a second boot
process is taken but without success. This is the point where a kernel
panic message is shown:
> > Kernel panic: VFS: Unable to mount root fs on 01:00
> >
> > This is all the output of the whole process I mention above:
> >
> HI,
>
> you will note the second time arount it is not finding the initrd.
>
> RedBoot> fis load vmlinux
> RedBoot> load -r -b 0x00600000 -h 10.0.0.34
ts7260-sdcard-initrd-1.02.gz
> Unable to reach host 10.0.0.34 (10.0.0.34)
>
> so later when it tries to use it it fails :
>
>
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
> Freeing initrd memory: 438K
> Kernel panic: VFS: Unable to mount root fs on 01:00
>
> The first time it works:
>
> RedBoot> load -r -b 0x00600000 -h 10.0.0.34
ts7260-sdcard-initrd-1.02.gz
> Using default protocol (TFTP)
> Raw file loaded 0x00600000-0x0066d8f7, assumed entry at 0x00600000
>
>
> I don't use SD but that is what you need to sort out. Look at why it
is not saying "using default protocol" the second time. May it is trying
something else. Specify the protocol explicitly in the script.
>
> Maybe , rather that the output, you could post your actual boot script
as shown by
>
> RedBoot> fconfig -l
>
> If you fsck the SD partition before booting and umount it cleanly does
it boot OK? That's not a solution but it may help you see what's up.
>
> HTH.
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|