Changelog for nRF Connect SDK v2.7.99

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, and tool support 

No changes since the latest nRF Connect SDK release.

Build and configuration system 

Added the SB_CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM sysbuild Kconfig option to system to allow 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.
Added the SB_CONFIG_MCUBOOT_NRF53_MULTI_IMAGE_UPDATE sysbuild Kconfig option that enables updating the network core on the nRF5340 SoC from external flash.

Bootloaders and DFU 

Added documentation for Using QSPI XIP split image functionality.
Added a section in the sysbuild-related migration guide about the migration of QSPI XIP flash split code from child/parent image to sysbuild.
Removed secure bootloader Kconfig CONFIG_SECURE_BOOT_DEBUG and replaced with usage of logging subsystem.

Developing with nRF91 Series 

No changes since the latest nRF Connect SDK release.

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.

Working with nRF54L Series 

No changes since the latest nRF Connect SDK release.

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 

No changes since the latest nRF Connect SDK release.

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

The correct SoftDevice Controller library CONFIG_BT_LL_SOFTDEVICE_MULTIROLE will now be selected automatically when using coexistence based on CONFIG_MPSL_CX for nRF52-series devices.
Added the APIs bt_hci_err_to_str() and bt_security_err_to_str() to allow printing error codes as strings. Each API returns string representations of the error codes when the corresponding Kconfig option, CONFIG_BT_HCI_ERR_TO_STR or CONFIG_BT_SECURITY_ERR_TO_STR, is enabled. The Bluetooth samples and nRF5340 Audio applications are updated to utilize these new APIs.
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_sdc with a devicetree binding compatible with nordic,bt-hci-sdc. The Zephyr Bluetooth LE Controller uses a devicetree node named bt_hci_controller with a devicetree binding compatible with zephyr,bt-hci-ll-sw-split. Applications using the Zephyr Bluetooth Controller need to be updated (see the migration guide).

Bluetooth Mesh

Updated:

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_SRV Kconfig option.

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 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.

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.

Zigbee

No changes since the latest nRF Connect SDK release.

Wi-Fi

No changes since the latest nRF Connect SDK release.

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

No changes since the latest nRF Connect SDK release.

Connectivity Bridge

Updated the new nrfx UARTE driver implementation by setting the CONFIG_UART_NRFX_UARTE_LEGACY_SHIM Kconfig option to n. 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_PATH Kconfig option, which specifies ZAP files location for the application. By default, the option points to the src/default_zap directory and can be changed to any path relative to application’s location that contains the ZAP file and zap-generated directory.
- Experimental support for the nRF54H20 DK.
- Optional smart plug device functionality.
- Experimental support for the Thread protocol.
- Added Bluetooth LE and Thread coexistence page.

nRF5340 Audio

Added:
- The APIs bt_hci_err_to_str() and bt_security_err_to_str() that are used to allow printing error codes as strings. Each API returns string representations of the error codes when the corresponding Kconfig option, CONFIG_BT_HCI_ERR_TO_STR or CONFIG_BT_SECURITY_ERR_TO_STR, is enabled.
Updated the nRF5340 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/cpuapp board target.
- An application versioning using the VERSION file. 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).
- Kconfig dependency that prevents enabling USB remote wakeup (CONFIG_DESKTOP_USB_REMOTE_WAKEUP) for the nRF54H20 SoC. The DWC2 USB device controller driver used by the nRF54H20 SoC does not support the remote wakeup capability.
- 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).
Updated:
- The CONFIG_BT_ADV_PROV_TX_POWER_CORRECTION_VAL Kconfig 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_SIZE Kconfig 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 the CONFIG_DESKTOP_HWINFO_BLE_ADDRESS_FICR_POSTFIX Kconfig option as a postfix constant is no longer needed for the Zephyr native driver. The driver uses BLE.ADDR, BLE.IR, and BLE.ER fields 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.

nRF Machine Learning (Edge Impulse)

No changes since the latest nRF Connect SDK release.

Serial LTE modem

Added:
- DTLS support for the #XUDPSVR and #XSSOCKET (UDP server sockets) AT commands when the overlay-native_tls.conf configuration file is used.
- The CONFIG_SLM_PPP_FALLBACK_MTU Kconfig 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 the AT+CGCONTRDP=0 AT command.
- Handler for new nRF Cloud event type NRF_CLOUD_EVT_RX_DATA_DISCON.
Removed:
- Support for the overlay-native_tls.conf configuration file with the thingy91/nrf9160/ns board 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, and AT_SO_RAI_WAIT_MORE.
Updated:
- AT string parsing to utilize the AT parser library instead of the AT command parser library.
- The #XUDPCLI and #XSSOCKET (UDP client sockets) AT commands to use Zephyr’s Mbed TLS with DTLS when the overlay-native_tls.conf configuration file is used.

