From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] tftpboot question
Date: Tue, 31 May 2005 15:31:26 -0400 [thread overview]
Message-ID: <429CBB8E.7070101@smiths-aerospace.com> (raw)
In-Reply-To: <7449982405053111384f930256@mail.gmail.com>
eagle keeper wrote:
> 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
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
next prev parent reply other threads:[~2005-05-31 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 18:38 [U-Boot-Users] tftpboot question eagle keeper
2005-05-31 18:59 ` richard at uclinux.net
2005-05-31 19:31 ` Jerry Van Baren [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 6:30 Bharath
2006-10-31 23:13 Reeve Yang
2006-11-01 0:42 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=429CBB8E.7070101@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox