On Wed, Nov 4, 2009 at 10:15 AM, Pieter Conradie
wrote:
> Hi Øyvind,
>
> I have tested and can confirm that
> "0001-target-5-second-timeout-megabyte-for-CRC-check-20-se.patch" works.
>
> I have successfully verified a 16 MByte image and a 512kByte image.
Pushed to master.
--
Øyvind Harboe
ht
.com]
Sent: 03 November 2009 11:18 PM
To: David Brownell
Cc: openocd-development@lists.berlios.de; Pieter Conradie
Subject: Re: [Openocd-development] CRC check timeout
How's this?
(Confirmation that *this* patch fixes the problem is still missing...)
--
Øyvind Harboe
http://www.zylin.com/z
> IMHO a timeout which depends on several unknown variables
> should be implemented otherwise. Perhaps the CRC routine can
> be modified to reset the time-out for every 1024 bytes/words/dwords.
> This should give little overhead but absolute certainty a timeout
> will only occur due to an error.
Subject: Re: [Openocd-development] CRC check timeout
>
> On Tuesday 03 November 2009, Øyvind Harboe wrote:
> > Should we include this fix for 0.3?
>
> Only if it's updated to comment that it *still* makes
> an unwise assumption about target clock rate. If it's
>
How's this?
(Confirmation that *this* patch fixes the problem is still missing...)
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
From 553e7bdd606ee0b7015e95f037b07e2dcddb375e Mon Sep 17 00:00:00 2001
From: =?utf-8?q?=C3=98yvi
On Tuesday 03 November 2009, Øyvind Harboe wrote:
> Should we include this fix for 0.3?
Only if it's updated to comment that it *still* makes
an unwise assumption about target clock rate. If it's
running with a 32 KHz clock, will that timeout be long
enough? How about 8 KHz? Or lower? :)
Test
On Tuesday 03 November 2009, Dean Glazeski wrote:
> I thought I might throw this in here, but the last time I tried to use the
> CRC check, it didn't work. This was a long time ago, but I believe the
> problem was due in part to interrupts being enabled on the chip. Is this
> resolved, too?
No i
I thought I might throw this in here, but the last time I tried to use the
CRC check, it didn't work. This was a long time ago, but I believe the
problem was due in part to interrupts being enabled on the chip. Is this
resolved, too?
// Dean Glazeski
On Tue, Nov 3, 2009 at 4:12 PM, David Brown
On Tuesday 03 November 2009, Øyvind Harboe wrote:
> How's this?
>
> (Confirmation that *this* patch fixes the problem is still missing...)
Seems fair to me.
If Pieter can confirm before 0.3 finalizes, merge it on
the grounds that it can't be _worse_ and may well fix that.
__
Should we include this fix for 0.3?
Confirmation that it works and looks OK would be a point
in favor. Hint! Hint! ;-)
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
From e37076a747bc1f1a709ec9feb57c9492dc18b062 Mon Sep 17 00:
10 matches
Mail list logo