nRF Connect SDK v2.1.3 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 minor release adds the following changes on top of the nRF Connect SDK v2.1.0, nRF Connect SDK v2.1.1, and nRF Connect SDK v2.1.2:

  • Updates the Matter ZAP Tool revision to be compatible with the zap files that define the Data Model in nRF Connect SDK Matter samples.

  • Bluetooth® fixes:

    • An issue in MPSL where the controller would assert when a Bluetooth role was running.

    • An issue in MPSL where the controller would abandon a link, causing a disconnect on the remote side.

    • An issue where RPA (Random Private Address) would not be changed when it should when the CONFIG_BT_EXT_ADV Kconfig option was enabled.

  • UART driver fixes:

    • Fixed an issue where re-enabling UART after calling uart_rx_disable() too early could cause random hardware faults.

    • Fixed an issue where NULL pointer was de-referenced if PM_DEVICE_ACTION_RESUME action was requested.

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.1.3. 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.1.3.

IDE and tool support

nRF Connect for Visual Studio Code extension is the only officially supported IDE for nRF Connect SDK v2.1.3. SEGGER Embedded Studio Nordic Edition is no longer tested or recommended for new projects.

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.1.3 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.

Bluetooth

Fixed:

  • An issue in MPSL where the controller would assert when a Bluetooth role was running. This was previously listed as the known issue with the issue ID (DRGN-17851).

  • An issue in MPSL where the controller would abandon a link, causing a disconnect on the remote side. This was previously listed as the known issue with the issue ID (DRGN-18105).

  • An issue where RPA (Random Private Address) would not be changed when it should when the CONFIG_BT_EXT_ADV Kconfig option was enabled.

Matter

  • Updated the ZAP submodule revision to fix opening the ZAP files included in Matter samples in nRF Connect SDK.

Zephyr

  • Fixed:

    • An issue where re-enabling UART after calling uart_rx_disable() too early could cause random hardware faults.

    • An issue where NULL pointer was de-referenced if PM_DEVICE_ACTION_RESUME action was requested.

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including 71ef669ea4a73495b255f27024bcd5d542bf038c. This is the same commit ID as the one used for nRF Connect SDK v2.1.0, v2.1.1 and v2.1.3. It also includes some nRF Connect SDK specific additions and commits cherry-picked from the upstream Zephyr repository.

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

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