Changelog for nRF Connect SDK v3.0.0-preview2

This changelog reflects the most relevant changes from the latest official release.

Known issues

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

Changelog

The following sections provide detailed lists of changes by component.

IDE, OS, and tool support

  • Updated:

    • The required SEGGER J-Link version to v8.18.

    • The Installation page with the following:

      • The Install prerequisites section with a list valid for both development environments. The list now includes nRF Util as an additional requirement for west runner for the nRF Connect for VS Code, and the Windows-only requirement to install SEGGER USB Driver for J-Link for both development environments.

      • The command-line instructions now use the nrfutil sdk-manager command instead of the nrfutil toolchain-manager command. You can read more about the new command in the nRF Util documentation.

Board support

  • Removed support for the nRF52810 Desktop Mouse board (nrf52810dmouse/nrf52810).

Build and configuration system

Bootloaders and DFU

No changes since the latest nRF Connect SDK release.

Developing with nRF91 Series

No changes since the latest nRF Connect SDK release.

Developing with nRF70 Series

Developing with nRF54L Series

Developing with nRF54H Series

Developing with nRF53 Series

No changes since the latest nRF Connect SDK release.

Developing with nRF52 Series

No changes since the latest nRF Connect SDK release.

Developing with Thingy:91 X

No changes since the latest nRF Connect SDK release.

Developing with Thingy:91

No changes since the latest nRF Connect SDK release.

Developing with Thingy:53

No changes since the latest nRF Connect SDK release.

Developing with Front-End Modules

Developing with PMICs

Developing with custom boards

No changes since the latest nRF Connect SDK release.

Security

Protocols

No changes since the latest nRF Connect SDK release.

Amazon Sidewalk

No changes since the latest nRF Connect SDK release.

Bluetooth® LE

  • Updated the Bluetooth LE SoftDevice Controller driver to make the hci_vs_sdc_llpm_mode_set() function return an error if Low Latency Packet Mode (LLPM) is not supported or not enabled in the Bluetooth LE Controller driver configuration (CONFIG_BT_CTLR_SDC_LLPM).

  • Fixed:

    • An issue where a flash operation executed on the system workqueue might result in -ETIMEDOUT, if there is an active Bluetooth LE connection.

    • An issue where Bluetooth applications built with the nordic-bt-rpc snippet (in the Bluetooth Low Energy Remote Procedure Call configuration) did not work on the nRF54H20 devices due to incorrect memory mapping.

Bluetooth Mesh

DECT NR+

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst (ESB)

  • Added loading of radio trims and a fix of a hardware errata for the nRF54H20 SoC to improve the RF performance.

Gazell

No changes since the latest nRF Connect SDK release.

Matter

Matter fork

  • Added a new kFactoryReset event that is posted during factory reset. The application can register a handler and perform additional cleanup.

nRF IEEE 802.15.4 radio driver

No changes since the latest nRF Connect SDK release.

Thread

No changes since the latest nRF Connect SDK release.

Zigbee

  • Removed all Zigbee resources. They are now available as separate Zigbee R22 and Zigbee R23 add-on repositories.

Wi-Fi®

Applications

This section provides detailed lists of changes by application.

Machine learning

Asset Tracker v2

  • Updated the application to use the Downloader library instead of the deprecated Download client library.

Connectivity Bridge

No changes since the latest nRF Connect SDK release.

IPC radio firmware

  • Updated:

    • The application to enable the Zephyr Memory Storage (ZMS) file system in all devices that contain MRAM, such as the nRF54H Series devices.

    • The documentation of applications and samples that use the IPC radio firmware as a companion component to mention its usage when built with Sysbuild.

Matter Bridge

  • Updated by enabling Link Time Optimization (LTO) by default for the release configuration.

  • Removed support for the nRF54H20 devices.

nRF5340 Audio

No changes since the latest nRF Connect SDK release.

