RE: enable/disable breakpoint in code

Vidar Berg — Tue, 21 Apr 2020 06:37:18 GMT

Thanks for the update. I'm glad to hear that you were able to locate the problem.

RE: enable/disable breakpoint in code

Allen — Mon, 20 Apr 2020 17:53:46 GMT

Yes, this is related to that thread.

At it turns out, this was a pointer issue which happened to be overwriting the timer structure. It certainly would be useful to find a workable debug technique for problems like this.

RE: enable/disable breakpoint in code

Vidar Berg — Fri, 17 Apr 2020 14:35:00 GMT

Hello,

Each (DWT) comparator instance comes with one compare register (Debug and trace + ARM® v7-M Architecture Reference Manual C1.8). So I don't believe it's possible to trigger a breakpoint based on multiple address inputs (ie both instruction address & data address in this case), unfortunately.

[quote user=""]We are currently suspecting that the type of data breakpoints in the device you’re using is limited (Data Ranges and PC> not possible).[/quote]

For address matching, you can use a mask to ignore a portion of the bits in the address and thus allow you to monitor a range of addresses. However, specifying range limits with "larger than" and "smaller than" is not supported as far as I can tell.

I have not been able to find a way to programmatically disable breakpoints set by the debugger either (sorry). It seems as if the debug control registers are read-only while in debug interface mode. At least the appeared to be when I tried it (control settings didn't change).

Is this related to the issue you reported in this other thread: https://devzone.nordicsemi.com/f/nordic-q-a/60274/request-for-review-of-app_timer2-backport-to-sdk14-0 ?