Cannot update firmware on Thingy:91 using nRF Connect v3.4.1 - Programmer on Windows 10

[sab]

I've tried to update the firmware on my Thingy:91 to version 1.2 using the file mfw:_nrf91060120.zip:

1. I set the Thingy:91 to 'application serial recovery mode by pushing the SW3 button while powering on to update the nRF9160 modem'.
2. The Thingy:91 goes into this mode (the blue LED does NOT flash).
3. I have the "Enable MCUboot" checkbox checked in nRF Connect Programmer. v3.4.1 on Windows 10.
4. I click on 'Update modem' and provide it the file: mwf_nrf9160_1.2.0.zip.
5. I receive the error message: 'Please make sure the device is in MCUboot mode and try again'
6. The Thingy:91 starts flashing the blue LED.

I've done this repeatedly to no avail.

As an FYI, when I check the firmware version using AT+CGMR in LTE Link Monitor, it reports: mfw_nrf9160_1.1.0

Please see screenshot below.

Thanks,

Sanjay

[Øyvind]

Hello, 

Have you tried to update the application using a precompiled FW first? I will talk to our Thingy:91 team.

Kind regards,
Øyvind

[sab]

Hi Oyvind,

Thank you for your reply.

I'm not sure exactly what you mean by 'precompiled FW'.

When I clicked on the link you provided, it eventually took me to the file: thingy91_fw_2020-04-29_bc7ade8b.zip. Inside this file is the modem firmware file: mfwnrf9160120.zip. Isn't this zip file the precompiled FW?

Perhaps you thought I was trying to update my Thingy:91 with a new application file? I'm actually just trying to update the modem firmware.

Thanks,

Sanjay

[Øyvind]

sab said:

Isn't this zip file the precompiled FW?

 No, the  thingy91_fw_2020-04-29_bc7ade8b.zip is the precompiled FW folder, while the mfwnrf9160120.zip is the modem FW (mfw).

[sab]

The key point is that even though I am using the correct modem fw (mfwnrf9160120.zip),  I keep receiving the error message :"Please make sure the device is in MCUboot mode and try again".

And, the Thingy:91 is in MCUboot mode because the blue LED is OFF.

That is the problem. It is not clear to me how to resolve this problem. Is there a workaround?

[Øyvind]

Hello, 

I've been investigating, and this issue seems to a driver issue in Windows which incompatible with your current version of MCUboot on the device. The only workaround at the moment is to program the modem using an external debug probe and/or update the MCUboot in a similar manner, programming the application with an external debug probe.

Kind regards,
Øyvind