Cannot flash Thingy91x

RE: Cannot flash Thingy91x

Peter Murphy — Fri, 09 May 2025 18:28:16 GMT

Hi MJJ,

Yes, I was able to program the nRF5340 with the connectivity bridge.

Thank you.

Peter

RE: Cannot flash Thingy91x

MJJ — Fri, 09 May 2025 16:57:22 GMT

The output shows network and application cores as recovered so are you now able to program the nRF5340 with the connectivity bridge?

RE: Cannot flash Thingy91x

Peter Murphy — Thu, 08 May 2025 04:36:10 GMT

Hi MJJ,

Here are the results of running the commands:

peter@peter-HP-ProBook-450-G3:~$ nrfjprog --version
nrfjprog version: 10.24.2 external
JLinkARM.dll version: 8.1

peter@peter-HP-ProBook-450-G3:~$ nrfjprog --deviceversion
960042162 - NRF5340_xxAA_REV1

peter@peter-HP-ProBook-450-G3:~$ nrfjprog --recover -f nrf53
Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 3 milliseconds with result -21
[error] [ Worker] - Eraseprotect is enabled and readback protection setting is ALL, can't recover device.
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.

peter@peter-HP-ProBook-450-G3:~$ nrfutil --version
nrfutil 8.0.0 (54d8087 2025-01-07)
commit-hash: 54d8087a38b73b6e56942fb1b024b62365f06731
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
build-timestamp: 2025-01-07T14:26:42.070728557Z
classification: nrf-external

peter@peter-HP-ProBook-450-G3:~$ nrfutil device recover --core Network
✔️ Recovered 960042162

peter@peter-HP-ProBook-450-G3:~$ nrfutil device recover --core Application
✔️ Recovered 960042162

Regards,

Peter

RE: Cannot flash Thingy91x

MJJ — Wed, 07 May 2025 22:15:49 GMT

Does this command work: .\nrfjprog.exe --recover -f nrf53

If not, can you try:

nrfutil.exe device recover --core Network

nrfutil.exe device recover --core Application

RE: Cannot flash Thingy91x

Peter Murphy — Wed, 07 May 2025 17:11:43 GMT

Hi Dejan,

Below are the results of trying to flash the connectivity bridge.

peter@peter-HP-ProBook-450-G3:~$ nrfjprog --version
nrfjprog version: 10.24.2 external
JLinkARM.dll version: 8.14

peter@peter-HP-ProBook-450-G3:~$ nrfjprog --deviceversion
960042162 - NRF5340_xxAA_REV1

peter@peter-HP-ProBook-450-G3:~$ nrfjprog --chiperase --verify --program merged.hex
[error] [ Client] - Encountered error -90: Command read_memory_descriptors executed for 0 milliseconds with result -90
[error] [ Worker] - Can't read memory descriptors, ap-protection is enabled.
[error] [ Client] - Encountered error -90: Command erase_file executed for 88 milliseconds with result -90
[error] [ nRF53] - Failed while erasing device. -90: Access protection is enabled, can't read block protection state.
[error] [ Worker] - Access protection is enabled, can't read block protection state.
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.

peter@peter-HP-ProBook-450-G3:~$ nrfjprog --chiperase --verify --log --program merged.hex
[error] [ Client] - Encountered error -90: Command read_memory_descriptors executed for 0 milliseconds with result -90
[error] [ Worker] - Can't read memory descriptors, ap-protection is enabled.
[error] [ Client] - Encountered error -90: Command erase_file executed for 63 milliseconds with result -90
[error] [ nRF53] - Failed while erasing device. -90: Access protection is enabled, can't read block protection state.
[error] [ Worker] - Access protection is enabled, can't read block protection state.
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.

Regards,

Peter

RE: Cannot flash Thingy91x

dejans — Tue, 06 May 2025 12:58:16 GMT

Hi,

[quote user=""]peter@peter-HP-ProBook-450-G3:~$ nrfjprog --recover -f nrf52
Recovering device. This operation might take 30s.
[error] [ Client] - Encountered error -21: Command recover executed for 1 milliseconds with result -21
[error] [ Worker] - Encountered unexpected debug port ID 6, expected 2
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.[/quote]

This might be just a typo, but you are recovering nrf52 instead of nrf53.
If you suspect that your firmware on nrf5340 got overwritten, you could try to re-flash connectivity bridge.

Best regards,
Dejan