Partition Manager: support for FIXED_PARTITION macros and update of sdk-zephyr with fixed flash-map tests

[de-nordic]

Two commits:

• support for FIXED_PARTITION macro that allows to obtain direct pointer to flash_area object representing partition, instead of using flash_area_open with id;
• Zephyr manifest update with sdk-zephyr changes to flash_map tests, that conditionally disable parts of tests that are not possible to run on Partition Manager enabled build.

You can build the Zephyr flash map test using:

west build --sysbuild -d builds/pm-flash -b nrf52840dk/nrf52840 zephyr/tests/subsys/storage/flash_map/ -DSB_CONFIG_PARTITION_MANAGER=y -DSB_CONFIG_BOOTLOADER_MCUBOOT=y

to get free PM definitions that allow you to run the test on nrf52840.

Depends on:
#22473

[NordicBuilder]

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

Name	Old Revision	New Revision	Diff

✅ 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: 16

Inputs:

Sources:

sdk-nrf: PR head: 0e45d400f4efccc926a2996ae2daed24f84310b6

more details

sdk-nrf:

PR head: 0e45d400f4efccc926a2996ae2daed24f84310b6
merge base: 063432abbc2478f6ab4a7b8908d14453f737fe5e
target head (main): 063432abbc2478f6ab4a7b8908d14453f737fe5e
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 (2)

include
│  │ flash_map_pm.h
subsys
│  ├── partition_manager
│  │  │ flash_map_partition_manager.c

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_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-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-fw-nrfconnect-ps-main
  • ✅ test-secdom-samples-public
  • ⚠️ test-fw-nrfconnect-fw-update

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.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-22496/16)