Failed to program the Network core on nRF5340DK

[ChristopherS]

Hi DevZone,

I am having trouble programming samples to my nRF5340DK.
I decided to try validating my issue by using the Quick Start application in nRF Connect for Desktop, and saw the following failure, where the step for flashing Network core fails for the Peripheral LBS and Peripheral UART services.

The corresponding log file contents:

2024-10-22T19:41:57.004Z INFO Initialising nrfutil module: device
2024-10-22T19:41:57.109Z DEBUG Started watching devices
2024-10-22T19:41:59.510Z INFO Using nrfutil-device core version: 7.13.0
2024-10-22T19:42:00.120Z INFO Using nrfutil-device version: 2.1.1
2024-10-22T19:42:00.121Z INFO Using nrf-device-lib version: 0.17.5
2024-10-22T19:42:00.121Z INFO Using nrfjprog DLL version: 10.24.0
2024-10-22T19:42:00.121Z INFO Using JLink version: JLink_V7.94e
2024-10-22T19:42:00.264Z DEBUG Selected device: nRF5340 DK
2024-10-22T19:42:00.278Z DEBUG Changed step: Info
2024-10-22T19:42:06.142Z DEBUG Changed step: Rename
2024-10-22T19:42:07.257Z DEBUG Changed step: Program
2024-10-22T19:42:14.659Z DEBUG Changed step: Verify
2024-10-22T19:42:17.666Z INFO Opened port with options: {"path":"COM4","baudRate":115200}
2024-10-22T19:42:19.166Z INFO Closed port: COM4
2024-10-22T19:42:22.643Z DEBUG Changed step: Program
2024-10-22T19:42:56.428Z DEBUG Changed step: Verify
2024-10-22T19:42:57.454Z DEBUG Changed step: Program
2024-10-22T19:43:05.400Z ERROR [jlink] [NRFJPROG][Client][001050097563] Encountered error -90: Command erase_file executed for 60 milliseconds with result -90
2024-10-22T19:43:05.401Z ERROR [jlink] [NRFJPROG][nRF53][001050097563] Failed while erasing device. -90: Access protection is enabled, can't erase memory.
2024-10-22T19:43:05.401Z ERROR [jlink] [NRFJPROG][Worker][001050097563] Access protection is enabled, can't erase memory.
2024-10-22T19:45:14.790Z ERROR [jlink] [NRFJPROG][Client][001050097563] Encountered error -90: Command erase_file executed for 47 milliseconds with result -90
2024-10-22T19:45:14.791Z ERROR [jlink] [NRFJPROG][nRF53][001050097563] Failed while erasing device. -90: Access protection is enabled, can't erase memory.
2024-10-22T19:45:14.791Z ERROR [jlink] [NRFJPROG][Worker][001050097563] Access protection is enabled, can't erase memory.

Not sure how access protection became enabled, as I used to be able to program various samples to the board.

`nrfjprog --recover` doesn't help.

Any ideas what to do? 

[ChristopherS]

For what it's worth, the logs for COM3 and COM4 when Serial Terminal is hooked up to 'Unknown' shows:

[Johnny Nguyen]

Can you try re-installing the j-link drivers found here? I haven't seen this issue persist between reboots before.

[Bruno Saraiva]

I have the absolutely same error. I can update the log's if the Nordic folks find them useful. I believe I already had a quite recent JLink driver, but reinstalled to V8.10d just in case, to no luck. PC OS is Win 11 64 with all the possible updates.

[Bruno Saraiva]

Exactly same problem here. Updated JLink drivers to no luck (they were already quite recent, last updated last week). PC OS is Windows 11 64.

`nrfjprog --recover --coprocessor CP_NETWORK` gives

Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.

`nrfjprog --recover`, gives the same output as above.

Log attached.

Fullscreen 2024-10-24T14_52_06.482Z-log.txt Download

