Yet another NFS boot problem

From your log above, it appears your bootargs have

"nfsroot=:/home/andre/workdir/filesys"

which is missing the ip address before the ":"

I don't know why the $(nfshost) does not want to resolve automatically.  I changed the boot args with the following command:

setenv bootargs video=davincifb:vid0=0,2500K:vid1=0,2500K:osd=720x576x16,2025K:davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd) console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.0.0.3:$(rootpath),nolock mem=118M

which resulted in the following environment settings:

bootdelay=3
baudrate=115200
filesize=13bf20
fileaddr=80700000
netmask=255.255.255.0
hostname=ProtocleaDVP
bootfile=uImage
nfshost=10.0.0.3
rootpath=/home/andre/workdir/filesys
setboot=setenv bootargs $(bootargs) davinci_end_mngr.ch0_mode=$(videostd)
ipaddr=10.0.0.6
bootargs=video=davincifb:vid0=0,2500K:vid1=0,2500K:osd=720x576x16,2025K:davinci_
enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal console=ttyS0,115200
n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.0.0.3:/home/andre/workdir/filesy
s,nolock mem=118M
bootcmd=bootm 0x2060000
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:53:ec
videostd=pal

And when I boot it:

Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.0.0.6
IP-Config: Complete:
      device=eth0, addr=10.0.0.6, mask=255.255.255.0, gw=10.0.0.2,
     host=10.0.0.6, domain=, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=10.0.0.3, rootpath=
Looking up port of RPC 100003/2 on 10.0.0.3
Looking up port of RPC 100005/1 on 10.0.0.3
Root-NFS: Server returned error -13 while mounting /home/andre/workdir/filesys
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

Is it possible that the error lies with the bootcmd variable, and if so, what should it be?

That error -13 is fairly common, please see this thread for some possible solutions.

Thanks.  The possible solutions led me to believe that the NFS was indeed the problem.  I could for example not run the exportfs command, because that file did not exist.  From theopenSUSE forum I then got advice, and uninstalled the NFS-server module from YaST->Software Manager, and installed the NFS-kernel-server.  This now allows me to successfully run the exportfs command as described in the GSG.

BUT.... instead of progressing I think I've gone back a number of steps or have now ended in another dead end.  After getting the NFS setup properly (at least I think I did because that does not seem to be the problem now), I rebooted the EVM and got to following ouput:

IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.0.0.6
IP-Config: Complete:
      device=eth0, addr=10.0.0.6, mask=255.255.255.0, gw=10.0.0.2,
     host=10.0.0.6, domain=, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=10.0.0.3, rootpath=
Looking up port of RPC 100003/2 on 10.0.0.3
Looking up port of RPC 100005/1 on 10.0.0.3
VFS: Mounted root (nfs filesystem).
Freeing init memory: 136K
FATAKernel panic - not syncing: Attempted to kill init!
L: kernel too ol d

I have not seen this error message before, and I can't find anything on your forum about this.  So do you have any idea what to do now?  The fact that it happened just after the NFS mounting makes me think the NFS may still have something to do with it, but what I don't know.

I have actually seen this one before too, though the error message is broken up a bit, it should say 'FATAL: kernel too old', and I believe this will stem from booting a kernel image that is not in line with the file system you are mounting, for an example of this being fixed see here.

Thanks Bernie

I had a look at the thread you linked to, but feel a bit stupid asking how I should update the kernel?  Am I correct when saying these are the sections described in GSG 4.5 and 4.6. So should I just skip the NFS section (4.3.8) and carry on as if it worked?

It makes sense that it is another mismatch in software.  I kept the old Virtual machine that worked (at least up to the login point of the EVM), so I checked the NFS and the bootargs, and they are all exactly the same, except for the ip address obviously.  Plus, the current EVM settings still boot on that board, so I think I can assume they are right. 

I am currently hoping that I do not need to go through 4.5 and 4.6 now... because nothing seems to work.   In section 4.5, all goes well until I start with the make commands, and the first make command returns the following error:

andre@ProtocleaDVM:~/workdir/lsp/ti-davinci/linux-2.6.18_pro500> make ARCH=arm CROSS_COMPILE=arm_v5t_le inci_dm644x_defconfig
  HOSTCC  scripts/basic/fixdep
