• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 87 subscribers
  • Views 411 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 279772
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ncs 52 serial bootloader update

Август

Hello

In my another ticket https://devzone.nordicsemi.com/f/nordic-q-a/81555/ncs-upgradable-bootloader.

I know there is currently no support for upgrading the bootloader (MCUboot) on nRF52 Series devices.

I want to know if you plan to support bootloader updates on nrf52 series devices at ncs project? The old sdk already supports the bootloader update.

Thank you

Parents
  • +1

    Hi 

    There are no current plans to allow MCUboot to be updated on the nRF52 series, no. 

    A critical difference when using the bootloader architecture in NCS is that the bootloader is essentially split in two. You have MCUboot which only validates the image, and copies a new image from slot 1 to slot 0, while everything else (like transferring new images over Bluetooth or some other transport) is handled elsewhere. 

    This makes it less important to be able to update MCUboot, compared to being able to update the bootloader in the nRF5 architecture, since you can still update all the higher level bootloader functionality that is handled outside MCUboot. 

    Best regards
    Torbjørn

Reply
  • +1

    Hi 

    There are no current plans to allow MCUboot to be updated on the nRF52 series, no. 

    A critical difference when using the bootloader architecture in NCS is that the bootloader is essentially split in two. You have MCUboot which only validates the image, and copies a new image from slot 1 to slot 0, while everything else (like transferring new images over Bluetooth or some other transport) is handled elsewhere. 

    This makes it less important to be able to update MCUboot, compared to being able to update the bootloader in the nRF5 architecture, since you can still update all the higher level bootloader functionality that is handled outside MCUboot. 

    Best regards
    Torbjørn

Children
No Data
Related