Hi,

First you need to get the board back booting the kernel. As u-boot is trying to 
tell you - there is no such command as  0x2050000 which is what you told it to 
use.

Break into the u-boot sequence & restore the original value of bootcmd...

setenv bootcmd nboot 0x80700000 0 0x400000; bootm
saveenv


The next step is to make sure DHCP is available. If you think it should already 
be available then you may have the 'infamous' 'DM355 not working 100% with some 
switches' - like my Netgear FS108. If it fails to work - I get the same error 
about IPv6 - just reboot & it usually works the next time.

Next for NFS root filesystem......

Break into the boot sequence and change the 'bootargs' value (this should be on 
one line - beware line wrap).

setenv bootargs 'mem=116M console=ttyS0,115200n8 noinitrd root=/dev/nfs rw 
nfsroot=172.18.0.13:/tftpboot/remote_fs/davinci_dm355 ip=dhcp'

The IP address & path will need to match whatever you exported from the NFS 
server and its IP address obviously. You can save the update with 'saveenv' or 
just use once with 'bootd' (whilst testing).

You can check that the NFS export is available by typing 'exportfs' on the NFS 
server as root. You may need to disable the firewall - which I do by removing 
it ;-)

You also need to make sure the nfs service set to run at boot time and then you 
can start it. In Fedora/CentOS/Redhat systems this is done by the command 
'chkconfig --list nfs' which should show 'on' against the current runlevel.

If not then enable it with 'chkconfig nfs on' & start it with 'service nfs 
start'.

If it still fails then you will need to post the console output so folks can 
see what is going on.

Regards

Phil 

Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Stillson
Sent: 18 April 2008 15:43
Cc: [email protected]
Subject: Re: how to test the shared file system

You need to set up IPv4 dhcpd on your server. The board won't boot off of IPv6.

C

On Fri, Apr 18, 2008 at 7:34 AM, YangZhijun <[EMAIL PROTECTED]> wrote:
>
>
>  Dear all,
>
>  I am a newby of Davinci technology and of TMS320DM355 DVEVM. I 
> followed the Getting Started Guide when I tried to test the shared 
> file system between my  laptop runing Ubuntu Linux and the board. However, 
> after I saved the three setenv as in the guide and boot, the board runs until 
> sending DHCP request, then  it said no IPv6 router present, so it keeps its 
> trial forever. I tried to install the radvd package but the issue remains, 
> even after I tried the Fedora 8 to run with the board.
>  I guess it might be that I did not give the IP address correctly. I 
> used /sbin/ifconfig to identify the IP associated with the eth0 Ethernet 
> port, I can only find the inet address  for eth0:avah (e.g., 169.254.7.95), 
> so I used it and got stuck as above.
>
>  And furthermore, I tried "setenv bootcmd 0x2050000", then saved it. 
> When I typed "boot", now it becomes worse as that the board does not boot up 
> for even a step by  directly saying 02050000 command not found. How can I 
> restore my original boot setup?  Thanks for your help.
>
>  Kind regards,
>  Michael
>  _________________________________________________________________
>  多个邮箱同步管理,live mail客户端万人抢用中
>  http://get.live.cn/product/mail.html
>  _______________________________________________
>  Davinci-linux-open-source mailing list  
> [email protected]
>  
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>



--
Chris
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to