/bin/sh: gcc: command not found
make[1]: *** [scripts/basic/fixdep] Error 127
make: *** [scripts_basic] Error 2
andre@ProtocleaDVM:~/workdir/lsp/ti-davinci/linux-2.6.18_pro500> make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm644x_defconfig
  HOSTCC  scripts/basic/fixdep
/bin/sh: gcc: command not found
make[1]: *** [scripts/basic/fixdep] Error 127
make: *** [scripts_basic] Error 2

I can't rebuild the kernel with the make commands either.   It returns a very long list of errors, and the last few are:

/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c:2104: error: too many arguments to function ‘__release_region’
/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c:2112: warning: implicit declaration of function ‘class_simple_device_remove’
/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c:2113: warning: implicit declaration of function ‘class_simple_destroy’
/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c: In function ‘cmem_exit’:
/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c:2226: error: too many arguments to function ‘__release_region’
make[3]: *** [/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.o] Error 1
make[2]: *** [_module_/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module] Error 2
make[2]: Leaving directory `/home/andre/workdir/lsp/ti-davinci/linux-2.6.18_pro500'
make[1]: *** [release] Error 2
make[1]: Leaving directory `/home/andre/dvsdk_2_00_00_22/linuxutils_2_23_01/packages/ti/sdo/linuxutils/cmem/src/module'
make: *** [cmem] Error 2

So I am now hoping that you are going to tell me that rebuilding the kernel should be done in another way...

AndreC said:

I had a look at the thread you linked to, but feel a bit stupid asking how I should update the kernel? 

Typically the easiest way to update the kernel is to boot it over TFTP as discussed in the GSG, you could also reflash the board with the new kernel uImage but for development purposes it is usually just as well to TFTP the kernel for easy changing. Just make sure you are booting a uImage file that was generated or included with the DVSDK install you are using for the filesystem.

AndreC said:

Am I correct when saying these are the sections described in GSG 4.5 and 4.6. So should I just skip the NFS section (4.3.8) and carry on as if it worked?

There should be a uImage file in your install already under something like dvsdk_2_00_00_22\PSP_02_00_00_140\bin\dm6446 so you may not need to go through the kernel rebuild process, though it is good to be able to rebuild your kernel for the future.

AndreC said:

andre@ProtocleaDVM:~/workdir/lsp/ti-davinci/linux-2.6.18_pro500> make ARCH=arm CROSS_COMPILE=arm_v5t_le inci_dm644x_defconfig
  HOSTCC  scripts/basic/fixdep
/bin/sh: gcc: command not found
make[1]: *** [scripts/basic/fixdep] Error 127
make: *** [scripts_basic] Error 2
andre@ProtocleaDVM:~/workdir/lsp/ti-davinci/linux-2.6.18_pro500> make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm644x_defconfig
  HOSTCC  scripts/basic/fixdep
/bin/sh: gcc: command not found
make[1]: *** [scripts/basic/fixdep] Error 127
make: *** [scripts_basic] Error 2

This sounds like your host may be missing some typical build tools, what host Linux distribution are you using? You may need to install a gcc build package for your host Linux distribution.

I've been able to fix a couple of my problems, to the point that I am now quite sure that my problems are not associated with the NFS anymore.  I had to delete the nfs-server module using YaST -> Software Manager, and replaced it with nfs-kernel-server.  This now allows me to use the exportfs commands, and everything seems to work.  When booting, I still got the FATAL panic message but at least I now know it is not the NFS.

I then tried booting the kernel that comes with the new software from the TFTP and did the following (BTW - I'm using a SUSE 10.3 Linux distribution):

1) I copied the uImage-dm6446 file from the ..\PSP_02_00_00_140\bin\dm6446 directory to the /srv/ftp directory, as that is where the ftp directory is suppose to be on my machine.

2)I set the environmental variables as described in section 4.7 of GSGv2

3)When I boot, it came up with the following error.  I've seen and fixed it before but I don't know what differenced there are with the FTP boot the normal NFS boot.  Last time I fixed "Bad Magic Number" errors by changing the bootm umber.  What should I do now?

DaVinci EVM # boot                  
## Booting image at 0000000d ...                                
Bad Magic Number                
## Booting image at 80700000 ...                                

