On Wed, Jan 20, 2010 at 6:58 AM, David Brownell <[email protected]> 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 issues, please post them!
* Flaky reset for STR710. This is an old bug. See: https://lists.berlios.de/pipermail/openocd-development/2010-January/014276.html * I see some error messages for STR710 config: Error: command 'str7x' is already registered in '<global>' context Error: command 'disable_jtag' is already registered in 'str7x' context * For STR710, I see wrong protected information in flash info: > flash protect 0 0 last off cleared protection for sectors 0 through 7 on flash bank 0 > flash info 0 #0 : str7x at 0x40000000, size 0x00040000, buswidth 0, chipwidth 0 # 0: 0x00000000 (0x2000 8kB) protected # 1: 0x00002000 (0x2000 8kB) protected # 2: 0x00004000 (0x2000 8kB) protected # 3: 0x00006000 (0x2000 8kB) protected # 4: 0x00008000 (0x8000 32kB) protected # 5: 0x00010000 (0x10000 64kB) protected # 6: 0x00020000 (0x10000 64kB) protected # 7: 0x00030000 (0x10000 64kB) protected * Formatting for mdh is wrong. Look at 0s: > mdh 0x0 32 0x00000000: beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef beef 0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Regards, Edgar > - Dave > > > 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. > > - ARM11 misbehavior ... JTAG reads fail with "SCREG OUT" errors > > Possible REGRESSIONS -- fix before release, if verified > > - MIPS 4K issue with (non?) CFI flash detect on one board; > and, presumably unrelated, byte order. I'm not clear on > status here, but this looked to be a regression... > > Open BUGS -- not regressions, but fixes are desirable: > > - STM32 first-load errors. (Seems to be a bug introduced in > the 0.3 series; not a regression *since* the 0.3 release.) > > - STM32 error recovery on boot from empty flash. (Unclear just > when this bug arrived. Pending verification from Zylin.) > > - 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.) > > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > -- Edgar Grimberg System Developer Zylin AS ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html Phone: (+47) 51 63 25 00 _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
