Re: [Openocd-development] Is this STM32F100x errata sheet discovery the cause of my problems?

2010-10-04 Thread Øyvind Harboe 
 Could anyone tell me whether this silicon bug will affect OpenOCD, and, if 
 so, how?

I don't think so. You can check the log whether there is a verify_ir capture
error message. Type help verify and you can turn off verification of the
ir capture(which is really just to verify that the communication is working)

-- 
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] Is this STM32F100x errata sheet discovery the cause of my problems?

2010-10-04 Thread Andreas Fritiofson 
On Mon, Oct 4, 2010 at 6:36 PM,  n...@bike-nomad.com wrote:
 I've been trying to use OpenOCD with the STM32F100C4T6B, one of the new low 
 density value line processors from STMicroelectronics.

 I haven't had too much success using it (not stopping at breakpoints, not 
 noticing when it has stopped at breakpoints, not working well with gdb, not 
 stepping once at a breakpoint, etc.) and I was thinking that this information 
 from the errata sheet might have something to do with my problems.

 Could anyone tell me whether this silicon bug will affect OpenOCD, and, if 
 so, how?

 2.5     Boundary scan TAP: wrong pattern sent out after the “capture IR” state

The errata mentions the boundary scan TAP only. It's not likely that
the core debug TAP is affected. But I have not read the whole errata
sheet.

Regards,
Andreas
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development