Bad Magic Number               
DaVinci EVM # printenv                      
bootdelay=3           
baudrate=115200
filesize=13bf20
fileaddr=80700000
netmask=255.255.255.0
hostname=ProtocleaDVP
nfshost=10.0.0.3
setboot=setenv bootargs $(bootargs) davinci_end_mngr.ch0_mode=$(videostd)
ipaddr=10.0.0.6
nfshost=10.0.0.3
rootpath=/home/andre/workdir/filesys
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:53:ec
videostd=pal
bootcmd=bootm dhcp;bootm
serverip=10.0.0.3
bootfile=uImage-dm6446
bootargs=video=davincifb:vid0=0,2500K:vid1=0,2500K:osd=720x576x16,2025K:davinci_
enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal console=ttyS0,115200
n8 noinitrd rw ip=dhcp root=/dev/hda1 mem=118M

Environment size: 652/65532 bytes
DaVinci EVM #

It looks to me like the problem lies with the fileaddr environment variable, but I don't know what to change it to?

As for rebuilding the kernel:  I was able to install the gcc components, and consequently I was able to successfully execute the make commands (thanks for the advice!).  So I was able to complete section 4.5 and I now have a fresh uImage situated in /srv/ftp on my computer. I think the FTP directory on my machine is at /srv/ftp, but when I boot the system as described in section A.4.4 of the GSG, it comes up with the following:

BOOTP broadcast 1
DHCP client bound to address 10.0.0.6
TFTP from server 10.0.0.3; our IP address is 10.0.0.6
Filename 'uImage'.
Load address: 0x80700000
Loading: T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again

How can I check whether the TFTP works?  It may be a directory problem, so here's my environment variables again (after I changed them from section 4.7 to A.4.4):

filesize=13bf20
fileaddr=80700000
netmask=255.255.255.0
hostname=ProtocleaDVP
nfshost=10.0.0.3
setboot=setenv bootargs $(bootargs) davinci_end_mngr.ch0_mode=$(videostd)
ipaddr=10.0.0.6
bootcmd=dhcp;bootm
serverip=10.0.0.3
bootfile=uImage
rootpath=/home/andre/workdir/filesys
nfshost=10.0.0.3
bootargs=video=davincifb:vid0=0,2500K:vid1=0,2500K:osd=720x576x16,2025K:davinci_
enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal console=ttyS0,115200
n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.0.0.3:/home/andre/workdir/filesy
s,nolock mem=118M
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:53:ec
videostd=pal

Environment size: 690/65532 bytes

Any ideas?  What difference does it make using the self built kernel vs the one from the PSP_02_00_00_140... directory?

AndreC said:

DaVinci EVM # boot                  
## Booting image at 0000000d ...                                
Bad Magic Number                
## Booting image at 80700000 ...                                

Bad Magic Number      

Bad magic number just means that the image you are trying to boot is corrupted or not there, in this case it probably means that the image does not exist at the location you specified because it has not been loaded there yet. I say this because of your second query here where your TFTP boot is failing, if TFTP never succeeds and you do nothing else to load up a kernel such as read from flash, than there will be no image at 80700000.

AndreC said:

BOOTP broadcast 1
DHCP client bound to address 10.0.0.6
TFTP from server 10.0.0.3; our IP address is 10.0.0.6
Filename 'uImage'.
Load address: 0x80700000
Loading: T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again

How can I check whether the TFTP works? 

 I have not tried running through this with SuSe so it is hard for me to say what exactly could be going wrong here, that /srv/ftp folder sounds unusual to me, but you can configure the TFTP server to work out of whatever directory you specify so its definately possible. The output you are getting is what can happen if there is no TFTP server at the IP address you are trying to access, so I would start by double checking your IP addressing scheme and the firewall on your host PC, as well as ensuring that the TFTP server is running on the host.

AndreC said:

What difference does it make using the self built kernel vs the one from the PSP_02_00_00_140... directory?

If you don't change any of the kernel build configurations (i.e. make menuconfig) than there should be no difference, generally in the long run however you will want to change the kernel build configuration and take out pieces you don't need as well as adding in pieces that you will need, primarily hardware driver support.

