Thingy91 does not show up in Programmer

[sv2k23]

I just got the Thingy91 today. I am trying to update the firmware in nRF52840 SoC.

As per developer.nordicsemi.com/.../thingy91_gsg.html),
1. I enabled the MCUboot in the Programmer.
2. I pressed SW4 while switching SW1 to ON position.

But I see the following
1. "Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device" message in the Programmer
2. The device keeps going through a loop of solid red, then switch off, then a quick green followed by the solid red.

I do not see the Thingy91 showing up in the programmer. So I am stuck at the very beginning. What is the issue here? Any help appreciated.

Thanks,
Surjit.

[Elias]

The Thingy91 does not show up in the programmer if you don't have the connectivity bridge installed. 
1. Download the newest firmware zip.

2. I had problems with the 64-bit version of nRF Connect for desktop, so I downloaded the 32 & 64 -bit version 4.0.1.

3. Enter the programmer from nRF Connect. Press SW4 while turning on the device (Should enter MCUBoot). Choose file: thingy91_nrf52_connectivity_bridge_2023-06-01_0677b099.hex, then write.

4. After written, turn off the thingy91, then press SW3 while turning on the device. Then choose mfw_nrf9160_1.3.4.zip. Then write. Now your thingy91 should have the newest firmware.

[sv2k23]

Also, the device doesn't show up as a COM port in Device Manager on my machine. Does that indicate some issue?

[Elias]

The "correct" connectivity bridge is in the folder img_fota_dfu_hex, not img_app_bl.

Is this "Unknown" from when you only use SW1 without SW4?

Does the device show up as MCUBoot when you hold SW4 while turning it on?
 

[sv2k23]

When I hold SW4 and turn on, the device still shows up as 'Unknown'. Programmer is set to 'Enable MCUBoot'. 

The device has never shown up as MCUBoot yet! 

[Menon]

Hello,

sv2k23 said:

Also, the device doesn't show up as a COM port in Device Manager on my machine. Does that indicate some issue?

Your thingy91 should be visible in the device manager. Can you change the USB cable you are using? Make sure the cable supports both power and data.

Try to use the USB port directly from the PC if you are using any USB hubs or sockets. Can you try connecting to another PC to make sure it's not an issue in the PC driver detecting the device?

Kind Regards,

Abhijith

 

[sv2k23]

Thank you! It looks like it was an issue with the USB cable being used. Once I changed it, I was able to program the Firmware and move ahead...