No longer able to program custom nRF52840 over SWD. No idcode detected

[NautDesigner]

I had been able to program my custom nRF52840 just fine until I wanted to change partitions. I erased everything and now am unable to communicate with the board at all. I get "Failed to connect to target. No idcode detected. Please check connection and Target Interface Type."

When I try to recover the board, I get:

>nrfjprog --recover --family NRF52 --log
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: Unable to connect to a debugger.
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

I'm using an nRF52840 DK to program the boards and it has no problem programming other boards. Not sure what I need to do to get the custom boards working again.

[Simonr]

Hi again

Seeing as you're able to program the DK as intended, but not the custom board, something seems to have damaged or erased the UICR of these external boards.

As Jay suggests, have you measured the voltage on VTG before and after an erase, as the REG0 voltage might have switched to 1.8V after an UICR erase. How to recover from this is explained in our nRF52840 Dongle programming tutorial? And have you updated the SEGGER/J-Link software to the latest available version?

Can you also try printing and uploading a log as the nrfjprog suggests "JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them."

Best regards,

Simon

[NautDesigner]

Where am I measuring VTG? I ran nrfjprog twice. Before is DK powered up first, custom board 2nd. After is custom board powered first and DK second.

Before:

[2022-Jan-03 18:50:11] [ info] --------------------------------------------------------------------------------
[2022-Jan-03 18:50:11] [ info] D:\Programs\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe --recover --family NRF52 --log
[2022-Jan-03 18:50:11] [ info] nrfjprog version 10.15.1 external
[2022-Jan-03 18:50:11] [ info] --------------------------------------------------------------------------------
[2022-Jan-03 18:50:11] [ info] Load library at D:\Programs\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.dll.
[2022-Jan-03 18:50:11] [ info] Library loaded, loading member functions.
[2022-Jan-03 18:50:11] [ info] Member functions succesfully loaded.
[2022-Jan-03 18:50:11] [debug] [ Client] - open
[2022-Jan-03 18:50:11] [debug] [ Client] - start
[2022-Jan-03 18:50:11] [ info] [ Client] - stdout: Jlinkarm nRF Worker ready. Handling sequence 99277e72-d630-49dd-ad1f-0e422ab573ad.
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - Logger sink registered in Segger backend logger
[2022-Jan-03 18:50:11] [debug] [  JLink] - Logger sink registered in JLink logger
[2022-Jan-03 18:50:11] [debug] [  nRF52] - open
[2022-Jan-03 18:50:11] [debug] [  nRF52] - just_check_family
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - open_dll
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - No J-Link DLL path was provided. Attempting to auto detect.
[2022-Jan-03 18:50:11] [ info] [SeggerBackend] - Load library at d:\SEGGER\JLink\JLink_x64.dll.
[2022-Jan-03 18:50:11] [ info] [SeggerBackend] - Library loaded, loading member functions.
[2022-Jan-03 18:50:11] [ info] [SeggerBackend] - Member functions succesfully loaded.
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - dll_version
[2022-Jan-03 18:50:11] [ info] [SeggerBackend] - Segger dll version 7.58.b loaded.
[2022-Jan-03 18:50:11] [trace] [ Worker] - Command open executed for 2 milliseconds with result 0
[2022-Jan-03 18:50:11] [trace] [ Client] - Command open executed for 38 milliseconds with result 0
[2022-Jan-03 18:50:11] [debug] [ Client] - enum_emu_snr
[2022-Jan-03 18:50:11] [trace] [ Client] - Command enum_emu_con_info executed for 15 milliseconds with result 0
[2022-Jan-03 18:50:11] [debug] [  nRF52] - enum_emu_con_info
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - enum_emu_con_info
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:50:11] [trace] [ Worker] - Command enum_emu_con_info executed for 1 milliseconds with result 0
[2022-Jan-03 18:50:11] [debug] [  nRF52] - close
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - close
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - disconnect_from_emu
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:50:11] [debug] [SeggerBackend] - Segger Backend closed.
[2022-Jan-03 18:50:11] [debug] [  nRF52] - nRF family DLL closed
[2022-Jan-03 18:50:11] [trace] [ Client] - Command close executed for 31 milliseconds with result 0
[2022-Jan-03 18:50:11] [debug] [ Client] - terminate
[2022-Jan-03 18:50:11] [trace] [ Client] - Command terminate executed for 0 milliseconds with result 0
[2022-Jan-03 18:50:11] [trace] [ Worker] - Command close executed for 30 milliseconds with result 0
[2022-Jan-03 18:50:11] [trace] [ Worker] - Command terminate executed for 0 milliseconds with result 0
[2022-Jan-03 18:50:11] [trace] [ Worker] - Executed 4 commands for 33 milliseconds
[2022-Jan-03 18:50:11] [debug] [ Client] - Worker process exited with code: 0
[2022-Jan-03 18:50:11] [debug] [ Client] - Worker process exited with code: 0
[2022-Jan-03 18:50:11] [debug] [ Client] - Child process terminated with result 0
[2022-Jan-03 18:50:11] [trace] [ Client] - Executed 4 commands for 84 milliseconds
[2022-Jan-03 18:50:11] [debug] [ Client] - terminate

