Re: tftp time outs

[Harm Berntsen <harm.berntsen@nedap.com>]

Great to hear U-Boot is helping you :). For documentation I go to the
documentation included in the source code (doc subfolder) and the
source code itself.

When CONFIG_NET_TFTP_VARS is enabled you can overwrite the compiled
settings with the environment variables (see net/tftp.c in the source
code).

I have no experience with boot.cmd files but it looks like you will
need the setenv variant :).
-----Original Message-----
From: Matteo Guglielmi <Matteo.Guglielmi@dalco.ch>
To: Harm Berntsen <harm.berntsen@nedap.com>
Cc: u-boot@lists.denx.de <u-boot@lists.denx.de>
Subject: Re: tftp time outs
Date: Tue, 07 Sep 2021 12:51:37 +0000

Hi Harm,


thanks for the suggestion.


I have this set in my .config file

for the compilation of u-boot:


CONFIG_TFTP_BLOCKSIZE=1468

CONFIG_TFTP_WINDOWSIZE=1

I'm also using a custom boot.cmd
file... should I instead just put
your vars in it like this:

tftpblocksize=512
tftptimeout=10000

or like this:

setenv tftpblocksize 512
setenv tftptimeout 10000

?

I'm still new to u-boot even though
I could make it do exactly what I
needed... extremely useful to boot
my cluster of raspberry pis 4 b with
individual kernel options each.

PS:

Any good book around on u-boot?

Good doc seems so difficult to get.


Thank you!

________________________________
From: Harm Berntsen <harm.berntsen@nedap.com>
Sent: Tuesday, September 7, 2021 10:12:45 AM
To: Matteo Guglielmi
Cc: u-boot@lists.denx.de
Subject: Re: tftp time outs

Hi Matteo,

Which version of U-Boot are you using?

Try setting the following environment variables:

tftpblocksize=512
tftptimeout=10000

-- Harm

-----Original Message-----
From: Matteo Guglielmi <Matteo.Guglielmi@dalco.ch>
To: u-boot@lists.denx.de <u-boot@lists.denx.de>
Subject: tftp time outs
Date: Sun, 05 Sep 2021 13:49:46 +0000

Dear All,


I've noticed that when u-boot is downloading

files from a tftp server (e.g. vmlinuz, initrd

etc.) it starts to time out quite heavily

"##T #T #T..." if I simply ping the NIC of

the raspberry 4b on which it's running.


Thanks for any comment or suggestion on this

behavior.