After a while I finally managed to get the TFTP server correctly installed.  (I should have installed the YaST2-TFTP-server and not just the TFTP module).  When I executed the the TFTP server, it also created the /tftpboot directory, so my system is now similar to the default one.  I then copied both the uImage I created from GSG2 4.5  and the uImage-dm6446 from the installation to the /tftpboot directory.  But, as always, there is another problem that popped up.  When I boot, the board seems to "crash" or freeze and doesn't get past the following section:

R
bootdelay=3latform dev
baudrate=115200emac           
filesize=13bf20               
fileaddr=80700000es driver        
netmask=255.255.255.0video capture interfa
hostname=ProtocleaDVP00x576x16,2025K:davin
nfshost=10.0.0.3                
setboot=setenv bootargs $(bootargs) davinci_end_mngr.ch0_mode=$(videostd)e.1'. Parent at platform                                                 
ipaddr=10.0.0.6ing platform de
bootcmd=dhcp;bootm                  
bootfile=uImage      
DaVinci
rootpath=/home/andre/workdir/filesys                                 
25
serverip=10.0.0.5rm Multi-Platform
nfshost=10.0.0.5                
hub 1-0:1.0: USB hub found                          

hub 1-0:
stdin=serialetectedbus r
stdout=serialigned bus    
stderr=serial             
ethaddr=00:0e:99:02:53:ecNET: Registered protocol
videostd=pal            

Environment size: 661/65532 byteshash table of 512 buckets, 4Kbyte
DaVinci EVM # printenv                      
bootdelay=3 1-0:1.0: U
baudrate=115200               
filesize=13bf20tables configur
fileaddr=8070000092 bind 16384)   
netmask=255.255.255.0                     
hostname=ProtocleaDVP0: 1 port detected   
nfshost=10.0.0.3        
NET: Re
rootpath=/home/andre/workdir/filesysng to colour frame buffer           
serverip=10.0.0.5            
    
nfshost=10.0.0.5omain=, nis-doma
bootargs=video=davincifb:vid0=0,2500K:vid1=0,2500K:osd0=720x576x16,2025K:davinci                        
     bootserver=0.0.0.0, rootserver=10.0.0.3, rootpath=
_enc_mngr.ch0_output=COMPOSITE console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/               
OSD_VIDWINMD=             
Looking up port of RPC 100003/2 on 10
dev/nfs nfsroot=10.0.0.5:/home/andre/workdir/filesys,nolock mem=120M                                                                  
p
stdin=serialr 10.0.0.3 n
stdout=serial timed out   
stderr=serial             
ethaddr=00:0e:99:02:53:ec     
OSD_OSDWIN1MD=00000
videostd=pal        
   

Kernel pan
DaVinci EVM # saveenv Unable to mount root
Saving Environment to Flash... idebu                        
Un-Protected 1 sectors                      
Erasing Flash...    
Bank #0: 80
Erasing sector  4 ... done.         


U-Boot 1.1.3 (M
 Erase Operation Completed.                           
Erased 1 sectorsting image at   
Writing to Flash...-doneRM Clock :- 283MZsing an
Protected 1 sector                
hostname=ProtocleaDVP    
bootdelay=3     
nfshost=10.0.0.315200           
setboot=setenv bootargs $(bootargs) davinci_end_mngr.ch0_mode=$(videostd)=80700000ompressed)                           
netmask=255.255.255.0     
ipaddr=10.0.0.6
hostname=Proto
bootcmd=dhcp;bootmn for             
bootfile=uImage         
bootf
rootpath=/home/andre/workdir/filesys.0.0.31294048 Bytes =               
serverip=10.0.0.5ootpath=/home/and
nfshost=10.0.0.5s               
stdin=serial        
fb0
stdout=serial   Load      
stderr=serialnv bootargs $
ethaddr=00:0e:99:02:53:ecr.ch0_mode=$(videostd)-0.
videostd=palst]         
bootargs=video=davincifb:vid0=0,2500K:vid1=0,2500K:osd=720x576x16,2025K:davinci_  

ipaddr=10.0.0.6um                 
stdout=serialia               
stderr=ser
bootdelay=3           
baudrate=115200             
 
filesize=13bf2080008000ne: vid
fileaddr=80700000                 
netmask=255.255.255.0           
   Verify
