https://devzone.nordicsemi.com/f/nordic-q-a/127883/nrf54l15-firmware-encryptionEnable the &quot;mcuboot_with_encryption&quot; function. 1: When using VSCode for flashing, by default, mcuboot is flashed with un-signed and un-encrypted firmware, while the application firmware is flashed with signed firmware. Can signed and encrypted firmwareen-USTelligent Community 13Thu, 23 Apr 2026 12:16:47 GMThttps://devzone.nordicsemi.com/thread/565398?ContentTypeID=1Thu, 23 Apr 2026 12:16:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1286bbc3-6c9b-4cc9-ae3b-d5eb67e326acNishant Gaurav<p>Hi, fredly</p> <p><span>When you build with encryption enabled, the build system generates both&nbsp;</span><code class="m_b183c0a2 mantine-Code-root" dir="ltr">zephyr.signed.bin</code><span>&nbsp;(unencrypted, signed) and&nbsp;</span><code class="m_b183c0a2 mantine-Code-root" dir="ltr">zephyr.signed.encrypted.bin</code><span>&nbsp;(signed and encrypted) in the application build directory.&nbsp;</span></p> <p><span>To enable encryption, you build with:</span></p> <p><span>&nbsp;west build -b nrf54l15dk/nrf54l15/cpuapp -- -DSB_CONFIG_BOOTLOADER_MCUBOOT=y -DSB_CONFIG_BOOT_ENCRYPTION=y</span></p> <p><span></span></p> <p><span>The&nbsp;<strong>MCUboot bootloader image itself is not encrypted</strong>&nbsp;&mdash; it is the&nbsp;<em>application</em>&nbsp;image that gets encrypted. MCUboot is the entity that&nbsp;<em>performs</em>&nbsp;decryption of the application image during the slot-swap process.</span></p> <p><span></span></p> <p><span></span></p> <p><span></span></p><div style="clear:both;"></div>