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

Unable to burn custom firmware.

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

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

Parents
  • 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.

  • 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).

Reply
  • 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).

Children
No Data
Related