The nRF5340DK's are not programmable on my pc. I have no issues using nRF52DK and nRF52840DK. I have 3 different nRF5340DK's, they all have the same issue.
When I try nrfjprog --recover, I get the following error:
ERROR: No debuggers were discovered.
Log output:
[2024-Jun-06 16:33:46] [debug] -------------------------------------------------------------------------------- [2024-Jun-06 16:33:46] [debug] C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe --recover --log lognew.txt [2024-Jun-06 16:33:46] [debug] nrfjprog version 10.24.2 external [2024-Jun-06 16:33:46] [debug] -------------------------------------------------------------------------------- [2024-Jun-06 16:33:46] [ info] Load library at C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.dll. [2024-Jun-06 16:33:46] [ info] Library loaded, loading member functions. [2024-Jun-06 16:33:46] [ info] Member functions succesfully loaded. [2024-Jun-06 16:33:46] [debug] [ Client] - open [2024-Jun-06 16:33:46] [debug] [ Client] - start [2024-Jun-06 16:33:46] [ info] [ Client] - stdout: Jlinkarm nRF Worker ready. Handling sequence 017612d0-6d04-4423-9ed0-43ab154abb77. [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - Logger sink registered in Segger backend logger [2024-Jun-06 16:33:46] [debug] [ JLink] - Logger sink registered in JLink logger [2024-Jun-06 16:33:46] [debug] [ nRFXX] - open [2024-Jun-06 16:33:46] [debug] [ nRFXX] - just_check_family [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - open_dll [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - No J-Link DLL path was provided. Attempting to auto detect. [2024-Jun-06 16:33:46] [trace] [ Client] - Command open executed for 55 milliseconds with result 0 [2024-Jun-06 16:33:46] [ info] [SeggerBackend] - Load library at C:\Program Files\SEGGER\JLink_V796a\JLink_x64.dll. [2024-Jun-06 16:33:46] [debug] [ Client] - config [2024-Jun-06 16:33:46] [ info] [SeggerBackend] - Library loaded, loading member functions. [2024-Jun-06 16:33:46] [ info] [SeggerBackend] - Member functions succesfully loaded. [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - Set batch mode [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - dll_version [2024-Jun-06 16:33:46] [ info] [SeggerBackend] - Segger dll version 7.96.a loaded. [2024-Jun-06 16:33:46] [trace] [ Worker] - Command open executed for 5 milliseconds with result 0 [2024-Jun-06 16:33:46] [trace] [ Client] - Command config executed for 15 milliseconds with result 0 [2024-Jun-06 16:33:46] [debug] [ nRFXX] - config [2024-Jun-06 16:33:46] [debug] [ Client] - enum_emu_snr [2024-Jun-06 16:33:46] [trace] [ Client] - Command enum_emu_con_info executed for 15 milliseconds with result 0 [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - enum_emu_snr [2024-Jun-06 16:33:46] [trace] [ Worker] - Command config executed for 14 milliseconds with result 0 [2024-Jun-06 16:33:46] [debug] [ nRFXX] - enum_emu_con_info [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - is_connected_to_emu [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - enum_emu_con_info [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - is_connected_to_emu [2024-Jun-06 16:33:46] [trace] [ Worker] - Command enum_emu_con_info executed for 4 milliseconds with result 0 [2024-Jun-06 16:33:46] [debug] [ nRFXX] - close [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - is_connected_to_emu [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - close [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - disconnect_from_emu [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - is_connected_to_emu [2024-Jun-06 16:33:46] [debug] [SeggerBackend] - Segger Backend closed. [2024-Jun-06 16:33:46] [debug] [ nRFXX] - nRF family DLL closed [2024-Jun-06 16:33:46] [trace] [ Worker] - Command close executed for 31 milliseconds with result 0 [2024-Jun-06 16:33:46] [trace] [ Client] - Command close executed for 49 milliseconds with result 0 [2024-Jun-06 16:33:46] [debug] [ Client] - terminate [2024-Jun-06 16:33:46] [trace] [ Client] - Command terminate executed for 0 milliseconds with result 0 [2024-Jun-06 16:33:46] [trace] [ Worker] - Command terminate executed for 0 milliseconds with result 0 [2024-Jun-06 16:33:46] [trace] [ Worker] - Executed 5 commands for 54 milliseconds [2024-Jun-06 16:33:46] [debug] [ Client] - Worker process exited with code: 0 [2024-Jun-06 16:33:46] [debug] [ Client] - Worker process exited with code: 0 [2024-Jun-06 16:33:46] [debug] [ Client] - Child process terminated with result 0 [2024-Jun-06 16:33:46] [trace] [ Client] - Executed 5 commands for 134 milliseconds [2024-Jun-06 16:33:46] [debug] [ Client] - terminate
When I try to use the Programmer from the nRF Connect for Desktop, I get the following error:
[PID:3308] [jlink] [NRFJPROG][Client][001050015604] Encountered error -13: Command connect_to_emu_with_snr executed for 15 milliseconds with result -13
[PID:3308] [jlink] [NRFJPROG][Worker][001050015604] Cannot call connect_to_emu_without_snr when there is no emulator connected.
[PID:3308] Error executing operations for 1050015604: [jlink] NO_EMULATOR_CONNECTED, code: Nrfjlink
Reading readback protection status for Application core
Failed to reading readback protection status for application core core. Error: [object Object], message: Batch task protection-get failed, [jlink] NO_EMULATOR_CONNECTED
[PID:3308] Error: Failed with exit code 1. One or more batch tasks failed: - [jlink] NO_EMULATOR_CONNECTED, code: Nrfjlink. Message: Batch task protection-get failed, [jlink] NO_EMULATOR_CONNECTED.
This is the full log output from the Programmer:
2024-06-06T14_38_08.532Z-log.txt
I already reinstalled nRF Connect for Desktop, and Jlink, but it didn't help.
Versions used:
nRF Connect for Desktop : v5.0.0
Programmer: v4.3.0
Jlink: V7.96a
nRF5340DK: 2.0.0