Thingy:53: Matter weather station

Added:
- The CONFIG_NCS_SAMPLE_MATTER_ZAP_FILES_PATH Kconfig option, which specifies ZAP files location for the application. By default, the option points to the src/default_zap directory and can be changed to any path relative to application’s location that contains the ZAP file and zap-generated directory.

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).
Bluetooth: ISO time synchronization:
- Fixed issues related to RTC wrapping that prevented the LED to toggle at the correct point in time.
Bluetooth: Event Trigger sample:
- Moved to the samples/bluetooth/event_trigger folder.

Bluetooth Fast Pair samples

Updated:
- The values for the CONFIG_BT_ADV_PROV_TX_POWER_CORRECTION_VAL Kconfig option in all configurations, and for the CONFIG_BT_FAST_PAIR_FMDN_TX_POWER_CORRECTION_VAL Kconfig option in configurations with the Find My Device Network (FMDN) extension support. The values are now aligned with the Fast Pair requirements.
Bluetooth Fast Pair: Locator tag sample:
- Added:
  - LED indication on development kits for the Fast Pair advertising state.
  - An application versioning using the VERSION file.
  - The DFU support which can be enabled using the SB_CONFIG_APP_DFU sysbuild Kconfig option. DFU is available for all supported targets except the debug configurations 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_adv module to use the trigger requests for the Fast Pair advertising state instead of setting the Fast Pair advertising mode directly.

Bluetooth Mesh samples

No changes since the latest nRF Connect SDK release.

Cellular samples

Cellular: Full modem firmware update using SMP Server sample:
- Removed the unused AT command parser library.
Cellular: Modem Shell sample:
- Added link modem command 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.
  - A call to the nrf_cloud_print_details() function and removed redundant logging.
Cellular: nRF Cloud multi-service sample:
- Added:
  - The CONFIG_TEST_COUNTER_MULTIPLIER Kconfig 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_DISCON to stop sensors and location services.
  - A call to the nrf_cloud_print_details() function and removed redundant logging.
  - Board support files to enable Wi-Fi scanning for the Thingy:91 X.
- Updated:
  - Wi-Fi overlays from newlibc to picolib.
  - Handling of JITP association to improve speed and reliability.
  - Renamed the overlay_nrf7002ek_wifi_no_lte.conf overlay to overlay_nrf700x_wifi_mqtt_no_lte.conf.
  - Renamed the overlay_nrf7002ek_wifi_coap_no_lte.conf overlay to overlay_nrf700x_wifi_coap_no_lte.conf.
- Fixed an issue where the accepted shadow was not marked as received because the config section did not yet exist in the shadow.
Cellular: nRF Cloud REST Device Message sample:
- Added:
  - Support for dictionary logs using REST.
  - A call to the nrf_cloud_print_details() function and removed redundant logging.
Cellular: nRF Cloud REST cellular location sample:
- Added a call to the nrf_cloud_print_details() function and removed redundant logging.

Cryptography samples

No changes since the latest nRF Connect SDK release.

Debug samples

Memfault sample:
- Increased the value of the CONFIG_MAIN_STACK_SIZE Kconfig option to 8192 bytes to avoid stack overflow.

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:
- The CONFIG_NCS_SAMPLE_MATTER_ZAP_FILES_PATH Kconfig option, which specifies ZAP files location for the sample. By default, the option points to the src/default_zap directory and can be changed to any path relative to sample’s location that contains the ZAP file and zap-generated directory.
- Support for Trusted Firmware-M on the nRF54L15 PDK.
- The Matter: Smoke CO Alarm sample that demonstrates implementation of Matter Smoke CO alarm device type.
Matter: Door lock sample:
- Added Matter Lock schedule snippet, and updated the documentation to use the snippet.
Enabled the OpenThread build report generation in all samples.

Networking samples

No changes since the latest nRF Connect SDK release.

NFC samples

No changes since the latest nRF Connect SDK release.

nRF RPC

Added the nRF RPC: Protocols serialization client and the nRF RPC: Protocols serialization server samples.

nRF5340 samples

nRF5340: SMP Server with external XIP sample:
- This sample has been converted to support sysbuild.
- Support has been added to demonstrate direct-XIP building and building without network core support.