nRF Desktop

  • Added:

    • System Power Management for the nRF54H20 DK board target on the application and radio cores.

    • Application configurations for the nRF54L05 and nRF54L10 SoCs (emulated on the nRF54L15 DK). The configurations are supported through nrf54l15dk/nrf54l10/cpuapp and nrf54l15dk/nrf54l05/cpuapp board targets. For details, see the nRF Desktop: Board configuration.

    • The dongle_small configuration for the nRF52833 DK. The configuration enables logs and mimics the dongle configuration used for small SoCs.

    • Requirement for zero latency in Zephyr’s System Power Management while USB is active (CONFIG_DESKTOP_USB_PM_REQ_NO_PM_LATENCY Kconfig option of the USB state power manager module). The feature is enabled by default if Zephyr power management (CONFIG_PM) is enabled. It prevents entering power states that introduce wakeup latency and ensure high performance.

    • Static Partition Manager memory maps for single-image configurations (without bootloader and separate radio/network core image). In the nRF Connect SDK, the Partition Manager is enabled by default for single-image sysbuild builds. The static memory map ensures control over settings partition placement and size. The introduced static memory maps may not be consistent with the storage_partition defined by the board-level DTS configuration.

  • Updated:

    • The Failsafe module to use the Zephyr Hardware Information driver for getting and clearing the reset reason information (see the hwinfo_get_reset_cause() and hwinfo_clear_reset_cause() functions). The Zephyr Hardware Information driver replaces the dependency on the nrfx reset reason helper (see the nrfx_reset_reason_get() and nrfx_reset_reason_clear() functions).

    • The release configuration for the nRF54H20 DK board target to enable the Failsafe module (see the CONFIG_DESKTOP_FAILSAFE_ENABLE Kconfig option).

    • Enabled Link Time Optimization (CONFIG_LTO and CONFIG_ISR_TABLES_LOCAL_DECLARATION) by default for an nRF Desktop application image. LTO was also explicitly enabled in configurations of other images built by sysbuild (bootloader, network core image).

    • Application configurations for nRF54L05, nRF54L10, and nRF54L15 SoCs to use Fast Pair PSA cryptography (CONFIG_BT_FAST_PAIR_CRYPTO_PSA). Using PSA cryptography improves security and reduces memory footprint. Also increased the size of the Bluetooth receiving thread stack (CONFIG_BT_RX_STACK_SIZE) to prevent stack overflows.

    • Application configurations for the nRF52820 SoC to reduce memory footprint:

    • Application configurations for HID peripherals by increasing the following thread stack sizes to prevent stack overflows during the settings_load() operation:

      This change results from the Bluetooth subsystem transition to the PSA cryptographic API. The GATT database hash calculation now requires larger stack size.

    • Support for Bluetooth LE legacy pairing is no longer enabled by default, because it is not secure. Using Bluetooth LE legacy pairing introduces, among others, a risk of passive eavesdropping. Supporting Bluetooth LE legacy pairing makes devices vulnerable for a downgrade attack. The CONFIG_BT_SMP_SC_PAIR_ONLY Kconfig option is enabled by default in Zephyr. If you still need to support the Bluetooth LE legacy pairing, you need to disable the option in the configuration.

    • HID state module and Function key module to use bsearch() implementation from C library. This simplifies maintenance and allows you to use Picolibc (CONFIG_PICOLIBC).

    • The IPC radio image configurations of the nRF5340 DK to use Picolibc (CONFIG_PICOLIBC). This aligns the configurations to the IPC radio image configurations of the nRF54H20 DK. Picolibc is used by default in Zephyr.

    • The nRF Desktop application image configurations to use Picolibc (CONFIG_PICOLIBC) by default. Using the minimal libc implementation (CONFIG_MINIMAL_LIBC) no longer decreases the memory footprint of the application image for most of the configurations.

    • Enabled USB Start of Frame (SOF) synchronization (CONFIG_DESKTOP_USB_HID_REPORT_SENT_ON_SOF Kconfig option) by default on the nRF54H Series SoC (CONFIG_SOC_SERIES_NRF54HX). The negative impact of USB polling jitter is more visible in case of USB High-Speed.

    • The Fast Pair sysbuild configurations to align the application with the sysbuild Kconfig changes for controlling the Fast Pair provisioning process. The Nordic device models intended for demonstration purposes are now supplied by default in the nRF Desktop Fast Pair configurations.

    • The DVFS module to no longer consume the ble_peer_conn_params_event. This allows to propagate the event to further listeners of the same or lower priority. This prevents an issue where Bluetooth LE latency module is not informed about the connection parameter update (it might cause missing connection latency updates).

  • Removed:

    • An imply from the nRF Desktop Bluetooth connectivity Kconfig option (CONFIG_DESKTOP_BT). The imply enabled a separate workqueue for connection TX notify processing (CONFIG_BT_CONN_TX_NOTIFY_WQ) if MPSL was used for synchronization between the flash memory driver and the radio (CONFIG_SOC_FLASH_NRF_RADIO_SYNC_MPSL). The workaround for the MPSL flash synchronization issue (NCSDK-29354 in the Known issues page) is no longer needed, as the issue is now fixed.

    • Application configurations for the nRF52810 Desktop Mouse board (nrf52810dmouse/nrf52810). The board is no longer supported in the nRF Connect SDK.

