From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Date: Wed, 1 Aug 2018 07:54:31 +0200
Subject: [U-Boot] xyz-modem: Change getc timeout loop waiting
In-Reply-To: <4f3ed6cb-cd68-8e78-38a5-5ab4f9fce305@vaisala.com>
References: <1479716331-94776-1-git-send-email-tomas.melin@vaisala.com>
 <20180801021507.d9061b74b8068bb32edfac5a@gmail.com>
 <4f3ed6cb-cd68-8e78-38a5-5ab4f9fce305@vaisala.com>
Message-ID: <20180801075431.765edc6d1eebfa0ccbf3693d@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi!

On Wed, 1 Aug 2018 08:44:13 +0300
Tomas Melin <tomas.melin@vaisala.com> wrote:

> > This commit breaks YMODEM SPL->U-Boot boot on Beagle Bone,
> > transfer is aborted (because of timeout) after 497kb
> > (u-boot.img is around 570kb).
> > Reverting the commit repairs YMODEM boot.
> 
> 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).
I need to check if timer overflow is possible on Beaglebone,
because the code is obviously not overflow-proof, but on the
other hand it happens within minutes and at least the timer variable
is 32 bit...

> In case watchdog is correctly configured, kicking should still
> happen.

-- 
Alexander Sverdlin.