External reset when debugging nRF52

[Remo]

Hi all

I'm using the nRF52832 and I've configured P0.21 as RESET pin.

When I reset the nRF52 via P0.21 while the debugger is running, the nRF52 actually resets but it seems that the debugger didn't recognize the reset (a breakpoint at the beginning of the main function didn't trigger).

How can I achieve that the debugger remains synchronous to the actual code execution when applying an external reset? Is that even possible?

Kind regards

[FormerMember]

Using an external reset will most likely "mess it up" for the debuggger..

If you want to test resetting when in debug mode, you can use nrfjprog to reset the chip. The code should then be able to hit a breakpoint in main.

Update 14.10.2016: If using nrjprog, you can choose between a soft reset and a pin reset.

[Remo]

Hi Kristin.

Would it help if I connect the nRESET signal of the NRF52 also to the debugger, so that the debugger sees that an external reset was applied? Currently, only SWDIO and SWDCLK are connected to the debugger.

What kind of reset is performed when using the nrfjprog?

[FormerMember]

I don't know if it will work to connect the reset signal to the debugger as well..

[Remo]

I'm not sure if I understand you correctly. I would like to debug the startup of my application with the IAR and the SEGGER J-link debugger after an external reset was applied. How can I debug with IAR when the nrfjprog is connected to the chip? Did I miss something?

[FormerMember]

I have only tried with Keil, but if I run the code in debug mode and then run "nrfjprog --reset --nrf52" (soft reset)the code will reset, and hit a breakpoint in main.

[Remo]

I've tried the nrfjprog with the IAR. When performing the soft reset, the IAR is able to follow it and hits the breakpoint, but when performing the pin reset (which was the one I wanted to test) the IAR can't follow it. So, unfortunately, it seems that there is no solution for this...