nRF Connect SDK v2.5.1 Release Notes

nRF Connect SDK delivers reference software and supporting libraries for developing low-power wireless applications with Nordic Semiconductor products in the nRF52, nRF53, nRF70, and nRF91 Series. The SDK includes open source projects (TF-M, MCUboot, OpenThread, Matter, and the Zephyr RTOS), which are continuously integrated and redistributed with the SDK.

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 Software maturity levels.

Highlights

This patch release adds changes on top of the nRF Connect SDK v2.5.0. The changes affect Matter, Wi-Fi®, nrfx, Zephyr, and Trusted Firmware-M (TF-M).

See Changelog for the complete list of changes.

Release tag

The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v2.5.1. Check the 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 Get the nRF Connect SDK code and Updating the repositories for more information.

For information on the included repositories and revisions, see Repositories and revisions for v2.5.1.

IDE and tool support

nRF Connect for Visual Studio Code extension is the only officially supported IDE for nRF Connect SDK v2.5.1.

Installation with Toolchain Manager, used to install the nRF Connect SDK automatically from nRF Connect for Desktop, is available for Windows, Linux, and macOS.

Supported modem firmware

See Modem firmware compatibility matrix for an overview of which modem firmware versions have been tested with this version of the nRF Connect SDK.

Use the latest version of the nRF Programmer app of nRF Connect for Desktop to update the modem firmware. See Updating the modem firmware for instructions.

Known issues

Known issues are only tracked for the latest official release. See known issues for nRF Connect SDK v2.5.1 for the list of issues valid for the latest release.

Changelog

The following sections provide detailed lists of changes by component.

Protocols

This section provides detailed lists of changes by protocol.

Matter

  • Updated the default values of attributes in ZAP files to comply with the Matter 1.1 specification.

  • Fixed:

    • An issue with commissioning Matter over Wi-Fi devices to the fifth fabric.

    • An issue with the Matter Bridge not being operational in commercial ecosystems, Apple Home and Samsung SmartThings.

Wi-Fi

  • Added improvements and fixes related to the following:

nrfx

  • Updated the nrfx QSPI driver behavior. Now, QSPI peripheral is not activated during the driver initialization but rather when the first operation is requested or when the nrfx_qspi_activate() function is called.

  • Fixed an issue when external memory requires a relatively long time for the operation to happen. This is done by adding a timeout member to nrfx_qspi_config_t, which can be configured at runtime. If the timeout value is 0, the old value is used instead (500 milliseconds).

  • Removed the ongoing custom instruction long transfer check from the nrfx_qspi_deactivate() function. The check could trigger errors, and now you must make sure that the custom instruction long transfer has ended, otherwise it will be interrupted. If a custom instruction long transfer is ongoing when the nrfx_qspi_uninit() and nrfx_qspi_deactivate() functions are called, the transfer will be interrupted.

Zephyr

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including a768a05e6205e415564226543cee67559d15b736. It also contains some nRF Connect SDK specific additions and commits cherry-picked from the upstream Zephyr repository including the following one:

  • Added workaround in sdk-zephyr for the Anomaly 168 that is affecting the nRF5340 SoC.

For a complete list of nRF Connect SDK specific commits and cherry-picked commits since v2.5.0, run the following command:

git log --oneline manifest-rev ^v3.4.99-ncs1

Trusted Firmware-M

  • Fixed:

    • An issue where TF-M does not compile without the gpio0 node enabled in the devicetree.

    • An issue where TF-M does not configure PDM and I2S as non-secure peripherals for the nRF91 Series devices. See the NCSDK-24986 issue in the Known Issues page for more details.