After:

[2022-Jan-03 18:53:17] [ info] --------------------------------------------------------------------------------
[2022-Jan-03 18:53:17] [ info] D:\Programs\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe --recover --family NRF52 --log
[2022-Jan-03 18:53:17] [ info] nrfjprog version 10.15.1 external
[2022-Jan-03 18:53:17] [ info] --------------------------------------------------------------------------------
[2022-Jan-03 18:53:17] [ info] Load library at D:\Programs\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.dll.
[2022-Jan-03 18:53:17] [ info] Library loaded, loading member functions.
[2022-Jan-03 18:53:17] [ info] Member functions succesfully loaded.
[2022-Jan-03 18:53:17] [debug] [ Client] - open
[2022-Jan-03 18:53:17] [debug] [ Client] - start
[2022-Jan-03 18:53:17] [ info] [ Client] - stdout: Jlinkarm nRF Worker ready. Handling sequence ad7df7f2-24e3-47a0-aa3b-b710d5090866.
[2022-Jan-03 18:53:17] [trace] [ Client] - Command open executed for 38 milliseconds with result 0
[2022-Jan-03 18:53:17] [debug] [ Client] - enum_emu_snr
[2022-Jan-03 18:53:17] [trace] [ Client] - Command enum_emu_con_info executed for 15 milliseconds with result 0
[2022-Jan-03 18:53:17] [debug] [ Client] - connect_to_emu_with_snr
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Logger sink registered in Segger backend logger
[2022-Jan-03 18:53:17] [debug] [  JLink] - Logger sink registered in JLink logger
[2022-Jan-03 18:53:17] [debug] [  nRF52] - open
[2022-Jan-03 18:53:17] [debug] [  nRF52] - just_check_family
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - open_dll
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - No J-Link DLL path was provided. Attempting to auto detect.
[2022-Jan-03 18:53:17] [ info] [SeggerBackend] - Load library at d:\SEGGER\JLink\JLink_x64.dll.
[2022-Jan-03 18:53:17] [ info] [SeggerBackend] - Library loaded, loading member functions.
[2022-Jan-03 18:53:17] [ info] [SeggerBackend] - Member functions succesfully loaded.
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - dll_version
[2022-Jan-03 18:53:17] [ info] [SeggerBackend] - Segger dll version 7.58.b loaded.
[2022-Jan-03 18:53:17] [trace] [ Worker] - Command open executed for 2 milliseconds with result 0
[2022-Jan-03 18:53:17] [debug] [  nRF52] - enum_emu_con_info
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - enum_emu_con_info
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:53:17] [trace] [ Worker] - Command enum_emu_con_info executed for 1 milliseconds with result 0
[2022-Jan-03 18:53:17] [debug] [  nRF52] - connect_to_emu_with_snr
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - connect_to_emu_with_snr
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_enum_emu_snr
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_get_num_emus
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_connect_to_emu_with_snr
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_connect_to_emu_without_snr
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Segger logging enabled.
[2022-Jan-03 18:53:17] [trace] [  JLink] - Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
[2022-Jan-03 18:53:17] [trace] [  JLink] - Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
[2022-Jan-03 18:53:17] [trace] [  JLink] - Hardware: V1.00
[2022-Jan-03 18:53:17] [trace] [  JLink] - S/N: 683801362
[2022-Jan-03 18:53:17] [trace] [  JLink] - OEM: SEGGER
[2022-Jan-03 18:53:17] [trace] [  JLink] - Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
[2022-Jan-03 18:53:17] [trace] [  JLink] - TELNET listener socket opened on port 19021
[2022-Jan-03 18:53:17] [trace] [  JLink] - WEBSRV WEBSRV_Init(): Starting webserver thread(s)
[2022-Jan-03 18:53:17] [trace] [  JLink] - WEBSRV Webserver running on local port 19080
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 15.107ms returns "O.K."
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_Lock()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_GetHWStatus(...)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.444ms returns 0
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_ExecCommand("SetRestartOnClose = 0", ...).
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.002ms returns 0x01
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_ExecCommand("DisableFlashDL", ...).
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.002ms returns 0x00
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.003ms returns 0x00
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_SetHookUnsecureDialog
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_SetHookUnsecureDialog(...)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.008ms returns 0
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_TIF_Select(JLINKARM_TIF_SWD)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.493ms returns 0x00
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_SetSpeed(2000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.339ms
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_GetSN()
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.003ms returns 683801362
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - read_debug_port_idr
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - read_debug_port_register
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_read_debug_port_register
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - coresight_configure
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_Configure()
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 100.980ms returns 0
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_select_debug_port_register
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Select AP 255, DP Bank 0, AP Bank 255
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.536ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.554ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.456ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.464ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.466ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.385ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.215ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.274ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.261ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.091ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.111ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.261ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.284ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.122ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.089ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [ Client] - Command connect_to_emu_with_snr executed for 185 milliseconds with result -102
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.117ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.008ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.084ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.116ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.123ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.048ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.124ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.086ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.141ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.112ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.138ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.073ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.109ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.106ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.128ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.054ms
[2022-Jan-03 18:53:17] [trace] [ Worker] - Command connect_to_emu_with_snr executed for 171 milliseconds with result -102
[2022-Jan-03 18:53:17] [debug] [  nRF52] - close
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - is_connected_to_emu
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_IsOpen()
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.013ms returns 0x01
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_Lock()
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - close
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - disconnect_from_emu
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_disconnect_from_emu
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - is_connected_to_device
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_IsConnected()
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.003ms returns FALSE
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_is_debug_region_powered
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_read_debug_port_register
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_select_debug_port_register
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Select AP 255, DP Bank 0, AP Bank 255
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.209ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.195ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.290ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.314ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.096ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.155ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.144ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.146ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.280ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.250ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.241ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.145ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.093ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.116ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.138ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.154ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.128ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.149ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.096ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.101ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.067ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.050ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.130ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.089ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.077ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - ---just_abort_debug_action
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Attempting to clear any configuration errors in debug port before closing connection.
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.094ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.107ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.130ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.164ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x00, 0x0000001F)
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 1.208ms returns -1
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_HasError()
[2022-Jan-03 18:53:17] [error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[2022-Jan-03 18:53:17] [trace] [  JLink] - - 0.011ms
[2022-Jan-03 18:53:17] [trace] [  JLink] - JLINK_Close()
[2022-Jan-03 18:53:17] [trace] [ Client] - Command close executed for 78 milliseconds with result 0
[2022-Jan-03 18:53:17] [debug] [ Client] - terminate
[2022-Jan-03 18:53:17] [trace] [ Client] - Command terminate executed for 0 milliseconds with result 0
[2022-Jan-03 18:53:17] [debug] [SeggerBackend] - Segger Backend closed.
[2022-Jan-03 18:53:17] [debug] [  nRF52] - nRF family DLL closed
[2022-Jan-03 18:53:17] [trace] [ Worker] - Command close executed for 77 milliseconds with result 0
[2022-Jan-03 18:53:17] [trace] [ Worker] - Command terminate executed for 0 milliseconds with result 0
[2022-Jan-03 18:53:17] [trace] [ Worker] - Executed 5 commands for 251 milliseconds
[2022-Jan-03 18:53:17] [debug] [ Client] - Worker process exited with code: 0
[2022-Jan-03 18:53:17] [debug] [ Client] - Worker process exited with code: 0
[2022-Jan-03 18:53:17] [debug] [ Client] - Child process terminated with result 0
[2022-Jan-03 18:53:17] [trace] [ Client] - Executed 5 commands for 316 milliseconds
[2022-Jan-03 18:53:17] [debug] [ Client] - terminate

[Simonr]

I see, that should make sure the connection is set up properly at least. After discussing this issue with some colleagues we don't see any reason that changing the storage partitions should have caused the external board to not be found when trying to recover it. In at least one of the logs you have uploaded, the computer doesn't seem to be able to communicate DK, which sounds like the onboard debugger is busy with a debug session for example. So you should make sure that the DK is "free" before running an nrfjprog command.

Either way, the issue here is that you're not able to communicate with external board, can you try checking, with a multi-meter for instance, what voltage the external board is operating on? Worst case scenario is that the external board's nRF52840 is in a reset-loop, which also would lead to this behavior, and the only remedy here is to try and try again in hopes of recovering the device "between" these reset loops.

Best regards,

Simon