Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-23 Thread David Brownell
On Tuesday 19 January 2010, David Brownell wrote: > REGRESSIONS -- must be fixed before release: > >  - GDB memory maps report sector sizes incorrectly.  This is >    actually a longstanding bug, which was previously masked >    by other now-fixed bugs. Fixed. >  - ARM11 misbehavior ... JTAG re

Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-20 Thread David Brownell
Feel free to submit patches for these! :) Priority on regression fixes, but any fixes that don't de-stabilize are still good to go. - Dave On Wednesday 20 January 2010, Edgar Grimberg wrote: > > * I see some error messages for STR710 config: > Error: command 'str7x' is already registered in '

Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-20 Thread Edgar Grimberg
On Wed, Jan 20, 2010 at 6:58 AM, David Brownell wrote: > Here's my current summary of *OPEN* issues with RC1. > > If you raised an issue and it's not on this list then either > it's now resolved, or else I missed that and it's still an > open issue.  Please verify. > > If you know about other issu

Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-20 Thread David Brownell
On Tuesday 19 January 2010, Øyvind Harboe wrote: > > > > I can't see anything to do with that beyond documenting it. > > > > If you write *without* enabling that checksum-updating feature, > > it won't boot (as I recall folk complaining). > > > > If you write with it *enabled*, then verify_image fa

Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-19 Thread David Brownell
On Tuesday 19 January 2010, Øyvind Harboe wrote: > > > Another "bug/feature" is that the LPC driver will update the checksum > > > automatically. This will cause verify_image to fail when writing to LPC > > > flashes. > > > > I can't see anything to do with that beyond documenting it. > > > > If yo

Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-19 Thread Øyvind Harboe
On Wed, Jan 20, 2010 at 8:22 AM, David Brownell wrote: > > On Tuesday 19 January 2010, Øyvind Harboe wrote: > > >  - NOR structural issue:  wrongly writing ones, instead of not > > >   writing anything.  Can corrupt some flashes; for example it > > >   would modify internal ECC codes.  Some flashe

Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-19 Thread David Brownell
On Tuesday 19 January 2010, Øyvind Harboe wrote: > >  - NOR structural issue:  wrongly writing ones, instead of not > >   writing anything.  Can corrupt some flashes; for example it > >   would modify internal ECC codes.  Some flashes don't seem to > >   care about this, but it violates all manufac

Re: [Openocd-development] RC1 status report, 19-Jan-2009

2010-01-19 Thread Øyvind Harboe
>  - NOR structural issue:  wrongly writing ones, instead of not >   writing anything.  Can corrupt some flashes; for example it >   would modify internal ECC codes.  Some flashes don't seem to >   care about this, but it violates all manufacturer guidelines. >   (Longstanding bug.) Another "bug/f

[Openocd-development] RC1 status report, 19-Jan-2009

2010-01-19 Thread David Brownell
Here's my current summary of *OPEN* issues with RC1. If you raised an issue and it's not on this list then either it's now resolved, or else I missed that and it's still an open issue. Please verify. If you know about other issues, please post them! - Dave REGRESSIONS -- must be fixed before