• State Verified Answer
  • Replies 18 replies
  • Subscribers 70 subscribers
  • Views 3256 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
  • +1

    Hello,

    While reading all your old threads I guess you are bit confused on 1st stage and 2nd stage bootloaders. I can see that your use case is only to update the Application via OTA DFU. For this you don't need a Second stage bootloader. You only want to include bootloader chain if you only want to update the bootloader itself while doing the upgrade. See our Secure bootloader chain section

    Take a look at this blog which will give you more idea on adding MCUboot to the application. IF you check the testing section it will show you how you can do the DFU via Bluetooth.

    Please let me know if you need anymore clarification.

    Kind Regards,

    Abhijith

  • 0 in reply to Menon

    i get it now. MCUboot works fine. I can update via Bluetooth too. However, I need to add encryption too to this implementation. I have a ECDSA256 key and I want to add it to the MCUboot implementation. I am following this thread. However, I have a few problems while building. I am not building this  as a child image. Should I compulsorily build it as a separate child image ?

    Assuming that I need not, I went ahead and tried the following

    When I tried setting this kConfig option,

    CONFIG_BOOT_SIGNATURE_KEY_FILE="priv.pem"

    the value was not set successfully and I understood that this option must be set for it to work.

    CONFIG_MCUBOOT_HEX_FILE=""

    But I have not built any images for MCUboot to give as a hex path to this option. So i tried building the MCUboot with this as a reference. However I ran into errors while building MCUboot.

    Also, while working through this thread, when I tried to set the key type using the option 

    CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y

    I could not find any such option in the Kconfig. Is that a deprecated one or am I doing something wrong ?

    I did find this in the \bootloader\mcuboot\boot\zephyr\prj.conf

    CONFIG_BOOT_ENCRYPT_EC256=n

    Is it the same thing as above ?

    I do not know if I am in the right path here. Please correct me if I am wrong at any point.

Reply
  • 0 in reply to Menon

    i get it now. MCUboot works fine. I can update via Bluetooth too. However, I need to add encryption too to this implementation. I have a ECDSA256 key and I want to add it to the MCUboot implementation. I am following this thread. However, I have a few problems while building. I am not building this  as a child image. Should I compulsorily build it as a separate child image ?

    Assuming that I need not, I went ahead and tried the following

    When I tried setting this kConfig option,

    CONFIG_BOOT_SIGNATURE_KEY_FILE="priv.pem"

    the value was not set successfully and I understood that this option must be set for it to work.

    CONFIG_MCUBOOT_HEX_FILE=""

    But I have not built any images for MCUboot to give as a hex path to this option. So i tried building the MCUboot with this as a reference. However I ran into errors while building MCUboot.

    Also, while working through this thread, when I tried to set the key type using the option 

    CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y

    I could not find any such option in the Kconfig. Is that a deprecated one or am I doing something wrong ?

    I did find this in the \bootloader\mcuboot\boot\zephyr\prj.conf

    CONFIG_BOOT_ENCRYPT_EC256=n

    Is it the same thing as above ?

    I do not know if I am in the right path here. Please correct me if I am wrong at any point.

Children
No Data
Related