hostname=ProtocleaDVPx16,200.             
nfshost=10.0.0.3         
OK  

setboot=setenv bootargs $(bootargs) davinci_end_mngr.ch0_mode=$(videostd)..............................................9, 8192 bytes)mvl401-davinc
ipaddr=10.0.0.6Bytes =  1     
bootcmd=dhcp;bootm                  
bootfile=uImage               
rootpath=/home/andre/workdir/filesys                       
            
n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.0.0.5:/home/andre/workdir/filesy                
spawn_desched_task(00000000)s permi                            
s,nolock mem=118Mche: 8192 bytes,

Environment size: 690/65532 bytessetsched cpu_callback 3/00000000
DaVinci EVM # boot                  
BOOTP broadcast 1                 
DHCP client bound to address 10.0.0.6hine: DaVinci EVM                    
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #####
done
Bytes transferred = 2017320 (1ec828 hex)
## Booting image at 80700000 ...
   Image Name:   Linux-2.6.18_pro500-davinci_evm-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2017256 Bytes =  1.9 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
........................................................................ done, b
ooting the kernel.

(THIS IS WHERE IT FREEZES, but there does not seem to be any error messages)

My bootargs are as follows:

baudrate=115200
filesize=13bf20
fileaddr=80700000
netmask=255.255.255.0
hostname=ProtocleaDVP
nfshost=10.0.0.3
setboot=setenv bootargs $(bootargs) davinci_end_mngr.ch0_mode=$(videostd)
ipaddr=10.0.0.6
bootcmd=dhcp;bootm
bootfile=uImage
rootpath=/home/andre/workdir/filesys
serverip=10.0.0.5
nfshost=10.0.0.5
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:53:ec
videostd=pal
bootargs=video=davincifb:vid0=0,2500K:vid1=0,2500K:osd=720x576x16,2025K:davinci_
enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal console=ttyS0,115200
n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.0.0.5:/home/andre/workdir/filesy
s,nolock mem=118M

Environment size: 690/65532 bytes
DaVinci EVM #

Any ideas?  Also, I can't seem to delete the first nfshost variable.  I can erase the second one with the setenv nfshost command, but the first one always remains?  I don't think this is a big problem, but it would be nice to clean the variables up a bit.

Usually when you get to this point and see no output from the kernel itself it would mean some problem in your bootargs, in particular the console= section being messed up would prevent any kernel output on the serial terminal, however what you have looks ok. You may want to try stripping back your bootargs to make it simpler and see if that has an impact, something like just 'console=ttyS0,115200n8 noinitrd rw ip=dhcp mem=118M'. Of course something like this will not boot entirely but it would hopefully print something after 'done, booting the kernel.'.

AndreC said:

I can erase the second one with the setenv nfshost command, but the first one always remains?  I don't think this is a big problem, but it would be nice to clean the variables up a bit.

I have noticed this happen on some of my boards, and I think it is caused by an invalid character making it into the U-Boot variable name some how, so the two are actually unique values and you just cannot see the character that makes the one you cannot remove different because your particular terminal program does not show it, using different terminal programs will sometimes make these more obvious.

Thanks for the advice, but unfortunately reducing the bootargs didn't help.  I also changed the boot file variable from uImage to uImage-dm6446 to see if using the file that came with the installation would help, but it did not.  I have absolutely no idea where to look for more problems.  I don't even know if starting from scratch will help? 

Hi,

Have you tried with ramdisk? Also have you tried on another board?

First try out with a simple bootargs configured for ramdisk and just try tftp of the ramdisk and uImage.

If you are using NFS, have you made sure that you untarred the NFS package as root. Also do you see a console file present under /dev of NFS.

I believe you would have checked but just reconfirming again . Also have you made sure /etc/exports is updated with appropriate NFS path and NFS service has been restarted after this update.

Thanks,

Prathap.

Are you sure you are not getting zeros and the letter 'O' mixed up in "console=ttyS0,115200n8"? they should all be zeros.

