Ozone conditional breakpoints cause nrf52840 to hardfault after softdevice starts

RE: Ozone conditional breakpoints cause nrf52840 to hardfault after softdevice starts

Kenneth — Tue, 11 Feb 2025 09:09:58 GMT

Hi,

You would need to check with Segger. But if I am right that conditional breakpoint actually means that the debugger do halt the code execution for a short period to evaluate the condition, then that may brake the realtime requirements by the softdevice. So I suggest to add code such as an if statement and instead set a normal breakpoint within the if statement.

Kenneth

RE: Ozone conditional breakpoints cause nrf52840 to hardfault after softdevice starts

tmuir_pct — Tue, 11 Feb 2025 04:32:01 GMT

Hi Kenneth,

I have had varying degrees of success, but the flakiness seems to come and go. Setting the breakpoint type to be software, rather than any, or hardware, has seemed to have had more success, but I still get hardfaults occasionally. Also, some of the conditions I tried out were problematic, even though they are valid C. For instance array[0] == 'A' doesn't seem to work, but array[0] == 0x41 is acceptable.

Is there documentation of what constitutes valid syntax for the condition expressions?

RE: Ozone conditional breakpoints cause nrf52840 to hardfault after softdevice starts

Kenneth — Mon, 10 Feb 2025 22:43:45 GMT

Hello,

Afaik in Ozone, when a conditional breakpoint is set, the debugger evaluates the condition every time the program execution reaches the breakpoint location. I don't see any other way than use if statements in code for temporary debugging.

Kenneth