From: PF4Public <PF4Public@mail.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot tftp problem
Date: Fri, 20 Feb 2015 19:51:47 +0300 [thread overview]
Message-ID: <54E76623.9040402@mail.ru> (raw)
In-Reply-To: <54E757D1.5090605@mail.bg>
Hello, Nikolay
Now I see, what you mean.
From every dump the requests made by U-Boot are the same. They're as follows:
00:00:00.000310 IP (tos 0x0, ttl 255, id 11267, offset 0, flags [DF], proto UDP (17),
length 66)
192.168.100.88.3821 > 192.168.100.254.69: 38 RRQ "uImage" octet timeout 5 blksize 1468
However the answers from servers are different.
Linux host answers with 516 byte packets for example:
00:00:00.004169 IP (tos 0x0, ttl 64, id 29290, offset 0, flags [DF], proto UDP (17),
length 544)
192.168.100.254.56334 > 192.168.100.88.3821: 516 DATA block 1
Whereas Windows host answers conforming to requested block size somewhat:
00:00:00.000136 IP (tos 0x0, ttl 128, id 20143, offset 0, flags [none], proto UDP (17),
length 1500)
192.168.100.86.63959 > 192.168.100.88.3811: 1472 DATA block 1
Also those configs, which contain "#define CONFIG_TFTP_BLOCKSIZE 4096", are from
completely different boards. As well as neither did I nor it was by default defined for
mine board.
So I believe that there must be something different with my set up. I have not yet tried
debugging network at U-Boot side, but it is the last thing, that left to check.
But anyway thank you for your insight for large packets and U-Boot.
Best regards
next prev parent reply other threads:[~2015-02-20 16:51 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
[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 [this message]
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=54E76623.9040402@mail.ru \
--to=pf4public@mail.ru \
--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