I'm back... and after a few months I'm still stuck where I started.  This is really getting frustrating!  I have started on a fresh Linux system (Virtual Machine of Ubuntu 9.04), and reinstalled all the software.  But I still can't get the system to reach the login point of Montavista Linux.  What do you think can be wrong?  As recommended in this thread, I tried booting from the TFTP.  This time, I know the TFTP is working because I have tested it from another computer.  Also, the NFS seems to be working fine as it does mount the NFS when booting up.  Do you have any other advice?

These are the outputs at the moment

U-Boot 1.1.3 (Jul 25 2007 - 14:44:13)S2 version 2.2. (NAN
RAM Configuratio

U-Boot code: 81080000 -> 81097F84  BSS: -> 810A0974c_mngr.ch
  
ya
MY AMD Flash: 16 MB4:52 Installing
RAM Configuration:cy initializ
Out:
Bank #0: 80000000 256 MB:   seriall too ol d  

MY AMD Flash: 16 MB                 

Err:   serial.1
ethaddr=00:0e:99:02:51:5497M
Retry count exceeded;
hostname=ProtocleaDVP80; o
BOOTP broa
I2C
bootfile=uImageom server 192.1
filesize=13bf20 address is 192
fileaddr=80700000 throughuIm
OSD_O
netmask=255.255.255.0 02
Turning on transp
bootcmd=bootm 0x2060000
 
gateway 192.168.1.1
serverip=192.168.1.180
Filename 'protoclea.g
gatewayip=192.168.1.180. 
Load address: 0x850
nfshost=192.168.1.180buff00
Loading: *  
   Load Address: 80008000d: 1 RAM disks of
Filenam
   Entry Point:  80008000me:
Load address: 0x85000
   Verifying Checksum ... OKoading: T T T T T T T T T T
OK T

Starting kernel .... Parent at platfor

Uncompressing Linu..............................................................: MAC address
TFTP from server 192.168.1.180; our IP address is 192.168.0.54; se
Linux version 2.6.10_mvl401-davinci_evm (george@davinci-vm) (gcc version 3.4.3 (MAC: Instal
gateway 192.168.1.18068.0.61:192.168.0.1:2
Filename 'uImage'.sole: n
MontaVista 3.4.3-25.0.135.0702900 2007-04-01)) #42 Fri Sep 14 05:33:38 SAST 2007 T T T T T T T T T T T T T Tnux video capture interface: v1.00m64xxfb:output
Ret

CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ) Parent at pl
TFTP from server 192.168.1.180; our IP a
CPU0: D VIVT write-back cacheg throughure driver V1.0 load
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets92.168.1.180ision: 7.00alpha213)
Filename 'uImage'.e
Console: colou
Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=192.168.1.203 root=/d'. read: I/O errorbc
Load address: 0x85000000tatus = 0xa1) entries: 5
Loading: T
ev/nfs nfsroot=192.168.1.180:/home/andre/workdir/filesys,nolock mem=120M video=dlevator: using an

U-Boot code: 81080000 -> 81097F84  BSS: -> 810A0974
spawn_des
m64xxfb:output=palerve
mice: PS/2 mo
PID hash table entries: 512 (order: 9, 8192 bytes)80000000 256 MBurning
musb_hdrc: versi
MY AMD Fla
Console: colour dummy device 80x30 serial00000
Load ad
Out:   serial
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)using PIO, IRQ 1
DDR Clock :- 162MHz.it isn't (no cpio
I2C re
Inode-cache hash table entries:
                            
Lo
davincifb: Options "output=pal" associativity 4, 32 byte lines
DaVinci: Output on PAL in COMPOSITE format, Enabled windows: Video0 Video1 OSD0PU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 setsE=200 tran   
OSD1SD_V
Setting Video0 size 720x576, position (0,0)Machine: DaVinci EVMing floppy.051:52vid
Me
Setting Video1 size 720x576, position (0,0)ackannot open root device "nfs" or unknown-
Setting OSD0 size 720x576, position (0,0)
e
Kernel command line: console=ttyS0,115
Setting OSD1 size 720x576, position (0,0)                 

OSD_MODE
Kernel panic
Registering platform device 'davincifb.0'. Parent at platformome/andre/workdir/file0              
Turning on tra       
Console: switching to colour frame buffer device 90x36setenv bootc
Mount-
In:   
Inode-cache hash table ent
fb0: dm_osd0_fb frame buffer deviceform devic
ARM Clock :- 297MHznt at
OSD_MODE=200t
DDR Cloc
M
OSD_VIDWINMD=0120MB totalso

