nRF Connect SDK v1.7.0 Release Notes
nRF Connect SDK delivers reference software and supporting libraries for developing low-power wireless applications with Nordic Semiconductor products. It includes the TF-M, 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 are now supported for production. Wireless protocol stacks and libraries may indicate support for development or support for production for different series of devices based on verification and certification status. See the release notes and documentation for those protocols and libraries for further information.
Development support for multi-image DFU for nRF53 - simultaneous application and network core firmware update.
Working with RF front-end modules for the nRF21540 FEM range extender is now supported for production.
Added Wi-Fi coexistence feature supported for development for Thread and Zigbee.
Added support for NFC and pair before use type of accessories to the Apple Find My add-on.
Added support for the nRF Connect SDK development in Visual Studio Code with the nRF Connect for Visual Studio Code extension.
Added production support for nRF52833 for Bluetooth® LE HomeKit accessories.
For Bluetooth® mesh, the choice of default Bluetooth® LE Controller changed from Zephyr Bluetooth® LE Controller to SoftDevice Controller.
Bluetooth® mesh profiles and models are ready for production.
Updated the required minimum CMake version to 3.20.0.
nRF Connect for Cloud is now nRF Cloud.
Added support for using nRF Cloud Location Services through REST and JWT for the nRF9160.
Programming nRF52832 revision 3 and nRF52840 revision 3 devices requires nrfjprog version 10.13 or newer. nrfjprog is part of the nRF Command Line Tools.
The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v1.7.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.
See Modem firmware compatibility matrix for an overview of which modem firmware versions have been tested with this version of the nRF Connect SDK.
See known issues for nRF Connect SDK v1.7.0 for the list of issues valid for this release.
The following sections provide detailed lists of changes by component.
All samples built for the nRF9160 SoC now have the Modem library library enabled by default.
nRF Cloud library:
nrf_cloud_uninit(), which can be used to uninitialize the nRF Cloud library. If cloud API is used, call
nrf_cloud_shadow_device_status_update(), which sets the device status in the device’s shadow.
nrf_cloud_modem_info_json_encode(), which encodes modem information into a cJSON object formatted for use with nRF Cloud.
nrf_cloud_service_info_json_encode(), which encodes service information into a cJSON object formatted for use with nRF Cloud.
nrf_cloud_client_id_get(), which returns the client ID used to identify the device with nRF Cloud.
nrf_cloud_tenant_id_get(), which returns the tenant ID used to identify a customer account with nRF Cloud.
nrf_cloud_register_gateway_state_handler()to implement a custom callback on shadow update events.
Added Kconfig option
CONFIG_NRF_CLOUD_GATEWAY, which enables functionality to behave as an nRF Cloud gateway.
Added the option to use the P-GPS API independent of nRF Cloud MQTT transport.
Implemented functionality for the
NRF_CLOUD_EVT_SENSOR_DATA_ACKevent. The event is now generated when a valid tag value (NCT_MSG_ID_USER_TAG_BEGIN through NCT_MSG_ID_USER_TAG_END) is provided with the sensor data when calling either
nrf_cloud_shadow_update()to expect that
param->data.ptrpoints to a JSON string. Previously, a cJSON object was expected.
nct_init()to perform FOTA initialization before setting the client ID. This fixes an issue that prevented an expected reboot during a modem FOTA update.
Removed the function
nrf_cloud_sensor_attach(), the associated structure
nrf_cloud_sa_param, and the event
NRF_CLOUD_EVT_SENSOR_ATTACHED. These items provided no useful functionality.
nRF9160: Serial LTE modem application:
Added IPv6 support to all SLM services.
Added the GNSS service to replace the existing GPS test functionality.
Added the optional support of location services from nRF Cloud, such as A-GPS, P-GPS, and cellular positioning.
Removed datatype in all sending AT commands. If no sending data is specified, switch data mode to receive and send any arbitrary data.
Added the Running in data mode documentation page to explain the data mode mechanism and how it works.
Added the FOTA AT commands documentation page to describe the FOTA service.
nRF9160: Asset Tracker v2 application:
Added support for A-GPS when configuring the application for AWS IoT.
Added support for P-GPS when configuring the application for AWS IoT.
Added support for the LwM2M carrier library.
LwM2M carrier library:
Added deferred event reason
LWM2M_CARRIER_DEFERRED_SERVICE_UNAVAILABLE, which indicates that the LwM2M server is unavailable due to maintenance.
Removed error code
LWM2M_CARRIER_ERROR_SERVICE_UNAVAILABLE, which was used incorrectly to indicate a deferred event reason.
LTE link controller library - Added API to enable modem domain events.
nrf5340dk_nrf5340_cpuappnsboards have been renamed respectively to
nrf5340dk_nrf5340_cpuapp_ns, in a change inherited from upstream Zephyr.
thingy91_nrf9160nsboard has been renamed to
thingy91_nrf9160_nsfor consistency with the changes inherited from upstream Zephyr.
nRF9160: Asset Tracker has been deprecated in favor of nRF9160: Asset Tracker v2.
at_notiflibrary library has been deprecated in favor of the AT monitor library.
at_cmdlibrary library has been deprecated in favor of Modem library’s native AT interface.
GPS driver has been deprecated in favor of the GNSS interface.
The following changes are relevant for the nRF52 and nRF53 Series.
Added a functionality to clear the button state reported over Bluetooth® LE if the USB was connected while the button was pressed. This fixes an issue related to reporting wrong button state over Bluetooth® LE.
Added support for HID keyboard LED output report. The report is handled by the nRF Desktop peripherals and forwarded by the nRF Desktop dongles.
Added support for nRF5340 DK working as an nRF Desktop dongle.
Added a functionality for forwarding HID boot reports in HID forward module.
Added GPIO LEDs to the
Changed settings backend from FCB to NVS.
Switched to using CAF: Power manager module.
Fixed an issue with generating motion in Motion module (
motion_simulated) while the HID boot protocol was in use.
Production support for nRF21540 GPIO for both nRF52 and nRF53 Series.
Running Speed and Cadence Service (RSCS) - This module implements the Running Speed and Cadence Service (RSCS) with the corresponding set of characteristics.
Bluetooth: Peripheral Running Speed and Cadence Service (RSCS) sample - This sample demonstrates how to use the Running Speed and Cadence Service (RSCS).
Experimental implementation of the UART async adapter extension inside the Bluetooth: Peripheral UART sample.
Bluetooth: Direction finding connectionless locator and Bluetooth: Direction finding connectionless beacon samples - Added default configuration for
Fixed the NCSDK-9820 known issue in the Bluetooth: Peripheral LBS sample. When Button 1 was pressed and released while holding one of the other buttons, the notification for release was the same as for press.
Fixed an issue in the GATT Discovery Manager library where a memory fault could happen if a peer device disconnected during the service discovery process.
LED Button Service (LBS) library - Added write request data validation in the LED characteristic.
The choice of default Bluetooth® LE Controller changed from Zephyr Bluetooth® LE Controller to SoftDevice Controller.
Bluetooth® mesh profiles and models are ready for production.
Updated samples with support for the Thingy:53.
Fixed an issue where beacons were stopped being sent after node reset.
Fixed an issue where the IV update procedure could be started immediately after the device has been provisioned.
Fixed multiple issues in the Bluetooth mesh sensor types module.
The model opcode callback
bt_mesh_model_op.funcis changed to return an error code if the message processing has failed. If you have implemented your own models, make sure to update opcode handlers of those models.
Scene Server now extends Generic Default Transition Time Server. If you are using the Scene Server, make sure that the Generic Default Transition Time Server instance is present on the element that is equal to or lower than the Scene Server’s element.
Light HSL Server and Light xyL Server no longer instantiate the Light Lightness Server through
BT_MESH_MODEL_LIGHT_XYL_SRVmacros respectively. Macros
BT_MESH_LIGHT_HSL_SRV_INITnow take a pointer to the
bt_mesh_lightness_srvinstance instead. Make sure to instantiate the Light Lightness Server if you are using any of these models.
Modified the ESB interrupts configuration to reduce the ISR latency and enable scheduling decision in the interrupt context.
Front-end module (FEM)
Added support for the nRF21540 GPIO interface to the nRF5340 network core.
Added support for RF front-end Modules (FEM) for nRF5340 in the Multiprotocol Service Layer library. The front-end module feature for nRF5340 in MPSL currently supports nRF21540, but does not support the SKY66112-11 device.
Added a device tree shield definition for the nRF21540 Evaluation Kit with the related documentation.
Thingy:53 weather station application.
Matter tools page with information about building options for Matter controllers.
PA/LNA GPIO interface support for RF front-end modules (FEM) in Matter.
Matter documentation set based on the documentation from the Matter submodule.
nRF IEEE 802.15.4 radio driver
IEEE 802.15.4 PHY test tool sample, with an experimental Antenna Diversity functionality.
Wi-Fi coexistence functionality supported for development.
Added support for nRF21540 for nRF52 Series and nRF53 Series, including Bluetooth® LE in the multiprotocol configuration.
Improvements in Thread 1.2 features:
Thread 1.2 supported in all samples.
Retransmissions are now supported when transmission security is handled by the radio driver.
Support for CSL Accuracy TLV in the MLE Parent Response.
Link Metrics data is now properly updated when using ACK-based Probing.
Added support for Thread Backbone Border Router on the Radio co-processor (RCP) architecture.
In this release, Zigbee is supported for development and should not be used for production. The nRF Connect SDK v1.5.1 contains the certified Zigbee solution supported for production.
Added production support for radio front-end module (FEM) for nRF52 Series devices and nRF21540 EK.
Added development support for radio front-end module (FEM) for nRF53 Series devices and nRF21540 EK.
Added development support for
nrf5340dk_nrf5340_cpuappto the Zigbee: NCP sample.
Zigbee ZCL scene helper library with documentation. This library was separated from the Zigbee light bulb sample.
Zigbee: Template sample. This minimal Zigbee router application can be used as the starting point for developing custom Zigbee devices.
Added user guide about Adding ZCL clusters to application that is based on the new template sample.
Added API for vendor-specific NCP commands. See the Zigbee NCP sample page for more information.
Added API for Zigbee command for getting active nodes.
ZBOSS Zigbee stack to version 18.104.22.168+4.0.0. See the Changelog in the nrfxlib documentation for detailed information.
ZBOSS NCP Host is now supported for production and updated to version 1.0.0.
Stack logs - Improved printing ZBOSS stack logs. Added new backend options to print ZBOSS stack logs with option for using binary format.
Fixed the KRKNWK-9743 known issue where the timer could not be stopped in Zigbee routers and coordinators.
Fixed the KRKNWK-10490 known issue that would cause a deadlock in the NCP frame fragmentation logic.
Fixed the KRKNWK-6071 known issue with inaccurate ZBOSS alarms.
Fixed the KRKNWK-5535 known issue where the device would assert if flooded with multiple Network Address requests.
Fixed an issue where the NCS would assert in the host application when the host started just after SoC’s SysReset.
The following changes are relevant for all device families.
Fixed a bug where
dfu_application.zipwould not be updated after rebuilding the code with changes.
Common Application Framework (CAF)
Updated the NFCT interrupt configuration to reduce the ISR latency and enable scheduling decision in the interrupt context.
Updated the URI messages and records library to allow encoding of URI strings longer than 255 characters.
Added profiling string data.
Optimized numeric data encoding.
Added a test case for the secure read service that verifies that only addresses within the accepted range can be read.
tfm_platform_system.cto fix a bug that returned
TFM_PLATFORM_ERR_INVALID_PARAMwhen the address passed is outside of the accepted read range.
Updated the default Remote procedure call library (nRF RPC) transport backend to use the RPMsg Service library.
See the changelog for each library in the nrfxlib documentation for additional information.
The AT socket API is now deprecated.
The DFU socket API is now deprecated.
nRF IEEE 802.15.4 radio driver
Modified the 802.15.4 Radio Driver Transmit API. For full information, see Changelog.
The MCUboot fork in nRF Connect SDK (
sdk-mcuboot) contains all commits from the upstream MCUboot repository up to and including
680ed07, plus some nRF Connect SDK specific additions.
The code for integrating MCUboot into nRF Connect SDK is located in
The following list summarizes the most important changes inherited from upstream MCUboot:
Added AES support for image encryption (based on mbedTLS).
MCUboot serial: Ported encoding to use the cddl-gen module (which removes dependency on the TinyCBOR library).
bootutil_public library: Made
The mcumgr library contains all commits from the upstream mcumgr repository up to and including snapshot
The following list summarizes the most important changes inherited from upstream mcumgr:
The Zephyr fork in nRF Connect SDK (
sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including
14f09a3b00, 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
git log --oneline 14f09a3b00 ^v2.6.0-rc1-ncs1
For a complete list of nRF Connect SDK specific commits, run:
git log --oneline manifest-rev ^14f09a3b00
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:
Support for Certificate-Authenticated Session Establishment (CASE) for communication among operational Matter nodes.
Support for OpenThread’s DNS Client to enable Matter node discovery on Thread devices.
Fixed the known issue KRKNWK-10387 where Matter service was needlessly advertised over Bluetooth® LE during DFU. Now if Matter pairing mode is not opened and the Bluetooth® LE advertising is needed due to DFU requirements, only the SMP service is advertised.
Reworked how external flash memory support is enabled. The MCUboot secondary partition can now be placed in external flash memory without modifying any nRF Connect SDK files.
In addition to documentation related to the changes listed above, the following documentation has been updated:
Added cross-search functionality to the documentation search feature available at the top-left corner of each documentation page. Searching now parses all documentation sets pages and displays the results for each set. For example, results from the nrfxlib documentation set will be listed with
nrfxlib >>before the page title.
Updated the pages in the Getting started section with information about the support for the new Visual Studio Code extension.
Updated the style and formatting of all figures across all documentation pages.
Renamed nRF Connect for Cloud to nRF Cloud.
Updated the FEM support section for the samples that offer this feature.
Implemented several formatting and style updates for consistency reasons.
Added the Developing with Thingy:53 user guide.
Added the Using nRF Cloud with the nRF Connect SDK user guide.
Added nRF9160: Serial LTE modem application pages:
Added the Thingy:53: Matter weather station application page.
Added the Crypto: PSA TLS sample page.
Added the Bluetooth GATT attribute pools library page.
Added the Running Speed and Cadence Service (RSCS) library page.
Added documentation pages for the following Zigbee libraries:
Glossary - Added definition for new terms, such as Attribute Protocol, CMSIS, GAP, and GATT.
Getting started section pages:
Requirements - Now includes information about the supported operating systems, previously listed on a separate page.
Installing automatically - Added information about Toolchain manager being available for macOS and steps for building from SEGGER Embedded Studio.
Installing manually - Added information about the version folder created when extracting the GNU Arm Embedded Toolchain and applied minor fixes based on usability testing (for example, to the Linux installation instructions).
Application development section pages:
Working with nRF91 Series user guide - Restructured into several subpages.
Working with nRF5340 DK user guide - Reworked with major updates.
Protocols section pages:
Applications section pages:
nRF9160: Asset Tracker v2 pages:
Restructured the single application page into several subpages.
Updated with information about using the LwM2M carrier library.
Updated the device modes section.
Added links and information about A-GPS and P-GPS support with nRF Cloud.
nRF9160: Serial LTE modem pages:
Removed the GPS AT commands page.
Samples section pages:
Bluetooth: Central SMP Client - Page added. Replaces Central DFU SMP sample.
Bluetooth: Direction finding connectionless locator - Updated with the section about Constant Tone Extension transmit and receive parameters.
Removed the weather station sample page for Matter. The sample has been upgraded to application.
nRF9160: HTTP full modem update - Updated with the description of its customization options for firmware files.
Zigbee: NCP - Updated with information about logging ZBOSS traces and about vendor-specific commands.
Libraries section pages:
nRF Profiler - Several updates.
About this documentation section pages:
Multiprotocol Service Layer section pages:
nRF 802.15.4 Radio Driver section pages:
Modem library section pages: