samples: matter: Refactor nRF54H20 partition in samples

[ArekBalysNordic]

• Refactored nRF54H20 partitions to support storing Nordic-related
  SoC binaries in external flash.
• Enabled storing Nordic SoC binaries in the external flash if
  the SUIT_ENVELOPE_NORDIC_TOP_DIRECTORY kconfig value is provided.
• Described SUIT DFU process in Matter samples which can be performed
  on nRF54H20 modules. Currently, only the Matter OTA protocol is fully supported.

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 426104d221903b3f9977cbbb3931c4fcc7de7323

more details

sdk-nrf:

PR head: 426104d221903b3f9977cbbb3931c4fcc7de7323
merge base: a30fb624e41f0282d4f9920f65cb840f4ac6a001
target head (main): 5eb1bd14753f2f8642afa8e1721a1b00ee8d75d7
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 (16)

applications
│  ├── matter_bridge
│  │  ├── Kconfig.sysbuild
│  │  ├── boards
│  │  │  ├── nrf54h20dk_nrf54h20_cpuapp.conf
│  │  │  │ nrf54h20dk_nrf54h20_cpuapp.overlay
│  │  ├── doc
│  │  │  │ matter_bridge_description.rst
config
│  ├── suit
│  │  ├── templates
│  │  │  ├── nrf54h20
│  │  │  │  ├── matter
│  │  │  │  │  ├── v1
│  │  │  │  │  │  ├── app_envelope.yaml.jinja2
│  │  │  │  │  │  ├── rad_envelope.yaml.jinja2
│  │  │  │  │  │  │ root_with_binary_nordic_top.yaml.jinja2
doc
│  ├── nrf
│  │  ├── app_dev
│  │  │  ├── device_guides
│  │  │  │  ├── nrf54h
│  │  │  │  │  │ ug_nrf54h20_suit_soc_binaries.rst
│  │  ├── releases_and_maturity
│  │  │  ├── releases
│  │  │  │  │ release-notes-changelog.rst
samples
│  ├── matter
│  │  ├── common
│  │  │  ├── dts
│  │  │  │  ├── nrf54h20
│  │  │  │  │  ├── nrf54h20_cpuapp_memory_map.dtsi
│  │  │  │  │  │ nrf54h20_cpurad_memory_map.dtsi
│  │  ├── lock
│  │  │  ├── Kconfig.sysbuild
│  │  │  │ README.rst
│  │  ├── template
│  │  │  ├── Kconfig.sysbuild
│  │  │  │ README.rst
sysbuild
│  │ Kconfig.matter

Outputs:

Toolchain

Version: b77d8c1312
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:b77d8c1312_912848a074

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_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
  • ✅ test-fw-nrfconnect-zigbee
  • ✅ test-sdk-find-my
  • ✅ test-fw-nrfconnect-nrf-iot_mosh
  • ✅ test-fw-nrfconnect-nrf-iot_positioning
  • ✅ test-sdk-sidewalk
  • ✅ test-sdk-wifi
  • ✅ test-low-level
  • ✅ test-fw-nrfconnect-nrf-iot_nrf_provisioning
  • ✅ test-sdk-pmic-samples
  • ✅ test-sdk-mcuboot
  • ✅ test-sdk-dfu
  • ✅ test-fw-nrfconnect-ps
  • ✅ test-secdom-samples-public

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

[NordicBuilder]

Memory footprint analysis revealed the following potential issues

sample.matter.template.debug[nrf7002dk/nrf5340/cpuapp]: High ROM usage: 911938[B] - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic)
sample.matter.template.release[nrf7002dk/nrf5340/cpuapp]: High ROM usage: 820770[B] - link (cc: @kkasperczyk-no @ArekBalysNordic @markaj-nordic)

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

[NordicBuilder]

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publish GitHub Action.

[ArekBalysNordic]

@nrfconnect/ncs-charon, @nrfconnect/ncs-charon-doc and @nrfconnect/ncs-co-build-system could you please review related changes?

[nordicjm]

should not be abusing Kconfig files as thought they are defconfig files. If these are needed then the symbols should depend on them, or select them if the known issues are adhered to properly

[ArekBalysNordic]

Hmm, I would like to set the SUIT_ENVELOPE_NORDIC_TOP_EXTRACT_PAYLOADS_TO_CACHE if the user provides a path to the top directory using SUIT_ENVELOPE_NORDIC_TOP_DIRECTORY. Currently in Kconfig.suit SUIT_ENVELOPE_NORDIC_TOP_EXTRACT_PAYLOADS_TO_CACHE depends on SUIT_ENVELOPE_NORDIC_TOP_IN_ROOT and SUIT_ENVELOPE_NORDIC_TOP_IN_ROOT is default y if SUIT_ENVELOPE_NORDIC_TOP_DIRECTORY != "". I don't understand the abuse here, which kconfig of all mentioned should select or have dependency?

[ArekBalysNordic]

@nordicjm what do you recommend in this case?