2024-10-24T14:52:06.624Z INFO Initialising nrfutil module: device
2024-10-24T14:52:06.630Z DEBUG Started watching devices
2024-10-24T14:52:07.870Z INFO Using nrfutil-device core version: 7.13.0
2024-10-24T14:52:08.435Z INFO Using nrfutil-device version: 2.1.1
2024-10-24T14:52:08.435Z INFO Using nrf-device-lib version: 0.17.5
2024-10-24T14:52:08.435Z INFO Using nrfjprog DLL version: 10.24.0
2024-10-24T14:52:08.435Z INFO Using JLink version: JLink_V7.94e
2024-10-24T14:52:14.317Z DEBUG Selected device: nRF5340 DK
2024-10-24T14:52:14.334Z DEBUG Changed step: Info
2024-10-24T14:52:20.811Z DEBUG Changed step: Rename
2024-10-24T14:52:39.430Z DEBUG Changed step: Program
2024-10-24T14:52:50.786Z ERROR [jlink] [NRFJPROG][nRF53][001050007419] Failed while erasing device. -90: Access protection is enabled, can't erase memory.
2024-10-24T14:52:50.786Z ERROR [jlink] [NRFJPROG][Worker][001050007419] Access protection is enabled, can't erase memory.
2024-10-24T14:52:50.787Z ERROR [jlink] [NRFJPROG][Client][001050007419] Encountered error -90: Command erase_file executed for 48 milliseconds with result -90
2024-10-24T14:55:50.717Z ERROR [jlink] [NRFJPROG][Client][001050007419] Encountered error -90: Command erase_file executed for 47 milliseconds with result -90
2024-10-24T14:55:50.732Z ERROR [jlink] [NRFJPROG][nRF53][001050007419] Failed while erasing device. -90: Access protection is enabled, can't erase memory.
2024-10-24T14:55:50.732Z ERROR [jlink] [NRFJPROG][Worker][001050007419] Access protection is enabled, can't erase memory.
2024-10-24T15:00:09.715Z DEBUG Changed step: Rename
2024-10-24T15:00:11.783Z DEBUG Changed step: Info
2024-10-24T15:00:14.046Z DEBUG Changed step: Connect
2024-10-24T15:00:31.734Z DEBUG Selected device: nRF5340 DK
2024-10-24T15:00:31.739Z DEBUG Changed step: Info
2024-10-24T15:00:32.909Z DEBUG Changed step: Rename
2024-10-24T15:00:40.430Z DEBUG Changed step: Program
2024-10-24T15:01:22.834Z ERROR [jlink] [NRFJPROG][JLink][001050007419] Communication timed out: Requested 8 bytes, received 0 bytes !
2024-10-24T15:01:22.834Z ERROR [jlink] [NRFJPROG][Worker][001050007419] An unknown error.
2024-10-24T15:01:22.849Z ERROR [jlink] [NRFJPROG][Client][001050007419] Encountered error -105: Command erase_file executed for 47 milliseconds with result -105
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3139.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3686.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3493.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3526.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3567.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3526.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3567.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3526.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3567.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3526.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3567.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3526.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3567.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3526.
2024-10-24T15:01:22.865Z ERROR [jlink] [NRFJPROG][SeggerBackend][001050007419] JLinkARM.dll reported error -256 at line 3567.
2024-10-24T15:01:30.352Z ERROR [jlink] [NRFJPROG][Client][001050007419] Encountered error -90: Command erase_file executed for 47 milliseconds with result -90
2024-10-24T15:01:30.353Z ERROR [jlink] [NRFJPROG][nRF53][001050007419] Failed while erasing device. -90: Access protection is enabled, can't erase memory.
2024-10-24T15:01:30.353Z ERROR [jlink] [NRFJPROG][Worker][001050007419] Access protection is enabled, can't erase memory.

[ChristopherS]

For some reason, a BLE headset (soundcore Q20i) that I had connected to my Windows 11 PC seemed to be causing my issue.

After removing that headset, the phantom 'Unknown' device went away, and I was able to program applications to the DK