Skip to content

Commit cbeb54f

Browse files
FrancescoSernordicjm
FrancescoSer
authored and
nordicjm
committed
doc: Release notes for 2.9.0-nRF54H20-1-rc2
Added release notes for 2.9.0-nRF54H20-1-rc2. Added migration guide for 2.9.0-nRF54H20-1-rc2. Added other release edits for 2.9.0-nRF54H20-1-rc2. Signed-off-by: Francesco Domenico Servidio <[email protected]>
1 parent efedd56 commit cbeb54f

37 files changed

+415
-256
lines changed

‎doc/nrf/app_dev/device_guides/nrf54h/index.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ Zephyr and the |NCS| provide support and contain board definitions for developin
3636
ug_nrf54h20_architecture
3737
ug_nrf54h20_configuration
3838
ug_nrf54h20_suit_dfu
39+
ug_nrf54h20_keys
3940
ug_nrf54h20_logging
4041
ug_nrf54h20_debugging
4142
ug_nrf54h20_custom_pcb

‎doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_architecture_lifecycle.rst‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,3 +55,10 @@ This figure shows the states and transitions (both forward and backward ones) th
5555

5656
Changing the lifecycle state will be useful during development.
5757
Test devices in their final configuration would require the device to be in the deployed state, however, updating the Secure Domain firmware and the System Controller firmware will be easier with the device in RoT state.
58+
59+
For more information, see the following pages:
60+
61+
* :ref:`ug_nrf54h20_gs`
62+
* :ref:`ug_nrf54h20_custom_pcb`
63+
* :ref:`ug_nrf54h20_suit_dfu`
64+
* :ref:`ug_nrf54h20_keys`

‎doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_gs.rst‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,11 @@ Getting started with the nRF54H20 DK
77
:local:
88
:depth: 2
99

10-
This document gets you started with your nRF54H20 Development Kit (DK) using the |NCS|.
10+
This document gets you started with your nRF54H20 Development Kit (DK) using the |NCS| for the first time.
1111
It tells you how to install the :zephyr:code-sample:`sysbuild_hello_world` sample and perform a quick test of your DK.
1212

13+
If you are migrating from an earlier version of the |NCS|, see :ref:`migration_guides`.
14+
1315
.. _ug_nrf54h20_gs_requirements:
1416

1517
Minimum requirements
@@ -138,7 +140,7 @@ Installing nRF Util and its commands
138140
Using the nRF54H20 DK with the |NCS| version |release| requires the following:
139141

140142
* nRF Util v7.13.0 or higher
141-
* nRF Util ``device`` command v2.7.10
143+
* nRF Util ``device`` command v2.7.14
142144
* nRF Util ``trace`` command v3.1.0
143145
* nRF Util ``suit`` command v0.9.0
144146

@@ -163,11 +165,11 @@ If you have not already installed nRF Util as part of :ref:`nRF Connect SDK prer
163165
For more information, consult the `Upgrading nRF Util core module`_ documentation.
164166

165167
#. Install the required versions of nRF Util commands, as listed above, using the command from `Installing specific versions of nRF Util commands`_.
166-
For example, the following command installs the nRF Util ``device`` command version 2.7.10:
168+
For example, the following command installs the nRF Util ``device`` command version 2.7.14:
167169

168170
.. code-block::
169171
170-
nrfutil install device=2.7.10 --force
172+
nrfutil install device=2.7.14 --force
171173
172174
.. _ug_nrf54h20_gs_bringup:
173175

@@ -209,7 +211,7 @@ After programming the BICR, program the nRF54H20 SoC with the :ref:`nRF54H20 SoC
209211
This bundle contains the precompiled firmware for the :ref:`Secure Domain <ug_nrf54h20_secure_domain>` and :ref:`System Controller <ug_nrf54h20_sys_ctrl>`.
210212
To program the nRF54H20 SoC binaries to the nRF54H20 DK, do the following:
211213

212-
1. Download the `nRF54H20 SoC Binaries v0.8.0`_, compatible with the nRF54H20 DK v0.9.0 and later revisions.
214+
1. Download the `nRF54H20 SoC binaries v0.9.1`_, compatible with the nRF54H20 DK v0.9.0 and later revisions.
213215

214216
.. note::
215217
On MacOS, ensure that the ZIP file is not unpacked automatically upon download.

