DM365 TFTP Download Problem

is there a serverip env variable? It has to be set to 192.168.2.100.

Thank you for your kind reply.

However, I did set up all needed parameters.  When I do printenv, I have the following set up:

ipaddr=192.168.2.102

serverip=192.168.2.101

ip=192.168.2.101:192.168.2.101:192.168.2.1:255.255.255.0

eth0=on

bootfile=u-boot-1.3.4-dm365_dvr.bin

after doing tftpboot 0x82000000 u-boot-1.3.4-dm368_dvr.bin

Nothing happened ~

Are there hardware jumpers or switches I forgot to set??

How about setting up "ethaddr"? Is the MAC address set? If it is not set, then your ping operation or tftp operation would not work. BTW, i hope you have ensured that the physical link is active and the LEDs are glowing on the network interface.

Regards,

Anshuman

PS: Please mark this post as verified, if you think it has answered your question. Thanks.

Thanks for getting back....

Here are the DVR's initial configuration upon power-on:

bootargs=mem=35M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=192.168.1.200:192.168.1.60:192.168.1.1:255.255.255.0::eth0:off video=davincifb:osd0=720x576x8,2500K:osd1=off:vid0=off:vid1=off  
bootcmd=setenv setboot setenv bootargs \$(bootargs) davinci_enc_mngr.ch0_mode=\$(videostd); run setboot;nboot 80700000 0 680000;bootm 80700000
bootdelay=1
baudrate=115200
stdin=serial
stdout=serial
stderr=serial
videostd=ntsc ethaddr=00:11:a1:98:a8:e9

(the following is added after coming up)
rootpath=/home/welson/DM368DVR_RDK/DM368_RDK/dvr/target/filesys
ipaddr=192.168.2.102
eth0=on
bootfile=u-boot-1.3.4-dm365_dvr.bin
serverip=192.168.2.101
nfshost=192.168.2.101
ip=192.168.2.101:192.168.2.101:192.168.2.1:255.255.255.0

ver=U-Boot 1.3.4 (Jan 26 2011 - 00:07:15)

Then, I do

"PING 192.168.2.1" --> alive, as the DHCP server is 192.168.2.1

"PING 192.168.2.100" , trying to PING host, --> alive

However, when I do "PING 192.168.2.102" (try to PING DVR from host), there are no ICMP packets coming back.  PING does not reach DVR.

The ethernet port on the DVR does have both LEDs glowing and the cable is good.

Anything I have missed?

Thanks for any reply....

Dear Anshuman, 

 Thanks for getting back.

 Like you suggested, once I did dhcp on DVR, 192.168.2.102 will be assigned to the DVR and "PING 192.168.2.1" surely works, as this is the DHCP server.

My host is configured (DHCP configured) with 192.168.2.101.  "PING 192.168.2.102" only gets responses at the same time I issue "dhcp" or "tftpboot 0x820000 u-boot-1.3.4-dm365_dvr.bin" at DVR.

When neither command is issued at DVR side, "PING 192.168.2.102" will never gets responses.  I suppose the PING should always work whether either command is issued or not as long as DVR has an IP, which it does.

Something not quite working here....  The DVR is brought up with 192.168.1.200 as its IP but somehow it takes 192.168.2.102 temporarily (to respond to ICMP) and never changes its IP to 192.168.2.102 even when dhcp is issued.  I guess this is why it never gets TFTP download from the host to work.

I am really stuck.... I am trying to reduce boot time by optimizing U-boot & Kernel iamges.  Without TFTP download working, are there any other ways I can get around to load new image onto the DVR?

Any help would be greatly appreciated.

The IP address for U-Boot and Linux can be different. Your settings are 192.168.2.102 for U-Boot and 192.168.1.200 for Linux. Only a few environment variables are used by tftp. U-Boot documentation is here.

http://www.denx.de/wiki/view/DULG/UBootEnvVariables

Since you can ping from DVR to host, the network must be working. A ping from host to DVR will probably not work because I think U-Boot does not have a ping daemon. When the DVR is running dhcp or tftpboot, those commands must be answering the ping messages as a side effect. I suggest looking at you TFTP setup. U-Boot has some instructions here.

http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.6.