doc: nrf54h: Add SDFW update description

[adsz-nordic]

Add description of SUIT based update of:

• Secure Domain Firmware
• Secure Domain Firmware Recovery

Jira: NCSDK-27725

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 4f39efd2e49857d57e069449b37951760a025294

more details

sdk-nrf:

PR head: 4f39efd2e49857d57e069449b37951760a025294
merge base: 771d5ce292c48893a30675179dfa1b0868d6c901
target head (main): 771d5ce292c48893a30675179dfa1b0868d6c901
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 (5)

doc
│  ├── nrf
│  │  ├── app_dev
│  │  │  ├── device_guides
│  │  │  │  ├── working_with_nrf
│  │  │  │  │  ├── nrf54h
│  │  │  │  │  │  ├── images
│  │  │  │  │  │  │  │ nrf54h20_suit_sdfw_sdrfw_update_flow.svg
│  │  │  │  │  │  ├── ug_nrf54h20_suit_components.rst
│  │  │  │  │  │  ├── ug_nrf54h20_suit_dfu.rst
│  │  │  │  │  │  ├── ug_nrf54h20_suit_hierarchical_manifests.rst
│  │  │  │  │  │  │ ug_nrf54h20_suit_sdfw_sdrfw_update.rst

Outputs:

Toolchain

Version:
Build docker image:

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

• ◻️ Toolchain
• ◻️ Build twister
• ◻️ Integration tests

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-boot
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_mosh
  • test-fw-nrfconnect-nrf-iot_nrf_provisioning
  • test-fw-nrfconnect-nrf-iot_positioning
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-proprietary_esb
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread
  • test-fw-nrfconnect-zigbee
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-sidewalk
  • test-sdk-wifi

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

[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 Publishing GitHub Action.

[FrancescoSer]

Just a few minor things

[adsz-nordic]

Applied suggested changes, please check again.

[maciejpietras]

Added suggestion for consideration

[maciejpietras]

Would be good to have one common naming convention for Recovery. As on the diagrams we call it SDRFW I would suggest to call it "Secure Domain Recovery Firmware" instead of "Secure Domain Firmware Recovery". On the other hand some diagrams call it "SDRFW" while others call it "SDFW_Recovery". I suggest to select one (e.g. SDRFW) and keep it consistent among documentation.

[adsz-nordic]

Would be good to have one common naming convention for Recovery. As on the diagrams we call it SDRFW I would suggest to call it "Secure Domain Recovery Firmware" instead of "Secure Domain Firmware Recovery". On the other hand some diagrams call it "SDRFW" while others call it "SDFW_Recovery". I suggest to select one (e.g. SDRFW) and keep it consistent among documentation.

Unified naming, replaced diagram.