From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 75488C433EF for ; Tue, 7 Sep 2021 12:51:47 +0000 (UTC) Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1FD9F604E9 for ; Tue, 7 Sep 2021 12:51:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 1FD9F604E9 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=dalco.ch Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.denx.de Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 5273A831A0; Tue, 7 Sep 2021 14:51:43 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=dalco.ch Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Received: by phobos.denx.de (Postfix, from userid 109) id 50A3C82DB4; Tue, 7 Sep 2021 14:51:41 +0200 (CEST) Received: from mail.dalco.ch (mail.dalco.ch [195.242.140.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id DA50E831DB for ; Tue, 7 Sep 2021 14:51:37 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=dalco.ch Authentication-Results: phobos.denx.de; spf=none smtp.mailfrom=Matteo.Guglielmi@dalco.ch From: Matteo Guglielmi To: Harm Berntsen CC: "u-boot@lists.denx.de" Subject: Re: tftp time outs Thread-Topic: tftp time outs Thread-Index: AQHXolwZJQ1Pk+nKEESJFeOMH5yFn6uYO4wAgABKNVE= Date: Tue, 7 Sep 2021 12:51:37 +0000 Message-ID: <4e3728c605044550be6c514b7959dbd4@dalco.ch> References: <9906d64ad53d41829b3881daf18b7ef1@dalco.ch>, <453cb861a8b80d52057bc8f5256d02abbb35f70f.camel@nedap.com> In-Reply-To: <453cb861a8b80d52057bc8f5256d02abbb35f70f.camel@nedap.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.16.200] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.34 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean Hi Harm, thanks for the suggestion. I have this set in my .config file for the compilation of u-boot: CONFIG_TFTP_BLOCKSIZE=3D1468 CONFIG_TFTP_WINDOWSIZE=3D1 I'm also using a custom boot.cmd file... should I instead just put your vars in it like this: tftpblocksize=3D512 tftptimeout=3D10000 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 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=3D512 tftptimeout=3D10000 -- Harm -----Original Message----- From: Matteo Guglielmi To: 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.