nRF Machine Learning (Edge Impulse)

No changes since the latest nRF Connect SDK release.

Serial LTE modem

  • Added an overlay overlay-memfault.conf file to enable Memfault. For more information about Memfault features in nRF Connect SDK, see Memfault.

  • Updated:

Thingy:53: Matter weather station

  • Updated by enabling Link Time Optimization (LTO) by default for the release configuration.

Samples

This section provides detailed lists of changes by sample.

Amazon Sidewalk samples

No changes since the latest nRF Connect SDK release.

Bluetooth samples

Bluetooth Mesh samples

Bluetooth Fast Pair samples

  • Added support for the nrf54l15dk/nrf54l05/cpuapp and nrf54l15dk/nrf54l10/cpuapp board targets in all Fast Pair samples.

  • Updated:

    • The non-secure target (nrf5340dk/nrf5340/cpuapp/ns and thingy53/nrf5340/cpuapp/ns) configurations of all Fast Pair samples to use configurable TF-M profile instead of the predefined minimal TF-M profile. This change results from the Bluetooth subsystem transition to the PSA cryptographic standard. The Bluetooth stack can now use the PSA crypto API in the non-secure domain as all necessary TF-M partitions are configured properly.

    • The configuration of all Fast Pair samples by increasing the following thread stack sizes to prevent stack overflows:

      This change results from the Bluetooth subsystem transition to the PSA cryptographic API.

    • The sysbuild configurations in samples to align them with the sysbuild Kconfig changes for controlling the Fast Pair provisioning process.

  • Removed using a separate workqueue for connection TX notify processing (CONFIG_BT_CONN_TX_NOTIFY_WQ) from configurations. The MPSL flash synchronization issue (NCSDK-29354 in the Known issues) is fixed. The workaround is no longer needed.

  • Bluetooth Fast Pair: Locator tag sample:

    • Added support for the following:

      • nRF54H20 DK board target.

      • Firmware update intents on the Android platform. Integrated the new connection authentication callback from the FMDN module and the Device Information Service (DIS) to support firmware version read operation over the Firmware Revision characteristic. For further details on the Android intent feature for firmware updates, see the Firmware update intent section of the Fast Pair integration guide.

    • Updated:

      • The partition layout for the nrf5340dk/nrf5340/cpuapp/ns and thingy53/nrf5340/cpuapp/ns board targets to accommodate the partitions needed due to a change in the TF-M profile configuration.

      • The debug (default) configuration of the main image to enable the Link Time Optimization (LTO) with the CONFIG_LTO Kconfig option. This change ensures consistency with the sample release configuration that has the LTO feature enabled by default.

