I had similar issues and there were a couple things I had to do to get around the booting from TFTP.
1. I had to open the port on the host linux machine, there was a firewall inplace that I didn't realize was blocking the port. 2. I had to manually do the TFTP I couldn't let the bootloader do it by itself. If you boot and interrupt the boot. Make sure your variables are set. And then just type TFTP uImage 8070000 it will transfer it then you can run another function to burn the kernel to flash... I never was able to get around the wrong IP address thing I am not sure what was up with that. ------------------------------------------ Tim Taylor Electrical Engineer L-3 Communications Linkabit-Florida 1200 South Woody Burke Rd Melbourne, Florida 32902-0550 [EMAIL PROTECTED] <BLOCKED::mailto:[EMAIL PROTECTED]> W: (321) 409-6231 F: (321) 953-8795 C: (321) 426-6799 ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gijo Prems Sent: Wednesday, March 26, 2008 8:49 AM To: António Silva Cc: [email protected] Subject: Re: Problem booting dm355 via TFTP Hi, For configuration (1), you could try the command setenv bootcmd 'tftpboot' followed by 'saveenv' and 'reset'. Make sure the tftp server is running on 192.168.1.53 (your server). I don't really use dhcp and hence, no clues for (2). -Gijo 2008/3/26 António Silva <[EMAIL PROTECTED]>: Hi all, I am trying to boot the board via TFTP using Board's NAND Flash File System, as explained at the Getting Started Guide, at section A.3.2 page A-9. I am not able to perform the tftp transfer with two different configurations This is strange since it was supposed that it tries to boot via tftp. Here are my environment variables for two configurations: 1. Direct connection between the host and the EVM board using a cross cable: bootdelay=3 baudrate=115200 stdin=serial stdout=serial stderr=serial videostd=pal bootcmd=bootm bootargs=mem=116M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=192.168.1.10 bootfile=uImage-dm355 serverip=192.168.1.53 Nonetheless after performing all steps described, when I boot the result is the following: ## Booting image at 80700000 Bad Magic Number 2. Exactly as explained on the manual at my company's LAN bootdelay=3 baudrate=115200 stdin=serial stdout=serial stderr=serial videostd=pal bootargs=mem=116M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=dhcp bootcmd=dhcp;bootm serverip=10.112.40.14 bootfile=uImage-dm355 At this case here are the results DM355 EVM # boot BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 43 *** Unhandled DHCP Option in OFFER/ACK: 43 DHCP client bound to address 10.112.40.239 TFTP from server 10.112.15.19; our IP address is 10.112.40.239; sending through gateway 10.112.40.254 Filename 'uImage-dm355'. 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 BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 43 *** Unhandled DHCP Option in OFFER/ACK: 43 DHCP client bound to address 10.112.40.239 TFTP from server 10.112.15.19; our IP address is 10.112.40.239; sending through gateway 10.112.40.254 Filename 'uImage-dm355'. Load address: 0x80700000 Loading: T T Abort DM355 EVM # In this case, it seems that the board is trying to access the tftp server (as opposed with the previous case, where the board desn't try). The problem in this case is that he is trying to connect to a tftp server different from that configured!!! Does anybody had this problem? Thanks in advance, A.SIlva _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