Peripheral samples

IEEE 802.15.4 Sniffer sample:
- Increased the number of RX buffers to reduce the chances of frame drops during high traffic periods.
- Disabled the nRF Connect SDK boot banner.
- Added sysbuild configuration for nRF5340.
- 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_rx command.

PMIC samples

No changes since the latest nRF Connect SDK release.

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

No changes since the latest nRF Connect SDK release.

Thread samples

Enabled the OpenThread build report generation in all samples.
Thread: CLI sample:
- Added support for the nRF54L15 DK in the low-power snippet.

Zigbee samples

Zigbee: Light switch sample:
- Added the option to configure transmission power.

Wi-Fi samples

Wi-Fi: Radio test sample:
- Added capture timeout as a parameter for packet capture.
- Expanded the scope of wifi_radio_test show_config subcommand and rectified the behavior of wifi_radio_test tx_pkt_preamble subcommand.
Wi-Fi: SoftAP based provision sample:
- Increased the value of the CONFIG_SOFTAP_WIFI_PROVISION_THREAD_STACK_SIZE Kconfig 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

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

No changes since the latest nRF Connect SDK release.

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_BN Kconfig 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_PAIRING Kconfig option allowing the user to control the support for the Fast Pair subsequent pairing feature.
  - The CONFIG_BT_FAST_PAIR_USE_CASE Kconfig choice option allowing the user to select their target Fast Pair use case. The CONFIG_BT_FAST_PAIR_USE_CASE_UNKNOWN, CONFIG_BT_FAST_PAIR_USE_CASE_INPUT_DEVICE, CONFIG_BT_FAST_PAIR_USE_CASE_LOCATOR_TAG and CONFIG_BT_FAST_PAIR_USE_CASE_MOUSE Kconfig options represent the supported use cases that can be selected as part of this Kconfig choice option.
- Removed:
  - The MbedTLS cryptographic backend support in Fast Pair, because it is superseded by the PSA backend. Consequently, the CONFIG_BT_FAST_PAIR_CRYPTO_MBEDTLS Kconfig option has also been removed.
  - The default overrides for the CONFIG_BT_DIS and CONFIG_BT_DIS_FW_REV Kconfig 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_STR Kconfig option that was set to CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION if CONFIG_BOOTLOADER_MCUBOOT was 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 the VERSION file.
- 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.
Bluetooth LE advertising providers:
- Updated the CONFIG_BT_ADV_PROV_FAST_PAIR_SHOW_UI_PAIRING Kconfig option and the bt_le_adv_prov_fast_pair_show_ui_pairing() function to require the enabling of the CONFIG_BT_FAST_PAIR_SUBSEQUENT_PAIRING Kconfig option.
- Added the bt_le_adv_prov_adv_state.adv_handle field to the bt_le_adv_prov_adv_state structure to store the advertising handle. If the CONFIG_BT_EXT_ADV Kconfig option is enabled, you can use the bt_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, the bt_le_adv_prov_adv_state.adv_handle field must be set to 0. This field is currently used by the TX Power provider (CONFIG_BT_ADV_PROV_TX_POWER).

Common Application Framework

No changes since the latest nRF Connect SDK release.

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.

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.
AT command parser library:
- 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.
- Renamed the at_parser_cmd_type_get() function to at_parser_at_cmd_type_get() to prevent a name collision.
LTE link control library:
- Removed:
  - The lte_lc_init() function. All instances of this function can be removed without any additional actions.
  - The lte_lc_deinit() function. Use the lte_lc_power_off() function instead.
  - The lte_lc_init_and_connect() function. Use the lte_lc_connect() function instead.
  - The lte_lc_init_and_connect_async() function. Use the lte_lc_connect_async() function instead.
  - The CONFIG_LTE_NETWORK_USE_FALLBACK Kconfig option. Use the CONFIG_LTE_NETWORK_MODE_LTE_M_NBIOT or CONFIG_LTE_NETWORK_MODE_LTE_M_NBIOT_GPS Kconfig option instead. In addition, you can control the priority between LTE-M and NB-IoT using the CONFIG_LTE_MODE_PREFERENCE Kconfig option.
