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

Thingy Custom FW

Can we build the FW manually and upload to the Thingy via the OTA uploader? We built the FW, created the DFU, and inserted the .zip file in the iOS app, however get an Error when attempting to update the FW. The code says the following, which implies we cannot build the FW this way and upload to the device. More Sighs.

    // The DFU from SDK 12 returns Invalid Object error when the signature does not match.
    // This means that the bootloader is either locked (requires fw signed by Nordic) or an invalid signature was
    // used to sign the new firmware. Let's show this info to the user. Until the NonSecure DFU is released the
    // only way to unlock the bootloader is by flashing user's own secure DFU bootloader with user's own public key
    // using USB. Unlocking the bootloader Over-The-Air is not supported yet.
    // TODO: This comment needs to be updated when NonSecure DFU or other way to unlock the Bootloader is implemented for Thingy.
Parents
  • As stated in the comment you copied above: only way to unlock the bootloader is by flashing user's own secure DFU bootloader with user's own public key

    So I'm afraid you need to recompile and program the bootloader including your own public key, so that you can create a valid signature for your FW.

  • Thank you for the reply. If I had the nRF DK I likely would not have ordered the Thingy:52. I went with the T52 due to the following:

    "The Nordic Thingy:52Tm is a compact, power-optimized, multi-sensor development kit. It is an easy-to-use development platform, designed to help you build IoT prototypes and demos, without the need to build hardware or write firmware."

    thinking that I would not need to write firmware or need anything else to use the available pins on the board, as stated in the users guide. It is also interesting that even creating prototypes and demos requires some other hardware, since the board itself cannot be programmed, without writing firmware. I will likely move to a different platform, and use this as a sensor node.

Reply
  • Thank you for the reply. If I had the nRF DK I likely would not have ordered the Thingy:52. I went with the T52 due to the following:

    "The Nordic Thingy:52Tm is a compact, power-optimized, multi-sensor development kit. It is an easy-to-use development platform, designed to help you build IoT prototypes and demos, without the need to build hardware or write firmware."

    thinking that I would not need to write firmware or need anything else to use the available pins on the board, as stated in the users guide. It is also interesting that even creating prototypes and demos requires some other hardware, since the board itself cannot be programmed, without writing firmware. I will likely move to a different platform, and use this as a sensor node.

Children
No Data
Related