public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot tftp problem
Date: Wed, 18 Feb 2015 19:31:03 +0200	[thread overview]
Message-ID: <54E4CC57.8000405@mail.bg> (raw)
In-Reply-To: <54E4B0DC.8080507@mail.ru>

Hi,

Here's what I think happens:

When working with large TFTP packets (probably 4096 bytes, as set in
your board config file), U-Boot TFTP code sends wrong acknowledges for
the TFTP packets. If the TFTP server implementation is too strict (the
OpenBSD server is a good example), the transfer will inevitably fail
very soon after start. Here's an example:

1. TFTP server sends block 0
2. Board acknowledges block 0
3. TFTP server sends block 1
4. Board acknowledges block 0

At this point you can see either proper or very obscure error messages
in the TFTP server logs, so trust only to network dumps for diagnostics.

What can you do to resolve your issue:

1. Fix the bug in U-Boot tftp networking code and submit a patch.
2. Reduce your TFTP blksize, by commenting CONFIG_TFTPBLOCKSIZE  in
your board config. The default value is 1468, which should work fine.
U-Boot behaves nicer with smaller packets.

Hope this helps. Regards,
Nikolay

  reply	other threads:[~2015-02-18 17:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-14  2:05 [U-Boot] u-boot tftp problem PF4Public
2015-02-17 17:10 ` Joe Hershberger
2015-02-18 15:33   ` PF4Public
2015-02-18 17:31     ` Nikolay Dimitrov [this message]
     [not found]       ` <54E4CE0E.5000308@mail.bg>
2015-02-20 14:43         ` [U-Boot] Fwd: " PF4Public
2015-02-20 15:50           ` [U-Boot] " Nikolay Dimitrov
2015-02-20 16:51             ` PF4Public
2015-02-23 23:02               ` Joe Hershberger
2015-02-25 22:01                 ` PF4Public
2015-03-02 22:22                 ` PF4Public

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=54E4CC57.8000405@mail.bg \
    --to=picmaster@mail.bg \
    --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