- 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.
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.
China Telecom ZZHC library 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.
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:
- Rename the nRF91 socket offload layer from nrf91_sockets to nrf9x_sockets to reflect that the offload layer is not exclusive to the nRF91 Series SiPs.
Modem information library:
- Fixed a potential issue with scanf in the modem_info_get_current_band() function, which could lead to memory corruption.
Modem library integration layer library:
- Updated the RTT trace backend to allocate the RTT channel at boot, instead of when the modem is activated.
- Removed support for deprecated RAI socket options SO_RAI_LAST, SO_RAI_NO_DATA, SO_RAI_ONE_RESP, SO_RAI_ONGOING, and SO_RAI_WAIT_MORE.
SMS library:
- Updated:
  - To use the AT+CMMS AT 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.

Multiprotocol Service Layer libraries

The Kconfig option CONFIG_MPSL_CX_THREAD has been renamed to CONFIG_MPSL_CX_3WIRE to better indicate multiprotocol compatibility.
The Kconfig option CONFIG_MPSL_CX_BT_1WIRE has been deprecated.
Added:
- A 1-wire coexistence implementation which can be enabled using the Kconfig option CONFIG_MPSL_CX_1WIRE.
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).

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_request() to 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 the CONFIG_NRF_CLOUD_CLIENT_ID_SRC_RUNTIME Kconfig option is enabled.
  - The functions nrf_cloud_sec_tag_set() and nrf_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_DISCON which is generated when a device is deleted from nRF Cloud.
  - The function nrf_cloud_print_details() to log common nRF Cloud connection information in a uniform way.
  - The CONFIG_NRF_CLOUD_VERBOSE_DETAILS Kconfig option to enable the nrf_cloud_print_details() function to print all details instead of only the device ID.
- Updated:
  - The CONFIG_NRF_CLOUD_CLIENT_ID_SRC_RUNTIME Kconfig option to be available with CoAP and REST.
  - The JSON string representing longitude in PVT reports from lng to lon to align with nRF Cloud. nRF Cloud still accepts lng for 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().
- Deprecated:
  - The CONFIG_NRF_CLOUD_IPV6 Kconfig option, which now no longer forces the nRF Cloud MQTT transport to use IPv4 when not enabled. Instead, use the CONFIG_NET_IPV4 and CONFIG_NET_IPV6 Kconfig options to customize which IP versions the nRF Cloud library uses.
  - The CONFIG_NRF_CLOUD_STATIC_IPV4 and CONFIG_NRF_CLOUD_STATIC_IPV4_ADDR Kconfig options. Support for statically configured nRF Cloud IP Addresses will soon be removed. Leave CONFIG_NRF_CLOUD_STATIC_IPV4 disabled to instead use automatic DNS lookup.
- Fixed an issue in the nrf_cloud_send() function that prevented data in the provided nrf_cloud_obj structure from being sent to the bulk and bin topics.
nRF Cloud CoAP library:
- Fixed:
  - A hard fault that occurred when encoding AGNSS request data and the net_info field of the nrf_cloud_rest_agnss_request structure is NULL.
  - An issue where certain CoAP functions could return zero, indidicating success, even though there was an error.
- Updated:
  - To use a shorter resource string for the d2c/bulk resource.
  - The function nrf_cloud_coap_shadow_get() to return -E2BIG if the received shadow data was truncated because the provided buffer was not big enough.
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 Log library:
- Added support for dictionary logs using REST.
- Added support for dictionary (binary) logs when connected to nRF Cloud using CoAP.
Firmware over-the-air (FOTA) updates library:
- Updated:
  - The CONFIG_NRF_CLOUD_FOTA_DOWNLOAD_FRAGMENT_SIZE Kconfig option to be available and used also when the CONFIG_NRF_CLOUD_FOTA_POLL Kconfig 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 asynchrounously if a callback to handle errors is provided.
nRF Cloud device provisioning library:
- Added support for the SO_KEEPOPEN socket option to keep the socket open even during PDN disconnect and reconnect.

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_data in the platform_internal_thread file.

nRF RPC libraries

Updated the internal Bluetooth serialization API and Bluetooth callback proxy API to become part of the public NRF RPC API.
Added:
- An experimental serialization of Openthread APIs.
- The logging backend that sends logs through nRF RPC events.

Other libraries

Added a compression/decompression library with support for the LZMA decompression.
Date-Time library:
- Fixed a bug that caused date-time updates to not be rescheduled under certain circumstances.
- 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_COUNT to control whether and how many consecutive date-time update retries may be performed, and CONFIG_DATE_TIME_RETRY_INTERVAL_SECONDS to control how quickly date-time update retries occur.
RAM power-down library:
- Added support for the nRF54L15 SoC.

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

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 integation

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.

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 Developing with Peripheral Sensor node shield page.
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.
Removed:
- 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.
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.