firmware update--which hex files need to be uploaded?

[Hared]

I am updating Nordic Thingy:91. I am following instructions on Nordic's DevZone web page: "Getting NB-IoT Demo running on Thingy:91

I have successfully updated modem using the latest firmware zip file. The nRFConnect for Desktop Programmer app successfully connects to the Thingy:91.

However, the device does not work without also loading NB-IoT demo application firmware. The web page does not spell out which hex files to upload.

Below is a list of the files contained in the firmware update zip file. Which hex files on this list do I need to upload to the device to make it work?

thingy91_fw_2022-06-02_880c82db(2)
A CONTENTS.txt
I mfw_nrf9160_1.3.2.zip
| img_fota_dfu_hex
serial_Ite_modem_2022-06-02_880c82db.hex
thingy91_at_client_2022-06-02_880c82db.hex
thingy91_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex
thingy91_asset_tracker_v2_nbiot_legacy_pco_2022-06-02_880c82db.hex
debug
thingy91_asset_tracker_v2_Item_2022-06-02 880c82db.hex
thingy91_rf52_connectivity_bridge_2022-06-02_880c82db.hex
img_fota_dfu_bin
L serial_Ite_modem_2022-06-02_880c82db.bin
L thingy91_at_client_2022-06-02_880c82db.bin
L thingy91_asset_tracker_v2_nbiot_2022-06-02_880c82db.bin
L thingy91_asset_tracker_v2_nbiot_legacy_pco_2022-06-02_880c82db.bin
debug
L thingy91_asset_tracker_v2_Item_2022-06-02_880c82db.bin
L thingy91_nrf52_connectivity_bridge_2022-06-02_880c82db.bin
img_app_bl
I serial_Ite_modem_2022-06-02880c82db.hex
thingy91_at_client_2022-06-02_880c82db.hex
I thingy91_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex
thingy91_asset_tracker_v2_nbiot_legacy_pco_2022-06-02_880c82db.hex
debug
thingy91_asset_tracker_v2_Item_2022-06-02_880c82db.hex
thingy91_nrf52_connectivity_bridge_2022-06-02_880c82db.he

[helsing]

Hi Harry,

The file contents.txt has a short explanation. Check the description for the folder named '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).

In the img_fota_dfu_hex folder you will find a file 'thingy91_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex'.

This will load the Asset Tracker v2 application, is this the application you were looking for? Many customers also start with the AT Client:  'thingy91_at_client_2022-06-02_880c82db.hex'

(Small side note: The links I provided are for nRF Connect SDK v2.0.2. However, the hex files mentioned are potentially compiled for a slightly older version of the SDK.)

[Hared]

After firmware update, LED light is not coming on (i.e., even after I press and hold SW 3). What would cause this? My Thingy is PCA 20035 V 1.0.0. I am updating using USB (MCUboot). 

When I attempt to load asset tracker, Programmer gives following warning: Some of the HEX files have overlapping data.

[helsing]

Hi Harry. Sorry for the delay, I was out of office.

Hared said:

When I attempt to load asset tracker, Programmer gives following warning: Some of the HEX files have overlapping data.

Could you please provide a screenshot from when this happens?

Try clicking 'Clear files' in nRF Connect Programmer, and then 'Add file' to select the file again.

If this lets you program the device and it still does not work, you could try programming 'thingy91_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex' from the folder 'img_app_bl'.

[Hared]

Here is the error message I get when I attempt to write the hex file. 

[helsing]

Thank you for providing the screenshot. Is this different from when you previously were seeing the warning "Some of the HEX files have overlapping data"? I forgot to ask you to take a screenshot of the whole nRF Programmer window, including the memory layouts. I am interested in seeing if the bootloader is still programmed into the thingy. Would you know if it is still there? Or would you be able to take a new screenshot? A screenshot would also contain some other useful information when debugging this issue.

Updating nRF Connect for Desktop and Programmer is also recommended in general.

There are two different procedures going forward, depending on whether a bootloader is present or not in your Thingy:91.

• If no bootloader is present, you will not be able to do a DFU update without re-programming the bootloader. You could reprogram the bootloader using an external debug proge, for example a DK(like nRF9160 DK). When reprogramming the bootloader, select an image from the folder 'img_app_bl'. The procedure is also covered here:
• If the bootloader is present, then the procedure is somewhat simpler and can be done through USB.

It could be worth starting the whole update procedure of the Thingy:91 from the top, and then you could let is know where you get stuck. There is also another getting started guide here:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy91_gsg.html#getting-started-with-thingy-91

Another consideration: Have you updated the firmware on the nRF52840? Your thingy might contain the older firmware. Updating to the newer Connectivity_bridge is recommended. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy91_gsg.html#updating-the-firmware-in-the-nrf52840-soc

[Hared]

Here is screenshot of the Programmer when selecting About tab

No files are shown in the File Memory Layout on the Programmer tab

[helsing]

Thank you for sharing. This looks promising.

Have you tried Updating the firmware in the nRF52840 SoC? You could now follow the steps and select 'thingy91_nrf52_connectivity_bridge_2022-06-02_880c82db.hex' in the folder named 'img_fota_dfu_hex'.

If you are able to successfully complete the update of the fw of the connectivity bridge, please proceed with the process in the link below and let us know how it goes.

helsing said:

It could be worth starting the whole update procedure of the Thingy:91 from the top, and then you could let is know where you get stuck. There is also another getting started guide here:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy91_gsg.html#getting-started-with-thingy-91