This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Firmware update for Thingy 91

I cant seem to get the Thingy 91 into boot MCU mode, so that I can update it to the latest firmware.
No matter how many times I try turning the unit off and powering up with the larger press button held down, the firmware programming returns an error complaining that the unit is not in BootMCU mode.

Is there anything else I could try?

Parents
  • Andrew8691 said:
    I hadn't yet installed the command line tools, but will now do that.

     Ok, good!

    Andrew8691 said:

     I’m very sorry for being unclear here, Andrew. What I meant is that the firmware package has different contents, as described in the CONTENTS.txt 

    Folder contents:
    img_app_bl/
      - Full application images including bootloader.
      - These files can be used with:
        - nRF Connect Programmer (only with SEGGER J-Link or another debug probe)
        - nrfjprog CLI
    img_fota_dfu_hex/
      - These images contain only application and bootloader is not included.
      - Images are in HEX format.
      - These files can be used with nRF Connect Programmer (only via USB bootloader).
    img_fota_dfu_bin/
      - These images contain only application and bootloader is not included.
      - Images are in binary format.
      - These files can be used with:
        - Over-the-air update, for example, via nRF Cloud, Azure or AWS.
        - mcumgr CLI (via USB bootloader only)
    
    The following folders contain images configured for modem debugging:
      - img_app_bl/debug 
      - img_fota_dfu_hex/debug
      - img_fota_dfu_bin/debug

    It is important that you choose the image from the right folder.

    Regards,

    Markus

Reply
  • Andrew8691 said:
    I hadn't yet installed the command line tools, but will now do that.

     Ok, good!

    Andrew8691 said:

     I’m very sorry for being unclear here, Andrew. What I meant is that the firmware package has different contents, as described in the CONTENTS.txt 

    Folder contents:
    img_app_bl/
      - Full application images including bootloader.
      - These files can be used with:
        - nRF Connect Programmer (only with SEGGER J-Link or another debug probe)
        - nrfjprog CLI
    img_fota_dfu_hex/
      - These images contain only application and bootloader is not included.
      - Images are in HEX format.
      - These files can be used with nRF Connect Programmer (only via USB bootloader).
    img_fota_dfu_bin/
      - These images contain only application and bootloader is not included.
      - Images are in binary format.
      - These files can be used with:
        - Over-the-air update, for example, via nRF Cloud, Azure or AWS.
        - mcumgr CLI (via USB bootloader only)
    
    The following folders contain images configured for modem debugging:
      - img_app_bl/debug 
      - img_fota_dfu_hex/debug
      - img_fota_dfu_bin/debug

    It is important that you choose the image from the right folder.

    Regards,

    Markus

Children
  • Thanks Markus, I opened the Zip folder (thingy91_fw_2021-06-28_7a076c22) and found another Zip file inside mfw_nrf9160_1.3.0.zip, which I took to be the required firmware and I was successfully able to install this on both Thingy91s. Tnstaller looks for a Zip file , when installing new modem firmware.

    [Unfortunately , the nrf Cloud connect refiuses to accept the updated devices (saying that the devices have not been provisioned - but that's another story.]

    I appreciate your help with getting the firmware up to date.

    Regards,

    Andrew.

Related