Bluetooth Mesh samples

Cellular samples

Cryptography samples

Debug samples

No changes since the latest nRF Connect SDK release.

DECT NR+ samples

No changes since the latest nRF Connect SDK release.

Edge Impulse samples

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst samples

No changes since the latest nRF Connect SDK release.

Gazell samples

No changes since the latest nRF Connect SDK release.

Keys samples

No changes since the latest nRF Connect SDK release.

Matter samples

  • Added Matter: Manufacturer-specific sample that demonstrates an implementation of custom manufacturer-specific clusters used by the application layer.

  • Matter: Template sample:

    • Updated:

      • The documentation with instructions on how to build the sample on the nRF54L15 DK with support for Matter OTA DFU and DFU over Bluetooth SMP, and using internal RRAM only.

      • Link Time Optimization (LTO) to be enabled by default for the release configuration and nrf7002dk/nrf5340/cpuapp build target.

    • Removed support for nRF54H20 devices.

  • Matter: Door lock sample:

    • Removed support for nRF54H20 devices.

    • Updated the API of AppTask, BoltLockManager, and AccessManager to provide additional information for the LockOperation event.

Networking samples

  • Updated:

NFC samples

No changes since the latest nRF Connect SDK release.

nRF5340 samples

  • Removed the nRF5340: Multiprotocol RPMsg sample. Use the IPC radio firmware application instead.

Peripheral samples

  • Radio test (short-range) sample:

    • Added:

      • Loading of radio trims and a fix of a hardware errata for the nRF54H20 SoC to improve the RF performance.

PMIC samples

  • Added:

    • The nPM2100: One button sample that demonstrates how to support wake-up, shutdown, and user interactions through a single button connected to the nPM2100 PMIC.

    • The nPM2100: Fuel gauge sample that demonstrates how to calculate the battery state of charge of primary cell batteries using the nRF Fuel Gauge library.

  • nPM1300: Fuel gauge sample:

    • Updated to accommodate API changes in nRF Fuel Gauge library v1.0.0.

Protocol serialization samples

No changes since the latest nRF Connect SDK release.

SDFW samples

  • Removed the SDFW: Service Framework Client sample as all services demonstrated by the sample have been removed.

Sensor samples

No changes since the latest nRF Connect SDK release.

SUIT samples

No changes since the latest nRF Connect SDK release.

Trusted Firmware-M (TF-M) samples

Thread samples

  • Thread: CLI sample:

    • Removed support for the nRF54H20 DK.

Zigbee samples

  • Removed all Zigbee samples. They are now available as separate Zigbee R22 and Zigbee R23 add-on repositories.

Wi-Fi samples

Other samples

  • CoreMark sample:

    • Added:

      • Support for the nRF54L05 and nRF54L10 SoCs (emulated on nRF54L15 DK).

      • FLPR core support for the nRF54L15 DK and nRF54H20 DK board targets.

    • Removed the following compiler options that were set in the CONFIG_COMPILER_OPT Kconfig option:

      • -fno-pie

      • -fno-pic

      • -ffunction-sections

      • -fdata-sections

      These options are enabled by default in Zephyr and do not need to be set with the dedicated Kconfig option.

  • CAF: Sensor manager sample:

    • Added low power configuration for the nRF54H20 DK board target.

Drivers

This section provides detailed lists of changes by driver.

No changes since the latest nRF Connect SDK release.

Wi-Fi drivers

No changes since the latest nRF Connect SDK release.

Libraries

This section provides detailed lists of changes by library.

Binary libraries

  • LwM2M carrier library:

    • Updated the glue to use the Downloader library instead of the deprecated Download client library.

