[U-Boot] TFTP Timeout Interval problem

[U-Boot] TFTP Timeout Interval problem

[Gong Q.Y.]

Hi,

I got a problem with tftp and found this patch.
-------------
commit 620776d734e4b126c407f636bda825a594a17723
Author: Pavel Machek <pavel@denx.de>
Date:   Tue Aug 18 14:34:26 2015 +0200

    tftp: adjust settings to be suitable for 100Mbit ethernet
--------------
The default timeout is changed to 100 (ms) and this causes "TFTP error: 'Unsupported option(s) requested' (8)".

Because the option is equal to timeout/1000, now it's zero(100/1000 -> 0) which is not supported.
Actually I find in an original doc RFC-2349 which specifies this value should range between "1" and "255" seconds.

So I think there may be a conflict?
Look forward to your help.

This is my test log:
=> tftp a0000000 gqy/bootscript
Using FM1 at DTSEC3 device
TFTP from server 10.192.208.233; our IP address is 10.193.20.130
Filename 'gqy/bootscript'.
Load address: 0xa0000000
Loading: *
TFTP error: 'Unsupported option(s) requested' (8)
Starting again
=> setenv tftptimeout 1000
=> tftp a0000000 gqy/bootscript
Using FM1 at DTSEC3 device
TFTP from server 10.192.208.233; our IP address is 10.193.20.130
Filename 'gqy/bootscript'.
Load address: 0xa0000000
Loading: #
         44.9 KiB/s
done
Bytes transferred = 92 (5c hex)
=>

Regards,
Qianyu

[U-Boot] TFTP Timeout Interval problem

[Pavel Machek]

Hi!

> I got a problem with tftp and found this patch.

Yes, sorry about that. Just revert it, or update to newer u-boot where
it should be reverted.

> -------------
> commit 620776d734e4b126c407f636bda825a594a17723
> Author: Pavel Machek <pavel@denx.de>
> Date:   Tue Aug 18 14:34:26 2015 +0200
> 
>     tftp: adjust settings to be suitable for 100Mbit ethernet
> --------------
> The default timeout is changed to 100 (ms) and this causes "TFTP error: 'Unsupported option(s) requested' (8)".
> 
> Because the option is equal to timeout/1000, now it's zero(100/1000 -> 0) which is not supported.
> Actually I find in an original doc RFC-2349 which specifies this value should range between "1" and "255" seconds.
> 
> So I think there may be a conflict?
> Look forward to your help.
> 
> This is my test log:
> => tftp a0000000 gqy/bootscript
> Using FM1 at DTSEC3 device
> TFTP from server 10.192.208.233; our IP address is 10.193.20.130
> Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: *
> TFTP error: 'Unsupported option(s) requested' (8)
> Starting again
> => setenv tftptimeout 1000
> => tftp a0000000 gqy/bootscript
> Using FM1 at DTSEC3 device
> TFTP from server 10.192.208.233; our IP address is 10.193.20.130
> Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: #
>          44.9 KiB/s
> done
> Bytes transferred = 92 (5c hex)
> =>
> 
> Regards,
> Qianyu
> 

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[U-Boot] TFTP Timeout Interval problem

[Gong Q.Y.]

Hi,

That's all right. Thanks a lot!

Regards,
Qianyu

-----Original Message-----
From: Pavel Machek [mailto:pavel at denx.de] 
Sent: Monday, August 31, 2015 8:16 PM
To: Gong Qianyu-B52263
Cc: u-boot at lists.denx.de
Subject: Re: TFTP Timeout Interval problem

Hi!

> I got a problem with tftp and found this patch.

Yes, sorry about that. Just revert it, or update to newer u-boot where it should be reverted.

> -------------
> commit 620776d734e4b126c407f636bda825a594a17723
> Author: Pavel Machek <pavel@denx.de>
> Date:   Tue Aug 18 14:34:26 2015 +0200
> 
>     tftp: adjust settings to be suitable for 100Mbit ethernet
> --------------
> The default timeout is changed to 100 (ms) and this causes "TFTP error: 'Unsupported option(s) requested' (8)".
> 
> Because the option is equal to timeout/1000, now it's zero(100/1000 -> 0) which is not supported.
> Actually I find in an original doc RFC-2349 which specifies this value should range between "1" and "255" seconds.
> 
> So I think there may be a conflict?
> Look forward to your help.
> 
> This is my test log:
> => tftp a0000000 gqy/bootscript
> Using FM1 at DTSEC3 device
> TFTP from server 10.192.208.233; our IP address is 10.193.20.130 
> Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: *
> TFTP error: 'Unsupported option(s) requested' (8) Starting again => 
> setenv tftptimeout 1000 => tftp a0000000 gqy/bootscript Using 
> FM1 at DTSEC3 device TFTP from server 10.192.208.233; our IP address is 
> 10.193.20.130 Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: #
>          44.9 KiB/s
> done
> Bytes transferred = 92 (5c hex)
> =>
> 
> Regards,
> Qianyu
> 

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[U-Boot] TFTP Timeout Interval problem

[Bin Meng]

Hi Qianyu,

On Mon, Aug 31, 2015 at 6:43 PM, Gong Q.Y. <Qianyu.Gong@freescale.com> wrote:
> Hi,
>
> I got a problem with tftp and found this patch.
> -------------
> commit 620776d734e4b126c407f636bda825a594a17723
> Author: Pavel Machek <pavel@denx.de>
> Date:   Tue Aug 18 14:34:26 2015 +0200
>
>     tftp: adjust settings to be suitable for 100Mbit ethernet
> --------------
> The default timeout is changed to 100 (ms) and this causes "TFTP error: 'Unsupported option(s) requested' (8)".
>
> Because the option is equal to timeout/1000, now it's zero(100/1000 -> 0) which is not supported.
> Actually I find in an original doc RFC-2349 which specifies this value should range between "1" and "255" seconds.
>
> So I think there may be a conflict?
> Look forward to your help.

Check this patch: http://patchwork.ozlabs.org/patch/511761/

I believe it should be applied soon.

>
> This is my test log:
> => tftp a0000000 gqy/bootscript
> Using FM1 at DTSEC3 device
> TFTP from server 10.192.208.233; our IP address is 10.193.20.130
> Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: *
> TFTP error: 'Unsupported option(s) requested' (8)
> Starting again
> => setenv tftptimeout 1000
> => tftp a0000000 gqy/bootscript
> Using FM1 at DTSEC3 device
> TFTP from server 10.192.208.233; our IP address is 10.193.20.130
> Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: #
>          44.9 KiB/s
> done
> Bytes transferred = 92 (5c hex)
> =>
>

Regards,
Bin