bootloader: mcuboot: Changes needed to support AES256

[ahasztag]

This commit adds changes which are necessary to support the AES256 encryption algorithm in mcuboot.

[NordicBuilder]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
mcuboot	nrfconnect/sdk-mcuboot@0fadab1	nrfconnect/sdk-mcuboot@3b20ec3 (main)	nrfconnect/[email protected]
zephyr	nrfconnect/sdk-zephyr@2cc69ef	nrfconnect/sdk-zephyr@51f0b2c (main)	nrfconnect/[email protected]

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 14

Inputs:

Sources:

sdk-nrf: PR head: 959528835172af7bd0aa4afc2b65c477cbc84dda
mcuboot: PR head: 3b20ec38019dc0841062ba0622b4d7b6792193e5
zephyr: PR head: 51f0b2c5c449b08826faef7cea0df23e9856ceed

more details

sdk-nrf:

PR head: 959528835172af7bd0aa4afc2b65c477cbc84dda
merge base: 3216ae0845705630ffab1e1b5738ecd43f5444cb
target head (main): 3216ae0845705630ffab1e1b5738ecd43f5444cb
Diff

mcuboot:

PR head: 3b20ec38019dc0841062ba0622b4d7b6792193e5
merge base: 0fadab126d9ba51365b3db1cdb6d55ed892c62b4
Diff

zephyr:

PR head: 51f0b2c5c449b08826faef7cea0df23e9856ceed
merge base: 2cc69ef97a5ce7871628b29a2eaf2a7b4a628388
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (17)

bootloader
│  ├── mcuboot
│  │  ├── boot
│  │  │  ├── bootutil
│  │  │  │  ├── src
│  │  │  │  │  │ image_validate.c
│  │  │  ├── zephyr
│  │  │  │  ├── Kconfig
│  │  │  │  ├── flash_map_extended.c
│  │  │  │  ├── include
│  │  │  │  │  ├── mcuboot_config
│  │  │  │  │  │  │ mcuboot_config.h
│  │  ├── docs
│  │  │  ├── release-notes.d
│  │  │  │  │ fix-pure-eddsa-base-address.md
│  │  ├── scripts
│  │  │  ├── imgtool
│  │  │  │  │ image.py
cmake
│  ├── sysbuild
│  │  ├── image_signing.cmake
│  │  ├── image_signing_firmware_loader.cmake
│  │  ├── image_signing_split.cmake
│  │  │ sign_nrf54h20.cmake
west.yml
zephyr
│  ├── cmake
│  │  │ mcuboot.cmake
│  ├── modules
│  │  │ Kconfig.mcuboot
│  ├── share
│  │  ├── sysbuild
│  │  │  ├── image_configurations
│  │  │  │  ├── BOOTLOADER_image_default.cmake
│  │  │  │  │ MAIN_image_default.cmake
│  │  │  ├── images
│  │  │  │  ├── bootloader
│  │  │  │  │  ├── CMakeLists.txt
│  │  │  │  │  │ Kconfig

Outputs:

Toolchain

Version: c5be9c56c7
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:c5be9c56c7_bba2ea5f2e

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
• ✅ Integration tests
  • ✅ test-sdk-audio
  • ✅ desktop52_verification
  • ✅ test-fw-nrfconnect-apps
  • ✅ test_ble_nrf_config
  • ✅ test-fw-nrfconnect-ble_mesh
  • ✅ test-fw-nrfconnect-ble_samples
  • ✅ test-fw-nrfconnect-chip
  • ✅ test-fw-nrfconnect-nfc
  • ✅ test-fw-nrfconnect-nrf-iot_cloud
  • ✅ test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • ✅ test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • ✅ test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • ✅ test-fw-nrfconnect-nrf-iot_samples
  • ✅ test-fw-nrfconnect-nrf-iot_lwm2m
  • ✅ doc-internal
  • ✅ test-fw-nrfconnect-nrf-iot_thingy91
  • ✅ test-fw-nrfconnect-nrf_crypto
  • ✅ test-fw-nrfconnect-proprietary_esb
  • ✅ test-fw-nrfconnect-rpc
  • ✅ test-fw-nrfconnect-rs
  • ✅ test-fw-nrfconnect-fem
  • ✅ test-fw-nrfconnect-tfm
  • ✅ test-sdk-find-my
  • ✅ test-fw-nrfconnect-nrf_lrcs_mosh
  • ✅ test-fw-nrfconnect-nrf_lrcs_positioning
  • ✅ test-sdk-wifi
  • ✅ test-low-level
  • ✅ test-sdk-pmic-samples
  • ✅ test-sdk-mcuboot
  • ✅ test-sdk-dfu
  • ✅ test-fw-nrfconnect-ps-main
  • ✅ test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[github-actions]

You can find the documentation preview for this PR here.

[NordicBuilder]

Memory footprint analysis revealed the following potential issues

applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 9090[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 5846[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 9090[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 5846[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 12430[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 9178[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 12430[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 9178[B] - link (cc: @nrfconnect/ncs-ll-ursus)

Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-23512/14)