Trouble trying to upload firmware to a Thingy 91 via USB

[XavierN]

Hello,

I have a brand new Thingy 91 running the default asset tracker application connected to nrfCloud.

I wanted to build the asset_tracker myself and upload it to validate that I got the process right.

I followed the instructions to build the hex file in SEGGER for the nrf9160_pca20035ns device and got the app_signed.hex file in the build folder. So far so good.

I follow this instructions to upload the hex file via nrf Connect since I don't have an nrf9160DK board so I am trying to upload it via USB:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_thingy91%2FUG%2Fthingy91%2Fintro%2Ffrontpage.html

Following the instructions, with the thingy 91 switched off I press the only button on the top side of the thingy 91, right beside the sim card holder, and with it still pressed down i switch the Thingy 91 on. I don't get any output in the Lte Link Monitor console and the led is not blinking or on but it is completely off.

I connect to the device using the nrfConnect Programmer, select the app_signed.hex file and then when I click on write and I get the error "Please make sure that the device is in MCUBoot mode and try again.

Questions:

• Is it the right choice to build for nrf9160_pca20035ns or should I build for nrf9160_pca20035?
• How do I make sure the Thingy 91 is in MCUBoot mode?
• The build produces several .hex files: merged, app_signed, etc.. I chose app_signed since it is the one that appears on the help screenshot, is this the right one?
• I am assuming that SW3 is the only visible button on the top of the device when the cover is removed, or is the SW3 button located on the under side and I need to remove the device from the case?

Thank you.

Xavier

[Øyvind]

Hello, 

---

Note that next week is Christmas holiday for the Nordic support team, and you must expect some delay in your answers. Full support is back at the beginning of January.

---

I assume you are following the Update Application FW on nRF9160 using MCUboot? In nRF Connect - Programmer, what shows in the drop-down list?

Is it the right choice to build for nrf9160_pca20035ns or should I build for nrf9160_pca20035?

 Yes, this is correct.

How do I make sure the Thingy 91 is in MCUBoot mode?

 As you did correct:

1. Connect Nordic Thingy:91 to the PC using USB.
2. Put the Nordic Thingy:91 into application serial recovery mode by pushing the SW3 button while powering on.
   1. The device will not blink any LED
3. Start nRF Connect Programmer.
   1. Will show in Programmer app as PCA20035_<SN> with two COM ports.
4. Click Select device and select the appropriate device entry from the drop-down list in the nRF Connect Programmer as shown in the following figure

 

The build produces several .hex files: merged, app_signed, etc.. I chose app_signed since it is the one that appears on the help screenshot, is this the right one?

 No, this is not correct, you should use the merged.hex as this includes SPM and application. I will report this as a bug. 

I am assuming that SW3 is the only visible button on the top of the device when the cover is removed, or is the SW3 button located on the under side and I need to remove the device from the case?

 You are correct! SW3 is the only visible button on top. 

Let me know how it works with merged.hex.

Kind regards,
Øyvind

[XavierN]

Hello Øyvind,

I chose the merged.hex file this time but unfortunately I get the same message and as as soon as I push the "write" button the thingy boots normally.

Is there anything else I could check?

Xavier

[XavierN]

Any suggestions before the weekend starts?

Xavier

[XavierN]

See: devzone.nordicsemi.com/.../nrf9160dk-unable-to-connect