• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 62 subscribers
  • Views 2905 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 127215
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nrf52832 can not be recovered

Jason

hi,

I tried to recover custom nrf52 board by nrfGo stuidio,and it failed,the logs as below:

--------------------------------------------------------------------------------
nrfjprog.exe --family --NRF52 -rbp --log
nrfjprog verion 9.7.1
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
nrfjprog.exe --family NRF52 -rbp --log
nrfjprog verion 9.7.1
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
nrfjprog.exe --family --NRF52 -rbp --log
nrfjprog verion 9.7.1
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
nrfjprog.exe --recover --log
nrfjprog verion 9.7.1
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_device_family.
FUNCTION: read_device_family.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.
Parents
  • 0

    Normally, if it were an nrf52 DK, I would tell you to turn off the board & turn it back on while holding the "IF BOOT/RESET" button. Then, you can open up file explorer (if you are using Windows) & the DK should be visible in bootloader mode. Then, you could download the latest version of the J-Link Interface MCU Firmware from here. Finally, you can just drag and drop the file to the nrf52 DK folder in file explorer. Do you have some kind of bootloader mode on your custom board?

Reply
  • 0

    Normally, if it were an nrf52 DK, I would tell you to turn off the board & turn it back on while holding the "IF BOOT/RESET" button. Then, you can open up file explorer (if you are using Windows) & the DK should be visible in bootloader mode. Then, you could download the latest version of the J-Link Interface MCU Firmware from here. Finally, you can just drag and drop the file to the nrf52 DK folder in file explorer. Do you have some kind of bootloader mode on your custom board?

Children
No Data
Related