From cbeb54f710176f373585e10aafc8bf8c64582031 Mon Sep 17 00:00:00 2001 From: Francesco Domenico Servidio Date: Mon, 30 Dec 2024 11:24:29 +0100 Subject: [PATCH] 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 --- .../app_dev/device_guides/nrf54h/index.rst | 1 + .../ug_nrf54h20_architecture_lifecycle.rst | 7 + .../device_guides/nrf54h/ug_nrf54h20_gs.rst | 12 +- .../device_guides/nrf54h/ug_nrf54h20_keys.rst | 87 ++++++++ doc/nrf/conf.py | 2 +- .../adding_code.rst | 4 +- doc/nrf/links.txt | 21 +- doc/nrf/protocols/matter/index.rst | 4 +- .../abi_compatibility.rst | 26 ++- .../releases_and_maturity/known_issues.rst | 205 +++++++++--------- ...e_2.4.99-cs3_to_2.6.99-cs2_application.rst | 2 + ...e_2.4.99-cs3_to_2.6.99-cs2_environment.rst | 2 + .../migration/migration_guide_1.x_to_2.x.rst | 2 + ...gration_guide_2.4.99-cs3_to_2.6.99-cs2.rst | 2 + .../migration/migration_guide_2.5.rst | 2 + .../migration/migration_guide_2.6.rst | 2 + .../migration/migration_guide_2.7.rst | 2 + .../migration/migration_guide_2.8.rst | 6 +- ... migration_guide_2.9.0-nRF54H20-1-rc2.rst} | 127 ++++++----- .../migration/migration_guide_2.9.rst | 2 + .../migration/migration_guide_3.0.rst | 2 + .../migration_guide_nRF54H20_cs_to_2_7.rst | 2 + ...ration_guide_nRF54H20_cs_to_2_7_99-cs1.rst | 2 + ...ration_guide_nRF54H20_cs_to_2_7_99-cs2.rst | 2 + .../migration/migration_guide_spm_to_tf-m.rst | 2 + .../migration/migration_hwmv2.rst | 2 + .../migration/migration_sysbuild.rst | 2 + ...on_guide_2.4.99-cs3_to_2.7_application.rst | 2 + ...on_guide_2.6.99-cs2_to_2.7_application.rst | 2 + ...on_guide_2.6.99-cs2_to_2_7_environment.rst | 2 + ...on_guide_2.4.99-cs3_to_2.7_environment.rst | 2 + .../migration_guides.rst | 21 +- .../releases_and_maturity/release_notes.rst | 6 +- ...=> release-notes-2.9.0-nRF54H20-1-rc2.rst} | 91 ++++---- .../releases/release-notes-changelog.rst | 4 +- doc/nrf/shortcuts.txt | 6 +- doc/versions.json | 3 +- 37 files changed, 415 insertions(+), 256 deletions(-) create mode 100644 doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_keys.rst rename doc/nrf/releases_and_maturity/migration/{migration_guide_2.9.0-nrf54h20-rc1.rst => migration_guide_2.9.0-nRF54H20-1-rc2.rst} (71%) rename doc/nrf/releases_and_maturity/releases/{release-notes-2.9.0-nrf54h20-rc1.rst => release-notes-2.9.0-nRF54H20-1-rc2.rst} (82%) diff --git a/doc/nrf/app_dev/device_guides/nrf54h/index.rst b/doc/nrf/app_dev/device_guides/nrf54h/index.rst index 81ad0771cf25..068032161a4f 100644 --- a/doc/nrf/app_dev/device_guides/nrf54h/index.rst +++ b/doc/nrf/app_dev/device_guides/nrf54h/index.rst @@ -36,6 +36,7 @@ Zephyr and the |NCS| provide support and contain board definitions for developin ug_nrf54h20_architecture ug_nrf54h20_configuration ug_nrf54h20_suit_dfu + ug_nrf54h20_keys ug_nrf54h20_logging ug_nrf54h20_debugging ug_nrf54h20_custom_pcb diff --git a/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_architecture_lifecycle.rst b/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_architecture_lifecycle.rst index c846e60c58cf..196aaa103ff1 100644 --- a/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_architecture_lifecycle.rst +++ b/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_architecture_lifecycle.rst @@ -55,3 +55,10 @@ This figure shows the states and transitions (both forward and backward ones) th Changing the lifecycle state will be useful during development. 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. + +For more information, see the following pages: + +* :ref:`ug_nrf54h20_gs` +* :ref:`ug_nrf54h20_custom_pcb` +* :ref:`ug_nrf54h20_suit_dfu` +* :ref:`ug_nrf54h20_keys` diff --git a/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_gs.rst b/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_gs.rst index 995c98603ece..759006fbdc02 100644 --- a/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_gs.rst +++ b/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_gs.rst @@ -7,9 +7,11 @@ Getting started with the nRF54H20 DK :local: :depth: 2 -This document gets you started with your nRF54H20 Development Kit (DK) using the |NCS|. +This document gets you started with your nRF54H20 Development Kit (DK) using the |NCS| for the first time. It tells you how to install the :zephyr:code-sample:`sysbuild_hello_world` sample and perform a quick test of your DK. +If you are migrating from an earlier version of the |NCS|, see :ref:`migration_guides`. + .. _ug_nrf54h20_gs_requirements: Minimum requirements @@ -138,7 +140,7 @@ Installing nRF Util and its commands Using the nRF54H20 DK with the |NCS| version |release| requires the following: * nRF Util v7.13.0 or higher -* nRF Util ``device`` command v2.7.10 +* nRF Util ``device`` command v2.7.14 * nRF Util ``trace`` command v3.1.0 * nRF Util ``suit`` command v0.9.0 @@ -163,11 +165,11 @@ If you have not already installed nRF Util as part of :ref:`nRF Connect SDK prer For more information, consult the `Upgrading nRF Util core module`_ documentation. #. Install the required versions of nRF Util commands, as listed above, using the command from `Installing specific versions of nRF Util commands`_. - For example, the following command installs the nRF Util ``device`` command version 2.7.10: + For example, the following command installs the nRF Util ``device`` command version 2.7.14: .. code-block:: - nrfutil install device=2.7.10 --force + nrfutil install device=2.7.14 --force .. _ug_nrf54h20_gs_bringup: @@ -209,7 +211,7 @@ After programming the BICR, program the nRF54H20 SoC with the :ref:`nRF54H20 SoC This bundle contains the precompiled firmware for the :ref:`Secure Domain ` and :ref:`System Controller `. To program the nRF54H20 SoC binaries to the nRF54H20 DK, do the following: -1. Download the `nRF54H20 SoC Binaries v0.8.0`_, compatible with the nRF54H20 DK v0.9.0 and later revisions. +1. Download the `nRF54H20 SoC binaries v0.9.1`_, compatible with the nRF54H20 DK v0.9.0 and later revisions. .. note:: On MacOS, ensure that the ZIP file is not unpacked automatically upon download. diff --git a/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_keys.rst b/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_keys.rst new file mode 100644 index 000000000000..0a7dc8c560a7 --- /dev/null +++ b/doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_keys.rst @@ -0,0 +1,87 @@ +.. _ug_nrf54h20_keys: + +Provisioning keys on the nRF54H20 SoC +##################################### + +.. contents:: + :local: + :depth: 2 + +The keys provisioning workflow for the nRF54H20 SoC consists of two main steps: + +1. Generating the required metadata using a script provided with the |NCS|. +#. Provisioning the keys to the nRF54H20 SoC. + +.. note:: + The nRF54H20 SoC must be in RoT lifecycle state for key provisioning to work. + For more details on lifecycle states, see :ref:`ug_nrf54h20_architecture_lifecycle`. + +Generating the keys +=================== + +A script is used to generate the necessary cryptographic keys, BLOBs, and metadata required for provisioning. +The script follows the PSA Crypto standard to generate the required 28-byte key. +It is located in the :file:`nrf/scripts/generate_psa_key_attributes.py` file. + +To generate the keys, follow these steps: + +1. Generate private keys using Ed25519:: + + openssl genpkey -algorithm Ed25519 -out MANIFEST_APPLICATION_GEN1_priv.pem + openssl genpkey -algorithm Ed25519 -out MANIFEST_RADIOCORE_GEN1_priv.pem + openssl genpkey -algorithm Ed25519 -out MANIFEST_OEM_ROOT_GEN1_priv.pem + +#. Extract public keys:: + + openssl pkey -in MANIFEST_APPLICATION_GEN1_priv.pem -pubout -out MANIFEST_APPLICATION_GEN1_pub.pem + openssl pkey -in MANIFEST_RADIOCORE_GEN1_priv.pem -pubout -out MANIFEST_RADIOCORE_GEN1_pub.pem + openssl pkey -in MANIFEST_OEM_ROOT_GEN1_priv.pem -pubout -out MANIFEST_OEM_ROOT_GEN1_pub.pem + +#. Check the required key IDs:: + + MANIFEST_PUBKEY_APPLICATION_GEN1 = 0x40022100 + MANIFEST_PUBKEY_APPLICATION_GEN2 = 0x40022101 + MANIFEST_PUBKEY_APPLICATION_GEN3 = 0x40022102 + MANIFEST_PUBKEY_OEM_ROOT_GEN1 = 0x4000AA00 + MANIFEST_PUBKEY_OEM_ROOT_GEN2 = 0x4000AA01 + MANIFEST_PUBKEY_OEM_ROOT_GEN3 = 0x4000AA02 + MANIFEST_PUBKEY_RADIOCORE_GEN1 = 0x40032100 + MANIFEST_PUBKEY_RADIOCORE_GEN2 = 0x40032101 + MANIFEST_PUBKEY_RADIOCORE_GEN3 = 0x40032102 + +#. Create a JSON input file with the ``generate_psa_key_attributes.py`` script: + + * For the application core:: + + 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 + + * For the radio core:: + + 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 + + * For the main root manifest:: + + 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 + + +The generated key data is stored in a JSON file, which serves as an input for the next step. + +Provisioning the keys +===================== + +nRF Util is used to provision the generated keys into the target device. +It takes the JSON file as input and injects it without validating its contents. +In this scenario, nRF Util functions as a transport layer, transferring the key data to the correct location in the device. + +The Secure Domain Firmware on the device handles the actual key provisioning using PSA Crypto's ``psa_import_key`` function. +Provisioning a key calls the function to import the key: + +* The ``metadata`` field from the JSON file is used for the function's attributes argument +* The ``value`` field is passed to the function's data argument +* The function's ``data_length`` is set to the length of the value field. + +To provision the keys from ``all_keys.json`` onto the KMU of the nRF54H20 SoC, use nRF Util as follows:: + + nrfutil device x-provision-nrf54h-keys --serial-number --key-file all_keys.json + +For more information on how to provision keys, see the `Provisioning keys for hardware KMU`_ page in the nRF Util documentation. diff --git a/doc/nrf/conf.py b/doc/nrf/conf.py index b13801c86807..1e0fe90b84d8 100644 --- a/doc/nrf/conf.py +++ b/doc/nrf/conf.py @@ -26,7 +26,7 @@ # General configuration -------------------------------------------------------- project = "nRF Connect SDK" -copyright = "2019-2024, Nordic Semiconductor" +copyright = "2019-2025, Nordic Semiconductor" author = "Nordic Semiconductor" version = release = os.environ.get("DOCSET_VERSION") diff --git a/doc/nrf/dev_model_and_contributions/adding_code.rst b/doc/nrf/dev_model_and_contributions/adding_code.rst index 867bf6b94a31..818c2dee4af5 100644 --- a/doc/nrf/dev_model_and_contributions/adding_code.rst +++ b/doc/nrf/dev_model_and_contributions/adding_code.rst @@ -162,7 +162,7 @@ This is demonstrated by the following code, that would be placed somewhere in yo - name: nrf repo-path: sdk-nrf remote: ncs - revision: 2.9.0-nRF54H20-rc1 + revision: 2.9.0-nRF54H20-1-rc2 import: true self: path: application @@ -189,7 +189,7 @@ For example: projects: - name: nrf remote: ncs - revision: 2.9.0-nRF54H20-rc1 + revision: 2.9.0-nRF54H20-1-rc2 import: true # Example for how to override a repository in the nRF Connect SDK with your own: - name: mcuboot diff --git a/doc/nrf/links.txt b/doc/nrf/links.txt index 1ed4ee9a6320..9f775ab0992f 100644 --- a/doc/nrf/links.txt +++ b/doc/nrf/links.txt @@ -436,7 +436,7 @@ .. _`nRF Connect SDK latest documentation`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/index.html .. _`known issues page on the main branch`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html -.. _`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 +.. _`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 .. _`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 .. _`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 .. _`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 @@ .. _`nRF socket options`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/nrf_modem/doc/sockets.html -.. _`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 +.. _`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 .. _`Repositories and revisions for v2.9.0`: https://docs.nordicsemi.com/bundle/ncs-2.9.0/page/nrf/releases_and_maturity/repository_revisions.html .. _`Repositories and revisions for v2.8.0`: https://docs.nordicsemi.com/bundle/ncs-2.8.0/page/nrf/releases_and_maturity/repository_revisions.html .. _`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 @@ .. _`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 .. _`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 -.. _`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 +.. _`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 .. _`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 .. _`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 .. _`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 @@ .. _`Programming application firmware using MCUboot serial recovery`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/programming_firmware_thingy91.html .. _`Programming application firmware on the nRF54L15 SoC`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/programming_nrf54L15.html .. _`Upgrading modem firmware using J-Link`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/programming_modem_9160.html +.. _`Provisioning keys for hardware KMU`: https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-device/guides/provisioning_keys.html .. _`anomaly 19`: https://docs.nordicsemi.com/bundle/errata_nRF5340_EngA/page/ERR/nRF5340/EngineeringA/latest/anomaly_340_19.html @@ -1591,8 +1592,8 @@ .. ### Source: files.nordicsemi.com -.. _`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 -.. _`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 +.. _`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 +.. _`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 .. _`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 .. _`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 .. _`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 @@ .. _`curl`: https://curl.se/ -.. _`nRF54H20 SoC Binaries v0.3.3`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.3.3.zip -.. _`nRF54H20 SoC Binaries v0.5.0`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.5.0.zip -.. _`nRF54H20 SoC Binaries v0.6.2`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.6.2.zip +.. _`nRF54H20 SoC binaries v0.3.3`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.3.3.zip +.. _`nRF54H20 SoC binaries v0.5.0`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.5.0.zip +.. _`nRF54H20 SoC binaries v0.6.2`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.6.2.zip .. _`nRF54H20 SoC binaries v0.6.5`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.6.5.zip -.. _`nRF54H20 SoC Binaries v0.7.0 for EngC DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engc.zip -.. _`nRF54H20 SoC Binaries v0.7.0 for EngB DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engb.zip +.. _`nRF54H20 SoC binaries v0.7.0 for EngC DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engc.zip +.. _`nRF54H20 SoC binaries v0.7.0 for EngB DKs`: https://files.nordicsemi.com/artifactory/SDSC/external/nrf54h20_soc_binaries_v0.7.0_engb.zip .. _`nRF54H20 SoC binaries v0.8.0`: https://files.nordicsemi.com/ui/native/SDSC/external/nrf54h20_soc_binaries_v0.8.0.zip .. _`nRF54H20 SoC binaries v0.9.1`: https://files.nordicsemi.com/ui/native/SDSC/external/nrf54h20_soc_binaries_v0.9.1.zip diff --git a/doc/nrf/protocols/matter/index.rst b/doc/nrf/protocols/matter/index.rst index ddadcb2e0c09..9312d4510733 100644 --- a/doc/nrf/protocols/matter/index.rst +++ b/doc/nrf/protocols/matter/index.rst @@ -23,9 +23,9 @@ For a full list of |NCS| and Matter versions, view the following table: +--------------------------+-----------------------------------------------------+------------------------+ | nRF Connect SDK version | Matter specification version | Matter SDK version | +==========================+=====================================================+========================+ - | v2.9.99 (latest) | :ref:`1.4.0 ` | 1.4.0.0 | + | |release| | :ref:`1.4.0 ` | 1.4.0.0 | +--------------------------+ | | - | |release| | | | + | v2.9.0-nRF54H20-1-rc2 | | | +--------------------------+ | | | v2.9.0 | | | +--------------------------+-----------------------------------------------------+------------------------+ diff --git a/doc/nrf/releases_and_maturity/abi_compatibility.rst b/doc/nrf/releases_and_maturity/abi_compatibility.rst index 582373abf173..434e964c2977 100644 --- a/doc/nrf/releases_and_maturity/abi_compatibility.rst +++ b/doc/nrf/releases_and_maturity/abi_compatibility.rst @@ -1,6 +1,6 @@ .. _abi_compatibility: -ABI Compatibility +ABI compatibility ################# .. contents:: @@ -18,7 +18,7 @@ When ABI compatibility is maintained, binaries of one component can interface co For example, adding a new function to a library is typically an ABI-compatible change, as existing binaries remain functional. 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. -ABI Compatibility Matrix for the nRF54H20 SoC Binaries +ABI compatibility matrix for the nRF54H20 SoC binaries ****************************************************** 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 * - |NCS| versions - Compatible nRF54H20 SoC binaries version * - |NCS| v2.9.0-nRF54H20-1-rc2 - - `nRF54H20 SoC Binaries v0.9.1`_, compatible with the nRF54H20 DK v0.9.0 and later revisions. + - `nRF54H20 SoC binaries v0.9.1`_, compatible with the nRF54H20 DK v0.9.0 and later revisions. * - |NCS| v2.9.0 - - `nRF54H20 SoC Binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions. + - `nRF54H20 SoC binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions. * - |NCS| v2.8.0 - - `nRF54H20 SoC Binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions. - `nRF54H20 SoC Binaries v0.7.0 for EngB DKs`_, compatible with the nRF54H20 DKs ranging from v0.8.0 to v0.8.2. + - `nRF54H20 SoC binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions. + `nRF54H20 SoC binaries v0.7.0 for EngB DKs`_, compatible with the nRF54H20 DKs ranging from v0.8.0 to v0.8.2. * - |NCS| v2.7.99-cs2 - - `nRF54H20 SoC Binaries v0.6.5`_ + - `nRF54H20 SoC binaries v0.6.5`_ * - |NCS| v2.7.99-cs1 - - `nRF54H20 SoC Binaries v0.6.2`_ + - `nRF54H20 SoC binaries v0.6.2`_ * - |NCS| v2.7.0 - - `nRF54H20 SoC Binaries v0.5.0`_ + - `nRF54H20 SoC binaries v0.5.0`_ * - |NCS| v2.6.99-cs2 - - `nRF54H20 SoC Binaries v0.3.3`_ + - `nRF54H20 SoC binaries v0.3.3`_ 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. Additionally, maintaining ABI compatibility allows the nRF54H20 SoC binary components to work together without recompilation when updating to newer |NCS| versions. -nRF54H20 SoC Binaries v0.9.1 changelog +nRF54H20 SoC binaries v0.9.1 changelog ************************************** +.. note:: + The nRF54H20 SoC binaries only support specific versions of the |NCS| and do not support rollbacks to a previous version. + Upgrading the nRF54H20 SoC binaries on your development kit might break the DK's compatibility with applications developed for previous versions of the |NCS|. + The following sections provide detailed lists of changes by component. Secure Domain Firmware (SDFW) v10.1.0 diff --git a/doc/nrf/releases_and_maturity/known_issues.rst b/doc/nrf/releases_and_maturity/known_issues.rst index aa007e706c1c..343f9f1b4dd4 100644 --- a/doc/nrf/releases_and_maturity/known_issues.rst +++ b/doc/nrf/releases_and_maturity/known_issues.rst @@ -75,7 +75,7 @@ KRKNWK-19647: nRF53 has high power consumption in sleep mode **Affected platforms:** nRF5340 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 KRKNWK-19459: AES crypt error occurs after a factory reset In the Sidewalk DUT application, authentication fails when starting FSK transport and performing a factory reset. @@ -189,7 +189,7 @@ KRKNWK-14299: NRPA MAC address cannot be set in Zephyr Bluetooth LE ============ -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-31528: Deadlock on system workqueue with ``tx_notify`` in host If the :kconfig:option:`CONFIG_BT_HCI_ACL_FLOW_CONTROL` Kconfig option is disabled, blocking of the system workqueue can cause a deadlock in the Bluetooth Host when running out of buffers in the HCI commands pool. @@ -210,7 +210,7 @@ NCSDK-31528: Deadlock on system workqueue with ``tx_notify`` in host This does not guarantee that the problem is solved, as multiple blocking calls may exhaust the buffer pool. You can also use the (experimental) :kconfig:option:`CONFIG_BT_CONN_TX_NOTIFY_WQ` Kconfig option to use a separate workqueue for connection TX notify processing. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 DRGN-24352: Missing disconnection events when HCI Controller to host flow control is enabled The :zephyr:code-sample:`bluetooth_hci_ipc` sample and :ref:`ipc_radio` application do not support stream flow control and drop bytes. @@ -220,7 +220,7 @@ DRGN-24352: Missing disconnection events when HCI Controller to host flow contro **Workaround:** Make sure that the value of the :kconfig:option:`CONFIG_BT_BUF_ACL_RX_COUNT` Kconfig option is smaller than the one for :kconfig:option:`CONFIG_BT_BUF_CMD_TX_COUNT` in your project. -.. rst-class:: v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 NCSDK-31095: Issues with the :kconfig:option:`CONFIG_SEGGER_SYSVIEW` Kconfig option Using this Kconfig option causes the data parameter in the macros :c:macro:`k_fifo_put`, :c:macro:`k_fifo_alloc_put`, :c:macro:`k_lifo_put`, and :c:macro:`k_lifo_alloc_put` to be evaluated multiple times. @@ -228,14 +228,15 @@ NCSDK-31095: Issues with the :kconfig:option:`CONFIG_SEGGER_SYSVIEW` Kconfig opt **Workaround:** Manually cherry-pick and apply the commit with the fix to ``sdk-zephyr`` (commit hash: ``f2f61094b5e1ba5b841d78e5dd88b2076fbc99ee`` from the `upstream Zephyr repository `_). -.. rst-class:: v2-9-0 v2-8-0 + +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 DRGN-23363: A flash operation executed on the system workqueue might result in ``-ETIMEDOUT`` A flash operation executed on the system workqueue might result in ``-ETIMEDOUT`` if there is an active Bluetooth LE connection. **Workaround:** Move flash operations to a different thread. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 NCSDK-30458: The Bluetooth LE applications built with the ``nordic-bt-rpc`` snippet do not work on nRF54H20 devices When using the ``nordic-bt-rpc`` sysbuild snippet for building Bluetooth LE applications for an nRF54H20 device in the Bluetooth RPC configuration, the build system creates an invalid memory map for the application core, resulting in a runtime failure. @@ -253,7 +254,7 @@ DRGN-23231: The Bluetooth subsystem may sometimes deadlock when a Bluetooth link **Affected platforms:** nRF5340 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 NCSDK-28239: On nRF54H20, a Bluetooth LE disconnect event is not generated once the central device (mobile phone) moves out of range while data is being transferred (during DFU) This will prevent the device from establishing new BLE connections. @@ -375,14 +376,14 @@ DRGN-23518: ACL reassembly may deadlock **Workaround:** Ensure that the value of :kconfig:option:`CONFIG_BT_BUF_ACL_RX_COUNT` is greater than the value of :kconfig:option:`CONFIG_BT_MAX_CONN`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 DRGN-23511: Building of multilink Bluetooth applications fails This happens when the :kconfig:option:`CONFIG_BT_BUF_ACL_RX_COUNT` Kconfig option is not explicitly set. **Workaround:** Set the Kconfig value explicitly. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-29354: Bluetooth traffic stalls while writing or erasing flash Using system workqueue for internal flash operations while Bluetooth is in use could result in Bluetooth hang or flash operation failures (timeout in MPSL flash synchronization). @@ -392,7 +393,7 @@ NCSDK-29354: Bluetooth traffic stalls while writing or erasing flash **Workaround:** Use a separate workqueue for connection TX notify processing (:kconfig:option:`CONFIG_BT_CONN_TX_NOTIFY_WQ`). -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 NCSDK-30959: The Bluetooth subsystem may deadlock when :kconfig:option:`CONFIG_BT_HCI_ACL_FLOW_CONTROL` is disabled When the :kconfig:option:`CONFIG_BT_HCI_ACL_FLOW_CONTROL` Kconfig option is disabled and a user application blocks any of the Bluetooth Host callbacks, the Bluetooth subsystem may deadlock. @@ -404,7 +405,7 @@ Bluetooth Mesh The issues in this section are related to the :ref:`ug_bt_mesh` protocol. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 NCSDK-30033: :ref:`bt_mesh_light_ctrl_srv_readme` never resumes the Lightness Controller automatically after it is disabled by a scene recall This occurs when the Lightness Controller is running and a scene recall for a scene with the Lightness Controller disabled is received. @@ -419,7 +420,7 @@ NCSDK-29893: Adding dynamic names to devices does not work The advertiser options to automatically add the name in the scan response and the advertising data is removed. The Mesh files :file:`proxy_srv.c` and :file:`pb_gatt_srv.c` were using ``BT_LE_ADV_OPT_USE_NAME`` that has been removed. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 NCSDK-28363: Local composition hash generator only considers the first portion of the Composition Data Page 0 (CDP0) when the size of CDP0 exceeds ``BT_TX_SDU_MAX`` This affects applications that use the Large Composition Data server together with the default DFU Metadata format enabled using the :kconfig:option:`CONFIG_BT_MESH_DFU_METADATA` Kconfig option. @@ -494,7 +495,7 @@ NCSDK-16579: Advertising Node Identity and Network ID might not work with the ex NCSDK-21780: Sensor types with floating point representation lose precision Sensor types with floating point representation lose precision when converted to ``sensor_value`` in the sensor API callbacks. -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-1 v1-9-0 v1-8-0 v1-7-1 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-1 v1-9-0 v1-8-0 v1-7-1 NCSDK-14399: Legacy advertiser can occasionally do more message retransmissions than requested When using the legacy advertiser, the stack sleeps for at least 50 ms after starting advertising a message, which might result in more messages to be advertised than requested. @@ -574,7 +575,7 @@ KRKNWK-19806: RPU recovery fails during Wi-Fi communication **Workaround:** Cherry-pick changes from PR #529 in the `Matter GitHub repository`_ . -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-28567: Swap time after DFU takes a very long time Due to the incorrect RRAM buffer configuration, the swap time after DFU can exceed three minutes. @@ -609,7 +610,7 @@ KRKNWK-19826: The Device Firmware Upgrade (DFU) fails for nRF5340 DK with RAM po **Workaround:** Set the :kconfig:option:`CONFIG_RAM_POWER_DOWN_LIBRARY` Kconfig option to ``n`` in the :file:`prj_release.conf` file of the application. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 KRKNWK-19388: The smart plug functionality of Matter Bridge application does not work with Apple Home application The additional functionality of a smart plug that runs alongside the Matter Bridge functionality is not visible in the Apple Home application. @@ -1099,7 +1100,7 @@ Thread The issues in this section are related to the :ref:`ug_thread` protocol. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 KRKNWK-19628: On nRF54H20, persistence of keys is not yet supported After rebooting the device, all persistent keys (Thread's network key) will be lost. @@ -1124,7 +1125,7 @@ KRKNWK-19036: High power consumption after parent loss **Workaround:** Manually cherry-pick and apply commit with fix to ``sdk-zephyr`` (commit hash: ``6c602a1bbd3b3f7811082bce391c6943663a2c64``). -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 KRKNWK-18612: nRF5340 sometimes fails to send a Child Update Response to an SSED child After performing an MLE Child Update Request by an SSED child, an nRF5340 parent sometimes does not respond with a Child Update Response. @@ -1284,7 +1285,7 @@ Wi-Fi The issues in this section are related to the :ref:`ug_wifi` protocol. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 SHEL-3345 : Wi-Fi Coex (Bluetooth LE and Thread) is broken The Wi-Fi Coex is broken for Bluetooth LE and Thread due to missing devicetree node in ``cpuapp``. @@ -1293,7 +1294,7 @@ SHEL-3345 : Wi-Fi Coex (Bluetooth LE and Thread) is broken **Affected platforms:** nRF7002 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-29650: Wi-Fi connection times are increased in ``_ns`` builds The latency has increased significantly in latest main branch. @@ -1303,21 +1304,21 @@ NCSDK-29650: Wi-Fi connection times are increased in ``_ns`` builds **Affected platforms:** nRF7002 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-29649: Flash firmware integrity check does not work due to Mbed TLS dependencies Due to this, nRF70 patches cannot be validated and corrupted patches can manifest in nRF70 bootup failures. **Affected platforms:** nRF7002 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-29651: nRF54H20 Legacy crypto not supported PSA crypto is used by default, which limits Wi-Fi security only up to WPA2. **Affected platforms:** nRF7002, nRF54H20 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 SHEL-3226: In nRF70 driver page docs, link to doxygen API has been removed The link will be brought back in coming releases. @@ -1342,7 +1343,7 @@ Zigbee The issues in this section are related to the :ref:`ug_zigbee` protocol. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 NCSIDB-1411: Clearing configuration data is not fully performed when processing the Leave Network command Configuration data of ZCL Reporting feature is not cleared when processing the leave network command, resulting in incomplete compliance with the specification. @@ -1369,7 +1370,7 @@ NCSIDB-1411: Clearing configuration data is not fully performed when processing ZB_ERROR_CHECK(zigbee_default_signal_handler(bufid)); break; -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 NCSIDB-1336: Zigbee Router device cannot rejoin after missing Network Key update or rotation If a Zigbee Router device does not receive a Network Key update or rotation messages (such as because of an ongoing reset or being powered off), it will not rejoin to a Zigbee Coordinator and will use old keys for communication. @@ -1473,26 +1474,26 @@ KRKNWK-16705: Router device is not fully operational in the distributed network **Workaround:** Add a call to the :c:func:`zb_enable_distributed` function in your application after setting Zigbee Router role for the device. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 KRKNWK-14024: Fatal error when the network coordinator factory resets in the Identify mode A fatal error occurs when the :ref:`Zigbee network coordinator ` triggers factory reset in the Identify mode. **Workaround:** Modify your application, so that the factory reset is requested only after the Identify mode ends. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 KRKNWK-12937: Activation of Sleepy End Device must be done at the very first commissioning procedure for Zigbee light switch sample After programming the :ref:`Zigbee light switch ` sample and its first commissioning, Zigbee End Device joins the Zigbee network as a normal End Device. Pressing **Button 3** does not switch the device to the Sleepy End Device configuration. **Workaround:** Keep **Button 3** pressed during the first commissioning procedure. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 KRKNWK-12615: Get Group Membership Command returns all groups the node is assigned to Get Group Membership Command returns all groups the node is assigned to regardless of the destination endpoint. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 KRKNWK-12115: Simultaneous commissioning of many devices can cause the Coordinator device to assert The Zigbee Coordinator device can assert when multiple devices are being commissioned simultaneously. @@ -1544,7 +1545,7 @@ KRKNWK-12522: Incorrect Read Attributes Response on reading multiple attributes When reading multiple attributes at once and the first one is not supported, the Read Attributes Response contains two records for the first supported attribute. The first one record has the Status field filled with Unsupported Attribute whereas the second record contains actual data. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 KRKNWK-12017: Zigbee End Device does not recover from broken rejoin procedure If the Device Announcement packet is not acknowledged by the End Device's parent, joiner logic is stopped and the device does not recover. @@ -1643,7 +1644,7 @@ KRKNWK-11602: Zigbee device becomes not operable after receiving malformed packe Given these two options, we recommend to upgrade your |NCS| version to the latest available one. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 KRKNWK-7723: OTA upgrade process restarting after client reset After the reset of OTA Upgrade Client, the client will start the OTA upgrade process from the beginning instead of continuing the previous process. @@ -1796,7 +1797,7 @@ Asset Tracker v2 The issues in this section are related to the :ref:`asset_tracker_v2` application. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-30983: :ref:`asset_tracker_v2` with :file:`overlay-lwm2m` (LwM2M overlay) reboots after GNSS fix This issue affects Asset Tracker v2 with the LwM2M overlay. @@ -1933,7 +1934,7 @@ Serial LTE Modem The issues in this section are related to the :ref:`serial_lte_modem` application. -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 NCSDK-20457: Modem traces captured through UART are corrupted if RTT logs are simultaneously captured When capturing modem traces through UART with the `Cellular Monitor app`_ and simultaneously capturing RTT logs, for example, with J-Link RTT Viewer, the modem trace misses packets, and captured packets might have incorrect information. @@ -1966,7 +1967,7 @@ NCSDK-24135: Serial LTE Modem (SLM) attempts to use UART hardware flow control e **Workaround:** Set the :ref:`CONFIG_SLM_UART_RX_BUF_SIZE ` Kconfig option to ``2048`` to ensure that there is adequate buffer space to receive traffic from the Connectivity bridge and disable the ``hw-flow-control`` from :file:`boards\thingy91_nrf9160_ns.overlay`. If even larger buffer spaces are required, set the :kconfig:option:`CONFIG_BRIDGE_BUF_SIZE` Kconfig option for Connectivity bridge and the :ref:`CONFIG_SLM_UART_RX_BUF_SIZE ` Kconfig option for SLM, must be set accordingly. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 NCSDK-23733: Full modem firmware update issue on the nRF91x1 DKs Failures of full modem firmware update on the nRF91x1 DK have been observed in certain conditions. @@ -2051,7 +2052,7 @@ NCSDK-25928: :ref:`nrf_desktop_hid_state` keeps sending empty HID reports to low **Workaround:** Manually cherry-pick and apply the commit with the fix from the ``main`` branch (commit hash: ``a87407fc29514b68a7bdaea5554f7b755466a77b``). -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0 NCSDK-8304: HID configurator issues for peripherals connected over Bluetooth LE to Linux host Using :ref:`nrf_desktop_config_channel_script` for peripherals connected to host directly over Bluetooth LE might result in receiving improper HID feature report ID. @@ -2196,35 +2197,35 @@ nRF5340 Audio The issues in this section are related to the :ref:`nrf53_audio_app` application. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 OCT-3179: CIS headset, potential for not establishing presentation synchronization lock in bidirectional mode If the CIS gateway is reset shortly after the headset has established synchronization lock, this issue may be triggered. **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 OCT-3174: Host on CIS gateway may throw assert if a connected headset is hard reset During a CIS stereo stream, if a headset suddenly disappears during the active stream, this issue may occur. **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 OCT-3152: Public address for broadcast source When trying to use a public address for the broadcast source, the address will still change on each boot and appears to be random. **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 OCT-2070: Detection issues with USB-C to USB-C connection Using USB-C to USB-C when connecting an nRF5340 Audio DK to PC is not correctly detected on some Windows systems. **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 OCT-2154: USB audio interface does not work correctly on macOS The audio stream is intermittent on the headset side after connecting the gateway to a Mac computer and starting the audio stream. @@ -2232,7 +2233,7 @@ OCT-2154: USB audio interface does not work correctly on macOS **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 OCT-2172: The headset volume is not stored persistently This means the volume will fall back to default level after a reset. @@ -2253,7 +2254,7 @@ OCT-2347: Stream reestablishment issues in CIS **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 OCT-2401: The HW codec has a variable (0-20 µs) audio interface (I2S) lock variability This will cause a static offset of the stream, which will cause an undesired extra L-R sync difference. @@ -2275,7 +2276,7 @@ OCT-2472: Headset fault upon gateway reset in the bidirectional stream mode **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 OCT-2501: Charging over seven hours results in error Since the nRF5340 Audio DK uses a large battery, the nPM1100 can go into error when charging time surpasses 7 hours. @@ -2286,7 +2287,7 @@ OCT-2501: Charging over seven hours results in error **Workaround:** To start the charging again, turn the nRF5340 Audio DK off and then on again. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 OCT-2539: Presentation delay may not work as expected under some configurations The data is not presented at the correct time. @@ -2316,7 +2317,7 @@ OCT-2569: BIS headset stuck if toggling gateway power quickly **Workaround:** Reset BIS headset -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 OCT-2585: Initial L-R sync may lock with an offset The left and right headset may lock as intended, but there will be a small static time offset between the two headsets. @@ -2391,14 +2392,14 @@ OCT-2897: Interleaved packing issue **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 OCT-3006: Setting a custom bitrate using :kconfig:option:`CONFIG_BT_AUDIO_BITRATE_UNICAST_SINK` will have no effect This is because the application reverts to one of the BAP presets. **Affected platforms:** nRF5340 Audio DK -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 OCT-3248: A race condition between capturing timers and the RTC tick resetting the HF timer This issue might cause time to jump ahead by about 30 µs. @@ -2583,7 +2584,7 @@ NCSDK-18112: :ref:`bluetooth_central_dfu_smp` sample cannot do discovery on the **Workaround:** Enable the legacy LLCP mechanism (:kconfig:option:`CONFIG_BT_LL_SW_LLCP_LEGACY`). -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0 v0-4-0 v0-3-0 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0 v0-4-0 v0-3-0 NCSDK-19942: HID samples do not work with Android 13 Bluetooth samples and applications that are set up for the HIDS use case and have the Bluetooth Privacy feature enabled (:kconfig:option:`CONFIG_BT_PRIVACY`) disconnect after a short period or enter a connection-disconnection loop when you try to connect to them from a device that is running Android 13. @@ -2593,7 +2594,7 @@ NCSDK-19942: HID samples do not work with Android 13 * :ref:`fast_pair_input_device` * Fast Pair configurations of the :ref:`nrf_desktop` application -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0 v0-4-0 v0-3-0 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0 v0-4-0 v0-3-0 NCSDK-26669: Reconnection with HID devices that have privacy enabled may not work on Android 14 If an Android 14 device is disconnected from the HID device without user intervention through the Bluetooth UI from Android settings (for example, due to a connection timeout caused by the HID device rebooting), the device faces issues. @@ -2778,7 +2779,7 @@ Antenna switching does not work on targets ``nrf5340dk_nrf5340_cpuapp`` and ``nr Bluetooth Mesh samples ====================== -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 NCSDK-26844: :ref:`ble_mesh_dfu_distributor` sample is not able to complete self-update When attempting to use the :ref:`ble_mesh_dfu_distributor` sample to perform a self-update, the DFU process is not completed successfully. @@ -2813,7 +2814,7 @@ NCSDK-21590: :ref:`bluetooth_mesh_sensor_client` sample does not compile for nRF Cellular samples ================ -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-30050: The :ref:`nrf_cloud_rest_fota` sample with experimental SMP FOTA support enabled crashes with a secure fault This happens approximately one out of five times during an SMP FOTA update. @@ -2835,7 +2836,7 @@ IRIS-7398: The :ref:`nrf_cloud_multi_service` sample does not support using the **Affected platforms:** nRF9161 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 IRIS-7381: :ref:`nrf_cloud_rest_cell_location` sample might attempt to take a neighbor cell measurement when a measurement is already in progress If cell information changes during a neighbor cell measurement, the sample will attempt to start a new measurement, resulting in warning and error log messages. @@ -2892,7 +2893,7 @@ KRKNWK-19806: RPU recovery fails on the nRF5340 DK with nRF7002 EK shield due to **Workaround:** Cherry-pick changes from PR #19826 in the `sdk-nrf`_ repository. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 KRKNWK-19861: ICD DSLS does not work with the :ref:`matter_smoke_co_alarm_sample` sample According to the sample's documentation the ICD DSLS can be enabled by setting the :kconfig:option:`CONFIG_CHIP_ICD_DSLS_SUPPORT` Kconfig option to ``y``. @@ -3062,7 +3063,7 @@ The issues in this section are related to :ref:`libraries`. Binary libraries ================ -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 NCSDK-26682: In the Verizon network, the :ref:`liblwm2m_carrier_readme` library fails to complete bootstrap process unless the same device has previously completed a bootstrap This is because one of the required pre-shared keys is not generated unless there is a pre-existing one in the modem. @@ -3233,7 +3234,7 @@ NCSDK-15512: Modem traces retrieval incompatible with TF-M Libraries for networking ======================== -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 CIA-1400: :ref:`lib_nrf_cloud` FOTA and P-GPS downloads over CoAP might fail to resume nRF Cloud FOTA and P-GPS downloads over CoAP might fail to resume at the correct file offset if the download is interrupted. @@ -3265,7 +3266,7 @@ NCSDK-28192: Hardfault in :c:func:`coap_codec_agnss_encode` ** Workaround:** Apply the fix from `sdk-nrf PR #16242`_. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 CIA-351: Connectivity issues with :ref:`lib_azure_iot_hub` If a ``device-bound`` message is sent to the device while it is in the LTE Power Saving Mode (PSM), the TCP connection will most likely be terminated by the server. @@ -3297,7 +3298,7 @@ NCSDK-23315: The :ref:`bt_le_adv_prov_readme` has an incorrect range and default **Workaround:** Manually cherry-pick and apply the commit with the fix from the ``main`` branch (commit hash: ``a8b668e82837295962348e9e681125c2ae11bb4e``). -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 NCSDK-23682: The Fast Pair Seeker might be unable to bond again after losing the bonding information multiple times If the :kconfig:option:`CONFIG_BT_SETTINGS_CCC_LAZY_LOADING` Kconfig option is disabled on the Fast Pair Provider side, the Fast Pair Seeker that uses the RPA address to connect with the Provider might be unable to bond again after losing the bonding information multiple times. @@ -3344,7 +3345,7 @@ The time returned by :ref:`lib_date_time` library becomes incorrect after one we Security ======== -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-29559: KMU slots 0-2 cannot be used to store keys in nRF54L15 The application cannot use KMU slots 0-2 to store keys in the nRF54L15. @@ -3361,12 +3362,12 @@ Build system The issues in this section are related to :ref:`app_build_system`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-30119: For nRF54L15 SoC, dynamic partitioning for a project building with MCUboot's direct-xip mode is not supported Static partition manager file is required for building such project. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 NCSDK-28495: Sysbuild runs CMake code before processing application :file:`sysbuild.cmake` When using a :file:`sysbuild.cmake` file to set configuration for images that have variants, this extra configuration might end up not being applied to the variant image, causing the images to be incompatible. @@ -3377,28 +3378,28 @@ NCSDK-28495: Sysbuild runs CMake code before processing application :file:`sysbu * If applying configuration to MCUboot with application secure boot enabled, also apply the configuration to ``s1_image``. * If applying configuration to the default image with application secure boot enabled and MCUboot disabled, also apply the configuration to ``s1_image``. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 NCSDK-28462: MCUboot signing configuration cannot be updated without pristine build When using :ref:`configuration_system_overview_sysbuild`, the MCUboot signing configuration cannot be updated in an already configured project. **Workaround:** Perform a :ref:`pristine build ` to change any of the MCUboot signing configuration. Do not update it using menuconfig, guiconfig or the nRF Kconfig GUI, and instead :ref:`provide it on the command line ` when configuring the application if it needs setting manually. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 NCSDK-28461: Sysbuild partition manager file changes cannot be propagated to builds unless they are pristine When using :ref:`configuration_system_overview_sysbuild` and a :ref:`partition_manager` file, the Partition Manager configuration for things such as MCUboot signing will not be updated if the Partition Manager configuration is changed in an already configured project. **Workaround:** Perform a :ref:`pristine build ` after changing configuration in Partition Manager files. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 NCSDK-28451: Sysbuild silently does not use relative path (relative to application config dir) user-specified (PM_STATIC_YML_FILE) static PM files When building an application using :ref:`configuration_system_overview_sysbuild` with a :ref:`static partition file ` specified using ``PM_STATIC_YML_FILE`` with a relative path, the relative path will be relative to the sysbuild folder in Zephyr, not to the application configuration directory, and the file will silently be ignored. **Workaround:** Use an absolute path when specifying the static partition file and ensure that the output shows the file as being used. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 NCSDK-20567: When building an application for MCUboot, the build system does not check whether the compiled application is too big for being an update image In this case the update cannot be applied, because the swap algorithm requires some free space in the secondary slot (even if the image fits inside the slot). @@ -3557,7 +3558,7 @@ NCSDK-23761: MCUboot fails to boot when both the :kconfig:option:`CONFIG_MCUBOOT **Workaround:** To fix the issue, disable either the :kconfig:option:`CONFIG_MCUBOOT_HW_DOWNGRADE_PREVENTION` or :kconfig:option:`CONFIG_BOOT_FIH_PROFILE_LOW` Kconfig option in MCUboot. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 SHEL-1352: Incorrect base address used in the OTP TX trim coefficients Incorrect base address used for TX trim coefficients in the One-Time Programmable (OTP) memory results in transmit power deviating by +/- 2 dB from the target value. @@ -3622,7 +3623,7 @@ DFU and FOTA The issues in this section are related to :ref:`app_dfu`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 NCSDK-31270: [suit] Entering the recovery mode by **HW** button press is disabled by default This is done for samples with external flash enabled. @@ -3631,7 +3632,7 @@ NCSDK-31270: [suit] Entering the recovery mode by **HW** button press is disable **Workaround:** In the manifest file, enable support for entering the recovery mode by **HW** button press. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 NCSDK-31300: [suit] Leaving the recovery mode using the default DFU candidate is not possible For samples with external flash and the Cache Pull mode, it is not possible to leave the recovery mode using the default DFU candidate. @@ -3640,7 +3641,7 @@ NCSDK-31300: [suit] Leaving the recovery mode using the default DFU candidate is **Workaround:** In such cases, preparation of a custom DFU candidate is needed. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 NCSDK-31135: [suit] DFU through the external flash is failing sporadically DFU through the external flash is failing sporadically, although no error is reported. @@ -3649,7 +3650,7 @@ NCSDK-31135: [suit] DFU through the external flash is failing sporadically **Workaround:** Repeat DFU procedure. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 NCSDK-30976: [suit] Update candidate envelope with oversized manifest are not rejected An update candidate envelope with a manifest that is too large to fit into its applicable storage slot is still attempted to be installed. @@ -3657,7 +3658,7 @@ NCSDK-30976: [suit] Update candidate envelope with oversized manifest are not re **Affected platforms:** nRF54H20 -.. rst-class:: v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-30161: Combination of :kconfig:option:`CONFIG_ASSERT`, :kconfig:option:`CONFIG_SOC_NRF54H20_GPD`, and external flash causes an assertion during boot time A combination of these three will cause an assert. @@ -3667,7 +3668,7 @@ NCSDK-30161: Combination of :kconfig:option:`CONFIG_ASSERT`, :kconfig:option:`CO **Workaround:** Set :kconfig:option:`CONFIG_ASSERT` to ``n`` or :kconfig:option:`CONFIG_SOC_NRF54H20_GPD` to ``n``. -.. rst-class:: v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-30117: [suit] It is possible to declare a MEM component pointing to a memory region not assigned to particular core An update candidate with envelope for APP/RAD containing declared MEM component that points to memory range outside of space assigned to a particular core is accepted and installed. @@ -3677,7 +3678,7 @@ NCSDK-30117: [suit] It is possible to declare a MEM component pointing to a memo **Workaround:** Declare MEM components pointing to correct regions. This issue will be fixed in further releases. -.. rst-class:: v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-29682: [suit] cose-alg-sha-512 is not supported SUIT envelope using digest with algorithm cose-alg-sha-512 is rejected due to unsupported algorithm. @@ -3686,7 +3687,7 @@ NCSDK-29682: [suit] cose-alg-sha-512 is not supported **Workaround:** Use sha-256 until next release of Nordic binaries where this issue will be fixed. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-28241: DFU transfer starts and fails if previous transfer is still in progress Since the mobile application implements the :guilabel:`Cancel` button, it is possible to restart the transfer on the mobile phone even if the first transfer is still in progress (image fetcher waits for a timeout event or the external flash is being erased, which takes ~5 seconds). @@ -3696,7 +3697,7 @@ NCSDK-28241: DFU transfer starts and fails if previous transfer is still in prog **Workaround:** Repeat DFU transfer attempt - the next transfer attempt will succeed. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 NCSDK-21790: Errors during DFU when using nRF Connect for mobile app MCUmgr is incorrectly reporting an error when DFU is performed using the nRF Connect for mobile app. @@ -3741,7 +3742,7 @@ NCSDK-18422: Serial recovery fails to write to slots in QSPI NCSDK-18108: ``s1`` variant image configuration mismatch If an image with an ``s1`` variant is configured and the ``s0`` image configuration is changed using menuconfig, these changes will not be reflected in the ``s1`` configuration, which can lead to a differing build configuration or the build does not upgrade. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 NCSDK-11308: Powering off device immediately after serial recovery of the nRF53 network core firmware results in broken firmware The network core will not be able to boot if the device is powered off too soon after completing a serial recovery update procedure of the network core firmware. @@ -3858,7 +3859,7 @@ MCUboot The issues in this section are related to :ref:`MCUboot `. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-30867: KMU keys are not protected against being revoked by the application that is running in secure mode You must provision *locked* keys if you cannot trust the application running in secure mode. @@ -3874,7 +3875,7 @@ NCSDK-30263: direct-xip with revert does not work on nRF54L15 **Workaround:** Manually cherry-pick the commit ``ff0e8fabe1566349dbfd1786b31b325b46be205a`` from the main branch of the ``sdk-nrf`` repository. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-31066: MCUboot updates take a long time The current implementation of MCUboot does not optimally utilize RRAM, which causes longer update times. @@ -3883,7 +3884,7 @@ NCSDK-31066: MCUboot updates take a long time **Workaround:** Set MCUBoot's Kconfig option :kconfig:option:`CONFIG_NRF_RRAM_WRITE_BUFFER_SIZE` to ``32``. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 NCSDK-20567: Partitioning limitation with MCUboot swap move The swap algorithm in MCUboot (especially the default one - swap_move) requires some extra space to perform the swap move operation, so not entire partition space can be spent for the image. @@ -3894,7 +3895,7 @@ NCSDK-20567: Partitioning limitation with MCUboot swap move Typically, for the nRF52, nRF53, and nRF91 devices, the size of the application must be less than ``mcuboot_primary_size - 80 - (mcuboot_primary_size/ 4096) * 12 -4096``. Some additional margin is suggested. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 NCSIDB-1194: MCUboot not properly disabling UARTE instances Increased power consumption may be observed (400 µA). @@ -3924,7 +3925,7 @@ Crypto The issues in this section are related to :ref:`nrfxlib:crypto`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 NSCDK-26412: Updating to TF-M 2.0 using Mbed TLS 3.5.2 introduced a regression in resolving legacy crypto configurations from ``PSA_WANT_ALG_XXXX`` configurations Wi-Fi samples enabling OpenThread are affected by this bug as well as possible use cases with a dependency on some legacy features while using PSA crypto APIs. @@ -3948,7 +3949,7 @@ NCSDK-22091: Selecting both :kconfig:option:`CONFIG_NORDIC_SECURITY_BACKEND` and **Workaround:** Manually define ``PSA_CORE_BUILTIN`` in the file :file:`nrf_security/configs/legacy_crypto_config.h.template`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 NCSDK-22593: Selecting :kconfig:option:`CONFIG_PSA_WANT_ALG_CCM` without :kconfig:option:`CONFIG_MBEDTLS_AES_C` causes a build failure Selecting :kconfig:option:`CONFIG_PSA_WANT_ALG_CCM` without :kconfig:option:`CONFIG_MBEDTLS_AES_C` results in a build failure due to unsatisfied dependencies in :file:`check_config.h`. @@ -4111,7 +4112,7 @@ Modem library The issues in this section are related to :ref:`nrfxlib:nrf_modem`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-29993: The :c:func:`nrf_send` function with ``NRF_MSG_WAITACK`` flag will incorrectly set the ``errno`` to ``0xBAADBAAD`` if the socket is closed before the send operation finishes This will trigger an assert in :c:func:`nrf_modem_os_errno_set` if asserts are enabled. @@ -4122,7 +4123,7 @@ NCSDK-29993: The :c:func:`nrf_send` function with ``NRF_MSG_WAITACK`` flag will **Workaround:** Disable asserts or remove the assert in :c:func:`nrf_modem_os_errno_set`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 NCSDK-10106: Elevated current consumption when using applications without :ref:`nrfxlib:nrf_modem` on nRF9160 When running applications that do not enable :ref:`nrfxlib:nrf_modem` on nRF9160 with build code B1A, current consumption will stay at 3 mA when in sleep. @@ -4169,7 +4170,7 @@ Multiprotocol Service Layer (MPSL) The issues in this section are related to :ref:`nrfxlib:mpsl`. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 UARTE will have a frequency error beyond the specific limits In low temperatures and if :ref:`nrfxlib:mpsl` (MPSL) (Bluetooth LE, 802.15.4) is not used, UARTE will have a frequency error beyond the specific limits. @@ -4183,14 +4184,14 @@ UARTE will have a frequency error beyond the specific limits DRGN-22314: MPSL can encounter fatal errors and crashes when used without SoftDevice Controller or the :ref:`nrfxlib:nrf_802154` This happens because of the of the allocation functions in the files :file:`nrfx_ppi.h` and :file:`nrfx_dppi.h` can allocate channels reserved by MPSL. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 DRGN-18247: Assertion with :c:enumerator:`MPSL_CLOCK_HF_LATENCY_BEST` When setting the ramp-up time of the high-frequency crystal oscillator with :c:enumerator:`MPSL_CLOCK_HF_LATENCY_BEST`, an assert in MPSL occurs. **Workaround:** Use :c:enumerator:`MPSL_CLOCK_HF_LATENCY_TYPICAL` instead of :c:enumerator:`MPSL_CLOCK_HF_LATENCY_BEST` when setting the time it takes for the HFCLK to ramp up. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 DRGN-15979: :kconfig:option:`CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION` must be set when :kconfig:option:`CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC` is set MPSL requires RC clock calibration to be enabled when the RC clock is used as the Low Frequency clock source. @@ -4201,7 +4202,7 @@ DRGN-14153: Radio Notification power performance penalty The Radio Notification feature has a power performance penalty proportional to the notification distance. This means an additional average current consumption of about 600 µA for the duration of the radio notification. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 KRKNWK-8842: MPSL does not support nRF21540 revision 1 or older The nRF21540 revision 1 or older is not supported by MPSL. @@ -4282,7 +4283,7 @@ DRGN-11059: Front-end module API not implemented for SoftDevice Controller The issues in this section are related to :ref:`nrfxlib:nrf_802154`. In addition to the known issues listed here, see also :ref:`802.15.4 Radio driver limitations ` for permanent limitations. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 KRKNWK-19574: nRF 802.15.4 Radio Driver stuck in ``RADIO RXDISABLE`` state The nRF 802.15.4 Radio Driver might get stuck in the function :c:func:`wait_until_radio_disabled` while waiting for the radio peripheral transition from state ``RXDISABLE`` to ``DISABLED``. @@ -4292,7 +4293,7 @@ KRKNWK-19574: nRF 802.15.4 Radio Driver stuck in ``RADIO RXDISABLE`` state **Affected platforms:** nRF54L Series -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 KRKNWK-19689: nRF 802.15.4 Radio Driver transmits frames without ensuring ``CLOCK.EVENTS_XOTUNED`` This issue affects only these transmissions that are started from sleep state and are not preceded by an automatic CCA operation. @@ -4551,7 +4552,7 @@ DRGN-21962: Assert when using SPI FEM with Coded PHY on nRF53 Series devices **Affected platforms:** nRF5340, Thingy:53 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 DRGN-21293: The LE Read ISO TX Sync command is implemented according to the raised errata ES-23138 In ES-23138, the return parameter ``TX_Time_Stamp`` is used as the SDU synchronization reference of the SDU previously scheduled for transmission. @@ -4659,7 +4660,7 @@ DRGN-17562: One of the LE Transmit Power Reporting Events might not be reported When multiple LE Transmit Power Reporting Events are generated at the same time for the same PHY, one of these events will be missed. This will occur only when there are simultaneous remote and local power level changes on the same PHY. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 DRGN-19039: Multirole advertiser not seen by peer in some cases This can happen when the controller attempts to reschedule the advertising events due to scheduling conflicts with the scanner or initiator and both of the following apply: @@ -4762,7 +4763,7 @@ DRGN-18655: Wrongly set the address if calling :c:func:`bt_ctlr_set_public_addr` DRGN-18568: Using :kconfig:option:`CONFIG_MPSL_FEM` Kconfig option lowers the value of radio output power The actual value is lower than the default one in case the :kconfig:option:`CONFIG_BT_CTLR_TX_PWR_ANTENNA` or :kconfig:option:`CONFIG_BT_CTLR_TX_PWR` Kconfig options are used together with the :kconfig:option:`CONFIG_MPSL_FEM` Kconfig option. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 DRGN-16013: Initiating connections over extended advertising is not supported when external radio coexistence and FEM support are enabled The initiator can assert when initiating a connection to an extended advertiser when both external radio coexistence and FEM are enabled. @@ -5262,7 +5263,7 @@ Trusted Firmware-M (TF-M) The issues in this section are related to the TF-M implementation in the |NCS|. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 NCSDK-29095: Writing assets to NVM using TF-M causes increased interrupt latencies Writes to NVM provoke increased latencies even for the highest-priority interrupts. @@ -5277,7 +5278,7 @@ NCSDK-29095: Writing assets to NVM using TF-M causes increased interrupt latenci **Workaround:** Write persistent assets using the PSA APIs only when there are no ongoing time-critical operations. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 CIA-1182: TF-M flash partition overflow When building for Thingy:91 and enabling debug optimizations (or enabling Debug build in the VS code extension), the TF-M flash partition will overflow. @@ -5337,7 +5338,7 @@ NRFJPROG-454: TF-M might fail to reset when using nrfjprog version 10.22.x on nR nrfjprog -f nrf91 --debugreset -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 NCSDK-18321: TF-M PSA architecture tests do not build with CMake v3.25.x The :ref:`tfm_psa_test` fails to build with CMake version 3.25.x with missing header files. @@ -5445,7 +5446,7 @@ NCSDK-12483: Missing debug symbols NCSDK-12342: Potential SecureFault exception while accessing protected storage When accessing protected storage, a SecureFault exception is sometimes triggered and execution halts. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 NCSDK-11195: Build errors when enabling :kconfig:option:`CONFIG_BUILD_WITH_TFM` option Enabling the :kconfig:option:`CONFIG_BUILD_WITH_TFM` Kconfig option in SES project configuration or using ``west -t menuconfig`` results in build errors. @@ -5605,7 +5606,7 @@ NCSDK-6832: SMP Server sample fails upon initialization Other issues ************ -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 KRKNWK-31013: Issues with ``nrfutil trace`` and missing STM stream information on the nRF54H20 SoC While running ``nrfutil trace`` without resetting any domain, the tool can synchronize against Coresight packets and the underlying STPv2 protocol. @@ -5614,7 +5615,7 @@ KRKNWK-31013: Issues with ``nrfutil trace`` and missing STM stream information o **Affected platforms:** nRF54H20 -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 KRKNWK-31038: Instruction trace reliability issues during ETM debugging on the nRF54H20 SoC During ETM debugging, disconnecting and reconnecting to the device often causes the instruction trace to fail to appear reliably. @@ -5622,7 +5623,7 @@ KRKNWK-31038: Instruction trace reliability issues during ETM debugging on the n **Affected platforms:** nRF54H20 - .. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 + .. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-28152: TPIU Trace Signal Skew on the nRF54H20 SoC Segger TPIU tracing on the nRF54H20 DK encounters instability due to a minimal skew between clock and data signals. @@ -5631,7 +5632,7 @@ NCSDK-28152: TPIU Trace Signal Skew on the nRF54H20 SoC **Workaround:** Adjusting the TPIU trace delay on SEGGER's J-Trace Pro can improve signal stability, enhancing ETM capture reliability. For more information on adjusting trace timing, refer to the SEGGER Wiki's `Adjusting Trace Timings and General Troubleshooting`_ section. -.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 +.. rst-class:: v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 NCSDK-30095: Cannot flash a device if the ``nrfutil device x-adac-discovery`` command is called before flashing It leaves the device into ``RomOperation`` mode. @@ -5719,7 +5720,7 @@ KRKNWK-16503: OTA DFU using the iOS Home app (over UARP) does not work on the nR **Workaround:** Manually cherry-pick and apply commit from the main branch (commit hash: ``09874a36edf21ced7d3c9356de07df6f0ff3d457``). -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 KRKNWK-13010: Dropping from Thread to Bluetooth LE takes too long Dropping from Thread to Bluetooth LE, after a Thread Border Router is powered off, takes much longer for FTD accessories than estimated in TCT030 test case. @@ -5756,14 +5757,14 @@ NCSDK-13947: Net core downgrade prevention does not work on nRF5340 KRKNWK-13607: Stateless switch application crashes upon factory reset When running Thread test suit on the stateless switch application, the CI crashes upon factory reset. -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 KRKNWK-13249: Unexpected assertion in HAP Bluetooth Peripheral Manager When Bluetooth LE layer emits callback with a connect or disconnect event, one of its parameters is an underlying Bluetooth LE connection object. On rare occasions, this connection object is no longer valid by the time it is processed in HomeKit, and this results in assertion. There is no proven workaround yet. -.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0-nRF54H20-rc1 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 +.. rst-class:: wontfix v2-9-0-nRF54H20-1-rc2 v2-9-0 v2-8-0 v2-7-0 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 KRKNWK-11729: Stateless switch event characteristic value not handled according to specification in Bluetooth LE mode The stateless programmable switch application does not handle the value of the stateless switch event characteristic in the Bluetooth LE mode according to the specification. diff --git a/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_application.rst b/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_application.rst index 7c7b49186ca1..1b5276aaa76f 100644 --- a/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_application.rst +++ b/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_application.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_cs3_to_2_6_99_cs2_app: Migrate your application to |NCS| v2.6.99_cs2 (for v2.4.99-cs3 users) diff --git a/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_environment.rst b/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_environment.rst index 6cb1e79c1ca6..575cd6d8c25c 100644 --- a/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_environment.rst +++ b/doc/nrf/releases_and_maturity/migration/2.4.99-cs3_to_2.6.99-cs2/migration_guide_2.4.99-cs3_to_2.6.99-cs2_environment.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_cs3_to_2_6_99_cs2_env: Update your development environment for |NCS| v2.6.99_cs2 (for v2.4.99-cs3 users) diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_1.x_to_2.x.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_1.x_to_2.x.rst index 667d89d834ad..ee3ccda30e55 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_1.x_to_2.x.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_1.x_to_2.x.rst @@ -1,3 +1,5 @@ +:orphan: + .. _ncs_2.0.0_migration: Migration notes for |NCS| v2.0.0 diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_2.4.99-cs3_to_2.6.99-cs2.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_2.4.99-cs3_to_2.6.99-cs2.rst index a5791574fac8..2fb0f6413515 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_2.4.99-cs3_to_2.6.99-cs2.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_2.4.99-cs3_to_2.6.99-cs2.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_cs3_to_2_6_99_cs2: Migration notes for |NCS| v2.6.99_cs2 for v2.4.99-cs3 users diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_2.5.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_2.5.rst index b7f4539c88be..b2cac995fd0b 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_2.5.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_2.5.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_2.5: Migration guide for |NCS| v2.5.0 diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst index d32a2ceab876..28c1318ccd70 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_2.6: Migration guide for |NCS| v2.6.0 diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_2.7.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_2.7.rst index f6512253d82d..abf3dfa28e46 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_2.7.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_2.7.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_2.7: Migration guide for |NCS| v2.7.0 diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_2.8.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_2.8.rst index 39bb523ae375..0d0390131b15 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_2.8.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_2.8.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_2.8: Migration guide for |NCS| v2.8.0 @@ -155,8 +157,8 @@ nRF54H20 SoC binaries 1. Download the nRF54H20 SoC binaries v0.7.0: - * `nRF54H20 SoC Binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions - * `nRF54H20 SoC Binaries v0.7.0 for EngB DKs`_, compatible with the nRF54H20 DKs ranging from v0.8.0 to v0.8.2. + * `nRF54H20 SoC binaries v0.7.0 for EngC DKs`_, compatible with the nRF54H20 DK v0.8.3 and later revisions + * `nRF54H20 SoC binaries v0.7.0 for EngB DKs`_, compatible with the nRF54H20 DKs ranging from v0.8.0 to v0.8.2. .. note:: On MacOS, ensure that the ZIP file is not unpacked automatically upon download. diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nrf54h20-rc1.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nRF54H20-1-rc2.rst similarity index 71% rename from doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nrf54h20-rc1.rst rename to doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nRF54H20-1-rc2.rst index 92dc7bd423ab..5bf48990717a 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nrf54h20-rc1.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.0-nRF54H20-1-rc2.rst @@ -1,13 +1,15 @@ -.. _migration_2.9.0-nrf54h20-rc1: +:orphan: -Migration guide for |NCS| v2.9.0-nRF54H20-rc1 -############################################# +.. _migration_2.9.0-nRF54H20-1-rc2: + +Migration guide for |NCS| v2.9.0-nRF54H20-1-rc2 +############################################### .. contents:: :local: :depth: 3 -This document describes the changes required or recommended when migrating your nRF54H20 application from the |NCS| v2.8.0 to the |NCS| v2.9.0-nRF54H20-rc1. +This document describes the changes required or recommended when migrating your nRF54H20 application from the |NCS| v2.8.0 to the |NCS| v2.9.0-nRF54H20-1-rc2. .. HOWTO @@ -21,7 +23,7 @@ This document describes the changes required or recommended when migrating your * Change1 and description * Change2 and description -.. _migration_2.9.0-nrf54h20-rc1_required: +.. _migration_2.9.0-nRF54H20-1-rc2_required: Required changes **************** @@ -38,7 +40,7 @@ DK compatibility .. toggle:: - * The |NCS| v2.9.0-nRF54H20-rc1 is compatible only with the Engineering C - v0.9.0 and later revisions of the nRF54H20 DK, PCA10175. + * The |NCS| v2.9.0-nRF54H20-1-rc2 is compatible only with the Engineering C - v0.9.0 and later revisions of the nRF54H20 DK, PCA10175. Check the version number on your DK's sticker to verify its compatibility with the |NCS|. Dependencies @@ -57,55 +59,14 @@ SDK and toolchain #. Click :guilabel:`SETTINGS` in the navigation bar to specify where you want to install the |NCS|. #. In :guilabel:`SDK ENVIRONMENTS`, click the :guilabel:`Install` button next to the |NCS| version |release|. -nRF54H20 SoC binaries -+++++++++++++++++++++ - -.. toggle:: - - * The *nRF54H20 SoC binaries* bundle has been updated to version 0.8.0. - - To update the SoC binaries bundle of your development kit while in Root of Trust, do the following: - - 1. Download the `nRF54H20 SoC Binaries v0.8.0`_. - - .. note:: - On macOS, ensure that the ZIP file is not unpacked automatically upon download. - - #. Purge the device as follows:: - - nrfutil device recover --core Application --serial-number - nrfutil device recover --core Network --serial-number - - #. Erase the device as follows:: - - nrfutil device erase --all --core Network --serial-number - nrfutil device erase --all --core Application --serial-number - nrfutil device reset --reset-kind RESET_PIN --serial-number - - #. Run ``west update``. - #. Move the correct :file:`.zip` bundle to a folder of your choice, then run nRF Util to program the binaries using the following command:: - - nrfutil device x-suit-dfu --firmware nrf54h20_soc_binaries_v0.8.0.zip --serial-number - - #. Purge the device again as follows:: - - nrfutil device recover --core Application --serial-number - nrfutil device recover --core Network --serial-number - - #. Erase the device again as follows:: - - nrfutil device erase --all --core Network --serial-number - nrfutil device erase --all --core Application --serial-number - nrfutil device reset --reset-kind RESET_PIN --serial-number - -nrfutil -+++++++ +nRF Util +++++++++ .. toggle:: - * ``nrfutil`` has been updated to version 7.13.0. + * ``nrfutil`` has been updated to v7.13.0. - Install nRF Util version 7.13.0 as follows: + Install nRF Util v7.13.0 as follows: 1. Download the nRF Util executable file from the `nRF Util development tool`_ product page. #. Add nRF Util to the system path on Linux and macOS, or environment variables on Windows, to run it from anywhere on the system. @@ -127,41 +88,77 @@ nrfutil For more information, see the `nRF Util`_ documentation. -nrfutil device -++++++++++++++ +nRF Util device ++++++++++++++++ .. toggle:: - * ``nrfutil device`` has been updated to version 2.7.10. + * nRF Util ``device`` command has been updated to v2.7.10. - Install the nRF Util ``device`` command version 2.7.10 as follows:: + Install the nRF Util ``device`` command v2.7.14 as follows:: - nrfutil install device=2.7.10 --force + nrfutil install device=2.7.14 --force For more information, consult the `nRF Util`_ documentation. -nrfutil trace -+++++++++++++ +nRF Util trace +++++++++++++++ .. toggle:: - * ``nrfutil trace`` has been updated to version 3.10.0. + * nRF Util ``trace`` command has been updated to v3.1.0. - Install the nRF Util ``trace`` command version 3.10.0 as follows:: + Install the nRF Util ``trace`` command v3.1.0 as follows:: - nrfutil install trace=3.10.0 --force + nrfutil install trace=3.1.0 --force For more information, consult the `nRF Util`_ documentation. -nrfutil suit -++++++++++++ +nRF Util suit ++++++++++++++ .. toggle:: - * ``nrfutil suit`` has been updated to version 0.9.0. + * nRF Util ``suit`` command has been updated to v0.9.0. - Install the nRF Util ``suit`` command version 0.9.0 as follows:: + Install the nRF Util ``suit`` command v0.9.0 as follows:: nrfutil install suit=0.9.0 --force For more information, consult the `nRF Util`_ documentation. + +nRF54H20 SoC binaries ++++++++++++++++++++++ + +.. toggle:: + + * The *nRF54H20 SoC binaries* bundle has been updated to version 0.9.1. + + .. note:: + The nRF54H20 SoC binaries only support specific versions of the |NCS| and do not support rollbacks to a previous version. + Upgrading the nRF54H20 SoC binaries on your development kit might break the DK's compatibility with applications developed for previous versions of the |NCS|. + For more information, see :ref:`abi_compatibility`. + + To update the SoC binaries bundle of your development kit while in Root of Trust, do the following: + + 1. Download the `nRF54H20 SoC binaries v0.9.1`_. + + .. note:: + On macOS, ensure that the ZIP file is not unpacked automatically upon download. + + #. Purge the device as follows:: + + nrfutil device recover --core Application --serial-number + nrfutil device recover --core Network --serial-number + nrfutil device reset --reset-kind RESET_PIN --serial-number + + #. Run ``west update``. + #. Move the correct :file:`.zip` bundle to a folder of your choice, then run nRF Util to program the binaries using the following command:: + + nrfutil device x-suit-dfu --firmware nrf54h20_soc_binaries_v0.9.1.zip --serial-number + + #. Purge the device again as follows:: + + nrfutil device recover --core Application --serial-number + nrfutil device recover --core Network --serial-number + nrfutil device reset --reset-kind RESET_PIN --serial-number diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.rst index 411b7cf4934e..56da75321269 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_2.9.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_2.9: Migration guide for |NCS| v2.9.0 diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_3.0.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_3.0.rst index aa651aadb384..ce053659f473 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_3.0.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_3.0.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_3.0: Migration guide for |NCS| v3.0.0 (Working draft) diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7.rst index faeeff027ef1..74fe158b2745 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_nrf54h20_to_2.7: Migration notes for |NCS| v2.7.0 and the nRF54H20 DK diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs1.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs1.rst index 615f6086bf7c..1885f9f2a449 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs1.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs1.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_nrf54h20_to_2.7.99-cs1: Migration notes for |NCS| v2.7.99-cs1 and the nRF54H20 DK diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs2.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs2.rst index fdc471bc30c7..882d359fac3d 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs2.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_nRF54H20_cs_to_2_7_99-cs2.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_nrf54h20_to_2.7.99-cs2: Migration notes for |NCS| v2.7.99-cs2 and the nRF54H20 DK diff --git a/doc/nrf/releases_and_maturity/migration/migration_guide_spm_to_tf-m.rst b/doc/nrf/releases_and_maturity/migration/migration_guide_spm_to_tf-m.rst index d4a524d5bcc1..44e8c90114ec 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_guide_spm_to_tf-m.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_guide_spm_to_tf-m.rst @@ -1,3 +1,5 @@ +:orphan: + .. _spm_to_tfm_migration: Migrating from Secure Partition Manager to Trusted Firmware-M diff --git a/doc/nrf/releases_and_maturity/migration/migration_hwmv2.rst b/doc/nrf/releases_and_maturity/migration/migration_hwmv2.rst index 5568857ddc18..6689347b3fdf 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_hwmv2.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_hwmv2.rst @@ -1,3 +1,5 @@ +:orphan: + .. _hwmv1_to_v2_migration: Migrating to the current hardware model diff --git a/doc/nrf/releases_and_maturity/migration/migration_sysbuild.rst b/doc/nrf/releases_and_maturity/migration/migration_sysbuild.rst index 9ab0bff08b9e..59963254f831 100644 --- a/doc/nrf/releases_and_maturity/migration/migration_sysbuild.rst +++ b/doc/nrf/releases_and_maturity/migration/migration_sysbuild.rst @@ -1,3 +1,5 @@ +:orphan: + .. _child_parent_to_sysbuild_migration: Migrating from multi-image builds to sysbuild diff --git a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.4.99-cs3_to_2.7_application.rst b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.4.99-cs3_to_2.7_application.rst index 484446bce9f2..9e06eb05f599 100644 --- a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.4.99-cs3_to_2.7_application.rst +++ b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.4.99-cs3_to_2.7_application.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_cs3_to_to_2_7_app: Migrate your application for the nRF54H20 DK to |NCS| v2.7.0 (for v2.4.99-cs3 users) diff --git a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2.7_application.rst b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2.7_application.rst index 52e414820b59..3bf7f344f5d3 100644 --- a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2.7_application.rst +++ b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2.7_application.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_2_6_99_cs2_to_2_7_app: Migrate your application for the nRF54H20 DK to |NCS| v2.7.0 (for v2.6.99-cs2 users) diff --git a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2_7_environment.rst b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2_7_environment.rst index dac4b7f1da1d..4a50dc60d614 100644 --- a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2_7_environment.rst +++ b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2_7_environment.rst @@ -1,3 +1,5 @@ +:orphan: + .. _migration_cs2_to_2_7_env: Migrate your development environment to |NCS| v2.7.0 (for v2.6.99-cs2 users) diff --git a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/transition_guide_2.4.99-cs3_to_2.7_environment.rst b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/transition_guide_2.4.99-cs3_to_2.7_environment.rst index fd1064794aeb..4bef0cc4b916 100644 --- a/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/transition_guide_2.4.99-cs3_to_2.7_environment.rst +++ b/doc/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/transition_guide_2.4.99-cs3_to_2.7_environment.rst @@ -1,3 +1,5 @@ +:orphan: + .. _transition_cs3_to_2_7_env: Transition your development environment to |NCS| v2.7.0 (for v2.4.99-cs3 users) diff --git a/doc/nrf/releases_and_maturity/migration_guides.rst b/doc/nrf/releases_and_maturity/migration_guides.rst index d169e313c883..ee7885295d2f 100644 --- a/doc/nrf/releases_and_maturity/migration_guides.rst +++ b/doc/nrf/releases_and_maturity/migration_guides.rst @@ -9,10 +9,19 @@ Migration guides are also provided for major functionality updates. .. note:: |migration_contact_devzone| -.. toctree:: - :maxdepth: 1 - :glob: - :reversed: - :caption: Subpages: +* `Migrating from multi-image builds to sysbuild`_ +* `Migrating to the current hardware model`_ +* `Migration guide for nRF Connect SDK v2.9.0`_ +* `Migration guide for nRF Connect SDK v2.8.0`_ +* `Migration guide for nRF Connect SDK v2.7.0`_ +* `Migration guide for nRF Connect SDK v2.6.0`_ +* `Migration guide for nRF Connect SDK v2.5.0`_ +* `Migration guide for nRF Connect SDK v2.0.0`_ - migration/* +For nRF54H20-exclusive releases: + +* `Migration guide for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`_ +* `Migration notes for nRF Connect SDK v2.7.99-cs2 and the nRF54H20 DK`_ +* `Migration notes for nRF Connect SDK v2.7.99-cs1 and the nRF54H20 DK`_ +* `Migration notes for nRF Connect SDK v2.7.0 for nRF54H20 DK users`_ +* `Migration guide for nRF Connect SDK v2.6.99_cs2 for v2.4.99-cs3 users`_ diff --git a/doc/nrf/releases_and_maturity/release_notes.rst b/doc/nrf/releases_and_maturity/release_notes.rst index da9e5a44eb9f..94f2c7635744 100644 --- a/doc/nrf/releases_and_maturity/release_notes.rst +++ b/doc/nrf/releases_and_maturity/release_notes.rst @@ -10,9 +10,8 @@ This page is included only in the latest documentation, because it might contain .. note:: A "99" at the end of the version number of this documentation indicates continuous updates on the main branch since the previous major.minor release. - When looking at this latest documentation, be aware of the following aspects: + When looking at this latest documentation, be aware of the following aspect: - * Changes between releases are tracked on the :ref:`ncs_release_notes_changelog` page, but the main branch might contain additional changes that are not listed on that page. * The release note pages that are available in the latest documentation might differ slightly from the release notes that were included in the respective |NCS| release at its release date. Therefore, to see the official version of the release notes for a specific |NCS| release, switch to the documentation for the corresponding |NCS| version using the selector in the upper left corner. @@ -20,8 +19,7 @@ This page is included only in the latest documentation, because it might contain :maxdepth: 1 :caption: Subpages: - releases/release-notes-changelog - releases/release-notes-2.9.0-nrf54h20-rc1 + releases/release-notes-2.9.0-nRF54H20-1-rc2 releases/release-notes-2.9.0 releases/release-notes-2.8.0 releases/release-notes-2.7.99-cs2 diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nrf54h20-rc1.rst b/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1-rc2.rst similarity index 82% rename from doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nrf54h20-rc1.rst rename to doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1-rc2.rst index 0879e5b05383..c04f358b0aeb 100644 --- a/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nrf54h20-rc1.rst +++ b/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1-rc2.rst @@ -1,7 +1,7 @@ -.. _ncs_release_notes_290-nrf54h20-rc1: +.. _ncs_release_notes_290-nrf54h20-1-rc2: -|NCS| v2.9.0-nRF54H20-rc1 Release Notes -####################################### +|NCS| v2.9.0-nRF54H20-1-rc2 Release Notes +######################################### .. contents:: :local: @@ -10,7 +10,7 @@ |NCS| delivers reference software and supporting libraries for developing low-power wireless applications with Nordic Semiconductor products. The SDK includes open source projects (TF-M, MCUboot, OpenThread, Matter, and the Zephyr RTOS), which are continuously integrated and redistributed with the SDK. -The |NCS| v2.9.0-nrf54h20-rc1 is an nRF54H20-exclusive release tag, only supporting products based on the nRF54H20 SoC. +The |NCS| v2.9.0-nRF54H20-1-rc2 is an nRF54H20-exclusive release tag, only supporting products based on the nRF54H20 SoC. Release notes might refer to "experimental" support for features, which indicates that the feature is incomplete in functionality or verification, and can be expected to change in future releases. To learn more, see :ref:`software_maturity`. @@ -42,60 +42,61 @@ Added the following features as experimental: * :ref:`Parallel scanning and initiating connection `. It reduces the overall waiting time when there are several Bluetooth devices to be discovered and connected at the same time. -Improved the following features: +Improved: -* Better BICR handling and generation. -* Enhanced power management features across various subsystems. +* BICR handling and generation. +* Power management features across various subsystems. -Implemented the following bug fixes: +Fixed: -* NCSDK-30802: Resolved an issue where the nRF54H20 device suddenly stopped transmitting ESB packets after nrfxlib 3.9.0. -* NCSDK-30161: Fixed an assertion during boot time caused by a combination of :kconfig:option:`CONFIG_ASSERT`, :kconfig:option:`CONFIG_SOC_NRF54H20_GPD`, and external flash. -* NCSDK-30117: Ensured that it is no longer possible to declare a MEM component pointing to a memory region not assigned to a particular core. +* NCSDK-30802: An issue where the nRF54H20 device suddenly stopped transmitting ESB packets after nrfxlib 3.9.0. +* NCSDK-30161: An assertion during boot time caused by a combination of :kconfig:option:`CONFIG_ASSERT`, :kconfig:option:`CONFIG_SOC_NRF54H20_GPD`, and external flash. +* NCSDK-30117: An issue where a MEM component could be declared pointing to a memory region not assigned to a specific core. * NCSDK-29682: Added support for the ``cose-alg-sha-512`` algorithm in the SUIT module. Limitations *********** On the nRF54H20 SoC, the Device Firmware Update (DFU) procedure from external flash memory does not work with the new flash memory driver based on the MSPI EXMIF handling. +You must use the :file:`spi_dw.c` driver in such case. Release tag *********** -The release tag for the |NCS| manifest repository (|ncs_repo|) is **v2.9.0-nRF54H20**. +The release tag for the |NCS| manifest repository (|ncs_repo|) is **v2.9.0-nRF54H20-1-rc2**. Check the :file:`west.yml` file for the corresponding tags in the project repositories. To use this release, check out the tag in the manifest repository and run ``west update``. See :ref:`cloning_the_repositories` and :ref:`gs_updating_repos_examples` for more information. -For information on the included repositories and revisions, see `Repositories and revisions for v2.9.0-nRF54H20-rc1`_. +For information on the included repositories and revisions, see `Repositories and revisions for v2.9.0-nRF54H20-1-rc2`_. Integration test results ************************ The integration test results for this tag can be found in the following external Artifactory: -* `Twister test report for nRF Connect SDK v2.9.0-nRF54H20-rc1`_ -* `Hardware test report for nRF Connect SDK v2.9.0-nRF54H20-rc1`_ +* `Twister test report for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`_ +* `Hardware test report for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`_ IDE and tool support ******************** -`nRF Connect extension for Visual Studio Code `_ is the recommended IDE for |NCS| v2.9.0-nrf54h20-rc1. +`nRF Connect extension for Visual Studio Code `_ is the recommended IDE for |NCS| v2.9.0-nRF54H20-1-rc2. See the :ref:`installation` section for more information about supported operating systems and toolchain. Known issues ************ Known issues are only tracked for the latest official release. -See `known issues for nRF Connect SDK v2.9.0-nRF54H20-rc1`_ for the list of issues valid for the latest release. +See `known issues for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`_ for the list of issues valid for the latest release. Migration notes *************** -See the `Migration guide for nRF Connect SDK v2.9.0-nRF54H20-rc1`_ for the changes required or recommended when migrating your nRF54H Series application from |NCS| v2.8.0 to |NCS| v2.9.0-nrf54h20-rc1. +See the `Migration guide for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`_ for the changes required or recommended when migrating your nRF54H Series application from |NCS| v2.8.0 to |NCS| v2.9.0-nRF54H20-1-rc2. -.. _ncs_release_notes_290-nRF54H20-rc1_changelog: +.. _ncs_release_notes_290-nrf54h20-1-rc2_changelog: Changelog ********* @@ -141,6 +142,8 @@ Bluetooth LE * Updated the Bluetooth LE SoftDevice Controller driver to make the :c:func:`hci_vs_sdc_llpm_mode_set` function return an error if Low Latency Packet Mode (LLPM) is not supported or not enabled in the Bluetooth LE Controller driver configuration (:kconfig:option:`CONFIG_BT_CTLR_SDC_LLPM`). +* Fixed an issue where Bluetooth applications built with the ``nordic-ble-rpc`` snippet (in the :ref:`ble_rpc` configuration) did not work on the nRF54H20 devices due to incorrect memory mapping. + Matter ------ @@ -151,6 +154,12 @@ Matter To use this class, enable the Kconfig options :kconfig:option:`CONFIG_PSA_WANT_ALG_PBKDF2_HMAC` and :kconfig:option:`CONFIG_PSA_WANT_KEY_TYPE_SPAKE2P_KEY_PAIR_DERIVE`. * The :ref:`ug_matter_device_watchdog_pause_mode` to the :ref:`ug_matter_device_watchdog` feature. +Enhanced ShockBurst (ESB) +------------------------- + +* Added support for loading radio trims. +* Fixed a hardware erratum for the nRF54H20 SoC to improve RF performance. + Matter fork +++++++++++ @@ -233,29 +242,13 @@ nRF Desktop * The :ref:`nrf_desktop_settings_loader` to make the :ref:`Zephyr Memory Storage (ZMS) ` the default settings backend for all board targets that use the MRAM technology. As a result, all :ref:`zephyr:nrf54h20dk_nrf54h20` configurations were migrated from the NVS settings backend to the ZMS settings backend. * :ref:`nrf_desktop_watchdog` by adding the :ref:`zephyr:nrf54h20dk_nrf54h20` release configuration. - * Updated the configuration files of the :ref:`nrf_desktop_click_detector` (:file:`click_detector_def.h`) to allow them to be used even when Bluetooth LE peer control using a dedicated button (:ref:`CONFIG_DESKTOP_BLE_PEER_CONTROL `) is disabled. + * The configuration files of the :ref:`nrf_desktop_click_detector` (:file:`click_detector_def.h`) to allow them to be used even when Bluetooth LE peer control using a dedicated button (:ref:`CONFIG_DESKTOP_BLE_PEER_CONTROL `) is disabled. * The DTS description for board targets with a different DTS overlay file for each build type to isolate the common configuration that is now defined in the :file:`app_common.dtsi` file. The :ref:`zephyr:nrf54h20dk_nrf54h20` board configuration has been updated. + * The :ref:`nrf_desktop_failsafe` to use the Zephyr :ref:`zephyr:hwinfo_api` driver for getting and clearing the reset reason information (see the :c:func:`hwinfo_get_reset_cause` and :c:func:`hwinfo_clear_reset_cause` functions). + The Zephyr :ref:`zephyr:hwinfo_api` driver replaces the dependency on the nrfx reset reason helper (see the :c:func:`nrfx_reset_reason_get` and :c:func:`nrfx_reset_reason_clear` functions). - * The :ref:`nrf_desktop_ble_conn_params` with the following changes: - - * Fixed the Bluetooth LE connection parameters update loop (NCSDK-30261) that replicated if an nRF Desktop dongle without Low Latency Packet Mode (LLPM) support was connected to an nRF Desktop peripheral with LLPM support. - * The module now waits until a triggered Bluetooth LE connection parameters update is completed before triggering subsequent updates for a given connection. - * Improved the log to also display the information if USB is suspended. - The information is needed to determine the requested connection parameters. - * The module now uses non-zero Bluetooth LE peripheral latency while USB is suspended. - This is done to prevent peripheral latency increase requests from :ref:`nrf_desktop_ble_latency` on peripheral's end. - * The module reverts the USB suspended Bluetooth LE connection parameter update when USB cable is disconnected. - - * The :ref:`nrf_desktop_ble_scan` to always use a connection interval of 10 ms for peripherals without Low Latency Packet Mode (LLPM) support if a dongle supports LLPM and more than one Bluetooth LE connection. - This is required to avoid Bluetooth Link Layer scheduling conflicts that could lead to HID report rate drop. - -nRF SoC flash driver --------------------- - -* Removed the ``imply`` for the partial erase feature of the nRF SoC flash driver (:kconfig:option:`CONFIG_SOC_FLASH_NRF_PARTIAL_ERASE`) for the USB next stack (:ref:`CONFIG_DESKTOP_USB_STACK_NEXT `). - The partial erase feature was used as a workaround for device errors that might be reported by the Windows USB host in Device Manager if a USB cable is connected while erasing a secondary image slot in the background. - The workaround is no longer needed after the nRF UDC driver was improved. + * The release configuration for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target to enable the :ref:`nrf_desktop_failsafe` (see the :ref:`CONFIG_DESKTOP_FAILSAFE_ENABLE ` Kconfig option). Samples ======= @@ -274,6 +267,11 @@ Bluetooth samples * The :ref:`bt_peripheral_with_multiple_identities` sample demonstrating how to use a single physical device to create and manage multiple advertisers, making it appear as multiple distinct devices by assigning each a unique identity. * The :ref:`bt_scanning_while_connecting` sample demonstrating how to establish multiple connections faster using the :kconfig:option:`CONFIG_BT_SCAN_AND_INITIATE_IN_PARALLEL` Kconfig option. + * :ref:`direct_test_mode`: + + * Added support for loading radio trims. + * Fixed a hardware erratum for the nRF54H20 SoC to improve RF performance. + * Updated: * Configurations of the following Bluetooth samples to make the :ref:`Zephyr Memory Storage (ZMS) ` the default settings backend for all board targets that use the MRAM technology: @@ -309,6 +307,14 @@ Bluetooth samples * Fixed an issue with data transmission (OCT-3251). Data is now sent on all BISes when generated by the application (no SD card inserted). +Peripheral samples +------------------ + +* :ref:`radio_test`: + + * Added support for loading radio trims. + * Fixed a hardware erratum for the nRF54H20 SoC to improve RF performance. + Bluetooth Fast Pair samples --------------------------- @@ -316,6 +322,10 @@ Bluetooth Fast Pair samples * Added support for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target. +* :ref:`fast_pair_locator_tag` sample: + + * Added support for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target. + Edge Impulse samples -------------------- @@ -386,8 +396,9 @@ Bluetooth libraries and services * :ref:`bt_fast_pair_readme` library: - * Added support in build system for devices that do not support the :ref:`partition_manager`. + * Added support in the build system for devices that do not support the :ref:`partition_manager`. The :ref:`zephyr:nrf54h20dk_nrf54h20` board target is the only example of such a device. + * Updated the :c:func:`bt_fast_pair_info_cb_register` API to allow registration of multiple callbacks. nRF RPC libraries diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst b/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst index 535c4ef47820..ae6c15ba3983 100644 --- a/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst +++ b/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst @@ -1,3 +1,5 @@ +:orphan: + .. _ncs_release_notes_changelog: Changelog for |NCS| v2.9.99 @@ -23,7 +25,7 @@ Known issues ************ Known issues are only tracked for the latest official release. -See `known issues for nRF Connect SDK v2.9.0-nRF54H20-rc1`_ for the list of issues valid for the latest release. +See `known issues for nRF Connect SDK v2.9.0-nRF54H20-1-rc2`_ for the list of issues valid for the latest release. Changelog ********* diff --git a/doc/nrf/shortcuts.txt b/doc/nrf/shortcuts.txt index 064446d0617d..fac30f60696c 100644 --- a/doc/nrf/shortcuts.txt +++ b/doc/nrf/shortcuts.txt @@ -2,9 +2,9 @@ .. ### Versions -.. |release| replace:: v2.9.0-nRF54H20-rc1 -.. |release_tt| replace:: ``v2.9.0-nRF54H20-rc1`` -.. |release_number_tt| replace:: ``2.9.0-nRF54H20-rc1`` +.. |release| replace:: v2.9.0-nRF54H20-1-rc2 +.. |release_tt| replace:: ``v2.9.0-nRF54H20-1-rc2`` +.. |release_number_tt| replace:: ``2.9.0-nRF54H20-1-rc2`` .. |jlink_ver| replace:: v8.10f .. |jlink_ver_vsc| replace:: v7.94i diff --git a/doc/versions.json b/doc/versions.json index 3cde48245433..882a4625bef7 100644 --- a/doc/versions.json +++ b/doc/versions.json @@ -1,6 +1,5 @@ [ - "2.9.99", - "2.9.0-nRF54H20-rc1", + "2.9.0-nRF54H20-1-rc2", "2.9.0", "2.8.0", "2.8.0-preview1",