Bluetooth libraries and services

  • Google Fast Pair Service (GFPS) library:

    • Added:

      • A restriction on the CONFIG_BT_FAST_PAIR_FMDN_TX_POWER Kconfig option in the Find My Device Network (FMDN) extension configuration. You must set this Kconfig option now to 0 at minimum as the Fast Pair specification requires that the conducted Bluetooth transmit power for FMDN advertisements must not be lower than 0 dBm.

      • A new information callback - bt_fast_pair_fmdn_info_cb.conn_authenticated - to the FMDN extension API. In the FMDN context, this change is required to support firmware update intents on the Android platform. For further details on the Android intent feature for firmware updates, see the Firmware update intent section in the Fast Pair integration guide.

      • A workaround for the issue where the FMDN clock value might not be correctly set after the system reboot for nRF54L Series devices. For details, see the NCSDK-32268 issue in the Known issues page.

      • A new function bt_fast_pair_fmdn_is_provisioned() for the FMDN extension API. This function can be used to synchronously check the current FMDN provisioning state. For more details, see the Provisioning state section in the Fast Pair integration guide.

    • Updated:

    • Removed the sysbuild control over the CONFIG_BT_FAST_PAIR Kconfig option that is defined in the main (default) image. Sysbuild no longer sets the value of this Kconfig option.

  • Bluetooth Mesh libraries library:

    • Fixed an issue in the Light Lightness Control Server model to automatically resume the Lightness Controller after recalling a scene (NCSDK-30033 known issue).

Common Application Framework

  • CAF: Buttons module:

    • Added possibility of using more GPIOs. Earlier, only GPIO0 and GPIO1 devices were supported. Now, the generic solution supports all GPIOs available in the DTS.

  • CAF: Power manager module:

    • Updated:

      • The CONFIG_CAF_POWER_MANAGER Kconfig option to imply the device power management (CONFIG_DEVICE_PM) instead of selecting it. The device power management is not required by the module.

      • The CONFIG_CAF_POWER_MANAGER Kconfig option to imply device runtime power management (CONFIG_PM_DEVICE_RUNTIME) for the nRF54H Series SoC (CONFIG_SOC_SERIES_NRF54HX). The feature can be used to reduce the power consumption of device drivers. Enabling the device runtime power management also prevents using system-managed device power management (CONFIG_PM_DEVICE_SYSTEM_MANAGED) by default. The system-managed device power management does not work properly with some drivers (for example, nrfx UARTE) and should be avoided.

Debug libraries

No changes since the latest nRF Connect SDK release.

DFU libraries

No changes since the latest nRF Connect SDK release.

Gazell libraries

No changes since the latest nRF Connect SDK release.

Security libraries

No changes since the latest nRF Connect SDK release.

Modem libraries

  • Deprecated the AT parameters library.

  • PDN library:

  • LTE link control library:

    • Fixed handling of %NCELLMEAS notification with status 2 (measurement interrupted) and no cells.

    • Added sending of LTE_LC_EVT_NEIGHBOR_CELL_MEAS event with current_cell set to LTE_LC_CELL_EUTRAN_ID_INVALID in case an error occurs while parsing the %NCELLMEAS notification.

  • Modem key management library:

    • Added:

      • The modem_key_mgmt_digest() function that would retrieve the SHA1 digest of a credential from the modem.

      • The modem_key_mgmt_list() function that would retrieve the security tag and type of every credential stored in the modem.

    • Fixed:

      • An issue with the modem_key_mgmt_clear() function where it returned -ENOENT when the credential was cleared.

      • A race condition in several functions where +CMEE error notifications could be disabled by one function before the other one got a chance to run its command.

      • An issue with the modem_key_mgmt_clear() function where +CMEE error notifications were not restored to their original state if the AT%CMNG AT command failed.

      • The modem_key_mgmt_clear() function to lock the shared scratch buffer.

  • Updated the Network interface driver to automatically set the actual link Maximum Transmission Unit (MTU) on the network interface when PDN connectivity is gained.

  • Modem library integration layer:

    • Fixed a bug where various subsystems would be erroneously initialized during a failed initialization of the library.

  • Location library:

    • Removed references to HERE location services.

  • AT Host library:

    • Fixed a bug where AT responses would erroneously be written to the logging UART instead of being written to the chosen ncs,at-host-uart UART device when the CONFIG_LOG_BACKEND_UART Kconfig option was set.

  • Modem information library:

