MCUBOOT

[YveWit]

For our project we switched over to using DIRECT_XIP mone primarily because of the faster boot time but it automatically enables downgrade protection. For our project we need the ability to downgrade. So is there anyway to have DIRECT_XIP while still allowing for the ability to downgrade.

[AHaug]

Hi,

Currently this is not supported as all of the variations of CONFIG_BOOT_BUILD_DIRECT_XIP_VARIANT, i.e CONFIG_MCUBOOT_BOOTLOADER_MODE_DIRECT_XIP and CONFIG_MCUBOOT_BOOTLOADER_MODE_DIRECT_XIP_WITH_REVERT selects MCUBOOT_BOOTLOADER_NO_DOWNGRADE due it's not possible to downgrade a running application.

Could you expand a bit upon the motivation for the need of not having downgrade protection while using DIRECT_XIP? Is it an option to investigate the use of non-direct_xip with downgrade protection disabled?

Kind regards,
Andreas

[YveWit]

We require the use of DIRECT_XIP for the boot speed. Because it does not copy over the secondary slot to the primary slot. As far as I know there is no other option that allows one to run directly from the slot that was updated. It is a requirement for our product to have the ability to update to any version. I just want to know if there is anyway to use DIRECT_XIP but disabling  the version checking 

[AHaug]

Noted, thank you for elaborating.

Then the answer is unfortunately no, not currently and not without a feature request that will implement a workaround through the configuration or that you create your own custom MCUboot (which is possible) that does not select MCUBOOT_BOOTLOADER_NO_DOWNGRADE when building your project with DIRECT_XIP.

I've checked in internally w.r.t the last option to see if there is any pitfalls that I've not considered and I'll get back to you with an update when I hear back from them

Kind regards,
Andreas

[AHaug]

The team says that this should be possible, but that doing so will cause you too loose out of the safetyfeatures that downgrade protection provides. Negating CONFIG_MCUBOOT_BOOTLOADER_NO_DOWNGRADE will also be quite hard due to how it's implemented.

The recommendation is to make CONFIG_MCUBOOT_BOOTLOADER_MODE_DIRECT_XIP_WITH_REVERT working with removing the selects.

Kind regards,
Andreas 

[YveWit]

Why Can I not enable  DIRECT_XIP and just set  CONFIG_MCUBOOT_BOOTLOADER_NO_DOWNGRADE to no. Why would that now work exactly?

[AHaug]

Hi,

What do you see when you set it to n and remove all dependencies?

Kind regards,
Andreas

[YveWit]

When I set it to n it say that it is still set to y in build. I am not sure it is possible to actually disable it with DIRECT_XIP:

[AHaug]

This would mean that you don't remove all dependencies. The configuration is selected by something else, which you can see in the KConfig documentation: https://docs.nordicsemi.com/bundle/ncs-latest/page/kconfig/index.html#CONFIG_MCUBOOT_BOOTLOADER_NO_DOWNGRADE 

You can modify the KConfigs in the SDK to make a custom fork of the SDK (disclaimer do not do this without knowing what you're doing) as an experiment to see if you're able to disable it.

Kind regards,
Andreas