[U-Boot-Users] Help about tftp download
Hi everyone:
I am trying to download u-boot.bin to OMAP5912OSK through tftp. But when I type the commad in u-boot prompt, it shows following error messages:
OMAP5912 OSK # tftpboot 0x10000000 /tftpboot/u-boot.bin TFTP from server 192.168.4.1; our IP address is 192.168.4.190 Filename '/tftpboot/u-boot.bin'. Load address: 0x10000000 Loading: T T T T T T T T T T Retry count exceeded; starting again .......
What's wrong with my setups?
Thank you and best regards!
Li Weichen 2005-11-1
In message 436764a6.227f90fc.6722.7dde@mx.gmail.com you wrote:
I am trying to download u-boot.bin to OMAP5912OSK through tftp. But when I type the commad in u-boot prompt, it shows following error messages:
OMAP5912 OSK # tftpboot 0x10000000 /tftpboot/u-boot.bin TFTP from server 192.168.4.1; our IP address is 192.168.4.190 Filename '/tftpboot/u-boot.bin'. Load address: 0x10000000 Loading: T T T T T T T T T T Retry count exceeded; starting again .......
What's wrong with my setups?
Given the little detail you provide: it's impossible to say. Maybe your hardware is broke, or the port of U-Boot to your board, or you use an illegal MAC address, or ...
Best regards,
Wolfgang Denk
I think the network is fine, because if I wanted to get a file that not exist in /tftpboot, if shows that file not found. And there are only the host and target board in the local net.
If I tried tcpdump I found the target board had got the correct IP.
-----Original Message----- From: wd@denx.de [mailto:wd@denx.de] Sent: Tuesday, November 01, 2005 9:12 PM To: Li Weichen Cc: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] Help about tftp download
In message 436764a6.227f90fc.6722.7dde@mx.gmail.com you wrote:
I am trying to download u-boot.bin to OMAP5912OSK through tftp. But
when
I
type the commad in u-boot prompt, it shows following error messages:
OMAP5912 OSK # tftpboot 0x10000000 /tftpboot/u-boot.bin TFTP from server 192.168.4.1; our IP address is 192.168.4.190 Filename '/tftpboot/u-boot.bin'. Load address: 0x10000000 Loading: T T T T T T T T T T Retry count exceeded; starting again .......
What's wrong with my setups?
Given the little detail you provide: it's impossible to say. Maybe your hardware is broke, or the port of U-Boot to your board, or you use an illegal MAC address, or ...
Best regards,
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "The whole world is about three drinks behind." - Humphrey Bogart
Hi Li,
The "T T T T T" messages indicate a timeout, which means the client thinks the packets are going out and not getting a reply. I've seen this many times and it can mean many different things. I'm not all-knowing and all-seeing, but I can make some suggestions. First, make sure that you have a file called "tftp" in /etc/xinetd.d/ (assuming you use xinetd rather than inetd). The file should look something like this:
service tftp { disable = no socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd } # server_args = /tftpboot
Second, make sure you have /usr/sbin/in.tftpd and if not, get it.
Third, make sure there aren't any duplicate devices in your network that may be holding the same address your tftp client is trying to use.
Fourth, check your client's u-boot environment variables to make sure the settings are right for client and server ip addresses.
If none of this works, use /usr/sbin/tcpdump -i eth0 (whatever your ethX is) on your host to see if the tftp packets are making it to the host at all.
Hope this helps.
Regards,
Bob Peterson
At 06:50 AM 11/1/2005, Li Weichen wrote:
Hi everyone:
I am trying to download u-boot.bin to OMAP5912OSK through tftp. But when I type the commad in u-boot prompt, it shows following error messages:
OMAP5912 OSK # tftpboot 0x10000000 /tftpboot/u-boot.bin TFTP from server 192.168.4.1; our IP address is 192.168.4.190 Filename '/tftpboot/u-boot.bin'. Load address: 0x10000000 Loading: T T T T T T T T T T Retry count exceeded; starting again .......
What's wrong with my setups?
Thank you and best regards!
Li Weichen 2005-11-1
At 06:50 AM 11/1/2005, Li Weichen wrote:
Hi everyone:
I am trying to download u-boot.bin to OMAP5912OSK through tftp. But when I type the commad in u-boot prompt, it shows following error messages:
OMAP5912 OSK # tftpboot 0x10000000 /tftpboot/u-boot.bin TFTP from server 192.168.4.1; our IP address is 192.168.4.190 Filename '/tftpboot/u-boot.bin'. Load address: 0x10000000 Loading: T T T T T T T T T T Retry count exceeded; starting again .......
What's wrong with my setups?
Thank you and best regards!
Li Weichen 2005-11-1
Bob Peterson wrote: Hi Li,
The "T T T T T" messages indicate a timeout, which means the client thinks the packets are going out and not getting a reply. I've seen this many times and it can mean many different things. I'm not all-knowing and all-seeing, but I can make some suggestions. First, make sure that you have a file called
[snipped good advice]
Hope this helps.
Regards,
Bob Peterson
Another suggestion: from a (linux) box command line, tftp to your server and verify that it works. Your message is indicating that your server is 192.168.4.1 and the file you are trying to get is /tftpboot/u-boot.bin so do the following (I'm typing this from memory, so it may not be quite right)...
$ tftp 192.168.4.1 tftp> get /tftpboot/u-boot.bin
Getting TFTP to work (i.e. properly configured) usually solves the problem in my experience.
gvb
Another suggestion: from a (linux) box command line, tftp to your server and verify that it works. Your message is indicating that your server is 192.168.4.1 and the file you are trying to get is /tftpboot/u-boot.bin so do the following (I'm typing this from memory, so it may not be quite right)...
$ tftp 192.168.4.1 tftp> get /tftpboot/u-boot.bin
Sorry but after I typed tftp 192.168.4.1, it came up with message looks like get uImage froam tftp server automatically.
Getting TFTP to work (i.e. properly configured) usually solves the problem in my experience.
gvb
Li Weichen wrote:
Another suggestion: from a (linux) box command line, tftp to your server and verify that it works. Your message is indicating that your server is 192.168.4.1 and the file you are trying to get is /tftpboot/u-boot.bin so do the following (I'm typing this from memory, so it may not be quite right)...
$ tftp 192.168.4.1 tftp> get /tftpboot/u-boot.bin
Sorry but after I typed tftp 192.168.4.1, it came up with message looks like get uImage froam tftp server automatically.
Getting TFTP to work (i.e. properly configured) usually solves the problem in my experience.
gvb
Hi Li,
You result description ment nothing to me. Please cut & paste real messages. Are you typing "tftp 192.168.4.1" from your _host_ (linux server) command line?
OK, I ran a real instance on my home box (Debian 3.1 x86) vanbaren@dellserver:~$ uname -a Linux dellserver.lan 2.4.27-050821 #17 SMP Sun Aug 21 22:46:01 EDT 2005 i686 GNU/Linux
vanbaren@dellserver:~$ dpkg-query -l "*tftp*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii tftp 0.17-13 Trivial file transfer protocol client ii tftpd 0.17-13 Trivial file transfer protocol server
vanbaren@dellserver:~$ ls /tftpboot/hello_world hello_world
vanbaren@dellserver:~$ tftp localhost tftp> get hello_world Received 101214 bytes in 0.1 seconds tftp> get /tftpboot/hello_world Received 101214 bytes in 0.0 seconds tftp> quit
vanbaren@dellserver:~$ grep tftp /etc/inetd.conf tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /tftpboot
I was a little surprised that the tftp "get" worked with the /tftpboot full path. On a different box that I used (RH), it is configured as "-s /tftpboot" for the option (rather than "/tftpboot") so tftpd treats paths as relative to /tftpboot and thus the get "/tftpboot/foo" won't work because there is no /tftpboot/tftpboot/foo on the server. This should not be your problem since your configuration matches mine.
HTH, gvb
I have found the reason. My host PC has 2 ethernet cards, and the tftp server is installed on the eth0 which ip is 192.168.0.11.
Thank you for your reply!
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Jerry Van Baren Sent: Wednesday, November 02, 2005 8:59 PM To: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] Help about tftp download
Li Weichen wrote:
Another suggestion: from a (linux) box command line, tftp to your server and verify that it works. Your message is indicating that your server is 192.168.4.1 and the file you are trying to get is /tftpboot/u-boot.bin so do the following (I'm typing this from memory, so it may not be quite right)...
$ tftp 192.168.4.1 tftp> get /tftpboot/u-boot.bin
Sorry but after I typed tftp 192.168.4.1, it came up with message looks
like
get uImage froam tftp server automatically.
Getting TFTP to work (i.e. properly configured) usually solves the problem in my experience.
gvb
Hi Li,
You result description ment nothing to me. Please cut & paste real messages. Are you typing "tftp 192.168.4.1" from your _host_ (linux server) command line?
OK, I ran a real instance on my home box (Debian 3.1 x86) vanbaren@dellserver:~$ uname -a Linux dellserver.lan 2.4.27-050821 #17 SMP Sun Aug 21 22:46:01 EDT 2005 i686 GNU/Linux
vanbaren@dellserver:~$ dpkg-query -l "*tftp*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description
+++-==============-==============-========================================
ii tftp 0.17-13 Trivial file transfer protocol client ii tftpd 0.17-13 Trivial file transfer protocol server
vanbaren@dellserver:~$ ls /tftpboot/hello_world hello_world
vanbaren@dellserver:~$ tftp localhost tftp> get hello_world Received 101214 bytes in 0.1 seconds tftp> get /tftpboot/hello_world Received 101214 bytes in 0.0 seconds tftp> quit
vanbaren@dellserver:~$ grep tftp /etc/inetd.conf tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /tftpboot
I was a little surprised that the tftp "get" worked with the /tftpboot full path. On a different box that I used (RH), it is configured as "-s /tftpboot" for the option (rather than "/tftpboot") so tftpd treats paths as relative to /tftpboot and thus the get "/tftpboot/foo" won't work because there is no /tftpboot/tftpboot/foo on the server. This should not be your problem since your configuration matches mine.
HTH, gvb
SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server.
Download
it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Hi Bob,
Thanks for your kind reply. I have tried your instructions. My system is Debian-amd64 sarge 3.1, so my configurations is more or less a little different from that in Redhat. My tftpd is configured in /etc/inetd.conf. There is a line is this file looks like
tftp dgram udp wait root /usr/sbin/tcpd /usr/sbin/in.tftpd /tftpboot
There are only my host and target board in my local net.
After I typed #tcpdump -i eth1, the messages are following,
# tcpdump -i eth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 18:11:30.010752 arp who-has omap1.Nankai.edu.cn tell 192.168.4.190 18:11:30.012669 arp reply omap1.Nankai.edu.cn is-at 00:e0:4c:df:3d:48 18:11:30.011040 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.tftp: 39 RRQ "/tftpboot/u-boot.bin" octet timeout 5 18:11:30.012061 IP 192.168.0.11.33311 > 192.168.4.190.2805: UDP, length: 12 18:11:30.012359 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:30.012382 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:30.635567 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:30.635607 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:31.260528 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:31.260567 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:31.885490 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:31.885529 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:32.510452 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:32.510492 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:33.135414 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:33.135454 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:33.226036 IP 192.168.0.11.33304 > 192.168.4.190.2248: UDP, length: 12 18:11:33.760376 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:33.760416 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:34.385347 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:34.385388 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:35.010310 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:35.010349 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:35.010732 arp who-has 192.168.4.190 tell omap1.Nankai.edu.cn 18:11:35.010891 IP 192.168.0.11.33311 > 192.168.4.190.2805: UDP, length: 12 18:11:35.011042 arp reply 192.168.4.190 is-at 00:0e:99:02:0a:21 18:11:35.011254 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:35.011268 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:35.635276 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:35.635314 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:36.260237 IP 192.168.4.190.2805 > omap1.Nankai.edu.cn.33311: UDP, length: 4 18:11:36.260275 IP omap1.Nankai.edu.cn > 192.168.4.190: icmp 40: omap1.Nankai.edu.cn udp port 33311 unreachable 18:11:38.152001 arp who-has omap1.Nankai.edu.cn tell 192.168.4.190
............
omap1.Nankai.edu.cn is my hostname, 192.168.0.11 is the IP of eth0 witch is connected to external LAN. If the message above shows that my client setup is correct? I am wondering about why the UDP packets were sent to 192.168.0.11 rather than 192.168.4.1? Is it the problem?
participants (4)
-
Bob Peterson -
Jerry Van Baren -
Li Weichen -
Wolfgang Denk