‎doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_keys.rst‎

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
.. _ug_nrf54h20_keys:
2+
3+
Provisioning keys on the nRF54H20 SoC
4+
#####################################
5+
6+
.. contents::
7+
:local:
8+
:depth: 2
9+
10+
The keys provisioning workflow for the nRF54H20 SoC consists of two main steps:
11+
12+
1. Generating the required metadata using a script provided with the |NCS|.
13+
#. Provisioning the keys to the nRF54H20 SoC.
14+
15+
.. note::
16+
The nRF54H20 SoC must be in RoT lifecycle state for key provisioning to work.
17+
For more details on lifecycle states, see :ref:`ug_nrf54h20_architecture_lifecycle`.
18+
19+
Generating the keys
20+
===================
21+
22+
A script is used to generate the necessary cryptographic keys, BLOBs, and metadata required for provisioning.
23+
The script follows the PSA Crypto standard to generate the required 28-byte key.
24+
It is located in the :file:`nrf/scripts/generate_psa_key_attributes.py` file.
25+
26+
To generate the keys, follow these steps:
27+
28+
1. Generate private keys using Ed25519::
29+
30+
openssl genpkey -algorithm Ed25519 -out MANIFEST_APPLICATION_GEN1_priv.pem
31+
openssl genpkey -algorithm Ed25519 -out MANIFEST_RADIOCORE_GEN1_priv.pem
32+
openssl genpkey -algorithm Ed25519 -out MANIFEST_OEM_ROOT_GEN1_priv.pem
33+
34+
#. Extract public keys::
35+
36+
openssl pkey -in MANIFEST_APPLICATION_GEN1_priv.pem -pubout -out MANIFEST_APPLICATION_GEN1_pub.pem
37+
openssl pkey -in MANIFEST_RADIOCORE_GEN1_priv.pem -pubout -out MANIFEST_RADIOCORE_GEN1_pub.pem
38+
openssl pkey -in MANIFEST_OEM_ROOT_GEN1_priv.pem -pubout -out MANIFEST_OEM_ROOT_GEN1_pub.pem
39+
40+
#. Check the required key IDs::
41+
42+
MANIFEST_PUBKEY_APPLICATION_GEN1 = 0x40022100
43+
MANIFEST_PUBKEY_APPLICATION_GEN2 = 0x40022101
44+
MANIFEST_PUBKEY_APPLICATION_GEN3 = 0x40022102
45+
MANIFEST_PUBKEY_OEM_ROOT_GEN1 = 0x4000AA00
46+
MANIFEST_PUBKEY_OEM_ROOT_GEN2 = 0x4000AA01
47+
MANIFEST_PUBKEY_OEM_ROOT_GEN3 = 0x4000AA02
48+
MANIFEST_PUBKEY_RADIOCORE_GEN1 = 0x40032100
49+
MANIFEST_PUBKEY_RADIOCORE_GEN2 = 0x40032101
50+
MANIFEST_PUBKEY_RADIOCORE_GEN3 = 0x40032102
51+
52+
#. Create a JSON input file with the ``generate_psa_key_attributes.py`` script:
53+
54+
* For the application core::
55+
56+
python generate_psa_key_attributes.py --usage VERIFY_MESSAGE_EXPORT --id 0x40022100 --type ECC_TWISTED_EDWARDS --size 255 --algorithm EDDSA_PURE --location PERSISTENT_CRACEN --key-from-file MANIFEST_APPLICATION_GEN1_pub.pem --file all_keys.json --cracen_usage RAW
57+
58+
* For the radio core::
59+
60+
python generate_psa_key_attributes_new.py --usage VERIFY_MESSAGE_EXPORT --id 0x40032100 --type ECC_TWISTED_EDWARDS --size 255 --algorithm EDDSA_PURE --location PERSISTENT_CRACEN --key-from-file MANIFEST_RADIOCORE_GEN1_pub.pem --file all_keys.json --cracen_usage RAW
61+
62+
* For the main root manifest::
63+
64+
python generate_psa_key_attributes_new.py --usage VERIFY_MESSAGE_EXPORT --id 0x4000AA00 --type ECC_TWISTED_EDWARDS --size 255 --algorithm EDDSA_PURE --location PERSISTENT_CRACEN --key-from-file MANIFEST_OEM_ROOT_GEN1_pub.pem --file all_keys.json --cracen_usage RAW
65+
66+
67+
The generated key data is stored in a JSON file, which serves as an input for the next step.
68+
69+
Provisioning the keys
70+
=====================
71+
72+
nRF Util is used to provision the generated keys into the target device.
73+
It takes the JSON file as input and injects it without validating its contents.
74+
In this scenario, nRF Util functions as a transport layer, transferring the key data to the correct location in the device.
75+
76+
The Secure Domain Firmware on the device handles the actual key provisioning using PSA Crypto's ``psa_import_key`` function.
77+
Provisioning a key calls the function to import the key:
78+
79+
* The ``metadata`` field from the JSON file is used for the function's attributes argument
80+
* The ``value`` field is passed to the function's data argument
81+
* The function's ``data_length`` is set to the length of the value field.
82+
83+
To provision the keys from ``all_keys.json`` onto the KMU of the nRF54H20 SoC, use nRF Util as follows::
84+
85+
nrfutil device x-provision-nrf54h-keys --serial-number <snr> --key-file all_keys.json
86+
87+
For more information on how to provision keys, see the `Provisioning keys for hardware KMU`_ page in the nRF Util documentation.

