• State Answer Suggested
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 749 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM365 EVM U-Boot TFTP problem

CW39920
Prodigy 90 points

Hi,

I tried to boot the DM365 EVM board with the kernel I built and stored in the linux host via TFTP. The TFTP server is running fine. I follow the GSG and set the U-Boot variables as the following:

 

EVM # setenv bootcmd 'dhcp;bootm'

EVM # setenv serverip 141.213.15.236

EVM # setenv bootfile uImage

EVM # setenv bootargs mem=76M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=dhcp video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=4

EVM # boot

 

When the booting starts, I got the following message:

 

BOOTP broadcast 1

DHCP client bound to address 141.213.15.251

TFTP from server 141.213.76.39; our IP address is 141.213.15.251

Filename '\OSChooser\i386\startrom.com'.

Load address: 0x80700000

Loading: ## Warning: gatewayip needed but not set

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

 

The TFTP server IP is different from what I setup, and hence U-Boot cannot find and load the kernel. What am I missing here?
Thanks and I appreciate any help.

 

CW

 

 

  • 0
    TI__Mastermind 19985 points

    Can you print your complete bootargs before you boot the EVM using "boot" cmd?

    Regards,

    Anshuman

  • 0
    Intellectual 525 points

    Hi,

    I beleive that your DHCP server is overriding your environment settings (in particular serverip). We have also had this issue which we resolved temporarily as follows.

    Try replacing 

    'ip=dhcp' in your bootargs variable with

    'ip=<Hostip>:<Serverip>:<Gatewayip>:<Netmask>

    eg ip=10.0.0.9:10.0.0.10:10.0.0.2:255.255.255.0

    as well as changing your bootcmd to the following

    'tftpboot 0x80700000 <KernalName>;bootm'

    You should be able to boot up with this until you modify your DHCP server settings (we personally still need to look into this but has moved down our priority list) .

    Rgds,
    NickA & SeanP

  • 0 in reply to Anshuman Saxena
    Prodigy 90 points

    Hi Anshuman,

     

    Here is the complete messages starting from powering up the board:

     

    Jumping to entry point at 0x81080000.

     

     LSP 2.10 BETA RELEASE 

     VERSION: 2.10.008.02 

     

    U-Boot 1.3.4 (Mar  2 2009 - 11:50:39)

     

    I2C:   ready

    DRAM:  128 MB

    NAND:  NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V)

    Bad block table found at page 524224, version 0x01

    Bad block table found at page 524160, version 0x01                              

    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit) 

    Bad block table found at page 524224, version 0x01                              

    Bad block table found at page 524160, version 0x01                              

    2048 MiB                                                                        

    In:    serial                                                                   

    Out:   serial                                                                   

    Err:   serial                                                                   

    Ethernet PHY: GENERIC @ 0x00                                                    

    Hit any key to stop autoboot:  0                                                

    DM365 EVM :>setenv bootcmd 'dhcp;bootm'                                         

    DM365 EVM :>setenv serverip 141.213.15.236                                      

    DM365 EVM :>setenv bootfile uImage                                              

    DM365 EVM :>setenv bootargs mem=76M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=dhcp video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=4

    DM365 EVM :>boot

     

    The bootargs is exactly the same as what I posted.

     

    Thanks,

     

    CW

  • 0 in reply to NickAllen
    Prodigy 90 points

    Hi Nick,

     

    Thanks. I thought it's the DHCP doing something, but I wasn't sure and didn't know how to fix it. I will try your solution.

     

    Thanks a lot,

     

    CW

  • 0 in reply to NickAllen
    Prodigy 90 points

    Hi Nick,

     

    I tried your solution, and it worked the first time. But I forgot to mount the file system via NFS, so I tried again. For the second time, it failed and I got the following message:

     

    *** ERROR: `ipaddr' not set

    ## Booting kernel from Legacy Image at 80700000 ...

       Image Name:   Linux-2.6.18_pro500-davinci_evm-

       Image Type:   ARM Linux Kernel Image (uncompressed)

       Data Size:    2026248 Bytes =  1.9 MB

       Load Address: 80008000

       Entry Point:  80008000

       Verifying Checksum ... Bad Data CRC

    ERROR: can't get kernel image!

    Then I setup ipaddr using
    setenv ipaddr 141.213.15.251
    and now I got the following message after boot:

     

    TFTP from server 141.213.15.236; our IP address is 141.213.15.251
    Filename 'uImage'.
    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

    It keeps looping now.

     

    Any idea what's going wrong?
    Thanks,
    CW

  • 0
    Genius 5240 points

    CW said:

    EVM # setenv bootcmd 'dhcp;bootm'

    Try this for bootcmd....

    setenv bootcmd tftpboot 0x80700000 uImage;bootm 0x80700000

    John