This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrfjprog ---pinreset not working on nRF52

Hello! I am using a custom board that contains a nRF52832 device. The board has the SWDIO and SWDCK lines connected, which I have successfully been using to flash and debug the firmware.

However, I cannot seem to make the device leave debug mode. I have tried to use the --pinresetenable and --pinreset command with nrfjprog, but with no success.

The procedure I followed was:

    1. Disconnect and reconnect device battery. Current consumption is bellow 0.1mA, as expected.
    1. Connect Segger debugger, start JLinkExe and run power on and connect. Current consumption becomes around 2mA. An increase was expected.
    1. Close JLinkExe.
    1. Run nrfjprog --pinresetenable -f nrf52. echo $? returns 0.
    1. Run nrfjprog --pinreset -f nrf52. echo $? returns 0.
    1. Disconnect debugger from board. Current consumption remains ~2mA

Do any other steps have to be taken to switch back to normal mode? Does the board have to implement anything else other than the SWD lines for these commands to work?

Parents
  • @endnode There is nothing connected to P0.21/RESET. Should this be connected to nReset? When the pinreset command is issued, the current consumption increases slightly (for about 3 seconds), the Segger LED blinks green a couple of times and blinks red one time. However, the chip does not reset.

    nrfjprog -r -f NRF52 does in fact reset the chip, but apparently it doesn't bright it out of debug mode, since the current consumption goes back to where it was (~2mA).

Reply
  • @endnode There is nothing connected to P0.21/RESET. Should this be connected to nReset? When the pinreset command is issued, the current consumption increases slightly (for about 3 seconds), the Segger LED blinks green a couple of times and blinks red one time. However, the chip does not reset.

    nrfjprog -r -f NRF52 does in fact reset the chip, but apparently it doesn't bright it out of debug mode, since the current consumption goes back to where it was (~2mA).

Children
No Data
Related