‎doc/nrf/conf.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
# General configuration --------------------------------------------------------
2727

2828
project = "nRF Connect SDK"
29-
copyright = "2019-2024, Nordic Semiconductor"
29+
copyright = "2019-2025, Nordic Semiconductor"
3030
author = "Nordic Semiconductor"
3131
version = release = os.environ.get("DOCSET_VERSION")
3232

‎doc/nrf/dev_model_and_contributions/adding_code.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ This is demonstrated by the following code, that would be placed somewhere in yo
162162
- name: nrf
163163
repo-path: sdk-nrf
164164
remote: ncs
165-
revision: 2.9.0-nRF54H20-rc1
165+
revision: 2.9.0-nRF54H20-1-rc2
166166
import: true
167167
self:
168168
path: application
@@ -189,7 +189,7 @@ For example:
189189
projects:
190190
- name: nrf
191191
remote: ncs
192-
revision: 2.9.0-nRF54H20-rc1
192+
revision: 2.9.0-nRF54H20-1-rc2
193193
import: true
194194
# Example for how to override a repository in the nRF Connect SDK with your own:
195195
- name: mcuboot

‎doc/nrf/links.txt‎

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -436,7 +436,7 @@
436436
.. _`nRF Connect SDK latest documentation`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/index.html
437437

438438
.. _`known issues page on the main branch`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html
439-
.. _`known issues for nRF Connect SDK v2.9.0-nRF54H20-rc1`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v2-9-0-nRF54H20-rc1
439+
.. _`known issues for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v2-9-0-nRF54H20-1-rc2
440440
.. _`known issues for nRF Connect SDK v2.9.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v2-9-0
441441
.. _`known issues for nRF Connect SDK v2.8.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v2-8-0
442442
.. _`known issues for nRF Connect SDK v2.7.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v2-7-0
@@ -492,7 +492,7 @@
492492

493493
.. _`nRF socket options`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/nrf_modem/doc/sockets.html
494494

495-
.. _`Repositories and revisions for v2.9.0-nRF54H20-rc1`: https://docs.nordicsemi.com/bundle/ncs-2.9.0-nrf54h20-rc1/page/nrf/releases_and_maturity/repository_revisions.html
495+
.. _`Repositories and revisions for v2.9.0-nRF54H20-1-rc2`: https://docs.nordicsemi.com/bundle/ncs-2.9.0-nRF54H20-1-rc2/page/nrf/releases_and_maturity/repository_revisions.html
496496
.. _`Repositories and revisions for v2.9.0`: https://docs.nordicsemi.com/bundle/ncs-2.9.0/page/nrf/releases_and_maturity/repository_revisions.html
497497
.. _`Repositories and revisions for v2.8.0`: https://docs.nordicsemi.com/bundle/ncs-2.8.0/page/nrf/releases_and_maturity/repository_revisions.html
498498
.. _`Repositories and revisions for v2.7.99-cs2`: https://docs.nordicsemi.com/bundle/ncs-2.7.99-cs2/page/nrf/releases_and_maturity/repository_revisions.html
@@ -587,7 +587,7 @@
587587
.. _`LwM2M carrier library changelog for v1.9.0`: https://docs.nordicsemi.com/bundle/ncs-1.9.0/page/nrf/libraries/bin/lwm2m_carrier/CHANGELOG.html
588588