OSD_OSDWIN0MD=2003S0 at
Memory: 1189
OSD_OSDWIN1MD=02215K code, 471
Turning on transparencyed cpu_call
## Booting
fb1: dm_vid0_fb frame buffer devicent-cache hash table entries: 512 (o
fb2: dm_osd1_fb frame buffer devicegistered gw=255.255.255.255,verth
d
fb3: dm_vid1_fb frame buffer deviceherency: oke (uncompressed)g if ima
Serial: 8250/16550 driver $Revision: 1.90 $ 3 ports, IRQ sharing disabledesched cpu_callback 3/0000000003, domain=, nis-d    
   Load
ksoftirqd s
Registering platform device 'serial8250'. _callback 2/000                       


elevator: using anticipatory as default io scheduler
mice: PS/2 mouse device common for all mice
musb_hdrc: version 2.2a/db-0.4.8 [pio] [host] [debug=0]
musb_hdrc: USB Host mode controller at c8060000 using PIO, IRQ 12
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.1.203, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.1.203, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=192.168.1.180, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.180
Looking up port of RPC 100005/1 on 192.168.1.180
VFS: Mounted root (nfs filesystem).
Freeing init memory: 136K
FATAKernel panic - not syncing: Attempted to kill init!
L: kernel too ol d

My bootargs are:

setboot=setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/hda1 rw noinit
rd ip=dhcp video=dm64xxfb:output=pal
ethaddr=00:0e:99:02:51:54
hostname=ProtocleaDVP
bootfile=uImage
filesize=13bf20
fileaddr=80700000
netmask=255.255.255.0
bootcmd=bootm 0x2060000
serverip=192.168.1.180
gatewayip=192.168.1.180
nfshost=192.168.1.180
rootpath=/home/andre/workdir/filesys
ipaddr=192.168.1.203
bootargs=console=ttyS0,115200n8 noinitrd rw ip=192.168.1.203 root=/dev/nfs nfsro
ot=192.168.1.180:/home/andre/workdir/filesys,nolock mem=120M video=dm64xxfb:outp
ut=pal
stdin=serial
stdout=serial
stderr=serial
videostd=pal

Environment size: 637/131068 bytes
Protoclea DVP #

Do you have any other ideas that I can try so that I can get this board going?  How do I update the kernel if the one provided with the recent updates  does not work

Regards

Andre?

AndreC said:

   Verifying Checksum ... OKoading: T T T T T T T T T T
OK T

Starting kernel .... Parent at platfor

Uncompressing Linu..............................................................: MAC address
TFTP from server 192.168.1.180; our IP address is 192.168.0.54; se
Linux version 2.6.10_mvl401-davinci_evm (george@davinci-vm) (gcc version 3.4.3 (MAC: Instal
gateway 192.168.1.18068.0.61:192.168.0.1:2
Filename 'uImage'.sole: n
MontaVista 3.4.3-25.0.135.0702900 2007-04-01)) #42 Fri Sep 14 05:33:38 SAST 2007 T T T T T T T T T T T T T Tnux video capture interface: v1.00m64xxfb:output

I think that your log is corrupted somehow, things seem to be out of order in the text, at least on my end. I do see that you have TFTP shown but I do not see where it is loading the image across TFTP, the 'TTTT' normally means timeouts have occoured, and you would see '****' for the actual successful transfer. Additionally I am wondering about what version of DVSDK you are trying to boot? The log there shows you booting Linux 2.6.10 from MontaVista 4.0.1 which is a bit of an old kernel which leads to the main issue at hand:

AndreC said:

FATAKernel panic - not syncing: Attempted to kill init!
L: kernel too ol d

This kernel too old message indicates that the Linux kernel (uImage) you are trying to boot is not of a close enough version to the file system you are trying to boot. Usually this would happen if you tried to boot an older kernel that may be flashed on the board with a newer file system from a recently installed DVSDK. In general the easiest solution would be to use TFTP and NFS like you are trying to do, while ensuring that both the uImage file you are sending via TFTP and the filesystem you are serving via NFS are from the same DVSDK release.