• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 452 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.

Booting the new Linux Kernel ...

Roy Wengler
Intellectual 405 points

hello,

u try to build a new Linux Kernel and transfer to the dm355 evm.

The building is complete and now i will it transfer via tftp to the board, but it didn't work ...

here the messages that i receive :

ARM Clock :- 216MHz
DDR Clock :- 171MHz
Hit any key to stop autoboot:  0
BOOTP broadcast 1
DHCP client bound to address 192.168.49.226
TFTP from server 192.168.49.11; our IP address is 192.168.49.226
Filename 'uImage-dm355'.
Load address: 0x80700000
Loading: *
TFTP error: 'File not found' (1)
Starting again

Here my ENVs :

DM355 EVM # printenv
ipaddr=192.168.0.2
bootdelay=3
baudrate=115200
ethaddr=00:40:95:36:35:33
netmask=255.255.255.0
rootpath=/home/roy/workdir/filesys
nfshost=192.168.49.188
bootcmd=dhcp;bootm
serverip=192.168.49.188
bootargs=mem=116M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstyle=yaffs2 ip=dhcp
stdin=serial
stdout=serial
stderr=serial
videostd=pal
bootfile=uImage-dm355

Environment size: 362/16380 bytes

 

The tftp-server is working fine on my host system. ( i have tested it with a windows pc)

I don't understand that line :

" TFTP from server 192.168.49.11; "

the host ip is 192.168.49.188 and not 192.168.49.11

 

can anybody help me ?

thanks

  • 0
    TI__Mastermind 41665 points

    My suggestion would be to try using static IPs as discussed in this application note, or to try using your board and PC on another network such as a local router.

    I believe the root of your problem is your particular network, some networks/routers have a setup that will corrupt/modify the serverip that clients on the network will attempt to TFTP to, routing it to some other IP instead of the one you define in your U-Boot arguments, which is why using a static IP or another network may resolve the issue.

  • 0
    Prodigy 140 points

    royw said:

    The tftp-server is working fine on my host system. ( i have tested it with a windows pc)

    I don't understand that line :

    " TFTP from server 192.168.49.11; "

    the host ip is 192.168.49.188 and not 192.168.49.11

    Hi Roy!  Some routers can be such a PITA   :)   

    Try this:    in your uEnv or the minicom script, there should be a line that contains somethng to the effect of:

    tftp ${loadaddr} ${bootfile}

    Being somewhat careful with any single or double quotes hanging about, change it to:

    tftp ${loadaddr} 192.168.49.188:${bootfile}

    Ensure that the colon ":" separating them is there. Save the script or uEnv. What this does is tell u-boot to ignore the nextserver option from DHCP and instead download the bootfile from the given server IP. You know, I still gotta try if ${serverip} will work in that place, assuming that "setenv serverip 192.168.49.188" was earlier done.

    Good luck and let me know how it goes