589589
.. _`Migration guide for nRF Connect SDK v3.0.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_3.0.html
590-
.. _`Migration guide for nRF Connect SDK v2.9.0-nRF54H20-rc1`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nrf54h20-rc1.html
590+
.. _`Migration guide for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nRF54H20-1-rc2.html
591591
.. _`Migration guide for nRF Connect SDK v2.9.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.9.html
592592
.. _`Migration guide for nRF Connect SDK v2.8.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.8.html
593593
.. _`Migration guide for nRF Connect SDK v2.7.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.7.html
@@ -871,6 +871,7 @@
871871
.. _`Programming application firmware using MCUboot serial recovery`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/programming_firmware_thingy91.html
872872
.. _`Programming application firmware on the nRF54L15 SoC`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/programming_nrf54L15.html
873873
.. _`Upgrading modem firmware using J-Link`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/programming_modem_9160.html
874+
.. _`Provisioning keys for hardware KMU`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/provisioning_keys.html
874875

875876
.. _`anomaly 19`: https://docs.nordicsemi.com/bundle/errata_nRF5340_EngA/page/ERR/nRF5340/EngineeringA/latest/anomaly_340_19.html
876877

@@ -1591,8 +1592,8 @@
15911592

15921593
.. ### Source: files.nordicsemi.com
15931594

1594-
.. _`Twister test report for nRF Connect SDK v2.9.0-nRF54H20-rc1`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v2.9.0-nrf54h20-rc1/test-report/twister_test_results_report.html?isNativeBrowsing=true
1595-
.. _`Hardware test report for nRF Connect SDK v2.9.0-nRF54H20-rc1`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v2.9.0-nrf54h20-rc1/test-report/common_ncs_test_results_report.html?isNativeBrowsing=true
1595+
.. _`Twister test report for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v2.9.0-nrf54h20-1-rc2/test-report/twister_test_results_report.html?isNativeBrowsing=true
1596+
.. _`Hardware test report for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v2.9.0-nrf54h20-1-rc2/test-report/common_ncs_test_results_report.html?isNativeBrowsing=true
15961597
.. _`Twister test report for nRF Connect SDK v2.9.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v2.9.0/test-report/twister_test_results_report.html?isNativeBrowsing=true
15971598
.. _`Hardware test report for nRF Connect SDK v2.9.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v2.9.0/test-report/common_ncs_test_results_report.html?isNativeBrowsing=true
15981599
.. _`Twister test report for nRF Connect SDK v2.8.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v2.8.0/test-report/twister_test_results_report.html?isNativeBrowsing=true
@@ -1782,12 +1783,12 @@
17821783

17831784
.. _`curl`: https://curl.se/
17841785

1785-
.. _`nRF54H20 SoC Binaries v0.3.3`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.3.3.zip
1786-
.. _`nRF54H20 SoC Binaries v0.5.0`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.5.0.zip
1787-
.. _`nRF54H20 SoC Binaries v0.6.2`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.6.2.zip
1786+
.. _`nRF54H20 SoC binaries v0.3.3`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.3.3.zip
1787+
.. _`nRF54H20 SoC binaries v0.5.0`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.5.0.zip
1788+
.. _`nRF54H20 SoC binaries v0.6.2`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.6.2.zip
17881789
.. _`nRF54H20 SoC binaries v0.6.5`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.6.5.zip
1789-
.. _`nRF54H20 SoC Binaries v0.7.0 for EngC DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engc.zip
1790-
.. _`nRF54H20 SoC Binaries v0.7.0 for EngB DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engb.zip
1790+
.. _`nRF54H20 SoC binaries v0.7.0 for EngC DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engc.zip
1791+
.. _`nRF54H20 SoC binaries v0.7.0 for EngB DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engb.zip
17911792
.. _`nRF54H20 SoC binaries v0.8.0`: https://files.nordicsemi.com/ui/native/SDSC/external/nrf54h20_soc_binaries_v0.8.0.zip
17921793
.. _`nRF54H20 SoC binaries v0.9.1`: https://files.nordicsemi.com/ui/native/SDSC/external/nrf54h20_soc_binaries_v0.9.1.zip
17931794

