nRF9151 doesn't flash anymore

Hello I'm working on a nRF9151 DK using nRF Connect plugin for VC.

I was able to program and run my  without any problem... but then suddenly the flash process stopped to work. 

On VC console I get: 

-- west flash: rebuilding
[0/5] Performing build step for 'dtls_upload'
[0/14] Performing build step for 'tfm'
ninja: no work to do.
[4/5] cmd.exe /C "cd /D C:\ncs\MyApp\dtls_upload\build\_sysbuild && C:\ncs\toolchains\b8b84efebd\opt\bin\cmake.exe -E true"
-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: C:\ncs\MyApp\dtls_upload\build\merged.hex
Error: One or more batch tasks failed:
 * 1051290792: Timed out waiting for response from worker. (Generic)

FATAL ERROR: command exited with status 1: nrfutil --json device x-execute-batch --batch-path 'C:\ncs\MyApp\dtls_upload\build\generated_nrfutil_batch.json' --serial-number 1051290792

 *  The terminal process terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

I tried to reset the status using  nRF Connect Desktop -> Programmer -> reset but the status of nRF9151 seems to be unrecoverable:

 

06:52:43.602	Initialising the bundled nrfutil device
06:52:43.736	Using the bundled core version for nrfutil device: 8.0.0
06:52:43.769	Using nrfutil-device version: 2.12.3
06:52:43.769	Using nrf-device-lib version: 0.17.81
06:52:43.769	Using nrf-probe version: 0.40.1
06:52:43.769	Using JLink version: JLink_V8.84
06:52:43.770	Your version of SEGGER J-Link (8.84) is newer than the one this app was tested with (8.18). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
06:52:43.782	Getting serial port options from the persistent store for 001051290792.pc-nrfconnect-programmer
06:52:43.782	Device connected with the serial number 001051290792
06:52:46.031	Selecting device with the serial number 001051290792
06:53:00.383	Error: Failed with exit code 1. One or more device info tasks failed: * 1051290792: Timed out waiting for response from worker. (Generic) Message: Operation device-info failed, Timed out waiting for response from worker.
06:53:00.383	Selected device with the serial number 001051290792
06:53:00.383	Using nrfutil device to communicate with target via JLink
06:53:03.334	Device connected with the serial number 001051290792
06:53:03.509	Error: Failed with exit code 1. One or more device info tasks failed: * 1051290792: Timed out waiting for response from worker. (Generic) Message: Operation device-info failed, Timed out waiting for response from worker.
06:53:03.588	Reading readback protection status for Application core
06:53:03.588	Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, Emulator error: Failed to open connection
06:53:03.596	Error: Failed with exit code 1. One or more batch tasks failed: * 1051290792: Emulator error: Failed to open connection (Generic) Message: Batch task protection-get failed, Emulator error: Failed to open connection.
06:53:03.596	Error: Failed with exit code 1. One or more batch tasks failed: * 1051290792: Emulator error: Failed to open connection (Generic) Message: Batch task protection-get failed, Emulator error: Failed to open connection.
06:53:03.702	Error: Failed with exit code 1. No devices with requested serial number(s) or trait(s) found
06:53:04.283	Getting serial port options from the persistent store for 001051290792.pc-nrfconnect-programmer
06:53:04.283	Device connected with the serial number 001051290792

Please, help me to come out form this blocking status.

Thanks, Joel

Parents Reply
  • Does it now successfully recover the board from the command line, or are you still seeing these "Timed out waiting for response from worker" errors?

    If it's just the VS Code nRF Connect SDK extension that doesn't show the connected board, you can try to close VS Code and reopen it to see if you get any pop-ups about updates of the extension. Alternatively try to uninstall and reinstall the extension?

    Best regards,

    Simon

Children
Related