External reset when debugging nRF52

RE: External reset when debugging nRF52

kvicky — Thu, 25 Aug 2022 05:59:09 GMT

Hi,

I am getting a similar error. I have nRF52832 board connected to raspberry pi for flashing and debugging using openocd. As soon as openocd command is executed I start getting this error:

Info : [nrf52.cpu] external reset detected

Following is the snippet of the output of the openocd command:

pi@vsense:~ $ openocd -c 'bindto 0.0.0.0' -f rpi_as_debugger.cfg -c 'transport s elect swd' -c 'adapter speed 250' -f target/nrf52.cfg
Open On-Chip Debugger 0.11.0+dev-00815-gf77c919cf (2022-08-23-18:35)
Licensed under GNU GPL v2
For bug reports, read
openocd.org/.../bugs.html
srst_only separate srst_gates_jtag srst_push_pull connect_deassert_srst

swd
adapter speed: 250 kHz

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : clock speed 1001 kHz
Info : SWD DPIDR 0x2ba01477
Info : [nrf52.cpu] Cortex-M4 r0p1 processor detected
Info : [nrf52.cpu] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for nrf52.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected
Info : [nrf52.cpu] external reset detected

.....

Does anyone have any idea what could be the root cause of this error propping up even when there is no IDE running, no flashing of program is done, no debugging through IDE is started/ going on.

Thanks in advance...

Regards,

Vicky

RE: External reset when debugging nRF52

Remo — Fri, 14 Oct 2016 14:39:45 GMT

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...

RE: External reset when debugging nRF52

FormerMember — Fri, 14 Oct 2016 12:00:56 GMT

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.

RE: External reset when debugging nRF52

Remo — Fri, 14 Oct 2016 09:39:13 GMT

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?

RE: External reset when debugging nRF52

FormerMember — Fri, 14 Oct 2016 09:00:55 GMT

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

RE: External reset when debugging nRF52

Remo — Wed, 12 Oct 2016 09:31:50 GMT

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?

RE: External reset when debugging nRF52

FormerMember — Wed, 12 Oct 2016 07:58:43 GMT

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.