doc: SUIT documentation on updating Nordic Bundles

[ahasztag]

Added the documnetation regarding updating of Nordic Semiconductor provided firmware components.

[NordicBuilder]

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 76622b12e47b123291192738b2e93a7234d95fad

more details

sdk-nrf:

PR head: 76622b12e47b123291192738b2e93a7234d95fad
merge base: f0654346b9c7b64482740b1ee730641f2470410b
target head (main): 18d7fd830f9293d5ce95ae70a70313b177257d03
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 (4)

doc
│  ├── nrf
│  │  ├── app_dev
│  │  │  ├── device_guides
│  │  │  │  ├── working_with_nrf
│  │  │  │  │  ├── nrf54h
│  │  │  │  │  │  ├── ug_nrf54h20_suit_customize_qsg.rst
│  │  │  │  │  │  ├── ug_nrf54h20_suit_dfu.rst
│  │  │  │  │  │  │ ug_nrf54h20_suit_soc_binaries.rst
│  │  ├── releases_and_maturity
│  │  │  ├── releases
│  │  │  │  │ release-notes-changelog.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_serial_lte_modem
  • 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-ps
  • 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
  • test-secdom-samples-public

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.

[maciejpietras]

Would be good to describe pros and cons of both solutions. Separate update needs less MRAM for DFU so it's worth to mention it. Disadvantage of this approach is a responsibility on customer side to manage compatibility between App/radio and Nordic bundle.
I would also consider adding this page as a part of https://developer.nordicsemi.com/nRF_Connect_SDK_dev/doc/PR-17417/nrf/samples/suit/smp_transfer/README.html instead of dedicated page.

[tomchy]

To my understanding this sentence is not correct - updating Nordic components is done through a single update, but the update of the whole device (incl. manufacturer application) is done in two steps.

[ahasztag]

After reading that the sentence indeed might sound confusing. Modified that.

[tomchy]

Please either add advantages/drawbacks here too or make a separate section that compares those two methods.

[ahasztag]

Ok, at first I wanted to avoid duplication, but I didn't have an idea how to do a "comparison" in a nice way, so I simply copied the pros/cons, switched them, and reworded them in the second section

[FrancescoSer]

Can you add a link to the new ABI compatibility page? It indicates the compatibility between NCS versions and soc binaries versions

[ahasztag]

I think this is already done

[FrancescoSer]

Please edit also the filename to match the shortcut

[ahasztag]

Done