Hi,
 
Try the following.....this works for me.
 
Set a static IP address on the DM355 for itself & the server. You may need to 
get the administrator of the DHCP server to allocate
you a static IP address (for your MAC address) or just use one you know is 
spare.
 
setenv ipaddr <ip address>
setenv serverip <sever ip address>
setenv netmask <mask>
 
Then load the file manually....Your filename will be different of course.
 
tftp 80700000 /tftpboot/uImage_dm355_trinity
bootm 0x80700000

If you can't get the kernel to load then you need to test the TFTP server with 
a tftp client from another box. The easiest way is to use a Linux box and 
install the 'tftp' package.
 
Once you are happy the kernel will load you can automate it by setting the 
'bootcmd' variable to something like.....
setenv bootcmd 'tftp 0x80700000;bootm 0x80700000' 
 
..or you can put the kernel in FLASH and boot from there.
 
 
Regards
 
Phil Q
 
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 <http://www.trinityconvergence.com/> 

 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gijo Prems
Sent: 26 March 2008 12:49
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

Reply via email to