Can't get started with Thingy:91 // MCUboot flash of modem firmware fails

Question

Hello everyone, 
 I wanted to start with Thingy:91 today, so I first wanted to update the device with the newest firmware. 
 First thing I found confusing is: On the Getting Started Tab of the product site , right above the Video there is a sentence: "To ensure optimal functionality, please update the nRF52840 SoC FW, the nRF9160 SiP modem FW and then the nRF9160 SiP app FW in that order." But when I follow along the video and/or read the docu ( here and here ) it seems there is no need to update the firmware of this 3 modules on there own, it seems now it is all together, maybe you should remove this sentence or maybe I had gotten something wrong? But this is not the point of my post, I tried to update the modem firmware of the thingy:91 and ran in a problem others mention here in devzone before, the Update fails with the following message: 
 I have pressed SW3 and then switched on the Thingy:91, at the first try(s) I only pressed SW3 until the device was available in the nRF Connect Programmer, later on I pressed it during the whole upgrade process, both failed. Also the Enable MCUboot was checked all the time. I am using: nRF Connect for Desktop v3.6.1 
 nRF Connect Programmer v1.4.8 
 macOS 10.15.7 
 Thingy:91 HW v1.4.0 
 The Full Error Log (maybe not really usefull): 
 2020-12-08T13:56:33.268Z INFO Application data folder: /Users/RudolphAschmoneit/Library/Application Support/nrfconnect/pc-nrfconnect-programmer 2020-12-08T13:56:33.333Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6 2020-12-08T13:56:33.385Z DEBUG App pc-nrfconnect-programmer v1.4.8 official 2020-12-08T13:56:33.385Z DEBUG App path: /Users/RudolphAschmoneit/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer 2020-12-08T13:56:33.385Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0) 2020-12-08T13:56:33.385Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar 2020-12-08T13:56:33.385Z DEBUG HomeDir: /Users/RudolphAschmoneit 2020-12-08T13:56:33.385Z DEBUG TmpDir: /var/folders/hf/dq9llqg57lj8c2jrwtl3d5280000gn/T/ 2020-12-08T13:56:34.273Z VERBOSE Could not fetch serial number for serial port at /dev/tty.TeufelBoomsterNG-CSRGAIA 2020-12-08T13:56:34.273Z VERBOSE Could not fetch serial number for serial port at /dev/tty.JBLGO-vCOMM-1 2020-12-08T13:56:34.273Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port 2020-12-08T13:56:34.274Z VERBOSE Could not fetch serial number for serial port at /dev/tty.JBLCharge3-SPPDev-6 2020-12-08T13:56:34.274Z VERBOSE Could not fetch serial number for serial port at /dev/tty.JBLCharge3-SPPDev-14 2020-12-08T13:57:06.730Z INFO Modem DFU starts to write... 2020-12-08T13:57:06.731Z INFO Writing /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/thingy91_fw_2020-10-30_5522ca2b/mfwnrf9160122.zip to device 2020-12-08T13:57:19.194Z ERROR MCUboot DFU failed. Please make sure that the device is in MCUboot mode and try again. 
 Have anyone an idea? Thank you really much in Advance fpr any Tips! Greetings Rudolph

Didrik Rokhaug · Accepted Answer

Rudolph Aschmoneit said: Sorry for getting this wrong 
 No problem at all. 
 
 Rudolph Aschmoneit said: In my experience so far, your getting started tutorials have always been very straightforward and easy to follow. 
 I am happy to hear that, and apologize for the Thingy:91 gtting started process not being as easy. 
 
 Rudolph Aschmoneit said: The LED was blinking, so I tried it again, cause I remembered you note that the LED should not Blink when in MCU Boot Mode. So I turned the device off, holding SW4 and powered it on again, LED was blinking, so I re-read your Post, and I mentioned, that the LED should be off when 9160 is in MCU Bootmode, so I thought maybe LED is off only when the nrf9160 is in MCU Bootmode and not when nRF52840 is in MCU Bootmode. 
 You are correct, and I could probably have been more clear. The nRF52840 is used only as a brdige between UART from the nRF9160 and USB, so it has no control of the LED. That is up to the application on the nRF9160. 
 
 Rudolph Aschmoneit said: what was the reason of the error? Was anything wrong in the procedure I was doing/ had described here? 
 It sounds to me like you did everything correctly. 
 Did the Programmer leave any log files? 
 You can find where they are stored by opening the current log (see picture), and selecting "save as". You should then get a file browser window opened at the location where the logs are stored by default (at least on Windows). 
 In Windows, the location is C:\Users\<user>\AppData\Roaming
rfconnect\pc-nrfconnect-programmer\logs. 
 
 Rudolph Aschmoneit said: But now the Programmer doesn't find the device, no matter if in MCU boot mode or not, and I also can't see it as USB Device at my computer 
 Are you using Linux? 
 If you connect the Thingy to your computer (or power it on while it is connected), and run 'dmes', do you see any lines indicating that you just connected a USB device? 
 Anyway, it seems you already have an nRF9160DK:

Rudolph Aschmoneit said: when I was getting started with the nrf9160 DK 
 The easiest solution is probably to connect a 10-pin cable from the 'Debug out' port on the DK to the debug connector on the Thingy, and set 'SWD SELECT' to the 'nRF52' position, and program the nRF52840 that way. 
 Remember that when using this method, you must use the images in the img_app_bl folder. 
 See this guide for more information: https://infocenter.nordicsemi.com/topic/ug_nc_programmer/UG/nrf_connect_programmer/ncp_pgm_thingy91_debugprobe.html

Can't get started with Thingy:91 // MCUboot flash of modem firmware fails

Top Replies