NRF53 programming by using nrfjprog-Q

[Steven Wen]

Here is my script for programming. Does the sequence is OK? or any advice to improve? 

nrfjprog --eraseall

nrfjprog --recover --family NRF53 --coprocessor CP_APPLICATION
nrfjprog --recover --family NRF53 --coprocessor CP_NETWORK
nrfjprog --qspieraseall

nrfjprog --recover --family NRF53 --coprocessor CP_APPLICATION
nrfjprog --recover --family NRF53 --coprocessor CP_NETWORK
nrfjprog --recover --family NRF53 --coprocessor CP_NETWORK --program B1_net.hex --verify

nrfjprog --pinreset --family NRF53 --coprocessor CP_NETWORK
nrfjprog --pinreset --family NRF53 --coprocessor CP_APPLICATION

nrfjprog --recover --family NRF53 --coprocessor CP_APPLICATION
nrfjprog --recover --family NRF53 --coprocessor CP_APPLICATION --program B2_app.hex --verify

nrfjprog --pinreset --family NRF53 --coprocessor CP_NETWORK
nrfjprog --pinreset --family NRF53 --coprocessor CP_APPLICATION

[SwRa]

Hi Steven,

It is not a problem with your command syntax, but rather with the device state or debug interface readiness. The error from the log indicates that the tool was unable to communicate properly with the target device. This is commonly caused when the device is in a blank or protected state or when access protection or readback protection is enabled. Sometimes, the J-Link or the target device may not be ready, especially right after a reset or power cycle. This might also be the reason.

As you have noticed, simply retrying the recover command works. Ensure your J-Link or debugger is properly connected and recognized by your system. Also, always recover the Network core first, then the Application core. Recovering the Application core first can lead to issues, as the Network core recovery erases both cores.

Regards,

Swathy