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

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

JB_Teufel — Wed, 04 Aug 2021 14:01:36 GMT

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.

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

Vidar Berg — Wed, 04 Aug 2021 13:24:33 GMT

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)

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

JB_Teufel — Wed, 04 Aug 2021 13:08:00 GMT

At the moment, I've got J-Link version 7.52 installed, along with the 7.50 version installed by nrfjprog. Both of these versions were 64-bit, it turns out. Installing the 32-bit version of 7.50 puts the dll on nrfjprog's search path, which resolves that issue.

At the moment, it looks like I can connect to the IC, but programming the network core is failing in both the nRF Connect programmer and nrfjprog. Log files are attached for both tools. I've also confirmed that I can write to both cores using J-link Commander without major issue (had to reduce the interface speed to 2000 kHz).

devzone.nordicsemi.com/.../27841.log.log

devzone.nordicsemi.com/.../2021_2D00_08_2D00_04T12_5F00_51_5F00_52.603Z_2D00_log.txt

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

Vidar Berg — Wed, 04 Aug 2021 12:47:04 GMT

Which version of Jlink did you install? I need to try and see if I can replicate this here.

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

JB_Teufel — Wed, 04 Aug 2021 11:41:33 GMT

nrfjprog is having trouble finding the correct DLL. If I run nrfjprog -v, I get the "ERROR: JLinkARM DLL is invalid. Please reinstall latest JLinkARM DLL.". I can work around that by using the -jdll argument, but I'm not sure it's working correctly. I was able to successfully erase the memory, but programming it again with the same bitfile doesn't seem to do anything.

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

Vidar Berg — Wed, 04 Aug 2021 11:03:45 GMT

Hello,

The BLE app in nRF connect for desktop does not support the nRF53 series, so the last error is as expected. However, I'm not sure why you get the programming error, could be a compatibility issue like you said. Logs shows indicates that the PC has problems communicating with the debugger (more common to have communication issues between jlink and target) Can you try to our command line tool nrfjprog for programming and see if you get the same result?

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

JB_Teufel — Wed, 04 Aug 2021 10:14:35 GMT

nRF Connect BLE log, as well, as it looks like it may be a bit more informative:
devzone.nordicsemi.com/.../2021_2D00_08_2D00_04T10_5F00_12_5F00_05.567Z_2D00_log.txt