Flashing Firmware on Thingy:91 X

[Ronald]

I've installed Visual Studio Code and nrfutil and nRF Connect and J-Link and managed to compile Blinky and flash the Thingy:91 X using the terminal:

./nrfutil device program --firmware build\dfu_application.zip --serial-number xxxxxxxxxxxxxx --traits mcuboot --x-family nrf91 --core Application

Now, however, the two com ports don't show up again, and if I try powering up as mcuboot com port, I get errors:

[00:00:00] ------ 0% [xxxxxxxxxxxxxxxxxx] Failed, [mcuBoot] Manifest does not contain supported SoC for multi-image update
Error: One or more program tasks failed:
* xxxxxxxxxxxxxxxxx: [mcuBoot] Manifest does not contain supported SoC for multi-image update (Argument)

If I try and just program a .hex file I get:

 [mcuBoot] Programming of Thingy:91 X requires a target when firmware is in HEX or BIN format. (Argument)

...and nRF Connect "Quick Start" doesn't see the board now

https://hello.nrfcloud.com/device/ still connects and interacts with the device ok

Please give me a hint on how to get my board back to square one........

Scott

[Ronald]

Nevermind, I solved it using an external debugger.

[Minsteur]

I get the same issue as you but with unstable COM port detection, it's not a normal way to use an external debugger as workaround.

I found this link USB UART on the Thingy:91 X · Daniel Mangum where the guy offer to flash the Thingy91X with the connectivity bridge to solve this issue but as the device is not yet detected to program the code ... it's a vicious circle !!

[Ronald]

I figured out that I broke it when I selected the incorrect target in the VS code build configuration.  I luckily happened to have a J-Link debugger board with the correct tiny connector on ribbon cable to use and VS connected to it nicely.

[Minsteur]

Ok.. what is the name of your board ?

[Ronald]

1. Segger Microcontroller programmer 8.08.91 J-LINK EDU MINI - mouser has it and SparkFun has the cable CAB-15364