From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Sverdlin Date: Thu, 2 Aug 2018 16:47:19 +0200 Subject: [U-Boot] xyz-modem: Change getc timeout loop waiting In-Reply-To: References: <1479716331-94776-1-git-send-email-tomas.melin@vaisala.com> <20180801021507.d9061b74b8068bb32edfac5a@gmail.com> <4f3ed6cb-cd68-8e78-38a5-5ab4f9fce305@vaisala.com> <20180801075431.765edc6d1eebfa0ccbf3693d@gmail.com> Message-ID: <20180802164719.a66642bea689ec07add06fb8@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Tomas, On Wed, 1 Aug 2018 09:16:38 +0300 Tomas Melin wrote: > >> Is the timeout a watchdog timeout or some communication freeze? > > I suppose, it reports false-positive timeout back to ymodem code. > > Because all it does is terminating communication gracefully (with 'C' > > and a bunch of CANs). > If you are using omap_wdt then check the configured value of the timeout > (WDT_HW_TIMEOUT). > Time the y-modem loading, and if the reset happens just after that > configured value, it would indicate that the watchdog is not kicked, for > one reason or another. Yes, I'm using omap_wdt with default 60 seconds timeout, but as I mentioned already, it's not WDT kicking in, but your patch breaking YMODEM protocol reporting false timeout back to YMODEM code. -- Alexander Sverdlin.