nrf5340-DK suddenly stopped flashing

RE: nrf5340-DK suddenly stopped flashing

Maria Gilje — Tue, 24 Jan 2023 14:38:48 GMT

Hello Maxime,

Good that you found a solution.

Keep in mind that the same problem can arise if your DK is missing the components necessary for DCDC to be enabled. If you want us to check this, we will need a high-resolution image of your DK.

Have a nice day!

RE: nrf5340-DK suddenly stopped flashing

MaximeCharriere — Tue, 24 Jan 2023 12:05:44 GMT

I was able to solve the problem by unsoldering and soldering a new nRF5340 chip and that solved the problem. Maybe there was a problem with the chip.

Best regards,

Maxime

RE: nrf5340-DK suddenly stopped flashing

Maria Gilje — Tue, 24 Jan 2023 11:50:58 GMT

Hello,

This issue looks like something that happens when the hardware does not support DCDC. Our DKs has this support, so it is strange that you are experiencing this fault.

Please upload a high-resolution image of your DK, so we can verify if all the components needed are present.

Kind Regards,
Maria

RE: nrf5340-DK suddenly stopped flashing

MaximeCharriere — Mon, 23 Jan 2023 07:08:50 GMT

The "--recover" command does not work in any order. This is what I get:

[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
Recovering device. This operation might take 30s.
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  JLink] - Not supported by current CPU + target interface combination.
[error] [SeggerBackend] - JLinkARM.dll reported "-2", "An unknown error.".
[error] [  nRF53] - Failed while checking eraseprotect status.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

The log is exactly the same as in my first message.

RE: nrf5340-DK suddenly stopped flashing

Maria Gilje — Tue, 17 Jan 2023 14:40:49 GMT

My bad, I wrote the commands in the wrong order in my last reply.

Recover the network core before recovering the application core.

If you still get errors, please share your log.

Also, very sorry for the delay.

Kind Regards,
Maria

RE: nrf5340-DK suddenly stopped flashing

MaximeCharriere — Tue, 10 Jan 2023 09:16:44 GMT

Hello,

Yes i tried, without success unfortunately

RE: nrf5340-DK suddenly stopped flashing

Maria Gilje — Tue, 10 Jan 2023 09:15:22 GMT

Hi Maxime,

I apologize for the delay on this. I am currently looking for a possible cause.

Can you please check if you are able to run both commands below:

nrfjprog --recover

nrfjprog --recover --coprocessor CP_NETWORK

Successful commands will recover both cores. You can try to program the board again after.

Kind Regards,
Maria

RE: nrf5340-DK suddenly stopped flashing

MaximeCharriere — Fri, 06 Jan 2023 08:26:21 GMT

Update : after 1 hour where I try to reprogram multiple times, it seems that J-Link discovered again my nRF5340 and told me that it was inaccessible because of the readback protection, I used recover, but without success. Here is what I got.

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\nordic\myapps\hello_world\build\zephyr\zephyr.hex
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
ERROR: runners.nrfjprog: Flashing failed because the target must be recovered.
To fix, run "west flash --recover" instead.
Note: your target is an nRF53; all flash memory for both the network and application cores will be erased prior to reflashing.
FATAL ERROR: command exited with status 16: nrfjprog --program 'c:\nordic\myapps\hello_world\build\zephyr\zephyr.hex' --sectorerase --verify -f NRF53 --snr 1050086439 --coprocessor CP_APPLICATION

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

* Executing task: nRF Connect: Flash: hello_world/build (active)

Flashing build to 1050086439
west flash -d c:\nordic\myapps\hello_world\build --skip-rebuild -r nrfjprog --dev-id 1050086439 --recover

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Recovering and erasing flash memory for both the network and application cores.
[error] [ nRF53] - Application core access protection is enabled, can't enable coprocessor.
Recovering device. This operation might take 30s.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 62: nrfjprog --recover -f NRF53 --coprocessor CP_NETWORK --snr 1050086439

After that, I was in the same state than before again (as first message)