On Mon, Oct 4, 2010 at 6:36 PM, 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 breakpo
> Can you git bisect to find the problem commit?
>
After having a look at the git commits, it seems that the first commit from
2009-12-29 already has the broken version.
The sane version I was referring to, was passed to the mailing list by Catalin
Patulea (cat at vv.carleton.ca) on Sun Dec 20
> 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 commun
Can you git bisect to find the problem commit?
Felix wrote:
Hi,
the driver for the Altera USB-Blaster and compatibles in version 0.4.0 (and up
to the current git snapshot) is (at least partially) broken.
Somewhere in the merge process, the bit which enables the output (and the LED
in the ori
Hi,
the driver for the Altera USB-Blaster and compatibles in version 0.4.0 (and up
to the current git snapshot) is (at least partially) broken.
Somewhere in the merge process, the bit which enables the output (and the LED
in the original altera usb blaster) must have got lost. It was included i
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 onc
