Failed to program thingy91x

[ToTo42]

Hello,

I recently bought a Thingy91x; before that, I was using a Thingy91. I activated it and successfully programmed the Hello nRF Cloud firmware via the Quick Start in nRF Connect. It worked perfectly. Then, I wanted to program it using the VS Code project, but out of habit, I loaded the Asset Tracker v2 project for the Thingy91 and programmed the nRF5340.

Since then, I’ve been unable to reprogram it using either nRF Connect or VS Code — even when using the correct project this time. I get the following error messages:

On nRF Connect:
Failed to program the Application core.
Contact support on DevZone and provide the Log if the problem persists.

On VS Code (v2.9.1) following the guide hello-nrfcloud.github.io/.../gsg_guide.html :

C:\dev\firmwares\hello-nrfcloud\project> west thingy91x-dfu
Trying to put nRF91 in bootloader mode...
nrf91 on THINGY91X_XX is in bootloader mode
[00:00:20] ###### 100% [4/4 THINGY91X_XX] Failed, Error when programming through MCUBoot: Unable to program mu
Error: One or more program tasks failed:
* THINGY91X_XX: Error when programming through MCUBoot: Unable to program multi-image file from file 'build/dfu_application.zip'. Error code: 603 (Timeout). (McubootTimeout)

Do I have a chance to recover my device?

Thanks in advance

 

[ToTo42]

I've tried on Ubuntu, with the hello-nrfcloud firmware, thingy91x is flashed by a nrf5240dk:

-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
Using board 001050240536
-- runners.nrfutil: Flashing file: /home/sylvain/dev/firmwares/recover/hello-nrfcloud/project/build/merged.hex
Error: One or more batch tasks failed:
* 1050240536: Device error: QSPI is not a valid peripheral option for external flash programming (Generic)

FATAL ERROR: command exited with status 1: nrfutil --json device x-execute-batch --batch-path /home/sylvain/dev/firmwares/recover/hello-nrfcloud/project/build/generated_nrfutil_batch.json --serial-number 1050240536

[Øyvind]

Hello,

ToTo42 said:

I've tried on Ubuntu, with the hello-nrfcloud firmware, thingy91x is flashed by a nrf5240dk:

The nRF52840DK is not compliant with the Thingy:91 X. Neither the nRF9151 nor nRF5340 are supported by the onboard debugger of the nRF52840DK. This is due to these devices being Arm Cortex-M33.

Then, I wanted to program it using the VS Code project, but out of habit, I loaded the Asset Tracker v2 project for the Thingy91 and programmed the nRF5340.

Did you program the nRF5340 with the Asset Tracker? If so, you will need to reprogram the nRF5340 with the thingy91x_nrf53_connectivity_bridge_v2.0.1 image, found in the Precompiled application and modem firmware package.

Kind regards,
Øyvind

[ToTo42]

Okay I tried with a nrf7002dk as debugger and I have this:

nrfutil device program --firmware thingy91x_nrf53_connectivity_bridge_v2.0.1.hex --serial-number 1050744317
[00:00:00] ###### 100% [1/2 1050744317] Failed, Device error: Address range 0x01000000..0x01005634 is not covered by any known memory region
Error: One or more program tasks failed:
* 1050744317: Device error: Address range 0x01000000..0x01005634 is not covered by any known memory region (Generic)

Thingy 91X is powered and switch is on nRF53 

[Øyvind]

Hello, apologies for the late reply. I will have a look at this today and get back to you within end of day.

Kind regards,
Øyvind

[Øyvind]

Are you able to program the device using the programmer app in nRF Connect for Desktop?

[ToTo42]

No I have this:

[Øyvind]

Are you using the nRF7002DK when programming the Thingy;:91 X in the programmer application? If so, please use the .hex file from the precompiled package. This should should restore the connectivity bridge.

Can you also please share the logs from the programmer app after doing the steps above?

Kind regards,
Øyvind