From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] TFTP times out?
Date: Thu, 10 Nov 2005 08:40:19 -0500 [thread overview]
Message-ID: <43734DC3.2000102@smiths-aerospace.com> (raw)
In-Reply-To: <518B77BB6246D54D9E88FC49AFB0389D2B1D34@seskoptronicmsx.optronic.local>
A: What really annoys Wolfgang?
Q: HTML (and I bet you thought I was going to say top posting ;-).
</humor>
"but when the next datapackage araives u-boot doesn?t seem to hear it"
I'm thinking the above quote is almost correct. "Doesn't process it" is
probably the correct statement. It sounds like your u-boot build has
problems receiving ethernet packets after a while. This could be many
things, but is almost undoubtedly a software problem and increasing
timeouts won't fix it, it will just ACK previous packets longer.
I would check packet handling. My first suspicion is that your receive
packet handling isn't handling the packet queue properly. An example of
this would be if two packets are received but you only handle one of
them and never go on to the next - as long as you only receive one
packet per poll, you are OK, but if you receive two you get stuck.
gvb
Andr? Berggren wrote:
> Hi!
>
> We have the same problem with one minor difference. U-boot get the
> first part of a file and then starts getting timeouts (TTTT).
> We used a Etheral to sniff and found out that u-boot ack one
> datapackage but when the next datapackage araives u-boot doesn?t seem
> to hear it. Instead u-boot timesout listening and sends another ack
> on the previous datapackage. The tftp server then retransmits the
> last datapackage again witch u-boot doesn?t hear, u-boot times out
> and send another ack on the previous datapackage, and we are stuck in
> this loop.
> We use a Moxa ED6008 switch where we attached the sniffer for the
recording.
>
> See appended ethereal capture-file. Mark one UDP-package and use
> Analyse->decode as and chose tftp to make it more readable.
>
> //Andr?
>
>
> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net on behalf of Wolfgang Denk
> Sent: Thu 11/10/2005 9:42 AM
> To: Zhen Wang
> Cc: Bharathi Subramanian; u-boot-users at lists.sourceforge.net
> Subject: Re: Re : [U-Boot-Users] TFTP times out?
>
> In message <4372E4BF.8020401@gmail.com> you wrote:
>
>> In a word, I think I should revise the tftpboot relevant codes to
>>prolong the time before time out. But I don't the exact file(location).
>
>
> No. This will NOT solve the problem.
>
> Run a network sniffer to find out if U-Boot is actually sending
> packets, and the TFTP server fails to reply, or if U-Boot does not
> send any packets at all.
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2005-11-10 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 9:23 [U-Boot-Users] TFTP times out? André Berggren
2005-11-10 13:40 ` Jerry Van Baren [this message]
2005-11-10 15:12 ` NZG
2005-11-11 6:18 ` Zhen Wang
-- strict thread matches above, loose matches on Subject: below --
2005-11-11 8:49 Martin Krause
2005-11-11 9:36 ` Wolfgang Denk
2005-11-10 3:10 Zhen Wang
2005-11-10 3:18 ` Sam Song
2005-11-10 4:19 ` Zhen Wang
2005-11-10 4:37 ` Bharathi Subramanian
2005-11-10 6:12 ` Zhen Wang
2005-11-10 8:42 ` Wolfgang Denk
2005-11-10 7:59 ` Eckart Goehler
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=43734DC3.2000102@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