Thank you, i also tried it with the GIT head build... unfortunately same
behavior.
On November 5, 2019 18:02:45 Tommy Murphy <tommy_mur...@hotmail.com> wrote:
Seems a bit odd to me.
Sometimes it's using a hardware breakpoint
Debug: 3162 10991 cortex_m.c:1228 cortex_m_set_breakpoint(): BPID: 0, Type:
0, Address: 0x08000354 Length: 2 (set=1)
Debug: 3163 10991 breakpoints.c:104 breakpoint_add_internal(): added
hardware breakpoint at 0x08000354 of length 0x00000002, (BPID: 0)
and sometimes it's using a software breakpoint
Debug: 4354 11046 cortex_m.c:1228 cortex_m_set_breakpoint(): BPID: 1, Type:
1, Address: 0x08000354 Length: 2 (set=1)
Debug: 4355 11046 breakpoints.c:104 breakpoint_add_internal(): added
software breakpoint at 0x08000354 of length 0x00000002, (BPID: 1)
For the same address (0x08000354).
If it tries to set a s/w BP in ROM/nvm then it is not going to work since
the target code memory is not (directly) writeable (I would have expected
it not to do this based on the flash bank declared in the openocd debug
script or to issue an error if it somehow got attempted).
I can't really explain why this is happening.
I could also point out that your build of openocd is quite old and there
have been many changes to Cortex-M support code in the meantime so it might
make more sense to use a more recent build.
Open On-Chip Debugger 0.10.0+dev-00730-ge243075 (2019-03-07-13:52)
Hope this helps.
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
