Non-halting debugging on nrf52840dk

[maheswara]

I am following following procedure to use Non-halting debugging on nrf52840dk  with simple app.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/test_and_optimize/debugging.html#enabling-non-halting-debugging-with-cortex-m-debug-monitor

Board used : nrf52840DK

SDK: nrfconnect 2.6.1

When the log point is hit following error is seen, Can you please check and help to resolve this

[00:00:00.251,800] <inf> nrfx_ir_sample: nrfx_gpiote sample on nrf52840dk_nrf52840
[00:00:00.251,922] <inf> nrfx_ir_sample: nrfx_gpiote initialized
[00:00:00.251,953] <inf> nrfx_ir_sample: Time to wait: 100 ms
[00:00:00.251,983] <inf> nrfx_ir_sample: Timer status: enable
[00:00:00.251,983] <inf> nrfx_ir_sample: (D)PPI configured, leaving main()
[00:00:03.020,874] <err> os: ***** HARD FAULT *****
[00:00:03.020,904] <err> os: Debug event
[00:00:03.020,935] <err> os: r0/a1: 0x00000000 r1/a2: 0x00000151 r2/a3: 0x4001a000
[00:00:03.020,935] <err> os: r3/a4: 0x00000044 r12/ip: 0x80000000 r14/lr: 0x00000dfb
[00:00:03.020,935] <err> os: xpsr: 0x01000016
[00:00:03.020,965] <err> os: Faulting instruction address (r15/pc): 0x00000dfc
[00:00:03.020,996] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:03.020,996] <err> os: Fault during interrupt handling

[00:00:03.021,057] <err> os: Current thread: 0x20000810 (idle)

Thanks,

Mahesh

[Menon]

Hello,

Yes, there can be issues when setting a breakpoint inside an IRQ handler or during haltmode debugging. This has been discussed in this forum before, and I guess this is not a limitation of the segger debugger but rather the nature of the interrupt handler and debugging in halt mode. Take a look at this old thread. This thread is also discussing something very similar.

Kind Regards,

Abhijith