From mboxrd@z Thu Jan  1 00:00:00 1970
From: PF4Public <PF4Public@mail.ru>
Date: Fri, 20 Feb 2015 19:51:47 +0300
Subject: [U-Boot] u-boot tftp problem
In-Reply-To: <54E757D1.5090605@mail.bg>
References: <54E4CC57.8000405@mail.bg> <54E4CE0E.5000308@mail.bg>
 <54E747FF.3010106@mail.ru> <54E757D1.5090605@mail.bg>
Message-ID: <54E76623.9040402@mail.ru>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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