NFS boot

You may want to check your ethernet cable and router/switch to ensure you are actually connected properly at the physical level as well as ensuring that your DHCP server is active on the network. You may also want to try using a static IP configuration instead as discussed in this application note.

Is the connected LED lit on the DM355 network port?

I have to unplug and reconnect my network cable every time I re-boot.

This is apparently a uboot issue where by the port is not automatically re-enabled.
I only see this in TFTP boot, but it may be the same issue.

This is interesting, I have rebooted my DM355 EVM several times without needing to reconnect my network cable every time; I am wondering if anyone else is experiencing this and if there is a particular sequence towards re-producing this.

The LED on the network port lits up when the cable is connected. But I still can't get the board connected via NFS....as you have read the messaged it keeps on trying forever to connect.

How do I ping the board from Ubuntu? How can I find the ip address of the board any more suggestions to resolve this issue?

Thanks

To be clear, I am referring to TFTP boot.
I see this issue daily particularly is I hit the reset button.
I read somewhere that it is an issue between uboot and certain routers/switches.

I am connected to a Dynamode WS80010-D 10/100 switch (who knows what's in side the box).

I saw a news group article (cn't find it again) that mentioned this a and suggested the cause as described above.

Quite simply, if I see the TTTTTTTTT when trying to boot, I unplug then plug in my network cable.

The link light comes on (was off) and the download begins immediately, indicated by the ###########....

I'm not sure if this is the same issue as being described by Saadia, but hope the info is helpful.

B

Hi,

I want to try tftp now. Can anyone tell me how to setup this, I am new to ubuntu...so I would want a step by step...or maybe something similar to the getting started guide like the nfs?

Thanks

saadia said:

How do I ping the board from Ubuntu? How can I find the ip address of the board any more suggestions to resolve this issue?

What I often do with a new setup is ping host os (Ubuntu) from EVM; this ensures my cables and hardware are good.  Then, I do type "dhcp" command on my EVMs u-boot prompt; this normally prints out a statement such as "TFTP from server 192.168.49.11; our IP address is 192.168.49.226", the second IP address is your EVM IP address. 

Brendan Cassidy said:

I read somewhere that it is an issue between uboot and certain routers/switches.

Do you see a message similar to "TFTP from server 192.168.49.11; our IP address is 192.168.49.226" in your boot log; normally, when a router dhcp server is not functioning properly, the first ip address is the gateway instead of the true host ip address.  We have seen people resolve this by upgrading the router's firmware.  Do you see this?  If so, does unconnecting the plug solve this as well?  This would be a very interesting finding...

saadia said:

I want to try tftp now. Can anyone tell me how to setup this, I am new to ubuntu...so I would want a step by step...or maybe something similar to the getting started guide like the nfs?

Unfortunately, I have not tried ubuntu yet, so I do not have step by step instructions for enabling tftp in this distro; hopefully someone more familiar with ubuntu can chime in.  FYI, we do have a few customers using ubuntu...

ok guys. When I type 'dhcp' on the command prompt : i see this:

DM355 EVM # dhcp
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10

Retry count exceeded; starting again
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10

Does anyone have any idea why this is happening...please help me im still not able to mount nfs or tftp!

Saadia,

Would you mind listing your u-boot variables. 

FYI, were you able to ping your host from the EVM u-boot prompt.  If so, and your u-boot environment variables are ok, tftp can fail due to 1) tftp service not properly enabled on host or 2) firewall is not disabled on host.

DM355 EVM # printenv
bootdelay=3
baudrate=115200
bootfile="uImage"
mfshost=00:0c:29:57:09:11
nfs=192.168.52.129
rootpaths=</home/saadia/workdir.filesys>
bootards=console=ttyS0,115200n8 noinitrd rw ip=192.168.11.0 root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M
serverip=192.168.1.40
ethaddr=00:0c:29:57:09:11
gateway=127.0.0.2
subnet=mask 255.255.0.0
netmask=255.255.0.0
dns1=161.131.7.233
dns2=161.131.7.203
bootcmd=nboot 0x80700000 0 0x400000;bootm
nfshost=169.254.4.234
rootpath=/home/saadia/workdir/filesys
bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M
gatewayip=169.254.5.234
mask=255.255.0.0
ipaddr=169.254.4.234
stdin=serial
stdout=serial
stderr=serial
videostd=ntsc

I notice that your serverip (host ip) and ipaddr (target ip) environment variables appear to be in different subnets, this is a problem and could be resulting on what you are seeing, 

This is what you get if you do not have a DHCP server on the network your board is connected to, so I would double check that your network has a functioning DHCP server that will accept your board's broadcasts.

Ok thanks Bernie.

Can you now tell me how to check for the DHCP on the host? Sorry im new to linux

Setting up DHCP to run from the host is something I have never done, but there is a lot of information out there, I believe the Linux utility you would use would be DHCPD, note you would only need to do this if you did not have a DHCP server elsewhere on the network (such as if you didnt want to use static IP and were directly connected to your host PC with a cross over cable). Typically one would not mess with this, and would either just use static IPs or even more commonly use an off the shelf broadband router that has a DHCP server within it, or similarly connecting both the board and the host PC into the same local network that happens to have a DHCP server on it (a typical corporate network will have DHCP if you are allowed to have your board on it).