Inquiry on Using Primary Slot Only for nRF54L05 in MCUboot with SPI-based Firmware Update

[Ozzy]

Dear Nordic Semiconductor Team and Community Members,

I am currently working on an nRF54L05 project where I aim to use only the primary slot in MCUboot due to memory constraints. Instead of the backup slot upgrade mechanism, I want to implement a non-backup upgrade solution. My setup involves an SPI host (a USB chip with a RISC-V core on my board) that will transfer the .bin file to the nRF54L05, which acts as the SPI slave to receive the data.

Unfortunately, I have not been able to find suitable examples to adapt for this specific configuration. I have reviewed information on CONFIG_SINGLE_APPLICATION_SLOT and CONFIG_MCUBOOT_SERIAL, but it seems these configurations may not directly address my requirements.

Could you please advise if this approach is feasible? I would greatly appreciate any guidance, examples, or insights you could provide on how to achieve this.

Thank you for your time and assistance.

Best regards

[Menon]

Hello,

You're right, it is not exactly as you described, but it does use a single-slot DFU method. If you're interested in MCUboot's XIP (Execute In Place) mode, it also supports single-slot firmware updates without a backup slot. In this mode, the bootloader directly executes the image from the specified slot.

You can refer to the documentation on configuring MCUboot in Direct XIP mode. There's also a sample available that you may find helpful.

Kind regards,
Abhijith