sysbuild: Use upstream firmware loader configuration system

[nordicjm]

Switches to using the upstream zephyr sysbuild configuration system for configuring the firmware loader image

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 713a39e8c37caa624de9ebcc211748129801d193

more details

sdk-nrf:

PR head: 713a39e8c37caa624de9ebcc211748129801d193
merge base: dd61a27360859efc5f5068e43138071aa952d21b
target head (main): dd61a27360859efc5f5068e43138071aa952d21b
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 (3)

cmake
│  ├── sysbuild
│  │  │ partition_manager.cmake
sysbuild
│  ├── CMakeLists.txt
│  ├── image_configurations
│  │  │ firmware_loader_image_default.cmake

Outputs:

Toolchain

Version: 3ae5dc3c63
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:3ae5dc3c63_776d264d2e

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-boot
  • ❌ test-fw-nrfconnect-apps
  • ✅ 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-rpc
  • ✅ test-fw-nrfconnect-rs
  • ✅ test-fw-nrfconnect-fem
  • ✅ test-fw-nrfconnect-tfm
  • ✅ test-fw-nrfconnect-thread-main
  • ✅ 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-secdom-samples-public

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

[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.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-22923/2)