Skip to contentSkip to conversation

tftpboot question

U-Boot-Users eagle keeper 3 participants 3 messages May 31, 2005

lore
Share & tools
lore
#0 lore raw

Hi all, and sorry for disturbing you again.
I'm trying to load an image from a tftp server using tftpboot. Server is reachable, and running. Address of image is correct. U-boot contacts the right IP, then tries to load the image and intead of printing "#" as documented, prints "T" (it means timeout I suppose).
But I continue getting an error message: "Retry count exceeded" Then the procedure starts again.

What this behaviour can depend from?
I excluded tftp configuration problems and network problems.

Thanks in andvance

#1 lore raw
Quoted 11 lines

Hi all, and sorry for disturbing you again.
I'm trying to load an image from a tftp server using tftpboot. Server is reachable, and running. Address of image is correct. U-boot contacts the right IP, then tries to load the image and intead of printing "#" as documented, prints "T" (it means timeout I suppose).
But I continue getting an error message: "Retry count exceeded" Then the procedure starts again.

What this behaviour can depend from?
I excluded tftp configuration problems and network problems.

1. You can ping your server from within u-boot, right?

2. You can tftp download your image locally on your server, right?

best regards
rick

#2 lore raw
In reply to eagle keeper
Quoted 9 lines · eagle keeper

Hi all, and sorry for disturbing you again.
I'm trying to load an image from a tftp server using tftpboot. Server is reachable, and running. Address of image is correct. U-boot contacts the right IP, then tries to load the image and intead of printing "#" as documented, prints "T" (it means timeout I suppose).
But I continue getting an error message: "Retry count exceeded" Then the procedure starts again.

Quoted 4 lines

What this behaviour can depend from?
I excluded tftp configuration problems and network problems.

Thanks in andvance

I would suspect your ethernet receiver is having problems with larger packets (probably a hardware configuration issue). I don't know what processor you are using, but a classic problem is that short packets (pings) work because the packet fits entirely in the ethernet FIFO buffer, but long packets (tftp data) break because the ethernet FIFO cannot buffer the whole packet and the at-speed store to SDRAM is broken (cannot keep up with packets of length 1500 or so bytes and/or SDRAM bursting is broken).

gvb