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
Hi!
On Wed, 1 Aug 2018 08:44:13 +0300
Tomas Melin 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
Hi,
On 08/01/2018 08:54 AM, Alexander Sverdlin 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
Hi,
On 08/01/2018 03:15 AM, Alexander Sverdlin 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
Hello!
On Mon, 21 Nov 2016 10:18:51 +0200
Tomas Melin wrote:
> This fixes the loop delay when using a hw watchdog.
>
> In case a watchdog is used that accesses CPU registers,
> the defined delay of 20us in a tight loop will cause a
> huge delay in the actual timeout seen. This is caused
> by
On Mon, Nov 21, 2016 at 10:18:51AM +0200, tomas.me...@vaisala.com wrote:
> This fixes the loop delay when using a hw watchdog.
>
> In case a watchdog is used that accesses CPU registers,
> the defined delay of 20us in a tight loop will cause a
> huge delay in the actual timeout seen. This is
6 matches
Mail list logo
