This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Brand new Thingy91 getting started not working

Hello,

Just received the Thingy91, I started following this video tutorial: https://www.youtube.com/watch?v=xQ7hDzRULJQ, and a few things didn't go as expected. A few things to add, I am connect via micro-USB cable to a Mac. SW0 SELECT is nRF91. I plugged in the SIM Card. 

1) when updating the modem firmware. I click and hold SW1 and turn on the device to see MCU*** show up. Then by selecting the modem's mfwnrf9160120.zip in the programmer application and clicking write, I receive the following error 

17:50:33.887
Update files regions according to Application core
17:50:33.887
Parse memory regions for file
17:54:04.836
Checking ZIP file: /Users/../mfwnrf9160120.zip
17:54:05.015
File was last modified at 12/31/2022, 5:53:39 PM
17:54:10.333
Modem DFU starts to write...
17:54:10.333
Writing /Users/../mfwnrf9160120.zip to device AE33D***4
17:54:13.797
Target device closed
17:54:19.197
Modem DFU failed with error: async task failure for id: 1613552859 msg: Error when programming through MCUBoot: Unable to program MCUBoot image from buffer.. Error code: 600 (Unknown). (Origin: "Error when running fw program.")
17:54:19.199
async task failure for id: 1613552859 msg: Error when programming through MCUBoot: Unable to program MCUBoot image from buffer.. Error code: 600 (Unknown). (Origin: "Error when running fw program.")
2) iBASIS SIM CARD Activation fail. I follow the same instructions on the video above, but I do not see the next steps and when I refresh I see the following error message:
warningThis sim is not active. Activate
for the record, I am in California for location purposes.  
Not sure if those two are connected but hopefully someone can give me pointers as this is my first Nordic device. 
Best
Parents Reply Children
  • Great, that's a new one. Then my experience with the expired SIM cards doesn't apply.

  • I mainly use the Jlink to update the firmware, so I'm no too common with the nRF Connect for Desktop approach.

    It's not recommended to downgrade the modem, so I'm not sure, if applying the mfwnrf9160120.zip is the right idea.

    SW1 on holding SW4 (small button) applies a firmware update for the nRF52840 SoC. Maybe your device stick here. Try to apply the "img_app_bl/thingy91_nrf52_connectivity_bridge???.hex" and see, if your device comes back.

    SW1 on holding SW3 (big central button) applies a firmware update for the nRF9160 SiP. Here you may apply the right modem firmware (e.g. mfw_nrf9160_1.3.3.zip) or the application (e.g. img_app_bl/thingy91_asset_tracker_v2_???.hex ).

    So, crossing the fingers, that you didn't brick it and you're able the "revive" it. If not, you may consider to use a Jlink.

  • Interesting, I tried what you recommended 

    SW1 on holding SW4 (small button) applies a firmware update for the nRF52840 SoC. Maybe your device stick here. Try to apply the "img_app_bl/thingy91_nrf52_connectivity_bridge???.hex" and see, if your device comes back.

    I saw MCUBOOT device on the programmer. Once I selected the image and Write I received the following error:

    I'm starting to think I have a faulty device OR need to utilize a jlink programmer. 

  • It's not recommended to downgrade the modem, so I'm not sure, if applying the mfwnrf9160120.zip is the right idea.

    I agree, I had tried the newest 1.3.3 version first, once that failed I tried to reverting back.

  • > I tried what you recommended 

    This was just a guess, that you device sticks somehow in updating the nRF52840 SoC.

    I use Ubuntu 20.04 and I was also able to update the modem firmware and the application using SW1 and SW3 with nRF Connect for Desktop. But I mainly use a jlink for that.

Related