Changelog for nRF Connect SDK v2.8.0-preview1
The most relevant changes that are present on the main branch of the nRF Connect SDK, as compared to the latest official release, are tracked in this file.
Note
This file is a work in progress and might not cover all relevant changes.
Known issues
Known issues are only tracked for the latest official release. See known issues for nRF Connect SDK v2.7.0 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
Added explicit mention of the J-Link Software and Documentation Pack being required in the Install prerequisites section of the installation page.
Updated:
The required SEGGER J-Link version to v7.94i.
The Supported operating systems (firmware) table on the Requirements reference page:
Linux 24.04 and macOS 15 have been added to the list.
macOS 10.15, macOS 11, macOS 12 have been removed from the list.
Tier descriptions have been updated.
Board support
Added support for the Thingy:91 X board.
Updated Thingy:91 X board to use the
nordic,pm-ext-flashnode instead of external flash device name in static partitions.Removed invalid external flash from static partitions for Thingy:91 X.
Build and configuration system
Added:
The
SB_CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAMsysbuild Kconfig option to system that allows utilizing all available RAM when using TF-M on an nRF5340 device.Note
This has security implications and may allow secrets to be leaked to the non-secure application in RAM.
The
SB_CONFIG_MCUBOOT_NRF53_MULTI_IMAGE_UPDATEsysbuild Kconfig option that enables updating the network core on the nRF5340 SoC from external flash.The AP-Protect sysbuild Kconfig options to enable the corresponding AP-Protect Kconfig options for all images in the build:
SB_CONFIG_APPROTECT_LOCKfor theCONFIG_NRF_APPROTECT_LOCKKconfig option.SB_CONFIG_APPROTECT_USER_HANDLINGfor theCONFIG_NRF_APPROTECT_USER_HANDLINGKconfig option.SB_CONFIG_APPROTECT_USE_UICRfor theCONFIG_NRF_APPROTECT_USE_UICRKconfig option.SB_CONFIG_SECURE_APPROTECT_LOCKfor theCONFIG_NRF_SECURE_APPROTECT_LOCKKconfig option.SB_CONFIG_SECURE_APPROTECT_USER_HANDLINGfor theCONFIG_NRF_SECURE_APPROTECT_USER_HANDLINGKconfig option.SB_CONFIG_SECURE_APPROTECT_USE_UICRfor theCONFIG_NRF_SECURE_APPROTECT_USE_UICRKconfig option.
Added the
SB_CONFIG_LWM2M_CARRIER_DIVIDED_DFUsysbuild Kconfig option that enables the generation of proprietary application update files required for the LwM2M carrier divided FOTA procedure.Removed the non-working support for configuring the NSIB signing key through the environmental or command line variable (
SB_SIGNING_KEY_FILE) along with child image.Note
This feature has never been functional. To configure the signing key, use any available Kconfig method.
Deprecated the following devicetree properties:
owner-idperm-readperm-writeperm-executeperm-securenon-secure-callable
It is recommended to replace them with the new devicetree property:
nordic,access. See the migration guide for more information.Removed the non-working support for configuring the NSIB signing key through the environmental or command line variable (
SB_SIGNING_KEY_FILE) along with child image.Note
This feature has never been functional. To configure the signing key, use any available Kconfig method.
Bootloaders and DFU
Added:
Documentation for MCUboot image compression.
Documentation for Using QSPI XIP split image functionality.
A section in the sysbuild-related migration guide about the migration of QSPI XIP flash split code from child/parent image to sysbuild.
Updated the procedure for signing the application image built for booting by MCUboot in direct-XIP mode with revert support. Now, the Intel-Hex file of the application image automatically receives a confirmation flag.
Removed secure bootloader Kconfig
CONFIG_SECURE_BOOT_DEBUGand replaced with usage of logging subsystem.
See also the MCUboot section.
Developing with nRF91 Series
Added:
The nRF91 modem tracing with RTT backend snippet to enable modem tracing using the RTT trace backend.
The nRF91 modem tracing with RAM backend snippet to enable modem tracing using the RAM trace backend.
Developing with nRF70 Series
No changes since the latest nRF Connect SDK release.
Working with nRF54H Series
No changes since the latest nRF Connect SDK release.
Developing with nRF54L Series
Added:
nRF54L snippets to emulate these targets on an nRF54L15 DK. These are used only for development purposes.
The Working with the KMU and CRACEN page that provides more information about the cryptographic peripherals of the nRF54L Series devices, programming model for referencing keys, and configuration.
Updated the name and the structure of the section, with Developing with nRF54L Series as the landing page.
Removed the Getting started with the nRF54L15 PDK page, and instead included the information about the Quick Start app support.
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 Front-End Modules
No changes since the latest nRF Connect SDK release.
Developing with PMICs
No changes since the latest nRF Connect SDK release.
Security
Added:
The
CONFIG_CRACEN_IKG_SEED_KMU_SLOTKconfig option to allow customization of the KMU slot used to store CRACEN’s Internal Key Generator (IKG) seed. The default IKG seed slot is now 183 (previously 0).TF-M support for the nRF54L15 DK (board target
nrf54l15dk/nrf54l15/cpuapp/ns), replacing the nRF54L15 PDK (board targetnrf54l15pdk/nrf54l15/cpuapp/ns).
Protocols
This section provides detailed lists of changes by protocol. See Samples for lists of changes for the protocol-related samples.
Amazon Sidewalk
No changes since the latest nRF Connect SDK release.
Bluetooth® LE
Added functions
bt_hci_err_to_str()andbt_security_err_to_str()to allow printing error codes as strings. Each function returns string representations of the error codes when the corresponding Kconfig option,CONFIG_BT_HCI_ERR_TO_STRorCONFIG_BT_SECURITY_ERR_TO_STR, is enabled. The Bluetooth samples and nRF Audio applications are updated to use these new functions.Updated:
The SoftDevice Controller library to automatically select the
CONFIG_BT_LL_SOFTDEVICE_MULTIROLEKconfig option when using coexistence based onCONFIG_MPSL_CXfor nRF52 Series devices.The Bluetooth HCI driver is now present as a devicetree node in the device tree. The SoftDevice Controller driver uses a devicetree node named
bt_hci_sdcwith a devicetree binding compatible withnordic,bt-hci-sdc. The Zephyr Bluetooth LE Controller uses a devicetree node namedbt_hci_controllerwith a devicetree binding compatible withzephyr,bt-hci-ll-sw-split. You need to update applications using the Zephyr Bluetooth Controller (see the migration guide).Host calls in GATT Discovery Manager (DM) callbacks are now scheduled in a workqueue. The
BT_GATT_DM_WORKQ_CHOICEKconfig option allows you to select the workqueue implementation. You can select either a workqueue specific to GATT DM (default) or the system workqueue. You can use the system workqueue if creating a new thread is not viable due to memory constraints, but it is not recommended to have potential blocking calls in the system workqueue.
Fixed an issue where the Bluetooth subsystem deadlocked when a Bluetooth link was lost during data transfer. In this scenario, the disconnected event was never delivered to the application. The issue only occurred when the
CONFIG_BT_HCI_ACL_FLOW_CONTROLKconfig option was enabled. This option is enabled by default on the nRF5340 DK.
Bluetooth Mesh
Added metadata as optional parameter for models Light Lightness Server, Light HSL Server, Light CTL Temperature Server, Sensor Server, and Time Server. To use the metadata, enable the
CONFIG_BT_MESH_LARGE_COMP_DATA_SRVKconfig option.Removed the
BT_MESH_SENSOR_USE_LEGACY_SENSOR_VALUEKconfig option, deprecated in the nRF Connect SDK v2.6.0, as the old APIs, based on thesensor_valuetype, are removed. You need to update applications using the old APIs, as described in the v2.6.0 migration guide.
DECT NR+
No changes since the latest nRF Connect SDK release.
Enhanced ShockBurst (ESB)
No changes since the latest nRF Connect SDK release.
Gazell
No changes since the latest nRF Connect SDK release.
Matter
Added:
The following Kconfig options to configure parameters impacting persistent subscriptions re-establishment:
The Profiling memory in Matter applications section to the Optimizing memory usage in Matter applications page. The section contains useful commands for measuring memory and troubleshooting tips.
The ZMS file subsystem to all devices that contain RRAM, such as the nRF54L Series devices.
Migration of the Device Attestation Certificates private key to Key Management Unit (KMU) for the nRF54L Series SoCs. See DAC in Key Management Unit (KMU) to learn how to enable it in your sample.
Updated:
The default Trusted Storage AEAD key to Hardware Unique Key (HUK) for supported nRF54L Series devices.
Renamed the
CONFIG_CHIP_FACTORY_RESET_ERASE_NVSKconfig option toCONFIG_CHIP_FACTORY_RESET_ERASE_SETTINGS. The new Kconfig option now works for both NVS and ZMS file system backends.The firmware version format used for informational purposes when using the
VERSIONfile. The format now includes the optionalEXTRAVERSIONcomponent.Storing the Device Attestation Certificates private key in the Trusted Storage library to be enabled for all platforms that support the PSA crypto API. See DAC in Trusted Storage library for more information.
Matter fork
The Matter fork in the nRF Connect SDK (sdk-connectedhomeip) contains all commits from the upstream Matter repository up to, and including, the v1.3.0.0 tag.
The following list summarizes the most important changes inherited from the upstream Matter:
No changes since the latest nRF Connect SDK release.
nRF IEEE 802.15.4 radio driver
No changes since the latest nRF Connect SDK release.
Thread
Added the OpenThread build report and described how to use it.
Updated the default Trusted Storage AEAD key to Hardware Unique Key (HUK) for supported nRF54L Series devices.
Zigbee
No changes since the latest nRF Connect SDK release.
Wi-Fi
Updated the WPA supplicant to switch to Zephyr upstream’s fork instead of nRF Connect SDK.
Applications
This section provides detailed lists of changes by application.
Machine learning
Added support for sampling ADXL362 sensor from PPR core on the nRF54H20 DK.
Asset Tracker v2
Added a note that the Asset Tracker v2 application is in the maintenance mode and recommended to use the nRF Cloud multi-service sample instead.
Connectivity Bridge
Updated the new nrfx UARTE driver implementation by setting the
CONFIG_UART_NRFX_UARTE_LEGACY_SHIMKconfig option ton. This resolves an issue where data from UART0 ends up in UART1 sometimes after the device was reset.
IPC radio firmware
No changes since the latest nRF Connect SDK release.
Matter Bridge
Added:
The
CONFIG_NCS_SAMPLE_MATTER_ZAP_FILES_PATHKconfig option that specifies ZAP files location for the application. By default, the option points to thesrc/default_zapdirectory and can be changed to any path relative to application’s location that contains the ZAP file andzap-generateddirectory.Experimental support for the nRF54H20 DK board.
Optional smart plug device functionality.
Experimental support for the Thread protocol.
The Bluetooth LE and Thread coexistence page.
nRF5340 Audio
Added the functions
bt_hci_err_to_str()andbt_security_err_to_str()that are used to allow printing error codes as strings. Each function returns string representations of the error codes when the corresponding Kconfig option,CONFIG_BT_HCI_ERR_TO_STRorCONFIG_BT_SECURITY_ERR_TO_STR, is enabled.Updated the nRF Audio overview and firmware architecture documentation page with the Source file architecture section.
nRF Desktop
Added:
A debug configuration enabling the Fast Pair feature on the nRF54L15 PDK with the
nrf54l15pdk/nrf54l15/cpuappboard target.An application versioning using the
VERSIONfile. The versioning is only applied to the application configurations that use the MCUboot bootloader.The CONFIG_DESKTOP_USB_HID_REPORT_SENT_ON_SOF Kconfig option to USB state module. The option allows to synchronize providing HID data with USB Start of Frame (SOF). The feature reduces the negative impact of jitter related to USB polls, but it also increases HID data latency. For details, see USB Start of Frame (SOF) synchronization.
Local HID report buffering in USB state module. This ensures that the memory buffer passed to the USB next stack is valid until a HID report is sent and allows to enqueue up to two HID input reports for a USB HID instance (used only when CONFIG_DESKTOP_USB_HID_REPORT_SENT_ON_SOF Kconfig option is enabled).
Bootup logs with the manifest semantic version information to Device Firmware Upgrade MCUmgr module when the module is used for SUIT DFU and the SDFW supports semantic versioning (requires v0.6.2 and higher).
Manifest semantic version information to the firmware information response in Device Firmware Upgrade module when the module is used for SUIT DFU and the SDFW supports semantic versioning (requires v0.6.2 and higher).
A missing DTS node compatible with
zephyr,hid-deviceto the nRF52840 DK in the MCUboot QSPI configuration. This ensures support for HID over USB when the USB next stack is selected.The USB next stack (CONFIG_DESKTOP_USB_STACK_NEXT) implies partial erase feature of the nRF SoC flash driver (
CONFIG_SOC_FLASH_NRF_PARTIAL_ERASE). This is done to improve stability of the USB next stack. The partial erase feature works around device errors that might be reported by Windows USB host in Device Manager if USB cable is connected while erasing secondary image slot in the background.Bluetooth connectivity support (CONFIG_DESKTOP_BT) implies using a separate workqueue for connection TX notify processing (
CONFIG_BT_CONN_TX_NOTIFY_WQ) if MPSL is used for synchronization between the flash memory driver and radio (CONFIG_SOC_FLASH_NRF_RADIO_SYNC_MPSL). This is done to work around the timeout in MPSL flash synchronization (NCSDK-29354known issue). See Known issues for details.
Updated:
The
CONFIG_BT_ADV_PROV_TX_POWER_CORRECTION_VALKconfig option value in configurations with the Fast Pair support. The value is now aligned with the Fast Pair requirements.The
CONFIG_NRF_RRAM_WRITE_BUFFER_SIZEKconfig option value in the nRF54L15 PDK configurations to ensure short write slots. It prevents timeouts in the MPSL flash synchronization caused by allocating long write slots while maintaining a Bluetooth LE connection with short intervals and no connection latency.The method of obtaining hardware ID using Zephyr’s Hardware Information on the nRF54H20 DK. Replaced the custom implementation of the
z_impl_hwinfo_get_device_id()function in the nRF Desktop application with the native Zephyr driver function that now supports the nRF54H20 DK board target. Removed theCONFIG_DESKTOP_HWINFO_BLE_ADDRESS_FICR_POSTFIXKconfig option as a postfix constant is no longer needed for the Zephyr native driver. The driver usesBLE.ADDR,BLE.IR, andBLE.ERfields of the Factory Information Configuration Registers (FICR) to provide 8 bytes of unique hardware ID.The Device Firmware Upgrade MCUmgr module to recognize the MCUmgr custom group ID (
CONFIG_MGMT_GROUP_ID_SUIT) from the SUITFU subsystem (CONFIG_MGMT_SUITFU) as a DFU-related command group.All build configurations with the DFU over MCUmgr support to require encryption for operations on the Bluetooth GATT SMP service (see the
CONFIG_MCUMGR_TRANSPORT_BT_PERM_RW_ENCRYPTKconfig option). The Bluetooth pairing procedure of the unpaired Bluetooth peers must now be performed before the DFU operation.The Device Firmware Upgrade MCUmgr module to enable the MCUmgr handler that is used to report the bootloader information (see the
CONFIG_MCUMGR_GRP_OS_BOOTLOADER_INFOKconfig option).The MCUboot image configurations for the nRF54L15 DK board to enable Link Time Optimization (LTO) (see the
CONFIG_LTOKconfig option) and reduce the memory footprint of the bootloader.The partition memory configurations for the nRF54L15 DK board to optimize the size of the MCUboot bootloader partition.
The Constant latency hotfix module to use the
nrfx_power_constlat_mode_request()andnrfx_power_constlat_mode_free()functions instead ofnrf_power_task_trigger()to control requesting Constant Latency sub-power mode. This ensures correct behavior if another source requests Constant Latency sub-power mode through the nrfx API.The CONFIG_DESKTOP_CONSTLAT_DISABLE_ON_STANDBY Kconfig option depends on
CONFIG_CAF_PM_EVENTS. CAF Power Management events support is necessary to disable constant latency interrupts on standby.
Removed support for the nRF54L15 PDK revision v0.2.x.
nRF Machine Learning (Edge Impulse)
No changes since the latest nRF Connect SDK release.
Serial LTE modem
Added:
DTLS support for the
#XUDPSVRand#XSSOCKET(UDP server sockets) AT commands when theoverlay-native_tls.confconfiguration file is used.The
CONFIG_SLM_PPP_FALLBACK_MTUKconfig option that is used to control the MTU used by PPP when the cellular link MTU is not returned by the modem in response to theAT+CGCONTRDP=0AT command.Handler for new nRF Cloud event type
NRF_CLOUD_EVT_RX_DATA_DISCON.Support for socket option
AT_SO_IPV6_DELAYED_ADDR_REFRESH.
Updated:
AT string parsing to utilize the AT parser library instead of the AT command parser library.
The
#XUDPCLIand#XSSOCKET(UDP client sockets) AT commands to use Zephyr’s Mbed TLS with DTLS when theoverlay-native_tls.confconfiguration file is used.
Removed:
Support for the
overlay-native_tls.confconfiguration file with thethingy91/nrf9160/nsboard target.Support for deprecated RAI socket options
AT_SO_RAI_LAST,AT_SO_RAI_NO_DATA,AT_SO_RAI_ONE_RESP,AT_SO_RAI_ONGOING, andAT_SO_RAI_WAIT_MORE.The
#XCARRIERCFG="bootstrap_smartcard"AT command.
Thingy:53: Matter weather station
Added the
CONFIG_NCS_SAMPLE_MATTER_ZAP_FILES_PATHKconfig option, which specifies ZAP files location for the application. By default, the option points to thesrc/default_zapdirectory and can be changed to any path relative to application’s location that contains the ZAP file andzap-generateddirectory.
Samples
This section provides detailed lists of changes by sample.
Amazon Sidewalk samples
No changes since the latest nRF Connect SDK release.
Bluetooth samples
Added:
The Bluetooth: Radio Notification callback sample demonstrating how to use the Radio Notification callback feature.
The Bluetooth: Connection time synchronization sample demonstrating microsecond-accurate synchronization of connections that are happening over Bluetooth® Low Energy Asynchronous Connection-oriented Logical transport (ACL).
The Bluetooth: Connection Subrating sample that showcases the effect of the LE Connection Subrating feature on the duty cycle of a connection.
The nRF Auraconfig sample that implements the BIS gateway mode and may act as an Auracast™ broadcaster if you are using a preset compatible with Auracast.
Support for the nRF54L15 DK board in the following samples:
Bluetooth: ISO time synchronization:
Fixed LED toggling issues on nRF52 and nRF53 Series devices that would occur after RTC wraps that occur every ~8.5 minutes. The LED previously toggled unintentionally, at the wrong point in time, or not at all.
Bluetooth: Event Trigger sample:
Moved to the
samples/bluetooth/event_triggerfolder.
Bluetooth: Peripheral Heart Rate Monitor with Coded PHY sample:
Fixed an issue where the HCI LE Set Extended Advertising Enable command was called with a NULL pointer.
Bluetooth: Peripheral Memfault Diagnostic Service (MDS) sample:
Fixed an issue where device ID was incorrectly set during system initialization because MAC address was not available at that time. The device ID is now set to
ncs-ble-testdeviceby default using theCONFIG_MEMFAULT_NCS_DEVICE_IDKconfig option.
Bluetooth: LLPM sample:
Added support for the nRF54H20 DK board.
Bluetooth: External radio coexistence using 1-wire interface sample:
Added support for the
nrf54h20dk/nrf54h20/cpuradandnrf54l15dk/nrf54l15/cpuappbuild targets.
Bluetooth Fast Pair samples
Updated:
The values for the
CONFIG_BT_ADV_PROV_TX_POWER_CORRECTION_VALKconfig option in all configurations, and for theCONFIG_BT_FAST_PAIR_FMDN_TX_POWER_CORRECTION_VALKconfig option in configurations with the Find My Device Network (FMDN) extension support. The values are now aligned with the Fast Pair requirements.The sample configurations to use a separate workqueue for connection TX notify processing (
CONFIG_BT_CONN_TX_NOTIFY_WQ). This is done to work around the timeout in MPSL flash synchronization (NCSDK-29354known issue). See Known issues for details.
Bluetooth Fast Pair: Locator tag sample:
Added:
LED indication on development kits for the Fast Pair advertising state.
An application versioning using the
VERSIONfile.The DFU support which can be enabled using the
SB_CONFIG_APP_DFUsysbuild Kconfig option. DFU is available for all supported targets except thedebugconfigurations of nRF52 DK and nRF52833 DK due to size constraints.
Updated:
The IPC radio firmware image configuration by splitting it into the debug and release configurations.
The location of the sample configuration. It has been moved from the root sample directory to the dedicated folder (
locator_tag/configuration).The
fp_advmodule to use the trigger requests for the Fast Pair advertising state instead of setting the Fast Pair advertising mode directly.
Bluetooth Mesh samples
For all Bluetooth Mesh samples:
Added support for the nRF54L15 DK board.
Added support for Zephyr Memory Storage (ZMS) when compiling for the nRF54L15 DK board.
Removed support for the nRF54L15 PDK.
Bluetooth Mesh: Coexistence with other LE services sample:
Updated the usage of the
BT_LE_ADV_CONNmacro. See the Bluetooth Host section in Zephyr’s Migration guide to Zephyr v3.7.0.
Cellular samples
Added the Cellular: UICC LwM2M sample.
Cellular: Full modem firmware update using SMP Server sample:
Removed the unused AT command parser library.
Cellular: Modem Shell sample:
Added
link modemcommand for initializing and shutting down the modem.Updated to use the AT parser library instead of the AT command parser library.
Cellular: nRF Cloud REST FOTA sample:
Added support for setting the FOTA update check interval using the config section in the shadow.
Removed redundant logging now done by the nRF Cloud library.
nRF Cloud multi-service sample:
Added:
The
CONFIG_TEST_COUNTER_MULTIPLIERKconfig option to multiply the number of test counter messages sent, for testing purposes.A handler for new nRF Cloud event type
NRF_CLOUD_EVT_RX_DATA_DISCONto stop sensors and location services.Board support files to enable Wi-Fi scanning for the Thingy:91 X.
The
CONFIG_SEND_ONLINE_ALERTKconfig option to enable calling thenrf_cloud_alertfunction on startup.Logging of the reset reason code.
The
CONFIG_POST_PROVISIONING_INTERVAL_MKconfig option to reduce the provisioning connection interval once the device successfully connects.
Updated:
Wi-Fi overlays from newlibc to picolib.
Handling of JITP association to improve speed and reliability.
Renamed the
overlay_nrf7002ek_wifi_no_lte.confoverlay tooverlay_nrf700x_wifi_mqtt_no_lte.conf.Renamed the
overlay_nrf7002ek_wifi_coap_no_lte.confoverlay tooverlay_nrf700x_wifi_coap_no_lte.conf.The value of the
CONFIG_COAP_EXTENDED_OPTIONS_LEN_VALUEKconfig option in theoverlay_coap.conffile. A larger value is required now that theCONFIG_NRF_CLOUD_COAP_DOWNLOADSKconfig option is enabled.Handling of credentials check to disable network if not using the provisioning service.
Fixed an issue where the accepted shadow was not marked as received because the config section did not yet exist in the shadow.
Removed redundant logging now done by the nRF Cloud library.
Cellular: nRF Cloud REST Device Message sample:
Added:
Support for dictionary logs using REST.
The
CONFIG_SEND_ONLINE_ALERTKconfig option to enable calling thenrf_cloud_alertfunction on startup.Logging of the reset reason code.
Updated:
Credentials check to also see if AWS root CA cert is likely present.
Credentials check failure to disable network if not using the provisioning service.
Removed redundant logging now done by the nRF Cloud library.
Cellular: nRF Cloud REST cellular location sample:
Removed redundant logging now done by the nRF Cloud library.
Cellular: SMP Server sample:
Added sysbuild configuration files.
Cryptography samples
Added support for the
nrf54l15dk/nrf54l15/cpuapp/nsboard target, replacingnrf54l15pdk/nrf54l15/cpuapp/ns.
Debug samples
Memfault sample:
Increased the value of the
CONFIG_MAIN_STACK_SIZEKconfig option to 8192 bytes to avoid stack overflow.
DECT NR+ samples
Added the nRF91x1: DECT NR+ Shell sample.
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:
The
CONFIG_NCS_SAMPLE_MATTER_ZAP_FILES_PATHKconfig option, which specifies ZAP files location for the sample. By default, the option points to thesrc/default_zapdirectory and can be changed to any path relative to sample’s location that contains the ZAP file andzap-generateddirectory.Support for the nRF54L15 DK.
Support for Trusted Firmware-M on the nRF54L15 SoC.
The Matter: Smoke CO Alarm sample that demonstrates implementation of Matter Smoke CO alarm device type.
The
CONFIG_NCS_SAMPLE_MATTER_LEDSKconfig option, which can be used to disable the LEDs in the Matter sample or application.
Updated all samples to enable the OpenThread build report generation.
Matter: Door lock sample:
Added Matter Lock schedule snippet and updated the documentation to use the snippet.
Matter: Template sample:
Updated the DAC private key migration from factory data to KMU to be enabled for the nRF54L Series SoCs by default.
Removed support for the nRF54L15 PDK from all samples.
Networking samples
HTTP Server sample:
Fixed not to fail with a fatal error if IPv4 or IPv6 server setup fails.
NFC samples
No changes since the latest nRF Connect SDK release.
nRF5340 samples
nRF5340: SMP Server with external XIP sample:
Added:
Support for sysbuild.
Support to demonstrate direct-XIP building and building without network core support.
Peripheral samples
IEEE 802.15.4 Sniffer sample:
Added sysbuild configuration for nRF5340.
Increased the number of RX buffers to reduce the chances of frame drops during high traffic periods.
Disabled the nRF Connect SDK boot banner.
Fixed the dBm value reported for captured frames.
IEEE 802.15.4 PHY test tool sample:
Added build configuration for the nRF54H20.
Radio test (short-range) sample:
Added packet reception limit for the
start_rxcommand.
PMIC samples
Added support for the nRF54L15 DK and nRF54H20 DK to the PMIC samples.
nPM1300: Fuel gauge sample:
Updated to accommodate API changes in nRF Fuel Gauge library v0.11.1.
Protocol serialization samples
Added the nRF RPC: Protocols serialization client and the nRF RPC: Protocols serialization server samples.
SDFW samples
No changes since the latest nRF Connect SDK release.
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
Replaced support for the
nrf54l15pdk/nrf54l15/cpuapp/nsboard target withnrf54l15dk/nrf54l15/cpuapp/ns.TF-M: PSA template sample:
Added support for updating the network core on the nRF5340 DK.
Thread samples
Updated all samples to enable the OpenThread build report generation.
Thread: CLI sample:
Added support for the nRF54L15 DK in the low-power snippet.
Added experimental support for Trusted Firmware-M on the nRF54L15 SoC.
Zigbee samples
Zigbee light switch sample:
Added the option to configure transmission power.
Fixed the FOTA configuration for the nRF5340 DK.
Wi-Fi samples
Wi-Fi: Radio test (Multi domain) sample:
Added capture timeout as a parameter for packet capture.
Expanded the scope of
wifi_radio_test show_configsubcommand and rectified the behavior ofwifi_radio_test tx_pkt_preamblesubcommand.
Wi-Fi: SoftAP based provision sample:
Increased the value of the
CONFIG_SOFTAP_WIFI_PROVISION_THREAD_STACK_SIZEKconfig option to 8192 bytes to avoid stack overflow.
Wi-Fi: Shell sample:
Added support for running the full stack on the Thingy:91 X. This is a special configuration that uses the nRF5340 as the host chip instead of the nRF9151.
Other samples
Added:
The MCUboot with decompression enabled sample that demonstrates how to enable and use image compression within MCUboot.
A sample for the Multicore idle GPIO test.
A sample for the PWM in low power states test.
CoreMark sample:
Updated the logging mode to minimal (
CONFIG_LOG_MODE_MINIMAL) to reduce the sample’s memory footprint and ensure no logging interference with the running benchmark.
Drivers
This section provides detailed lists of changes by driver.
No changes since the latest nRF Connect SDK release.
Wi-Fi drivers
nRF70 Series Wi-Fi driver is upstreamed to Zephyr, so, removed from the nRF Connect SDK.
Libraries
This section provides detailed lists of changes by library.
Binary libraries
No changes since the latest nRF Connect SDK release.
Bluetooth libraries and services
Google Fast Pair Service (GFPS) library:
Added:
The
CONFIG_BT_FAST_PAIR_BNKconfig option that enables support for the Battery Notification extension. You must enable this option to access Fast Pair API elements associated with the Battery Notification extension.The
CONFIG_BT_FAST_PAIR_SUBSEQUENT_PAIRINGKconfig option allowing the user to control the support for the Fast Pair subsequent pairing feature.The
CONFIG_BT_FAST_PAIR_USE_CASEKconfig choice option allowing the user to select their target Fast Pair use case. TheCONFIG_BT_FAST_PAIR_USE_CASE_UNKNOWN,CONFIG_BT_FAST_PAIR_USE_CASE_INPUT_DEVICE,CONFIG_BT_FAST_PAIR_USE_CASE_LOCATOR_TAGandCONFIG_BT_FAST_PAIR_USE_CASE_MOUSEKconfig options represent the supported use cases that can be selected as part of this Kconfig choice option.The
CONFIG_BT_FAST_PAIR_BOND_MANAGERKconfig option that enables the Fast Pair bond management functionality. If this option is enabled, the Fast Pair subsystem tracks the Bluetooth bonds created through the Fast Pair Procedure and unpairs them if the procedure is incomplete or the Account Key associated with the bonds is removed. It also unpairs the Fast Pair Bluetooth bonds on Fast Pair factory reset. The option is enabled by default for Fast Pair use cases that are selected usingCONFIG_BT_FAST_PAIR_USE_CASE_INPUT_DEVICEandCONFIG_BT_FAST_PAIR_USE_CASE_MOUSEKconfig options.
Updated the default values of the following Fast Pair Kconfig options:
These Kconfig options are now disabled by default and are selected only by the Fast Pair use cases that require them.
Removed:
The Mbed TLS cryptographic backend support in Fast Pair, because it is superseded by the PSA backend. Consequently, the
CONFIG_BT_FAST_PAIR_CRYPTO_MBEDTLSKconfig option has also been removed.The default overrides for the
CONFIG_BT_DISandCONFIG_BT_DIS_FW_REVKconfig options that enable these options together with the Google Fast Pair Service. This configuration is now selected only by the Fast Pair use cases that require the Device Information Service (DIS).The default override for the
CONFIG_BT_DIS_FW_REV_STRKconfig option that was set toCONFIG_MCUBOOT_IMGTOOL_SIGN_VERSIONifCONFIG_BOOTLOADER_MCUBOOTwas enabled. The default override is now handled in the Kconfig of the Zephyr Device Information Service (DIS) module and is based on Zephyr’s Application version management that uses theVERSIONfile.The
bt_fast_pair_factory_reset_user_action_prepare()weak function definition, which could previously be overridden to prepare for the incoming Fast Pair factory reset. You can still override thebt_fast_pair_factory_reset_user_action_perform()weak function to perform custom actions during the Fast Pair factory reset.
Bluetooth LE advertising providers:
Added the
bt_le_adv_prov_adv_state.adv_handlefield to thebt_le_adv_prov_adv_statestructure to store the advertising handle. If theCONFIG_BT_EXT_ADVKconfig option is enabled, you can use thebt_hci_get_adv_handle()function to obtain the advertising handle for the advertising set that employs Bluetooth LE advertising providers. If the Kconfig option is disabled, thebt_le_adv_prov_adv_state.adv_handlefield must be set to0. This field is currently used by the TX Power provider (CONFIG_BT_ADV_PROV_TX_POWER).Updated the
CONFIG_BT_ADV_PROV_FAST_PAIR_SHOW_UI_PAIRINGKconfig option and thebt_le_adv_prov_fast_pair_show_ui_pairing()function to require the enabling of theCONFIG_BT_FAST_PAIR_SUBSEQUENT_PAIRINGKconfig option.
Common Application Framework
No changes since the latest nRF Connect SDK release.
Debug libraries
Memfault library:
Added location metrics, including GNSS, cellular, and Wi-Fi specific metrics. The metrics are enabled with the
CONFIG_MEMFAULT_NCS_LOCATION_METRICSKconfig option.
DFU libraries
Added the
subsys_suitlibrary that provides functionality to a local domain for orchestrating the update based on the SUIT manifest.DFU target library:
Added SUIT cache processing to the DFU Target SUIT library, as described in the
lib_dfu_target_suit_style_updatesection.Updated the DFU Target SUIT implementation to the newest version of the SUIT.
Gazell libraries
No changes since the latest nRF Connect SDK release.
Security libraries
nRF Security library:
Removed the Kconfig options
CONFIG_PSA_WANT_ALG_CFBandCONFIG_PSA_WANT_ALG_OFBsince the Cipher Feedback (CFB) mode and the Output Feedback (OFB) mode are not tested in the test framework.
Modem libraries
Added:
The AT parser library. The AT parser is a library that parses AT command responses, notifications, and events. Compared to the deprecated AT command parser library, it does not allocate memory dynamically and has a smaller footprint. For more information on how to transition from the AT command parser library to the AT parser library, see the migration guide.
The UICC LwM2M library. This library reads the LwM2M bootstrap configuration from SIM.
AT command parser library:
Updated to use the
at_parser_cmd_type_get()function instead ofat_parser_at_cmd_type_get()to prevent a name collision.Deprecated:
The AT command parser library in favor of the AT parser library. The AT command parser library will be removed in a future version. For more information on how to transition from the AT command parser library to the AT parser library, see the migration guide.
The
CONFIG_AT_CMD_PARSER. This option will be removed in a future version.
LTE link control library:
Added:
The
CONFIG_LTE_LC_CONN_EVAL_MODULEKconfig option to enable the Connection Parameters Evaluation module.The
CONFIG_LTE_LC_EDRX_MODULEKconfig option to enable the eDRX module.The
CONFIG_LTE_LC_NEIGHBOR_CELL_MEAS_MODULEKconfig option to enable the Neighboring Cell Measurements module.The
CONFIG_LTE_LC_PERIODIC_SEARCH_MODULEKconfig option to enable the Periodic Search Configuration module.The
CONFIG_LTE_LC_PSM_MODULEKconfig option to enable the PSM module.The
CONFIG_LTE_LC_RAI_MODULEKconfig option to enable the RAI module.The
CONFIG_LTE_LC_MODEM_SLEEP_MODULEKconfig option to enable the Modem Sleep Notifications module.The
CONFIG_LTE_LC_TAU_PRE_WARNING_MODULEKconfig option to enable the TAU Pre-warning module.The
LTE_LC_EVT_RAI_UPDATEevent that is enabled with theCONFIG_LTE_RAI_REQKconfig option. This requires theCONFIG_LTE_LC_RAI_MODULEKconfig option to be enabled.
Updated:
To use the AT parser library instead of the AT command parser library.
The
lte_lc_neighbor_cell_measurement()function to return an error for invalid GCI count.The library was reorganized into modules that are enabled through their respective Kconfig options. By default, the library now enables only the core features related to the network connectivity. This reorganization reduces flash memory consumption for applications that only use the core features of the library related to network connectivity. For more information on how to update your project, see the migration guide.
The
lte_lc_conn_eval_params_get()function now requires the newCONFIG_LTE_LC_CONN_EVAL_MODULEKconfig option to be enabled.The
LTE_LC_EVT_EDRX_UPDATEevent and thelte_lc_ptw_set(),lte_lc_edrx_param_set(),lte_lc_edrx_req(), andlte_lc_edrx_get()functions require the newCONFIG_LTE_LC_EDRX_MODULEKconfig option to be enabled.The
LTE_LC_EVT_NEIGHBOR_CELL_MEASevent and thelte_lc_neighbor_cell_measurement_cancel(), andlte_lc_neighbor_cell_measurement()functions require the newCONFIG_LTE_LC_NEIGHBOR_CELL_MEAS_MODULEKconfig option to be enabled.The
lte_lc_periodic_search_request(),lte_lc_periodic_search_clear(),lte_lc_periodic_search_get(), andlte_lc_periodic_search_set()functions require the newCONFIG_LTE_LC_PERIODIC_SEARCH_MODULEKconfig option to be enabled.The
LTE_LC_EVT_PSM_UPDATEevent and thelte_lc_psm_param_set(),lte_lc_psm_param_set_seconds(),lte_lc_psm_req(),lte_lc_psm_get(), andlte_lc_proprietary_psm_req()functions require the newCONFIG_LTE_LC_PSM_MODULEKconfig option to be enabled.The
LTE_LC_EVT_MODEM_SLEEP_EXIT_PRE_WARNING,LTE_LC_EVT_MODEM_SLEEP_ENTER, andLTE_LC_EVT_MODEM_SLEEP_EXITevents require the newCONFIG_LTE_LC_MODEM_SLEEP_MODULEKconfig option to be enabled.The
LTE_LC_EVT_TAU_PRE_WARNINGevent requires the newCONFIG_LTE_LC_TAU_PRE_WARNING_MODULEKconfig option to be enabled.
Deprecated:
The
LTE_LC_ON_CFUNmacro. Use theNRF_MODEM_LIB_ON_CFUNmacro instead.The
lte_lc_factory_reset()function. Use theAT%XFACTORYRESETAT command instead. Refer to the migration guide for more details.The
lte_lc_factory_reset_typetype.The
lte_lc_reduced_mobility_get()andlte_lc_reduced_mobility_set()functions. Refer to the migration guide for more details.The
lte_lc_reduced_mobility_modetype. Refer to the migration guide for more details.
Removed:
The
lte_lc_initfunction. All instances of this function can be removed without any additional actions.The
lte_lc_deinitfunction. Use thelte_lc_power_off()function instead.The
lte_lc_init_and_connectfunction. Use thelte_lc_connect()function instead.The
lte_lc_init_and_connect_asyncfunction. Use thelte_lc_connect_async()function instead.The
CONFIG_LTE_NETWORK_USE_FALLBACKKconfig option. Use theCONFIG_LTE_NETWORK_MODE_LTE_M_NBIOTorCONFIG_LTE_NETWORK_MODE_LTE_M_NBIOT_GPSKconfig option instead. In addition, you can control the priority between LTE-M and NB-IoT using theCONFIG_LTE_MODE_PREFERENCEKconfig option.
Location library:
Fixed:
A bug causing the GNSS obstructed visibility detection to sometimes count only part of the tracked satellites.
A bug causing the GNSS obstructed visibility detection to be sometimes performed twice.
Removed the unused AT command parser library.
-
Updated to use the AT parser library instead of the AT command parser library.
Modem information library:
Updated:
To use the AT parser library instead of the AT command parser library.
The formulas of RSRP and RSRQ values in
RSRP_IDX_TO_DBMandRSRQ_IDX_TO_DBbased on AT command reference guide updates. The formulas are now aligned with the modem implementation that has not changed but the AT command reference guide has not been up to date with the modem implementation.
Removed
RSRP_OFFSET_VAL,RSRQ_OFFSET_VALandRSRQ_SCALE_VALfrom the API. Clients should have used theRSRP_IDX_TO_DBMand theRSRQ_IDX_TO_DBmacros.
Network interface driver library:
Added a log warning suggesting a SIM card to be installed if a UICC error is detected by the modem.
Fixed a bug causing the cell network to be treated as offline if IPv4 is not assigned.
Modem library integration layer:
Added support for socket option
SO_IPV6_DELAYED_ADDR_REFRESH.Updated:
The RTT trace backend to allocate the RTT channel at boot, instead of when the modem is activated.
The flash trace backend to solve concurrency issues when reading traces while writing, and when reinitializing the application (warm start).
Renamed the nRF91 socket offload layer from
nrf91_socketstonrf9x_socketsto reflect that the offload layer is not exclusive to the nRF91 Series SiPs.The Modem trace module to let the trace thread sleep when the modem trace level is set to
NRF_MODEM_LIB_TRACE_LEVEL_OFFusing thenrf_modem_lib_trace_level_set()function, and the trace backend returns-ENOSPC. The trace thread wakes up when another trace level is set.The RTT trace backend to return
-ENOSPCwhen the RTT buffer is full. This allows the trace thread to sleep to save power.The nRF91 socket offload layer is renamed from
nrf91_socketstonrf9x_socketsto reflect that the offload layer is not exclusive to the nRF91 Series SiPs.
Removed:
Support for deprecated RAI socket options
SO_RAI_LAST,SO_RAI_NO_DATA,SO_RAI_ONE_RESP,SO_RAI_ONGOING, andSO_RAI_WAIT_MORE.The mutex in the
nrf9x_socket_offload_getaddrinfo()function after updating thenrf_getaddrinfo()function to handle concurrent requests.
Modem information library:
Fixed a potential issue with scanf in the
modem_info_get_current_band()function, which could lead to memory corruption.
Modem key management library:
Added the
modem_key_mgmt_clear()function to delete all credentials associated with a security tag.
PDN library:
Added the event
PDN_EVENT_CTX_DESTROYEDto indicate when a PDP context is destroyed. This happens when the modem is switched to minimum functionality mode (CFUN=0).
SMS library:
Added the
CONFIG_SMS_STATUS_REPORTKconfig option to configure whether the SMS status report is requested.Updated:
To use the
AT+CMMSAT command when sending concatenated SMS message.To set “7” as a fallback SMS service center address for type approval SIM cards which do not have it set.
AT shell library:
Added the
CONFIG_AT_SHELL_UNESCAPE_LFKconfig option to enable reception of multiline AT commands.Updated the
at_shell()function to replace\nwith<CR><LF>ifCONFIG_AT_SHELL_UNESCAPE_LFis enabled.
Modem key management library:
Updated the
modem_key_mgmt_read()function to return the actual size buffer required to read the certificate if the size provided is too small.
Multiprotocol Service Layer libraries
Added a 1-wire coexistence implementation that you can enable using the Kconfig option
CONFIG_MPSL_CX_1WIRE.Updated the name of the Kconfig option
CONFIG_MPSL_CX_THREADtoCONFIG_MPSL_CX_3WIREto better indicate multiprotocol compatibility.Fixed an issue where the HFXO would be left on after uninitializing MPSL when the RC oscillator was used as the Low Frequency clock source (DRGN-22809).
Deprecated the Kconfig option
CONFIG_MPSL_CX_BT_1WIRE.
Libraries for networking
LwM2M client utils library:
Updated to use the AT parser library instead of the AT command parser library.
nRF Cloud REST library:
Added the function
nrf_cloud_rest_shadow_transform_requestto request shadow data using a JSONata expression.
nRF Cloud library:
Added:
The function
nrf_cloud_client_id_runtime_set()to set the device ID string if theCONFIG_NRF_CLOUD_CLIENT_ID_SRC_RUNTIMEKconfig option is enabled.The functions
nrf_cloud_sec_tag_set()andnrf_cloud_sec_tag_get()to set and get the sec tag used for nRF Cloud credentials.A new nRF Cloud event type
NRF_CLOUD_EVT_RX_DATA_DISCONwhich is generated when a device is deleted from nRF Cloud.The functions
nrf_cloud_print_details()andnrf_cloud_print_cloud_details()to log common nRF Cloud connection information in a uniform way.The
CONFIG_NRF_CLOUD_PRINT_DETAILSKconfig option to enable the above functions.The
CONFIG_NRF_CLOUD_VERBOSE_DETAILSKconfig option to print all details instead of only the device ID.Experimental support for shadow transform requests over MQTT using the
nrf_cloud_shadow_transform_request()function. This functionality is enabled by theCONFIG_NRF_CLOUD_MQTT_SHADOW_TRANSFORMSKconfig option.The
CONFIG_NRF_CLOUD_COMBINED_CA_CERT_SIZE_THRESHOLDandCONFIG_NRF_CLOUD_COAP_CA_CERT_SIZE_THRESHOLDKconfig options to compare with the current root CA certificate size.The functions
nrf_cloud_sec_tag_coap_jwt_set()andnrf_cloud_sec_tag_coap_jwt_get()to set and get the sec tag used for nRF Cloud CoAP JWT signing.
Updated:
The
CONFIG_NRF_CLOUD_CLIENT_ID_SRC_RUNTIMEKconfig option to be available with CoAP and REST.The JSON string representing longitude in
PVTreports fromlngtolonto align with nRF Cloud. nRF Cloud still acceptslngfor backward compatibility.The handling of MQTT JITP device association to improve speed and reliability.
To use nRF Cloud’s custom MQTT topics instead of the default AWS topics.
MQTT and CoAP transports to use a single unified DNS lookup mechanism that supports IPv4 and IPv6, fallback to IPv4, and handling of multiple addresses returned by
getaddrinfo().The log module in the
nrf_cloud_fota_common.cfile fromNRF_CLOUDtoNRF_CLOUD_FOTA.The
nrf_cloud_credentials_configured_check()function to retrieve the size of the root CA, and compare it to thresholds to decide whether the CoAP, AWS, or both root CA certs are present. Use this information to log helpful information and decide whether the root CA certificates are compatible with the configured connection type.
Fixed:
An issue in the
nrf_cloud_send()function that prevented data in the providednrf_cloud_objstructure from being sent to the bulk and bin topics.An issue where the modem was not shut down from bootloader mode before attempting to initialize in normal mode after an unsuccessful update.
Deprecated:
The
CONFIG_NRF_CLOUD_IPV6Kconfig option, which now no longer forces the nRF Cloud MQTT transport to use IPv4 when not enabled. Instead, use theCONFIG_NET_IPV4andCONFIG_NET_IPV6Kconfig options to customize which IP versions the nRF Cloud library uses.The
CONFIG_NRF_CLOUD_STATIC_IPV4andCONFIG_NRF_CLOUD_STATIC_IPV4_ADDRKconfig options. Support for statically configured nRF Cloud IP Addresses will soon be removed. LeaveCONFIG_NRF_CLOUD_STATIC_IPV4disabled to instead use automatic DNS lookup.
nRF Cloud CoAP library:
Added:
The
CONFIG_NRF_CLOUD_COAP_DISCONNECT_ON_FAILED_REQUESTKconfig option to disconnect the CoAP client on a failed request.The
CONFIG_NRF_CLOUD_COAP_JWT_SEC_TAGKconfig option to allow for a separate sec tag to be used for nRF Cloud CoAP JWT signing.
Updated:
To use a shorter resource string for the
d2c/bulkresource.The function
nrf_cloud_coap_shadow_get()to return-E2BIGif the received shadow data was truncated because the provided buffer was not big enough.The
CONFIG_NRF_CLOUD_COAP_DOWNLOADSKconfig option to be enabled by default if either theCONFIG_NRF_CLOUD_FOTA_POLLorCONFIG_NRF_CLOUD_PGPSKconfig option is enabled.
Fixed:
A hard fault that occurred when encoding AGNSS request data and the
net_infofield of thenrf_cloud_rest_agnss_requeststructure is NULL.An issue where certain CoAP functions could return zero, indicating success, even though there was an error.
Removed the experimental status (
CONFIG_EXPERIMENTAL) from theCONFIG_NRF_CLOUD_COAP_DOWNLOADSKconfig option.
LwM2M client utils library:
Fixed an issue where a failed delta update for the modem would not clear the state and blocks future delta updates. This only occurred when an LwM2M Firmware object was used in push mode.
nRF Cloud Logging library library:
Added:
Support for dictionary logs using REST.
Support for dictionary (binary) logs when connected to nRF Cloud using CoAP.
Updated to use INF log level when the cloud side changes the log level.
Fixed the missing log source when passing a direct log call to the nRF Cloud logging backend. This caused the log parser to incorrectly use the first declared log source with direct logs when using dictionary mode.
FOTA download library:
Fixed an issue where the download client instance did not use native TLS although the
CONFIG_FOTA_DOWNLOAD_NATIVE_TLSKconfig option was enabled.
Firmware over-the-air (FOTA) updates library:
Added:
FOTA status callback.
The
CONFIG_NRF_CLOUD_FOTA_SMPKconfig option to enable experimental support for SMP FOTA.
Updated:
The
CONFIG_NRF_CLOUD_FOTA_DOWNLOAD_FRAGMENT_SIZEKconfig option to be available and used also when theCONFIG_NRF_CLOUD_FOTA_POLLKconfig option is enabled. The range of the option is now from 128 to 1900 bytes, and the default value is 1700 bytes.The function
nrf_cloud_fota_poll_process()to be used asynchronously if a callback to handle errors is provided.
MQTT helper library:
Updated the
CONFIG_MQTT_HELPER_PROVISION_CERTIFICATESKconfig option to depend onCONFIG_TLS_CREDENTIALSinstead of specific boards.
nRF Cloud device provisioning library:
Added support for the
SO_KEEPOPENsocket option to keep the socket open even during PDN disconnect and reconnect.Updated the check interval logging to use INF to improve customer experience.
nRF Cloud Alert library:
Updated to use INF log level when cloud side changes the alert enable flag.
Libraries for NFC
Added an experimental serialization of NFC tag 2 and tag 4 APIs.
Fixed a potential issue with handling data pointers in the function
ring_buf_get_datain theplatform_internal_threadfile.
nRF RPC libraries
Added:
An experimental serialization of Openthread APIs.
The logging backend that sends logs through nRF RPC events.
Updated the internal Bluetooth serialization API and Bluetooth callback proxy API to become part of the public NRF RPC API.
Other libraries
Added the nRF Compression library with support for the LZMA decompression.
Date-Time library:
Added:
A retry feature that reattempts failed date-time updates up to a certain number of consecutive times.
The Kconfig options
CONFIG_DATE_TIME_RETRY_COUNTto control whether and how many consecutive date-time update retries may be performed, andCONFIG_DATE_TIME_RETRY_INTERVAL_SECONDSto control how quickly date-time update retries occur.
Fixed a bug that caused date-time updates to not be rescheduled under certain circumstances.
RAM power-down library:
Added support for the nRF54L15 SoC.
Security libraries
nRF Security library:
Added the
CONFIG_PSA_WANT_ALG_SP800_108_COUNTER_CMACKconfig option to key derivation function configurations in Configuring PSA Crypto API. The Kconfig option enables support for the derivation function SP 800-108r1 CMAC in counter mode, which is supported by the nrf_cracen driver.
Trusted storage library:
Added support for Zephyr Memory Storage (ZMS), as an alternative to the NVS file system.
Shell libraries
No changes since the latest nRF Connect SDK release.
Libraries for Zigbee
No changes since the latest nRF Connect SDK release.
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.
Added semantic version support to HID configurator for nRF Desktop Python script for devices that use the SUIT DFU.
Integrations
This section provides detailed lists of changes by integration.
Google Fast Pair integration
No changes since the latest nRF Connect SDK release.
Edge Impulse integration
No changes since the latest nRF Connect SDK release.
Memfault integration
No changes since the latest nRF Connect SDK release.
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 a4eda30f5b0cfd0cf15512be9dcd559239dbfc91, 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:
No changes since the latest nRF Connect SDK release.
Zephyr
The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including ea02b93eea35afef32ebb31f49f8e79932e7deee, 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 ea02b93eea ^23cf38934c
For the list of nRF Connect SDK specific commits, including commits cherry-picked from upstream, run:
git log --oneline manifest-rev ^ea02b93eea
The current nRF Connect SDK main branch is based on revision ea02b93eea 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
Added possibility to read UICR.OTP registers through platform services.
cJSON
No changes since the latest nRF Connect SDK release.
Documentation
Added:
The Application development section, which includes pages from the Configuring and building section and from the removed Device configuration guides section.
The MCUmgr Command-line tool page after it was removed from the Zephyr repository.
The
ug_nrf54h20_suit_soc_binariespage.The
ug_nrf54h20_suit_pushpage documenting the SUIT push model-based update process.The
ug_nrf54h20_suit_recoverypage.The nRF RPC UART transport page.
The Bluetooth stack architecture and the Bluetooth solution areas documentation to the Bluetooth protocols page.
Updated:
The Debugging page with the new snippets added for the nRF70 driver debug and WPA supplicant debug logs.
The Optional programming parameters section on the Programming an application page with information about readback protection moved from the Building and programming with nRF53 Series page.
The Security page with a table that provides an overview of the available general security features. This table replaces the subpage that was previously describing these features in more detail and was duplicating information available in other sections.
Restructured the Bootloaders and DFU documentation and combined the DFU and bootloader articles. Additionally, created a new bootloader Quick start guide.
Separated the instructions about building from Configuring and building and moved it to a standalone Building an application page.
Restructured the Bluetooth Mesh documentation for clearer distinction between concepts or overview topics and how-to topics, thus moved some information from the Bluetooth Mesh library sections.
The CRACEN driver section with a reference to the Working with the KMU and CRACEN page.
The Trusted Firmware-M in the nRF Connect SDK page with the correct list of samples demonstrating TF-M.
The Configuring AP-Protect per device section on the Managing access port protection page with details on setting the Kconfig options and register values to enable AP-Protect.
Removed:
The Device configuration guides section and moved its contents to Application development.
The Advanced building procedures page and moved its contents to the Building an application page.
nRF70 Series support is upstreamed to Zephyr, hence the documentation is removed from the nRF Connect SDK.
The standalone pages for getting started with nRF52 Series and with the nRF5340 DK. These pages have been replaced by the Quick Start app, which now supports the nRF52 Series devices and the nRF5340 DK.