Looking more closely at your error messages, I think your DHCP server (router) isn't handing you a DHCP address.
Here's what the output looks like when my DHCP server gave me an address (but, I got errors because the TFTP server was on a different machine): >> BOOTP broadcast 1 >> DHCP client bound to address 10.100.5.42 >> TFTP from server 10.32.2.140; our IP address is 10.100.5.42 >> Filename '/tftpboot/uImage'. >> Load address: 0x80700000 >> Loading: *>> >> TFTP error: 'File not found' (1) >> Starting again >> >> BOOTP broadcast 1 >> DHCP client bound to address 10.100.5.42 >> TFTP from server 10.32.2.140; our IP address is 10.100.5.42 >> Filename '/tftpboot/uImage'. >> Load address: 0x80700000 >> Loading: *>> >> TFTP error: 'File not found' (1) >> Starting again >> >> >> Abort So, after a single "BOOTP broadcast" message, it receives an IP address from the DHCP server. Once it has an IP, it starts the TFTP download. In my case, the TFTP download failed because using "dhcp;bootm" for the "bootcmd" caused the DVEVM to try to TFTP from the DHCP server (NOT the TFTP server). In your situation, it's just printing the "BOOTP broadcast" messages over and over. This tells me that your DHCP server isn't sending back a response. Again, I think that even if you 'fix' your DHCP server to hand your DVEVM an IP address, you'll run into the same problem I ran into (if your TFTP server is on a different machine, it'll fail the TFTP download (because the DVEVM will try to TFTP download from your DHCP server). The only 'solution' to this (from my experimentation) was to set a "static" IP address for my DVEVM (with the "ipaddr" env var), set the TFTP server's IP address (with the "serverip" env var), and use "tftpboot;bootm" instead of "dhcp;bootm" for "bootcmd". - Paul -----Original Message----- From: Alan Li [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 27, 2006 9:06 PM To: Paul Bartholomew; Maughan, Thomas; [email protected] Subject: how to do TFTP booting Hi, Following the instruction given in Startup guide (sprue66a.pdf), A.5.4 Booting via TFTP Using NFS File System, it always comes out with error, DaVinci EVM # boot BOOTP broadcast 1 BOOTP broadcast 2 ..... BOOTP broadcast 10 Retry count exceeded; starting again Here is what my env setting is: bootdelay=3 baudrate=115200 root=path /home/alanli/workdir/filesys stdin=serial stdout=serial stderr=serial ethaddr=00:0e:99:02:53:3a videostd=ntsc serverip=192.168.1.5 rootpath=/home/alanli/workdir/filesys nfshost=192.168.1.5 bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.5:/home/alanli/workdir/filesys,nolock mem=120M bootcmd=dhcp;bootm bootfile=uImage And the DVEVM and Host PC are connected via a router which has DHCP server. It seems like the command, dhcp, is stuck somewhere with those message. I don't have any idea what is going on. any help is apreciated. alan _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
