[U-Boot-Users] TFTP PROBLEM

Hi all,
We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a problem with tftp.
We know that the tftp server works because we've tested it with other clients. But with tftp in u-boot we're only able to transfer little files (1, 2 Kb)..
Which can be the problem?? Newer versions work fine??
Thanks in advance
Regards,
Sonia

TFTP can work fine in 1.0.0, but be affected by network environment. What's kind of the server do you use for the host configuration, DHCP, BOOTP ?
Could you show the console messages ? Also I want to know your environment variables. That is shown by "printenv" command.
Masami Komiya
Sonia Martinez wrote:
Hi all,
We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a problem with tftp.
We know that the tftp server works because we've tested it with other clients. But with tftp in u-boot we're only able to transfer little files (1, 2 Kb)..
Which can be the problem?? Newer versions work fine??
Thanks in advance
Regards,
Sonia
This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

TFTP server in the host (Mandrake 9.2 ) is configured like this:
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot
#per_source = 11
#cps = 100 2
#flags = IPv4
}
The environment variables are:
$ printenv
bootargs=root=/dev/mtdblock2 devfs=mount console=ttyS0,115200
bootcmd=bootm 40000
bootdelay=3
baudrate=115200
ethaddr=00:08:33:33:00:01
stdin=serial
stdout=serial
stderr=serial
filesize=4a6
netmask=255.255.0.0
ipaddr=172.16.16.220
serverip=172.16.16.70
Output with minicom:
$ tftp a1000000 little
TFTP from server 172.16.16.70; our IP address is 172.16.16.220
Filename 'little'.
Load address: 0xa1000000
Loading: T T #T #
done
Bytes transferred = 1190 (4a6 hex)
$ tftp a1000000 hello.img
TFTP from server 172.16.16.70; our IP address is 172.16.16.220
Filename 'hello.img'.
Load address: 0xa1000000
Loading: T T invalid RARP header
invalid RARP header
#T T #T T T #T T T
Retry count exceeded; starting again
TFTP from server 172.16.16.70; our IP address is 172.16.16.220
Filename 'hello.img'.
Load address: 0xa1000000
Loading: #T T T T T T #T T T #T
Retry count exceeded; starting again
----- Original Message ----- From: "Masami Komiya" mkomiya@sonare.it To: "Sonia Martinez" anexwarrior@hotmail.com Cc: u-boot-users@lists.sourceforge.net Sent: Monday, May 10, 2004 11:08 AM Subject: Re: [U-Boot-Users] TFTP PROBLEM
TFTP can work fine in 1.0.0, but be affected by network environment. What's kind of the server do you use for the host configuration, DHCP, BOOTP ?
Could you show the console messages ? Also I want to know your environment variables. That is shown by "printenv" command.
Masami Komiya
Sonia Martinez wrote:
Hi all,
We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a problem with tftp.
We know that the tftp server works because we've tested it with other clients. But with tftp in u-boot we're only able to transfer little files (1, 2 Kb)..
Which can be the problem?? Newer versions work fine??
Thanks in advance
Regards,
Sonia
This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

Sonia Martinez wrote:
TFTP server in the host (Mandrake 9.2 ) is configured like this: service tftp { disable = no
(snip)
#flags = IPv4 }
as the same as mine.
The environment variables are: $ printenv
(snip)
netmask=255.255.0.0 ipaddr=172.16.16.220 serverip=172.16.16.70
no problem.
Output with minicom: $ tftp a1000000 little TFTP from server 172.16.16.70; our IP address is 172.16.16.220 Filename 'little'. Load address: 0xa1000000 Loading: T T #T # done Bytes transferred = 1190 (4a6 hex)
$ tftp a1000000 hello.img TFTP from server 172.16.16.70; our IP address is 172.16.16.220 Filename 'hello.img'. Load address: 0xa1000000 Loading: T T invalid RARP header invalid RARP header #T T #T T T #T T T Retry count exceeded; starting again TFTP from server 172.16.16.70; our IP address is 172.16.16.220 Filename 'hello.img'. Load address: 0xa1000000 Loading: #T T T T T T #T T T #T Retry count exceeded; starting again
Many timeout are occured. It seems hardware trouble...
I recommend recompile with debug flag of net.c and the driver's code to get the more messages. also observe the packet with ethereal or tcpdump command.
Masami Komiya

Sonia Martinez wrote:
Hi all,
We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a problem with tftp.
We know that the tftp server works because we've tested it with other clients. But with tftp in u-boot we're only able to transfer little files (1, 2 Kb)..
Which can be the problem?? Newer versions work fine??
You've probably checked this, but make sure the cable is good. I've had a bunch of problems with crossover cables in particular. For example, I worked on one board that had no problems with the crossover cable under Linux, but under U-Boot, TFTP just wouldn't work. Using an Ethernet hub alleviated this.
I also have a Sony notebook computer that connects fine over a crossover cable to a 10Base-T card, but not to a 100Base-T card.
Consequently, I've pretty much given up using crossover cables, for the time being.

On 10 May 2004 at 13:20, DeLaGarza, Robert wrote:
Sonia Martinez wrote:
Hi all,
We're using u-boot 1.0.0 to boot Linux on a Lubbock based platform. We've been able to boot Linux from RAM, with JFFS2 and nfsroot too. But we've a problem with tftp.
We know that the tftp server works because we've tested it with other clients. But with tftp in u-boot we're only able to transfer little files (1, 2 Kb)..
Which can be the problem?? Newer versions work fine??
You've probably checked this, but make sure the cable is good. I've had a bunch of problems with crossover cables in particular. For example, I worked on one board that had no problems with the crossover cable under Linux, but under U-Boot, TFTP just wouldn't work. Using an Ethernet hub alleviated this.
I also have a Sony notebook computer that connects fine over a crossover cable to a 10Base-T card, but not to a 100Base-T card.
Consequently, I've pretty much given up using crossover cables, for the time being.
It sounds like some of you have duplex negotiation or mismatch problems.
Regards, Tolunay
participants (4)
-
DeLaGarza, Robert
-
Masami Komiya
-
Sonia Martinez
-
Tolunay Orkun