‎doc/nrf/protocols/matter/index.rst‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,9 @@ For a full list of |NCS| and Matter versions, view the following table:
2323
+--------------------------+-----------------------------------------------------+------------------------+
2424
| nRF Connect SDK version | Matter specification version | Matter SDK version |
2525
+==========================+=====================================================+========================+
26-
| v2.9.99 (latest) | :ref:`1.4.0 <ug_matter_overview_dev_model_support>` | 1.4.0.0 |
26+
| |release| | :ref:`1.4.0 <ug_matter_overview_dev_model_support>` | 1.4.0.0 |
2727
+--------------------------+ | |
28-
| |release| | | |
28+
| v2.9.0-nRF54H20-1-rc2 | | |
2929
+--------------------------+ | |
3030
| v2.9.0 | | |
3131
+--------------------------+-----------------------------------------------------+------------------------+

‎doc/nrf/releases_and_maturity/abi_compatibility.rst‎

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
.. _abi_compatibility:
22

3-
ABI Compatibility
3+
ABI compatibility
44
#################
55

66
.. contents::
@@ -18,7 +18,7 @@ When ABI compatibility is maintained, binaries of one component can interface co
1818
For example, adding a new function to a library is typically an ABI-compatible change, as existing binaries remain functional.
1919
However, changes that affect data structure layouts, such as altering field order or size, break ABI compatibility as they change the memory layout expected by existing binaries.
2020

21-
ABI Compatibility Matrix for the nRF54H20 SoC Binaries
21+
ABI compatibility matrix for the nRF54H20 SoC binaries
2222
******************************************************
2323

2424
The following table illustrates ABI compatibility between different versions of the nRF54H20 SoC binaries and the |NCS|:
@@ -29,27 +29,31 @@ The following table illustrates ABI compatibility between different versions of
2929
* - |NCS| versions
3030
- Compatible nRF54H20 SoC binaries version
3131
* - |NCS| v2.9.0-nRF54H20-1-rc2
32-
- `nRF54H20 SoC Binaries v0.9.1`_, compatible with the nRF54H20 DK v0.9.0 and later revisions.
32+
- `nRF54H20 SoC binaries v0.9.1`_, compatible with the nRF54H20 DK v0.9.0 and later revisions.
3333
* - |NCS| v2.9.0
34-
- `nRF54H20 SoC Binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions.
34+
- `nRF54H20 SoC binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions.
3535
* - |NCS| v2.8.0
36-
- `nRF54H20 SoC Binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions.
37-
`nRF54H20 SoC Binaries v0.7.0 for EngB DKs`_, compatible with the nRF54H20 DKs ranging from v0.8.0 to v0.8.2.
36+
- `nRF54H20 SoC binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions.
37+
`nRF54H20 SoC binaries v0.7.0 for EngB DKs`_, compatible with the nRF54H20 DKs ranging from v0.8.0 to v0.8.2.
3838
* - |NCS| v2.7.99-cs2
39-
- `nRF54H20 SoC Binaries v0.6.5`_
39+
- `nRF54H20 SoC binaries v0.6.5`_
4040
* - |NCS| v2.7.99-cs1
41-
- `nRF54H20 SoC Binaries v0.6.2`_
41+
- `nRF54H20 SoC binaries v0.6.2`_
4242
* - |NCS| v2.7.0
43-
- `nRF54H20 SoC Binaries v0.5.0`_
43+
- `nRF54H20 SoC binaries v0.5.0`_
4444
* - |NCS| v2.6.99-cs2
45-
- `nRF54H20 SoC Binaries v0.3.3`_
45+
- `nRF54H20 SoC binaries v0.3.3`_
4646

4747
ABI compatibility ensures that the Secure Domain and System Controller firmware binaries do not need to be recompiled each time the application, radio binaries, or both are recompiled, as long as they are based on a compatible |NCS| version.
4848
Additionally, maintaining ABI compatibility allows the nRF54H20 SoC binary components to work together without recompilation when updating to newer |NCS| versions.
4949

50-
nRF54H20 SoC Binaries v0.9.1 changelog
50+
nRF54H20 SoC binaries v0.9.1 changelog
5151
**************************************
5252

53+
.. note::
54+
The nRF54H20 SoC binaries only support specific versions of the |NCS| and do not support rollbacks to a previous version.
55+
Upgrading the nRF54H20 SoC binaries on your development kit might break the DK's compatibility with applications developed for previous versions of the |NCS|.
56+
5357
The following sections provide detailed lists of changes by component.
5458

5559
Secure Domain Firmware (SDFW) v10.1.0

0 commit comments

Comments
 (0)