Unable to burn custom firmware.

[Gova]

I was able to create a Distribution package with the command as shown in the following photo.

I have taken the zip file from email app in my iPhone and have opened in thingy app. After that I am unable to burn the latest firmware even though I am able to select the same in my thingy app's inbox. Please watch the video in attachments to know my problem. Any help would be appreciated. Thanks a ton in advance.

www.youtube.com/watch

[bjorn-spockeli]

You do not have the private key which corresponds to the public key in the factory programmed bootloader on the Thingy so you will not be able to update the application via OTA DFU.

The Over-the-air device firmware update section in the Thingy User Guide describes how you update the application that is made by Nordic Semiconductor through the Thingy app. It does not cover how to update your own application, which requires you to compile your own bootloader with your public key and flash the bootloader using a programmer and a cable.

You should look at the nRF5 SDK documentation on the bootloader, see this page on Infocenter.

[Otavio Borges]

You'll need something with an ARM programmer, like nRF52-DK, to replace the factory bootloader. You can use devzone.nordicsemi.com/.../ as guideline.

[Gova]

I have already been advised to burn the bootloader first in my previous question whose URL is

how-to-flash-bootloader-to-thingy-52

If you can see the comments, I was told to hold down the button and bring the thingy to DFU mode and then straight away burn the firmware. But now I understood that that will not work and I need a nRF DK to program the bootloader. Please confirm if my understanding is correct.

[Otavio Borges]

I'm not familiar with the DFU bootloader on Thingy. But, basing on nrf52-DK DFU bootloader, the only way to upload your custom firmware without an ARM programmer is either if Thingy bootloader does not have key-pair validation or you find the original private key from nordic. Search a little deeper if nordic provides any documentation in that matter. Remember that once you reflash the device with another bootloader you won't need to use the programmer unless you want to recover the device (rewrite the bootloader), so perhaps you could borrow one DK board (a Segger J-Link would do the trick as well).

[bjorn-spockeli]

@govardhanan (Gova): Yes, you are correct.