Sysbuild, Partition manager and mcuboot from external flash problems

RE: Sysbuild, Partition manager and mcuboot from external flash problems

Vidar Berg — Thu, 14 Nov 2024 10:58:27 GMT

I will create an internal request to include more DFU samples in the SDK. It's a good suggestion. With regards to NSIB, the motivation for including it is usually to enable support for DFU of MCUBOOT, but it does increase the flash memory fooprint.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/bootloaders_dfu/mcuboot_nsib/bootloader.html#ug-bootloader

RE: Sysbuild, Partition manager and mcuboot from external flash problems

Bruno Randolf — Thu, 14 Nov 2024 09:59:35 GMT

The crucial thing was the overlay file in sysbuild/mcuboot which activates the external flash as below. It's not obvious that mcuboot does not use the overlays from the application boards directory.

/ {
    chosen {
        nordic,pm-ext-flash = &mx25r64;
    };
};

RE: Sysbuild, Partition manager and mcuboot from external flash problems

Bruno Randolf — Thu, 14 Nov 2024 09:43:35 GMT

I still don't quite understand what's the point of NSIB though...

RE: Sysbuild, Partition manager and mcuboot from external flash problems

Bruno Randolf — Thu, 14 Nov 2024 09:38:23 GMT

Thank you - that works and will help. Maybe this should be part of the official ncs samples?

RE: Sysbuild, Partition manager and mcuboot from external flash problems

Vidar Berg — Wed, 13 Nov 2024 16:06:52 GMT

Hello,

Attached is a sample I made earlier based on the peripheral_lbs sample. It includes NSIB as the first-stage bootloader, but this can be disbled through the sysbuild.conf file. Please have a look at this sample and compare the MCUBoot configurations. The error suggests that the QSPI nor driver initialization failed in MCUBOOT.

devzone.nordicsemi.com/.../2388.peripheral_5F00_lbs.zip

Best regards,

Vidar