• State Verified Answer
  • Replies 18 replies
  • Subscribers 70 subscribers
  • Views 3240 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 300491
Options

Question about Over the Air update in NCS_V2

Midhunjac

Does the NCS V2 .x support OTA updates ? I used OTA update with encryption in older SDK and i was looking to migrate that to the new SDK. Is there some example or  guide to how to do the exact same implementation in NCS ? I know NCS uses mcuboot but does that mean that DFU and OTA is no longer supported in NCS ?

Thank you.

Parents
  • 0

    Hello,

    Midhunjac said:
    CONFIG_BOOT_SIGNATURE_KEY_FILE="priv.pem"

    In this configuration you need to mention the full path length of the key file. I assume you are only using MCUboot( bit confused as the thread you shared is from bootloader chain).

    As a starting point take a look at this repo from my colleague which explains how to  work with custom key. Take a look at the generating key section which gives you more idea on this.

    Let me know if you are still struggling.

    Kind Regards,

    Abhijith

  • 0 in reply to Menon

    I could get the whole encryption and OTA functionality working, thanks to your guidance. However, there is also one slight problem. My application image is a bit too much and so, during the swapping, it fails.

    I am aware that I have an option to move the second image to an external flash. But the thing is, changing the whole layout to accommodate an external flash is not a really feasible idea. I could get this working by disabling the logging module CONFig_LOG=n and I saved almost 40kb. But it would suit the application to have the logger enabled.

    Is there any other way I can get the application image reduced or get the image swap to be successful ? My application is built on the peripheral_uart sample.

    Edit : Also, I noticed that once I upload an image successfully and the swapping is all done, the SMP service will no longer be active until I reboot the device. The SMP service will be listed in the NRF Connect android application but in the NRF Device manager application, the device wont show up until there the device is rebooted. Is that a normal response for an invalid image ?

    Thank you.

Reply
  • 0 in reply to Menon

    I could get the whole encryption and OTA functionality working, thanks to your guidance. However, there is also one slight problem. My application image is a bit too much and so, during the swapping, it fails.

    I am aware that I have an option to move the second image to an external flash. But the thing is, changing the whole layout to accommodate an external flash is not a really feasible idea. I could get this working by disabling the logging module CONFig_LOG=n and I saved almost 40kb. But it would suit the application to have the logger enabled.

    Is there any other way I can get the application image reduced or get the image swap to be successful ? My application is built on the peripheral_uart sample.

    Edit : Also, I noticed that once I upload an image successfully and the swapping is all done, the SMP service will no longer be active until I reboot the device. The SMP service will be listed in the NRF Connect android application but in the NRF Device manager application, the device wont show up until there the device is rebooted. Is that a normal response for an invalid image ?

    Thank you.

Children
No Data
Related