nRF Connect Programmer not able to probe devices after updating J-Link drivers

[JB_Teufel]

Hi.  I'm working on several projects, some of which are not using Nordic chips.  I installed the latest Segger J-Link drivers to support a different project.  I believe this up-revved the drivers included with the nRF Connect Programmer.  It looks like the update has caused the nRF Connect Programmer to fail, however, as I can't talk to the nRF5340 Audio DK.  How may I get both pieces of software to co-exist harmoniously?  Logs and system report attached.

Fullscreen 2021-08-04T10_03_23.621Z-log.txt Download

2021-08-04T10:03:24.174Z INFO Application data folder: C:\Users\Jason.Bens\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-08-04T10:03:24.301Z DEBUG App pc-nrfconnect-programmer v1.4.11 official
2021-08-04T10:03:24.301Z DEBUG App path: C:\Users\Jason.Bens\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-08-04T10:03:24.301Z DEBUG nRFConnect 3.7.0, required by the app is (^3.6.0)
2021-08-04T10:03:24.301Z DEBUG nRFConnect path: C:\Users\Jason.Bens\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-08-04T10:03:24.302Z DEBUG HomeDir: C:\Users\Jason.Bens
2021-08-04T10:03:24.302Z DEBUG TmpDir: C:\Users\JASON~1.BEN\AppData\Local\Temp
2021-08-04T10:03:24.315Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-08-04T10:03:25.175Z ERROR Error while probing devices: Error occured when get serial numbers. Errorcode: CouldNotCallFunction (0x9)
Lowlevel error: INVALID_OPERATION (fffffffe)

2021-08-04T10:05:29.161Z INFO Using nrfjprog to communicate with target
2021-08-04T10:05:29.164Z ERROR Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: INVALID_OPERATION (fffffffe)

2021-08-04T10:05:36.635Z INFO Generating system report...
2021-08-04T10:05:55.979Z INFO System report: C:\Users\Jason.Bens\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer\nrfconnect-system-report-2021-08-04T10-05-36.635Z.txt

Fullscreen nrfconnect-system-report-2021-08-04T10-05-36.635Z.txt Download

# nRFConnect System Report - 2021-08-04T10-05-36.635Z

- System:     Dell Inc. Precision 3560
- BIOS:       Dell Inc. DELL   - 2
- CPU:        1 x 11th Gen Intel® Core™ i7-1165G7 2.8 GHz 8 cores (4 physical)
- Memory:     9 GB free of 15.7 GB total
- Filesystem: C: (NTFS) 476.3 GB 24.7% used

- OS:         Microsoft Windows 10 Enterprise (10.0.19042) win32 ia32

- Versions
    - kernel: 10.0.19042
    - git: 2.32.0.windows.1
    - node: 12.13.0
    - python: 3.9.5
    - python3: 

- Connected devices:
    - COM19: 000960374295 

[Vidar Berg]

Interesting. I guess you installed the 32-bit version of nrfjprog. But have you tried to unlock the network core by running nrfjprog --recover first?

nrfjprog --recover --coprocessor CP_NETWORK
nrfjprog --recover

Note

Make sure to recover the network core before you recover the application core.

The --recover command erases the flash memory and then writes a small binary into the recovered flash memory. This binary prevents the readback protection from enabling itself again after a pin reset or power cycle.

Recovering the network core erases the flash memory of both cores. Recovering the application core erases only the flash memory of the application core. Therefore, you must recover the network core first. Otherwise, if you recover the application core first and the network core last, the binary written to the application core is deleted and readback protection is enabled again after a reset. (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html#readback-protection)

[JB_Teufel]

Ah, I wasn't aware of that behaviour.  Using nrfjprog to recover in the order you've specified, then writing to the network core, then finally the app core seems to work fine.  In the same vein, the nRF Connect Programmer also succeeds if I separately write to the network core, then to the app core.  That's good enough for me.  Thanks for your help.