MCUBoot says Thingy:91 broken USB descriptor and broken CDC UART

[torgil]

When trying to update the connectivity bridge I get this error message:

This show right after power on while holding SW4. Same thing on two different devices. Label on device says 1.4.0 and 2020.24.

Using freshly installed nrf Connect with programmer 3.0.9 on Mac M1.

Also tried on Windows 11. The error message above does not show but MCUBoot flashing result in timeout.

[Didrik Rokhaug]

Hi,

Do you have a DK (nRF9160, nRF7002, nRF5340 or any of the nRF52 variants) or an external programmer that you can use to program the nRF52840 on the Thingy:91?

See the "Through external debug probe" part of the documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.0/nrf/working_with_nrf/nrf91/thingy91_gsg.html#updating-the-firmware-in-the-nrf52840-soc

Best regards,

Didrik

[torgil]

Hi,

Now I've updated my two Thingy:91 using a nRF9160 DK and it works ok. Modem shows latest fw, application is updated and no error when updating connectivity bridge.

But after updating connectivity bridge, modem fw and application to latest available I'm still not able to update application using MCUBoot. 

I've tried both devices on both Windows and Mac. Same error message.

Full log:

2023-09-02T06:38:06.322Z INFO Getting serialport options from persistent store THINGY91_E7C0FE20A430.pc-nrfconnect-programmer
2023-09-02T06:38:06.598Z INFO Getting serialport options from persistent store THINGY91_E7C0FE20A430.pc-nrfconnect-programmer
2023-09-02T06:38:07.338Z INFO Getting serialport options from persistent store THINGY91_E7C0FE20A430.pc-nrfconnect-programmer
2023-09-02T06:38:29.566Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"mcuboot"}
2023-09-02T06:38:29.582Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF91_FAMILY"}
2023-09-02T06:38:29.585Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"Thingy91"}
2023-09-02T06:38:29.588Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA20035"}
2023-09-02T06:38:29.592Z INFO Update files regions according to Application core
2023-09-02T06:38:29.593Z INFO Parse memory regions for file
2023-09-02T06:38:36.215Z INFO Does not need to be reloaded: /Users/torgil/Downloads/thingy91_fw_2023-06-01_0677b099/img_fota_dfu_hex/thingy91_serial_lte_modem_2023-06-01_0677b099.hex
2023-09-02T06:38:37.813Z INFO Writing /Users/torgil/Downloads/thingy91_fw_2023-06-01_0677b099/img_fota_dfu_hex/thingy91_serial_lte_modem_2023-06-01_0677b099.hex to device THINGY91_E7C0FE20A430
2023-09-02T06:38:58.747Z ERROR MCUboot DFU failed with error: async task failure for id: 956706714652 msg: [mcuBoot] Error when programming through MCUBoot: Error verifying MCUBoot image prior to update. Error code: 603 (Timeout). (Origin: "Error when running device operation program")
2023-09-02T06:38:58.748Z ERROR Please make sure that the device is in MCUboot mode and try again.
2023-09-02T06:39:13.728Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Close device","label":""}
2023-09-02T06:39:13.770Z INFO Target device closed

Any ideas? Update application fw during development using MCUBoot would really make things a lot easier during development compared to connecting to DK board.