nRF Connect SDK v1.4.1 Release Notes

nRF Connect SDK delivers reference software and supporting libraries for developing low-power wireless applications with Nordic Semiconductor products. It includes the MCUboot and the Zephyr RTOS open source projects, which are continuously integrated and re-distributed with the SDK.

The nRF Connect SDK is where you begin building low-power wireless applications with Nordic Semiconductor nRF52, nRF53, and nRF91 Series devices. nRF53 Series devices (which are pre-production) and Zigbee and Bluetooth mesh protocols are supported for development in v1.4.1 for prototyping and evaluation. Support for production and deployment in end products is coming soon.

Highlights

  • Qualified Zephyr Host to be conformant with Bluetooth Core Specification v5.2

  • Updated Carrier Library to v0.10.1

Release tag

The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v1.4.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 for more information.

Supported modem firmware

This version of the nRF Connect SDK has been tested with the following modem firmware for cellular IoT applications:

  • mfw_nrf9160_1.2.2

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.

Changelog

The following sections provide detailed lists of changes by component.

nRF9160

Multiprotocol Service Layer (MPSL)

  • Fixed the DRGN-15064 known issue where the External Full swing and External Low swing configuration sources of Low Frequency Clock were not working correctly.

Zephyr

sdk-zephyr

Note

Except for changes in Zephyr that were cherry-picked into nRF Connect SDK and described in the following section, there were no upstream commits incorporated into nRF Connect SDK in this release compared with the v1.4.0 release.

The sdk-zephyr fork in nRF Connect SDK contains all commits from the upstream Zephyr repository up to and including 7a3b253ced, plus some nRF Connect SDK specific additions.

For a complete list of upstream Zephyr commits incorporated into nRF Connect SDK since the most recent release, run the following command from the ncs/zephyr repository (after running west update):

git log --oneline 7a3b253ced ^v2.3.0-rc1-ncs1

For a complete list of nRF Connect SDK specific commits, run:

git log --oneline manifest-rev ^7a3b253ced

The current nRF Connect SDK release is based on Zephyr v2.4.0. See the Zephyr v2.4.0 release notes for the list of changes.

Zephyr changes incorporated into nRF Connect SDK

This section contains changes in Zephyr that were cherry-picked into nRF Connect SDK for this release.

Bluetooth Host

  • Qualified Zephyr Host to be conformant with Bluetooth Core Specification v5.2. These changes were cherry-picked in the nRF Connect SDK v1.4.1 Bluetooth Host qualification update, which contains the following changes:

    • Added qualification for Bluetooth Core Specification v5.2. Qualified new features are the following:

      • Advertising extension

      • Legacy OOB pairing

  • Fixed an issue where a pairing fail could lead to a GATT procedure failure. This fixes the NCSDK-6844 known issue in nRF Connect SDK.

Known issues

See known issues for nRF Connect SDK v1.4.1 for the list of issues valid for this release.