Multiprotocol Service Layer libraries

  • Added:

    • Integration with the nrf2 clock control driver for the nRF54H20 SoC.

    • Integration with Zephyr’s system power management for the nRF54H20 SoC.

    • Global domain HSFLL120 320MHz frequency request if MPSL is enabled. The high frequency in global domain is required to ensure that fetching instructions from L2-cache and MRAM is as fast as possible. It is needed for the radio protocols to operate correctly.

    • MRAM always-on request for scheduled radio events. It is needed to avoid MRAM wake-up latency for radio protocols.

Libraries for networking

Libraries for NFC

No changes since the latest nRF Connect SDK release.

nRF RPC libraries

No changes since the latest nRF Connect SDK release.

Other libraries

  • Removed the following unused SDFW services: echo_service, reset_evt_service, and sdfw_update_service.

  • Distance Measurement library:

    • Updated the default timeslot duration to avoid an overstay assert when the ranging failed.

Security libraries

No changes since the latest nRF Connect SDK release.

Shell libraries

No changes since the latest nRF Connect SDK release.

Libraries for Zigbee

  • Removed Zigbee libraries. They are now available as separate Zigbee R22 and Zigbee R23 add-on repositories.

sdk-nrfxlib

See the changelog for each library in the nrfxlib documentation for additional information.

Scripts

This section provides detailed lists of changes by script.

  • HID configurator for nRF Desktop:

    • Removed HID device type mapping for Development Kits. A Development Kit may use various HID roles (depending on configuration). Assigning a fixed type for each board might be misleading. HID device type is still defined for boards that are always configured as the same HID device type.

Integrations

This section provides detailed lists of changes by integration.

Google Fast Pair integration

  • Added:

    • Instructions on how to provision the Fast Pair data onto devices without the Partition Manager support, specifically for the nRF54H20 DK.

    • Information on how to support the firmware update intent feature on the Android platform. Expanded the documentation for the Fast Pair devices with the FMDN extension, which requires additional steps to support this feature.

  • Updated:

Edge Impulse integration

No changes since the latest nRF Connect SDK release.

Memfault integration

AVSystem integration

No changes since the latest nRF Connect SDK release.

nRF Cloud integration

No changes since the latest nRF Connect SDK release.

CoreMark integration

No changes since the latest nRF Connect SDK release.

DULT integration

No changes since the latest nRF Connect SDK release.

MCUboot

The MCUboot fork in nRF Connect SDK (sdk-mcuboot) contains all commits from the upstream MCUboot repository up to and including a2bc982b3379d51fefda3e17a6a067342dce1a8b, with some nRF Connect SDK specific additions.

The code for integrating MCUboot into nRF Connect SDK is located in the ncs/nrf/modules/mcuboot folder.

The following list summarizes both the main changes inherited from upstream MCUboot and the main changes applied to the nRF Connect SDK specific additions:

  • Fixed an issue where an unusable secondary slot was cleared three times instead of once during cleanup.

Zephyr

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including fdeb7350171279d4637c536fcceaad3fbb775392, with 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 west update):

git log --oneline fdeb735017 ^beb733919d

For the list of nRF Connect SDK specific commits, including commits cherry-picked from upstream, run:

git log --oneline manifest-rev ^fdeb735017

The current nRF Connect SDK main branch is based on revision fdeb735017 of Zephyr.

Note

For possible breaking changes and changes between the latest Zephyr release and the current Zephyr version, refer to the Zephyr release notes.

Additions specific to nRF Connect SDK

No changes since the latest nRF Connect SDK release.

zcbor

No changes since the latest nRF Connect SDK release.

Trusted Firmware-M

No changes since the latest nRF Connect SDK release.

cJSON

No changes since the latest nRF Connect SDK release.

Documentation