nRF Connect SDK v2.0.0 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, and nRF91 Series. The SDK includes open source projects (TF-M, MCUboot, OpenThread, Matter, and the Zephyr RTOS), which are continuously integrated and re-distributed 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.
The feature is made available in its current state though the design and interfaces can change between release tags.
The feature will also be labeled with “EXPERIMENTAL” in Kconfig files to indicate this status.
Build warnings will be generated to indicate when features labeled EXPERIMENTAL are included in builds unless the Kconfig option
CONFIG_WARN_EXPERIMENTAL is disabled.
Simplified Software License Report generation is now possible for any nRF Connect SDK project. See the sbom documentation for more information.
The Zephyr SDK toolchain replaces the GNU ARM Embedded toolchain.
Trusted Firmware M (TF-M) replaces the Secure Partition Manager (SPM) for secure image firmware. TF-M is now enabled by default for most nRF9160 and nRF5340 applications and samples. See TF-M known issues for details.
Added experimental Bluetooth LE Audio support, including an application for the nRF5340 Audio DK.
The SoftDevice Controller is now Bluetooth v5.3 qualified.
Improved DFU over Bluetooth Low Energy (SMP server improvements).
Support for Thread v1.2 is no longer experimental. HomeKit over Thread and Matter over Thread use Thread v1.2 libraries by default now.
Support for the Zigbee Cluster Library specification v8 (ZCL 8) and Base Device Behavior specification v3.0.1 (BDB 3.0.1) is no longer experimental. ZCL 8 and BDB 3.0.1 libraries are now used by default in Zigbee samples.
Updated Zephyr LwM2M stack to v1.1, which provides extended commands and options for more efficient data transmission.
Added nRF Cloud Location Services support in the AVSystem’s Coiote LwM2M server.
Added power consumption optimization for poor satellite coverage when using GNSS.
A migration guide is available for users moving from nRF Connect SDK v1.x to v2.x.
Sign up for the nRF Connect SDK v2.0.0 webinar to learn more about the new features.
The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v2.0.0.
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
See Get the nRF Connect SDK code for more information.
For information on the included repositories and revisions, see Repositories and revisions for v2.0.0.
nRF Connect extension for Visual Studio Code is the only officially supported IDE for nRF Connect SDK v2.0.0. SEGGER Embedded Studio Nordic Edition is no longer tested and recommended for new projects.
Toolchain Manager, used to install the nRF Connect SDK automatically from nRF Connect for Desktop, is now also available for Linux, in addition to the previously available version for Windows and macOS. The Linux version only supports installing the nRF Connect SDK v2.0.0 and later.
See Modem firmware compatibility matrix for an overview of which modem firmware versions have been tested with this version of the nRF Connect SDK.
Known issues are only tracked for the latest official release. See known issues for nRF Connect SDK v2.0.0 for the list of issues valid for the latest release.
The following sections provide detailed lists of changes by component.
This section provides lists of changes related to Application development.
Added necessary reset functionality for using the nRF52840 SoC on the Thingy:91 as a Bluetooth controller.
Fixed an issue with nRF Connect SDK Toolchain delimiter handling on MacOS, which could in special situations result in the build system not being able to properly locate the correct program needed.
See Bluetooth mesh samples for the list of changes for the Bluetooth mesh samples.
The CHIP Tool controller is now the recommended controller for Matter. The documentation about Matter controller has been updated accordingly. For more information about the CHIP Tool controller, read the Working with the CHIP Tool page in the Matter documentation.
See Matter samples for the list of changes for the Matter samples.
The Matter fork in the nRF Connect SDK (
sdk-connectedhomeip) contains all commits from the upstream Matter repository up to, and including,
The following list summarizes the most important changes inherited from the upstream Matter:
Added the Binding cluster and Groupcast communication to the Light Switch sample.
Updated the nRF Connect platform by adding
Kconfig.multiprotocol_rpmsg.defaultsfiles that contain the default configuration for all nRF Connect SDK samples.
Added support for Thread Synchronized Sleepy End Devices.
Added support for the Link Metrics and CSL Thread v1.2 features for the nRF53 Series devices.
Removed support for the Network co-processor (NCP) architecture and the related tools.
The OpenThread memory requirements page shows requirements based on the configuration used for certification instead of minimal configuration, which has been removed.
Updated nrfconnect/otbr docker.
Updated OpenThread pre-built libraries for Thread v1.2.
Removed OpenThread pre-built libraries for Thread v1.1.
See Thread samples for the list of changes for the Thread samples.
Support for Zigbee Cluster Library ver8 (ZCL8). The support is not experimental anymore.
Support for Zigbee Base Device Behavior v3.0.1 (BDB 3.0.1). The support is not experimental anymore.
Zigbee Network Co-processor Host package to the new version v2.2.0.
An issue where the Zigbee: Light bulb sample was flickering when set to 50 kHz.
An issue with an assertion fail in
An issue where a wrong value was reported for attributes
MaxMeasuredValuein the Weather Station.
An issue with ZBOSS fatal error after factory reset and before bdb start.
An issue where the Coordinator did not form a new network after factory reset.
An issue with identifying when not in a network.
An issue with ZBOSS binding table corruption.
An issue where the Zigbee shell did not inform if the network address request was not sent.
See Zigbee samples for the list of changes for the Zigbee samples.
Production support for Thread 1.2.
Support for 3-button actions (long press, short press, double press).
LED indicating BLE connectivity status.
Development support for OTA-DFU using the iOS Home App (over UARP - BLE and Thread).
LED output can be fully disabled using Kconfig.
Flash usage optimization for debug versions of samples and applications.
DFU mode can now be enabled by a button press.
CLI is no longer required for DFU configuration.
HAP_TESTING is now configurable using Kconfig.
An issue where RTT logs did not work with the Light Bulb multiprotocol sample with DFU on nRF52840.
An issue where Nordic DFU was not compliant with HAP certification requirements.
An issue where a change in KVS key naming scheme caused an error for updated devices.
An issue where activating DFU caused increased power consumption.
This section provides detailed lists of changes by application.
nRF9160: Asset Tracker v2
Support for Bosch Software Environmental Cluster (BSEC) library.
Support for Indoor Air Quality (IAQ) readings retrieved from the BME680 sensor on Thingy:91. For more information, see the Sensor module documentation.
Support for QEMU x86 emulation.
Support for the nRF Cloud P-GPS flash memory partition under certain conditions.
Support for Quality of Service library to handle multiple in-flight messages for MQTT based cloud backends such as AWS IoT, Azure IoT Hub, and nRF Cloud.
Support for Lightweight Machine to Machine (LwM2M).
Support for filtering updates to cloud based on LTE connection evaluation (AT%CONEVAL).
For nRF Cloud builds, the configuration section in the shadow is now initialized during the cloud connection process.
nRF9160: Serial LTE modem
#XDFURUNAT commands to support the cloud-to-nRF52 DFU service.
Native TLS support to the HTTPS client.
#XCMNGcommand to support the use of native TLS.
#XSOCKETSELECTAT command to support multiple sockets in the Socket service.
#XPOLLAT command to poll selected or all sockets for incoming data.
#XHTTPCREQAT command for better HTTP upload and download support.
#XSLEEPAT command to support data indication when idle.
Enhanced the MQTT client to support the reception of large PUBLISH payloads.
The nRF Cloud library is now used directly instead of the Cloud API.
The secondary MCUboot partition information is no longer passed to the P-GPS library if the P-GPS partition is enabled.
The combined use of A-GPS and P-GPS so that ephemeris and almanac data is not requested through A-GPS, saving both power and bandwidth.
nRF Machine Learning (Edge Impulse)
Increased the value of
CONFIG_CAF_POWER_MANAGER_TIMEOUTto 30 seconds for Thingy:53.
Added managing BLE connection interval depending on the USB state to reduce power consumption when USB is suspended.
Changed default Bluetooth connection interval from 7.5 ms to 10 ms for nRF Desktop centrals that support LLPM and two simultaneous Bluetooth connections. This is needed to prevent Bluetooth Link Layer scheduling issues.
Removed configurations without a bootloader. The B0 bootloader is enabled by default on all boards if the configuration with two image slots fits in memory. Alternatively, MCUboot bootloader with a single image slot and serial recovery is enabled. In case the configuration with the MCUboot does not fit in memory, no bootloader is enabled.
Thingy:53 Zigbee weather station
Added new Thingy:53: Zigbee weather station application.
Fixed an issue where the buffer was being freed incorrectly.
Removed Peripheral Alexa Gadgets Bluetooth sample due to Amazon pausing support for the Gadgets ecosystem.
Bluetooth: Direct Test Mode sample:
Added the vendor-specific
FEM_DEFAULT_PARAMS_SETcommand for restoring the default front-end module parameters.
Added possibility to build with the limited nRF21540 front-end module hardware pinout.
Fixed handling of the disable Constant Tone Extension command.
The front-end module test parameters are not set to their default value after the DTM reset command.
Changed the radio antennas array hardware description. It is now based on the radio bindings instead of custom configuration.
Bluetooth: Peripheral HIDS mouse sample:
Increased the main stack size from 1024 to 1536 bytes.
Increased the stack size of the nRF RPC threads from 1024 to 1280 bytes.
Bluetooth: Peripheral UART sample:
Fixed handling of RX buffer releasing in this sample and in the UARTE driver. Before this fix, the RX buffer might have been released twice by the main thread.
Bluetooth: Central UART sample:
Added debug logs for the UART events.
Bluetooth: Central SMP Client sample:
Changed the current CBOR library from TinyCBOR to zcbor.
Bluetooth: HCI low power UART sample:
Added support for Thingy:91.
Added support for the nRF52832 device.
Fixed handling of the empty Generic Attribute Service.
Bluetooth mesh samples
nRF9160: nRF Cloud REST Device Message sample, demonstrating how to send an arbitrary device message with the nRF Cloud REST API.
nRF9160: Modem callbacks sample, showcasing initialization and de-initialization callbacks.
nRF9160: nRF Cloud MQTT multi-service sample, demonstrating a simple but robust integration of location services, FOTA, sensor sampling, and more.
Shell functionality to HTTP Update samples.
nRF9160: TLS ciphersuites sample, demonstrating how to use TLS ciphersuites.
Secure Partition Manager (rather than TF-M) is enabled by default for the applications and samples that support Thingy:91.
nRF9160: AT monitor sample:
UICC failureCEREG status codes to
nRF9160: Modem Shell sample:
Remote control support over MQTT using the Terminal window in the nRF Cloud portal. It enables executing any MoSh command on the device remotely.
--interval(in seconds) to neighbor cell measurements in continuous mode (
link ncellmeas --continuous). When using this option, a new measurement is started in each interval.
Separate plain AT command mode that can be started with the command
at at_cmd_mode start. AT command termination methods can be configured using Kconfig options. The default method is CR termination. In AT command mode, a maximum of 10 AT commands can be pipelined with
|as the delimiter character between pipelined AT commands.
Threading support for the
Iperf3 usage over Zephyr native TCP/IP stack and nRF9160 LTE default context.
Support for the GNSS features introduced in modem firmware v1.3.2. This includes several new fields in the PVT notification and a command to query the expiry times of assistance data.
Support for the
Device information is sent to nRF Cloud when connecting with MQTT using the
New options to send acquired GNSS location to nRF Cloud for
locationcommand, either in NMEA or in PVT format. Both MQTT and REST transports are supported (compile-time configuration).
Improved the nRF9160 DK out-of-the box experience and the process of adding the DK to nRF Cloud using MoSh and LTE Link Monitor.
The behavior of this sample when built with the
CONFIG_NRF_MODEM_LIB_TRACE_MEDIUM_UARToption enabled, is changed as follows:
When disabling of UART is requested either by a shell command or by a button press, modem traces are disabled before disabling UART1.
When the UART1 is re-enabled (either after timer expiry or button press), the modem traces are also re-enabled.
nRF9160: nRF Cloud REST FOTA sample:
Enabled building of bootloader FOTA update files.
Corrected handling of the bootloader FOTA updates.
Enabled the AT Host library to make it easier to update certificates.
nRF9160: LTE Sensor Gateway sample:
Added support for Thingy:91.
nRF9160: LwM2M Client sample:
Reworked the retry logic so that the sample can fall back to bootstrap mode and need not always restart the LTE connection.
Replaced the deprecated GPS driver with the new GNSS interface.
LwM2M v1.1 uses SenML CBOR by default as content format.
nRF9160: Download client sample:
Updated the default HTTPS URL and certificate due to the old link being broken.
nRF9160: GNSS sample:
nRF9160: Location sample:
Enabled the AT Host library to make it easier to update certificates.
Removed the Cloud client sample.
Thread 1.2 version is now the default configuration option.
Thread Beacon payload has been removed after changes in the latest Thread Specification.
Minimal configuration for CLI sample has been removed.
BLE advertising interval has been increased from 100 ms to 300 ms for CLI sample when multiprotocol is enabled.
Release configuration for all samples.
Matter: Window covering sample, based on the Matter upstream sample. This sample utilizes Thread Synchronized Sleepy End Device role.
prj.conffile of each sample by using the default configuration from the
Kconfig.defaultsfile in Matter upstream.
All ZAP configurations due to changes in Matter upstream.
Added OTA DFU support.
Matter: Light switch sample:
A binding cluster to the sample.
Overlay enabling low power mode support.
Updated the Pairing process to Binding process in the sample.
Matter: Door lock sample:
Added support for the Door Lock cluster, which replaced the previous temporary solution based on the On/Off cluster.
NFC: Tag reader sample:
Skips NDEF content printing when message parsing returns an error.
Changed the transport layer for inter-core communication on the nRF5340 device from the RPMsg to the IPC service library. The IPC service library can work with different transport backends and uses the RPMsg backend with static VRINGs by default. This transport layer change affects all samples that use Bluetooth HCI driver over RPMsg, 802.15.4 spinel backend over IPC or nRF RPC libraries.
nRF5340: nRF RPC Entropy sample:
Converted from TinyCBOR to zcbor.
Added support for the factory reset functionality from Zigbee application utilities in the following samples:
Zigbee: Light switch sample:
Added identify handler.
Zigbee: Light bulb sample:
Removed implementation of Home Automation Profile Specification logic. This logic added dependency between On/Off and Level clusters, so changes in Level cluster were affecting the On/Off one.
Updated the frequency of the LED PWM signal to 100 Hz to remove excessive flickering.
Radio test sample:
Added new configuration that builds the sample with support for remote IPC Service shell on nRF5340 application core through USB.
Added possibility to build with the limited nRF21540 front-end module hardware pinout.
Improved the calculation of the total payload size for the radio duty cycle.
Fast ramp-up is enabled for all radio modes.
The duty cycle for modulated transmission is limited to 1-90%.
Improved the DFU throughput in the SMP Server Sample for the Bluetooth transport by optimizing Bluetooth MTU configuration and by leveraging the MCUmgr packet reassembly feature.
This section provides detailed lists of changes by driver.
Removed the deprecated GPS driver.
This section provides detailed lists of changes by library.
Bluetooth libraries and services
Removed Alexa Gadgets Service library due to Amazon pausing support for the Gadgets ecosystem.
GATT Discovery Manager library:
Added option to discover several service instances using the UUID.
Fixed discovery of empty services.
Bluetooth mesh profile library:
Added Modem antenna library, a new library for setting the antenna configuration on an nRF9160 DK or a Thingy:91.
SMS subscriber library:
Fixed time zone handling for received SMSs.
The time zone is now returned in quarters of an hour.
Added handling for SMS client unregistration notification from the modem. When the notification is received, the library re-registers the SMS client automatically.
Support for the
Improved integration of A-GPS and P-GPS when both are enabled.
A missing call to the
nrf_cloud_pgps_notify_prediction()function, when using the REST interface with P-GPS.
Support for P-GPS data retrieval from an external source, implemented separately by the application. Enabled by setting the
CONFIG_LOCATION_METHOD_GNSS_PGPS_EXTERNALoption. The library triggers a
LOCATION_EVT_GNSS_PREDICTION_REQUESTevent when assistance is needed.
Obstructed satellite visibility detection feature for GNSS. When this feature is enabled, the library tries to detect occurrences where getting a GNSS fix is unlikely or would consume a lot of energy. When such an occurrence is detected, GNSS is stopped without waiting for a fix or a timeout.
In addition to the current default fallback mode for acquiring a location, it can also be acquired using the
LOCATION_REQ_MODE_ALLmode that runs all methods in the list sequentially. Each run method receives a location event, either a success or a failure.
requestmember of the
location_event_datastructure renamed to
Current system time is attached to the
location_datetimeparameter of the location request response with Wi-Fi and cellular methods. The timestamp comes from the moment of scanning or neighbor measurements.
Removed support for Skyhook.
Modem library integration layer library:
NRF_MODEM_LIB_ON_INITmacro for compile-time registration of callbacks on modem initialization.
NRF_MODEM_LIB_ON_SHUTDOWNmacro for compile-time registration of callbacks on modem de-initialization.
CONFIG_NRF_MODEM_LIB_LOG_FW_VERSION_UUIDto enable logging for both FW version and UUID at the end of the library initialization step.
CONFIG_NRF_MODEM_LIB_TRACE_THREAD_PROCESSINGto process modem traces in a thread (experimental).
The modem fault handler’s signature now takes a pointer as parameter to the
The modem fault handler callback is now configurable through the
LTE link controller library:
Modem attestation token library:
CBOR parsing is now performed with the zcbor module. TinyCBOR is deprecated.
Removed the deprecated A-GPS library.
Fixed an issue where the compiler would generate an error when building
ncs/nrf/include/modem/lte_lc.hwith C++ applications.
Libraries for networking
nRF Cloud REST library:
Added JSON Web Token (JWT) autogeneration feature. If enabled, the nRF Cloud REST library automatically generates a JWT if none is provided by the user when making REST requests.
Centralized error handling.
Error return values.
For cellular positioning responses, the type is now set based on the
fulfilledWithresponse from the nRF Cloud.
nRF Cloud error codes are now parsed and set in the
Download client library:
Fixed an issue where downloads of COAP URIs would fail when they contained multiple path elements.
set_native_tlsparameter in the configuration structure to configure native TLS support at runtime.
FOTA download library:
nRF Cloud library:
nrf_cloud_bootloader_fota_slot_set()function that sets the active bootloader slot flag during bootloader FOTA updates.
nrf_cloud_pending_fota_job_process()function that processes the state of pending FOTA jobs.
nrf_cloud_handle_error_message()function that handles error message responses (MQTT) from nRF Cloud.
Shadow data behavior during the connection process. The data is now sent to the application even if no
"config"section is present.
The application can now send shadow updates earlier in the connection process.
nRF Cloud error message responses to location service MQTT requests are now handled.
The value of the
CONFIG_NRF_CLOUD_HOST_NAMEoption is now
Removed support for the Cloud API.
Fixed the validation of bootloader FOTA updates.
AWS IoT library:
Removed support for the Cloud API.
LwM2M client utils library:
Added support for using location assistance when using the Coiote LwM2M server.
Updated the library to store credentials and server settings permanently on bootstrap.
Updated the library to let an application control the network connection state.
Azure IoT Hub library:
CONFIG_AZURE_IOT_HUB_NATIVE_TLSoption to configure the socket to be native for TLS instead of offloading TLS operations to the modem.
Removed support for the Cloud API.
nRF Cloud P-GPS library:
The passing of the current prediction, if one is available, along with the
The following three ways to define the storage location in the flash memory:
A dedicated P-GPS partition, enabled with the
The use of the MCUboot secondary partition as storage, enabled with the
An application-specific storage, enabled with the
nRF Cloud A-GPS library:
Fixed premature assistance suppression when the
CONFIG_NRF_CLOUD_AGPS_FILTEREDoption is enabled. Added a 10 minute margin of error to ensure A-GPS assistance is downloaded every two hours even if the modem requests assistance a little early.
Multicell location library:
Removed support for Skyhook.
Removed the Cloud API library.
Libraries for NFC
Event type flags to represent if event type should be logged, traced, and whether it has dynamic data. To update your application, pass a flag variable as a parameter in
APP_EVENT_FLAGS_CREATEto set multiple flags:
APP_EVENT_TYPE_DEFINE(my_event, log_my_event, &my_event_info, APP_EVENT_FLAGS_CREATE(APP_EVENT_TYPE_FLAGS_1, APP_EVENT_TYPE_FLAGS_2));
Universal hooks for Application Event Manager initialization, event submission, preprocessing, and postprocessing. This includes implementation of macros that register hooks, grouped as follows:
Renamed Event Manager to Application Event Manager.
The library is no longer directly referenced from the Application Event Manager. Instead, it uses the Application Event Manager hooks to connect with the manager.
Fixed a compilation error for nRF52833.
Renamed Profiler to nRF Profiler.
Updated versions of required python modules (pynrfjprog and matplotlib).
CONFIG_EI_WRAPPER_PROFILINGfor logging time of classifier execution.
Hardware unique key library:
Fixed a bug where the random key would not be deleted from RAM after being generated and written.
RAM power-down library:
Common Application Framework (CAF)
Added CAF: Sensor data aggregator module, which buffers sensor events and sends them as packages to the listener.
Added IPC service shell transport library.
Libraries for Zigbee
Zigbee application utilities library:
Added factory reset functionality in Zigbee application utilities library.
Zigbee shell library:
nbr monitorshell command for monitoring the list of active Zigbee neighbors.
zcl groupsshell commands for managing Zigbee groups.
CONFIG_ZIGBEE_SHELL_ZCL_CMD_TIMEOUTfor timing out ZCL cmd commands.
Zigbee shell structure to make it an independent library.
zigbee_cli*and changed it to
zigbee_cli*and changed it to
bdb factory_resetcommand. Now the command checks if the ZBOSS stack is started before performing the factory reset.
zcl cmdshell command extended to allow sending groupcasts.
zdoshell commands extended to allow binding to a group address.
Internal context manager structures.
Fixed an issue where the
zcl cmdshell command was using the incorrect index of a context manager entry during cleanup after the command was sent.
Zigbee ZCL scene helper library:
Updated the library, so that it is allowed to store empty scenes.
Zigbee ZBOSS OSIF library:
Crypto library used for performing software AES encryption. Now, the nrf_oberon crypto library is used instead of the Tinycrypt library.
Optimize calling ZBOSS API in nRF Connect SDK platform. If the ZBOSS API is called in the ZBOSS thread context, processing by the workqueue is now skipped.
Zigbee FOTA library:
CONFIG_ZIGBEE_FOTA_SERVER_DISOVERY_INTERVAL_HRSKconfig option to configure the interval between queries for the Zigbee FOTA server.
CONFIG_ZIGBEE_FOTA_IMAGE_QUERY_INTERVAL_MINKconfig option to configure the interval between queries for the available Zigbee FOTA images.
Support for the combined application and network core updates for the nRF5340 SoC.
Download logic to use the DFU multi-image library API and image structure.
The image generation script by introducing the sub-element structure inside the Zigbee OTA image. Enable
CONFIG_ZIGBEE_FOTA_GENERATE_LEGACY_IMAGE_TYPEto generate images compatible with previous nRF Connect SDK releases.
Default value of the
Setting of the
CONFIG_NRF53_ENFORCE_IMAGE_VERSION_EQUALITYfor nRF5340 SoC to ensure integrity of the upgrade image.
An issue where printing binding table containing group-binding entries results in corrupted output.
An issue where Zigbee shell coordinator would not form a new network after the factory reset operation.
See the changelog for each library in the nrfxlib documentation for additional information.
Support for connectionless angle of arrival (AoA) transmitter.
Support for peripheral-initiated feature exchange.
nak_countfield into QoS Connection event reports.
Added support for nRF52832 and nRF5340.
This section provides detailed lists of changes by script.
The MCUboot fork in nRF Connect SDK (
sdk-mcuboot) contains all commits from the upstream MCUboot repository up to and including
e86f575f68fdac2cab1898e0a893c8c6d8fd0fa1, plus some nRF Connect SDK specific additions.
The code for integrating MCUboot into nRF Connect SDK is located in the
The following list summarizes both the main changes inherited from upstream MCUboot and the main changes applied to the nRF Connect SDK specific additions:
CONFIG_NRF53_ENFORCE_IMAGE_VERSION_EQUALITYto attach the dependencies between application and network core images. This option links the upgrade images in such a way that either both or none is applied.
Added support for the Dual-slot execute-in-place (XIP) feature in the nRF Connect SDK build system. See the
ncs/nrf/tests/modules/mcuboot/direct_xiptest project for an example of how to leverage this feature in your application.
boot_serialto Zephyr’s new CRC APIs (boot_serial implements the serial recovery).
boot_serial_extensionimplements the serial recovery extension).
Loader was reworked so it allows larger minimum flash write size (was 8 B, now 32 B).
Added optional timeout to enter serial recovery for
zephyrto use a smaller SHA-256 implementation.
Added support for the echo command to
Modified the single loader to fix image decryption for any SoC flash of the pages with size not fitting in 1024 B.
Fixed usage of
The Zephyr fork in nRF Connect SDK (
sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including
53fbf40227de087423620822feedde6c98f3d631, plus some nRF Connect SDK specific additions.
For the list of upstream Zephyr commits (not including cherry-picked commits) incorporated into nRF Connect SDK since the most recent release, run the following command from the
ncs/zephyr repository (after running
git log --oneline 53fbf40227 ^45ef0d2
For the list of nRF Connect SDK specific commits, including commits cherry-picked from upstream, run:
git log --oneline manifest-rev ^53fbf40227
The current nRF Connect SDK main branch is based on revision
53fbf40227 of Zephyr.
In March 2022, cddl-gen has been renamed to zcbor. zcbor is now provided through Zephyr instead of directly in nRF Connect SDK.
The zcbor module has been updated from version 0.3.0 to 0.4.0.
Release notes for 0.4.0 can be found in
The following major changes have been implemented:
zcborthroughout the repository.
Regenerated fmfu code from cddl.
Added Kconfig options to control the zcbor configuration options.
Updated tests to run with updated zcbor.
NCSDK-13949 known issue where the TF-M secure image would copy FICR to RAM on the nRF9160 SiP.
NCSDK-12306 known issue where a usage fault would be triggered in the debug build on nRF9160 SiP.
NCSDK-14015 known issue that would cause crash during boot when the
CONFIG_RPMSG_SERVICEKconfig option is enabled on the nRF5340 SoC.
Fixed an issue with floats in the cJSON module when using NEWLIB_LIBC without the
Migration notes for nRF Connect SDK v2.0.0 reflecting major changes in nRF Connect SDK v2.0.0 that might require a migration action.
Section describing how to enable Amazon Frustration-Free Setup (FFS) support in Matter device identification user guide.
Notes to the Bluetooth: Central SMP Client sample document specifying the intended use of the sample.
A page on Software maturity levels listing the different software maturity levels for the available features.
A page on Pin control.
Documentation for Getting started with Thingy:53.
Documentation page about Zigbee commissioning.
Documentation for Asset tracker v2 Unit tests.
New Security page on the top level, with a brief introduction to core security features available in Nordic Semiconductor products.
The nRF Connect SDK documentation website with a new look-and-feel to improve its usability.
Working with nRF5340 DK and Working with nRF91 Series user guides with information about Trusted Firmware-M replacing Secure Partition Manager as the default solution for creating a Trusted Execution Environment.
Some samples and applications built as a non-secure firmware image for the
_nsbuild target to reflect that the Trusted Firmware-M (TF-M) is automatically included instead of Secure Partition Manager (SPM).
Power optimization guide with information on how to disable serial logging when using TF-M.
Replaced reference to Secure Partition Manager with reference to Trusted Firmware-M for multi-image project builds (nRF9160 samples) in Building and programming an application page.
Updating repositories and tools page with information about updating Visual Studio Code and the toolchain.
Protocol architecture diagram in Matter architecture page.
Memory footprint optimization page with sections for Matter and Zigbee.
Updating pre-built OpenThread libraries section to clarify the use, and added Visual Studio Code instructions.
Added a note to several nRF Cloud samples using the nRF Cloud REST API indicating the need for valid and registered request signing credentials.
OpenThread memory requirements page with definitions of variants listed on the tables.
Using nRF Cloud with the nRF Connect SDK page with more information about security.
Working with Thingy:53 user guide with new information, and renamed it to Developing with Thingy:53.
nRF Desktop documentation with the following additions:
nRF9160: LwM2M Client sample documentation with a state diagram.
The relevant Thread sample documentation pages with information about support for Trusted Firmware-M.
All Thread samples documentation with a Configuration section, and organized relevant information under that section.
Gazell samples documentation by separating the Gazell samples into their own pages for Host and Device. There are now four different sample pages, where each Host sample must be used along with its corresponding Device sample.
Moved the Using nRF Cloud with the nRF Connect SDK page to the top level of the navigation.
Documentation on the Getting Started Assistant, as this tool is no longer in use. Linux users can install the nRF Connect SDK by using the Installing using Visual Studio Code instructions or by following the steps on the Installing manually page.
Documentation on the SEGGER Embedded Studio, as this tool will no longer be supported moving forward. The previous nRF Connect SDK releases still support SEGGER Embedded Studio (Nordic edition). To migrate from SEGGER Embedded Studio IDE or on the command line to Visual Studio Code, follow the instructions in the migrating from other IDEs to VS Code documentation.
Added Visual Studio Code instructions on the following documentation: