Issues with XIP execution from external QSPI on nRF with MCUBOOT

RE: Issues with XIP execution from external QSPI on nRF with MCUBOOT

PjGlasso — Thu, 27 Nov 2025 21:59:22 GMT

Hi there,

Use multi-image DFU / split image

Nordic has a QSPI XIP split-image feature: one image in internal flash, one in QSPI, managed as separate images under MCUboot.

High level:

Partition manager defines:
- mcuboot_primary (internal flash)
- xip_image (external flash, QSPI) or similar
Build produces two images:
- Image 0: main app (internal)
- Image 1: XIP data (model in QSPI)
With mcumgr/dfu-util they upload:
- Slot 0 → internal app
- Slot 1 → QSPI image

This is more work, but it’s the “official” way if they need firmware-style updates to the QSPI contents.

HTH

GL :-) PJ :v:

RE: Issues with XIP execution from external QSPI on nRF with MCUBOOT

Vidar Berg — Thu, 06 Nov 2025 12:31:52 GMT

Hello Rémi,

I'm not aware of any plans to add support direct-xip with external memory on this device, and I'm not sure how much effort it will take. Based on your current findings it seems that you will at least need to run parts of the application such as the QSPI driver from flash.

[quote user="Remi Moessner"]The main advantage of using external QSPI is to avoid SWAP during update (by using xip_offset). Do you have any solution to avoid swapping between two bank with a split image ? Is it possible ?[/quote]

But is reducing the FW activation times with a few seconds worth performance reduction during normal operation? Your FW is going to run differently depending on whether it's being executed from internal or external flash which also may increase your test requirements.

Best regars,

Vidar

RE: Issues with XIP execution from external QSPI on nRF with MCUBOOT

Remi Moessner — Thu, 06 Nov 2025 09:34:53 GMT

Hello VIdar,

Thanks for your answer

[quote userid="4240" url="~/f/nordic-q-a/125422/issues-with-xip-execution-from-external-qspi-on-nrf-with-mcuboot/553488"]The mcuboot direct xip feature is currently not supported with external memory. [/quote]

OK, is it planned ?

[quote userid="4240" url="~/f/nordic-q-a/125422/issues-with-xip-execution-from-external-qspi-on-nrf-with-mcuboot/553488"]However, since executing code from directly from QSPI flash also adds a significant performance penalty in terms of execution speed and power consumption compared to running code from internal flash (see Indication of XIP performance) I would recommend consiering the QSPI XIP split image approach described here: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/bootloaders_dfu/qspi_xip_split_image.html instead. This is assuming that goal is to free up internal memory.[/quote]

I based my initial investigation on this example and tried to simplified to avoid using internal memory :)

The main advantage of using external QSPI is to avoid SWAP during update (by using xip_offset). Do you have any solution to avoid swapping between two bank with a split image ? Is it possible ?

Thanks

Best Regards,

Rémi

RE: Issues with XIP execution from external QSPI on nRF with MCUBOOT

Vidar Berg — Wed, 05 Nov 2025 19:49:21 GMT

Hello Rémi,

The mcuboot direct xip feature is currently not supported with external memory. However, since executing code from directly from QSPI flash also adds a significant performance penalty in terms of execution speed and power consumption compared to running code from internal flash (see Indication of XIP performance) I would recommend consiering the QSPI XIP split image approach described here: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/bootloaders_dfu/qspi_xip_split_image.html instead. This is assuming that goal is to free up internal memory.

Best regards,

Vidar