public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: PF4Public <PF4Public@mail.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot tftp problem
Date: Tue, 03 Mar 2015 01:22:46 +0300	[thread overview]
Message-ID: <54F4E2B6.40106@mail.ru> (raw)
In-Reply-To: <CANr=Z=bdaQgpc=ib3ZHBLhpe_6eT0oE1ACRTy0sRHvdREGupeA@mail.gmail.com>

Hello, Joe

Recently I have repeated my tests.
U-Boot logs along with pcap dump could be found here: 
https://mega.co.nz/#!g4UnVaDL!K6ej1OQXg5VE6pU5cmFoELkeqasIDXH1OZbDwdLiXSU

I may be wrong, but after careful examination of these dumps (and older ones), I came to 
the following conclusion:
Somehow lost packets coincide with "--- NetLoop timeout handler set" and "--- NetLoop 
timeout".
Which is supported by these facts: a) both server and u-boot tftp timeouts are equal to 5 
sec; b) whenever I define "#define TIMEOUT     8000UL", even if U-Boot fails to catch the 
first packet, it catches the second one and does not reset it's timer (which seems to 
generate another one ACK for the last received block upon reset); c) similarly if I set 
"tftptimeout 1000", U-Boot still catches the second packet if it could not catch the first 
one. Moreover after yet another examination of windows server session dump I find, this is 
exactly what happens with windows server, which ignores u-boot's request for 5 second 
timeout and resends blocks after 1 second, which are perfectly captured by U-Boot; d) all 
those packets within 5 seconds' timeout got caught by U-Boot.
Please correct me if I'm wrong.
And if I'm not - is there anything to mitigate this, other than "set tftptimeout 1000" and 
"put switch inbetween"? Referring someone at ti.com to this thread maybe?

BTW: putting switch inbetween makes it easier for U-Boot to catch up with tftp server.
Compare:
U-Boot > dhcp
BOOTP broadcast 1
DHCP client bound to address 192.168.100.88 (81 ms)
Using DaVinci-EMAC device
TFTP from server 192.168.100.254; our IP address is 192.168.100.88
Filename 'uImage'.
Load address: 0xc0700000
Loading: ##T T ##T ##
Abort
U-Boot > dhcp
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 192.168.100.88 (1074 ms)
Using DaVinci-EMAC device
TFTP from server 192.168.100.254; our IP address is 192.168.100.88
Filename 'uImage'.
Load address: 0xc0700000
Loading: #T #T ####T ##T #T T #T #T #T ##T #T ###
Abort
U-Boot > dhcp
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
DHCP client bound to address 192.168.100.88 (4817 ms)
Using DaVinci-EMAC device
TFTP from server 192.168.100.254; our IP address is 192.168.100.88
Filename 'uImage'.
Load address: 0xc0700000
Loading: #################################################################
#################################################################
#################################################################
          ####T ##########################################T ###################
#################################################################
#################################################################
          #############################################T
          34.2 KiB/s
done
Bytes transferred = 2225360 (21f4d0 hex)
U-Boot > dhcp
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 192.168.100.88 (1079 ms)
Using DaVinci-EMAC device
TFTP from server 192.168.100.254; our IP address is 192.168.100.88
Filename 'uImage'.
Load address: 0xc0700000
Loading: ################################################T #######T ##########
          ####################T ###############T ####################T ###########
#################################################################
#################################################################
          ####################################################T #############
#################################################################
          #############################################T
          32.2 KiB/s
done
Bytes transferred = 2225360 (21f4d0 hex)


Best regards

      parent reply	other threads:[~2015-03-02 22:22 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
2015-02-23 23:02               ` Joe Hershberger
2015-02-25 22:01                 ` PF4Public
2015-03-02 22:22                 ` PF4Public [this message]

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=54F4E2B6.40106@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