release-notes-changelog.rst

Changelog for |NCS| v2.9.99

• Known issues
• Changelog
  • IDE, OS, and tool support
  • Board support
  • Build and configuration system
  • Bootloaders and DFU
  • Developing with nRF91 Series
  • Developing with nRF70 Series
  • Working with nRF54H Series
  • Developing with nRF54L Series
  • Developing with nRF53 Series
  • Developing with nRF52 Series
  • Developing with Front-End Modules
  • Developing with PMICs
  • Security
  • Protocols
  • Applications
  • Samples
  • Drivers
  • Libraries
  • Scripts
  • Integrations
  • MCUboot
  • Zephyr
  • zcbor
  • Trusted Firmware-M
  • cJSON
  • Documentation

The most relevant changes that are present on the main branch of the |NCS|, 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.9.0-nRF54H20-1-rc3`_ 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.10f.
  • The :ref:`installing_vsc` section on the :ref:`installation` page with the Windows-only requirement to install SEGGER USB Driver for J-Link.

Board support

|no_changes_yet_note|

Build and configuration system

• Removed support for the deprecated multi-image builds (parent-child images) functionality. All |NCS| projects must now use :ref:`sysbuild`. See :ref:`child_parent_to_sysbuild_migration` for an overview of differences with parent-child image and how to migrate.

Bootloaders and DFU

|no_changes_yet_note|

Developing with nRF91 Series

|no_changes_yet_note|

Developing with nRF70 Series

• :ref:`ug_nrf70_developing_fw_patch_ext_flash`

  • Removed support for storing the nRF70 firmware patches in external flash without the :ref:`partition_manager`.

Working with nRF54H Series

• Removed the note on installing SEGGER USB Driver for J-Link on Windows from the :ref:`ug_nrf54h20_gs` page and moved its contents to the `nRF Util prerequisites`_ documentation. The Windows-only requirement to install the SEGGER USB Driver for J-Link is now mentioned in the :ref:`installing_vsc` section on the :ref:`installation` page.

Developing with nRF54L Series

• Added HMAC SHA-256 with a 128-bit key type to KMU, as detailed in the :ref:`ug_nrf54l_crypto_kmu_supported_key_types` documentation section.

Developing with nRF53 Series

|no_changes_yet_note|

Developing with nRF52 Series

|no_changes_yet_note|

Developing with Front-End Modules

• Added support for the following:
  • :ref:`nRF2220 Front-End Module <ug_radio_fem_nrf2220>`.
  • :ref:`nRF2220 EK shield <ug_radio_fem_nrf2220ek>`.
  • :ref:`nRF21540 Front-End Module in GPIO mode <ug_radio_fem_nrf21540_gpio>` for the nRF54L Series devices.

Developing with PMICs

|no_changes_yet_note|

Security

• Added:
  • Support for HKDF-Expand and HKDF-Extract in CRACEN.
  • Support for Ed25519ph(HashEdDSA) to CRACEN.
  • Documentation page about the :ref:`ug_tfm_architecture`.
• Updated:
  • The :ref:`app_approtect` page with nRF Util commands that replaced the nrfjprog commands. This is part of the ongoing work of archiving `nRF Command Line Tools`_ and replacing them with nRF Util.
  • The Running applications with Trusted Firmware-M page by renaming it to :ref:`ug_tfm` and moving it under :ref:`ug_tfm_index`.
• Moved the :ref:`app_boards_spe_nspe` documentation page under :ref:`ug_tfm_index` from the :ref:`ug_app_dev` section.

Protocols

|no_changes_yet_note|

Amazon Sidewalk

|no_changes_yet_note|

Bluetooth® LE

• Fixed an issue where a flash operation executed on the system workqueue might result in -ETIMEDOUT, if there is an active Bluetooth LE connection.
• Fixed an issue where Bluetooth applications built with the nordic-bt-rpc snippet (in the :ref:`ble_rpc` configuration) did not work on the nRF54H20 devices due to incorrect memory mapping.
• Updated the Bluetooth LE SoftDevice Controller driver to make the :c:func:`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 (:kconfig:option:`CONFIG_BT_CTLR_SDC_LLPM`).

Bluetooth Mesh

|no_changes_yet_note|

DECT NR+

|no_changes_yet_note|

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

Matter

• Added:
  • A new documentation page :ref:`ug_matter_group_communication` in the :ref:`ug_matter_intro_overview`.
  • A new section :ref:`ug_matter_creating_accessory_vendor_cluster` in the :ref:`ug_matter_creating_accessory` page.
  • A description for the new :ref:`ug_matter_gs_tools_matter_west_commands_append` within the :ref:`ug_matter_gs_tools_matter_west_commands` page.
  • New arguments to the :ref:`ug_matter_gs_tools_matter_west_commands_zap_tool_gui` to provide a custom cache directory and add new clusters to Matter Data Model.
  • :ref:`ug_matter_debug_snippet`.
  • Storing Matter key materials in the :ref:`matter_platforms_security_kmu`.
• Disabled the :ref:`mpsl` before performing factory reset to speed up the process.

Matter fork

|no_changes_yet_note|

nRF IEEE 802.15.4 radio driver

|no_changes_yet_note|

Thread

|no_changes_yet_note|

Zigbee

• Fixed the :file:`zb_add_ota_header.py` script to allow a patch version higher than 9 in an APPLICATION_VERSION_STRING.

Wi-Fi

|no_changes_yet_note|

Applications

This section provides detailed lists of changes by :ref:`application <applications>`.

Machine learning

• Updated the application to enable the :ref:`Zephyr Memory Storage (ZMS) <zephyr:zms_api>` file system for the :ref:`zephyr:nrf54h20dk_nrf54h20` board.

Asset Tracker v2

• Updated the application to use the :ref:`lib_downloader` library instead of the deprecated :ref:`lib_download_client` library.

Connectivity Bridge

|no_changes_yet_note|

IPC radio firmware

• Updated the application to enable the :ref:`Zephyr Memory Storage (ZMS) <zephyr:zms_api>` file system in all devices that contain MRAM, such as the nRF54H Series devices.
• Updated documentation of applications and samples that use the IPC radio firmware as :ref:`companion component <companion_components>` to mention its usage when built with :ref:`configuration_system_overview_sysbuild`.

Matter Bridge

• Removed support for the nRF54H20 devices.
• Enabled Link Time Optimization (LTO) by default for the release configuration.

nRF5340 Audio

|no_changes_yet_note|

nRF Desktop

• Updated:

  • The :ref:`nrf_desktop_failsafe` to use the Zephyr :ref:`zephyr:hwinfo_api` driver for getting and clearing the reset reason information (see the :c:func:`hwinfo_get_reset_cause` and :c:func:`hwinfo_clear_reset_cause` functions). The Zephyr :ref:`zephyr:hwinfo_api` driver replaces the dependency on the nrfx reset reason helper (see the :c:func:`nrfx_reset_reason_get` and :c:func:`nrfx_reset_reason_clear` functions).

  • The release configuration for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target to enable the :ref:`nrf_desktop_failsafe` (see the :ref:`CONFIG_DESKTOP_FAILSAFE_ENABLE <config_desktop_app_options>` Kconfig option).

  • Enabled Link Time Optimization (:kconfig:option:`CONFIG_LTO` and :kconfig:option:`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 (:kconfig:option:`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 (:kconfig:option:`CONFIG_BT_RX_STACK_SIZE`) to prevent stack overflows.

  • Application configurations for nRF52810 and nRF52820 SoCs to reduce memory footprint:

    • Disabled Bluetooth long workqueue (:kconfig:option:`CONFIG_BT_LONG_WQ`).
    • Limited the number of key slots in the PSA Crypto core to 10 (:kconfig:option:`CONFIG_MBEDTLS_PSA_KEY_SLOT_COUNT`).

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

    • The system workqueue thread stack (:kconfig:option:`CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE`).
    • The CAF settings loader thread stack (:kconfig:option:`CONFIG_CAF_SETTINGS_LOADER_THREAD_STACK_SIZE`).

    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 :kconfig:option:`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.

  • :ref:`nrf_desktop_hid_state` and :ref:`nrf_desktop_fn_keys` to use :c:func:`bsearch` implementation from C library. This simplifies maintenance and allows you to use Picolibc (:kconfig:option:`CONFIG_PICOLIBC`).

  • The IPC radio image configurations of the nRF5340 DK to use Picolibc (:kconfig:option:`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 (:kconfig:option:`CONFIG_PICOLIBC`) by default. Using the minimal libc implementation (:kconfig:option:`CONFIG_MINIMAL_LIBC`) no longer decreases the memory footprint of the application image for most of the configurations.

• Added:

  • System Power Management for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target on the application and radio cores. The application still has high power consumption as the Bluetooth LE controller running on the radio core requires disabling MRAM latency (:kconfig:option:`CONFIG_MRAM_LATENCY_AUTO_REQ`). Enabling MRAM latency makes the Bluetooth LE controller unstable.
  • 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 :ref:`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.

• Removed an imply from the nRF Desktop Bluetooth connectivity Kconfig option (:ref:`CONFIG_DESKTOP_BT <config_desktop_app_options>`). The imply enabled a separate workqueue for connection TX notify processing (:kconfig:option:`CONFIG_BT_CONN_TX_NOTIFY_WQ`) if MPSL was used for synchronization between the flash memory driver and radio (:kconfig:option:`CONFIG_SOC_FLASH_NRF_RADIO_SYNC_MPSL`). The MPSL flash synchronization issue (NCSDK-29354 in the :ref:`known_issues`) is fixed. The workaround is no longer needed.

nRF Machine Learning (Edge Impulse)

|no_changes_yet_note|

Serial LTE modem

• Added an overlay :file:`overlay-memfault.conf` file to enable Memfault. For more information about Memfault features in |NCS|, see :ref:`mod_memfault`.
• Updated the application to use the :ref:`lib_downloader` library instead of the deprecated :ref:`lib_download_client` library.

Thingy:53: Matter weather station

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

Samples

This section provides detailed lists of changes by :ref:`sample <samples>`.

Amazon Sidewalk samples

|no_changes_yet_note|

Bluetooth samples

• Added support for the nrf54l15dk/nrf54l05/cpuapp and nrf54l15dk/nrf54l10/cpuapp board targets in the following samples:

  • :ref:`bluetooth_central_hids`
  • :ref:`peripheral_hids_keyboard`

• Updated:

  • The configurations of the non-secure nrf5340dk/nrf5340/cpuapp/ns board target in the following samples to properly use the TF-M profile instead of the predefined minimal TF-M profile:

    • :ref:`bluetooth_central_hids`
    • :ref:`peripheral_hids_keyboard`
    • :ref:`peripheral_hids_mouse`

    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 configurations of the following samples by increasing the main thread stack size (:kconfig:option:`CONFIG_MAIN_STACK_SIZE`) to prevent stack overflows:

    • :ref:`bluetooth_central_hids`
    • :ref:`peripheral_hids_keyboard`
    • :ref:`peripheral_hids_mouse`

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

  • The following samples to use LE Secure Connection pairing (:kconfig:option:`CONFIG_BT_SMP_SC_PAIR_ONLY`).

    • :ref:`peripheral_gatt_dm`
    • :ref:`peripheral_mds`
    • :ref:`peripheral_cts_client`

• :ref:`direct_test_mode` sample:

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

• :ref:`central_uart` sample:

  • Added reconnection to bonded devices based on their address.

• :ref:`bluetooth_central_hr_coded` sample:

  • Added the Advertising Coding Selection feature to the sample.

• :ref:`peripheral_hr_coded` sample:

  • Added the Advertising Coding Selection feature to the sample.

Bluetooth Mesh samples

• :ref:`bluetooth_mesh_light_lc` sample:
  • Disabled the Friend feature when the sample is compiled for the :ref:`zephyr:nrf52dk_nrf52832` board target to increase the amount of RAM available for the application.

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:

    • The system workqueue thread stack (:kconfig:option:`CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE`).
    • The Bluetooth receiving thread stack (:kconfig:option:`CONFIG_BT_RX_STACK_SIZE`).

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

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

• :ref:`fast_pair_locator_tag` sample:

  • Added:
    • Support for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target.
    • Support for the 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 :ref:`ug_bt_fast_pair_provisioning_register_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 change in the TF-M profile configuration.

Bluetooth Mesh samples

• Added:

  • Support for nRF54L10 in the following samples:
    • :ref:`bluetooth_mesh_sensor_client`
    • :ref:`bluetooth_mesh_sensor_server`
    • :ref:`bluetooth_ble_peripheral_lbs_coex`
    • :ref:`bt_mesh_chat`
    • :ref:`bluetooth_mesh_light_switch`
    • :ref:`bluetooth_mesh_silvair_enocean`
    • :ref:`bluetooth_mesh_light_dim`
    • :ref:`bluetooth_mesh_light`
    • :ref:`ble_mesh_dfu_target`
    • :ref:`bluetooth_mesh_light_lc`
    • :ref:`ble_mesh_dfu_distributor`
  • Support for nRF54L05 in the following samples:
    • :ref:`bluetooth_mesh_sensor_client`
    • :ref:`bluetooth_mesh_sensor_server`
    • :ref:`bluetooth_ble_peripheral_lbs_coex`
    • :ref:`bt_mesh_chat`
    • :ref:`bluetooth_mesh_light_switch`
    • :ref:`bluetooth_mesh_silvair_enocean`
    • :ref:`bluetooth_mesh_light_dim`
    • :ref:`bluetooth_mesh_light`
    • :ref:`bluetooth_mesh_light_lc`

• Updated the following samples to include the value of the :kconfig:option:`CONFIG_BT_COMPANY_ID` option in the Firmware ID:

  • :ref:`ble_mesh_dfu_distributor`
  • :ref:`ble_mesh_dfu_target`

Cellular samples

• Updated the following samples to use the :ref:`lib_downloader` library instead of the :ref:`lib_download_client` library:

  • :ref:`http_application_update_sample`
  • :ref:`http_modem_delta_update_sample`
  • :ref:`http_modem_full_update_sample`
  • :ref:`location_sample`
  • :ref:`lwm2m_carrier`
  • :ref:`lwm2m_client`
  • :ref:`modem_shell_application`
  • :ref:`nrf_cloud_multi_service`
  • :ref:`nrf_cloud_rest_fota`

• :ref:`modem_shell_application` sample:

  • Removed the CONFIG_MOSH_LINK Kconfig option. The link control functionality is now always enabled and cannot be disabled.

• :ref:`nrf_cloud_multi_service` sample:

  • Fixed:
    • Wrong header naming in :file:`provisioning_support.h` that was causing build errors when :file:`sample_reboot.h` was included in other source files.
    • An issue with an uninitialized variable in the :c:func:`handle_at_cmd_requests` function.
    • An issue with the too small :kconfig:option:`CONFIG_COAP_EXTENDED_OPTIONS_LEN_VALUE` Kconfig value in the :file:`overlay-coap_nrf_provisioning.conf` file.
    • Slow Wi-Fi connectivity startup by selecting TFM_SFN instead of TFM_IPC.
    • The size of TLS credentials buffer for Wi-Fi connectivity to allow installing both AWS and CoAP CA certificates.

• :ref:`lte_sensor_gateway` sample:

  • Fixed an issue with devicetree configuration after HCI updates in `sdk-zephyr`_.

• :ref:`pdn_sample` sample:

  • Added dynamic PDN information.

Cryptography samples

|no_changes_yet_note|

Debug samples

|no_changes_yet_note|

DECT NR+ samples

|no_changes_yet_note|

Edge Impulse samples

|no_changes_yet_note|

Enhanced ShockBurst samples

|no_changes_yet_note|

Gazell samples

|no_changes_yet_note|

Keys samples

|no_changes_yet_note|

Matter samples

• :ref:`matter_template_sample` 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.
• :ref:`matter_lock_sample` sample:
  • Removed support for nRF54H20 devices.

Networking samples

• Updated:
  • The :kconfig:option:`CONFIG_HEAP_MEM_POOL_SIZE` Kconfig option value to 1280 for all networking samples that had it set to a lower value. This is a requirement from zephyr and removes a build warning.
  • The following samples to use the :ref:`lib_downloader` library instead of the :ref:`lib_download_client` library:
    • :ref:`aws_iot`
    • :ref:`azure_iot_hub`
    • :ref:`download_sample`

NFC samples

|no_changes_yet_note|

nRF5340 samples

• Removed the nRF5340: Multiprotocol RPMsg sample. Use the :ref:`ipc_radio` application instead.

Peripheral samples

• :ref:`radio_test` 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 :ref:`npm2100_fuel_gauge` sample that demonstrates how to calculate the battery state of charge of primary cell batteries using the :ref:`nrfxlib:nrf_fuel_gauge`.
• :ref:`npm1300_fuel_gauge` sample:
  • Updated to accommodate API changes in nRF Fuel Gauge library v1.0.0.

|no_changes_yet_note|

Protocol serialization samples

|no_changes_yet_note|

SDFW samples

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

Sensor samples

|no_changes_yet_note|

SUIT samples

|no_changes_yet_note|

Trusted Firmware-M (TF-M) samples

• :ref:`tfm_psa_template` sample:
  • Added support for the following attestation token fields:
    • Profile definition
    • PSA certificate reference (optional), configured using the :kconfig:option:`SB_CONFIG_TFM_OTP_PSA_CERTIFICATE_REFERENCE` sysbuild Kconfig option
    • Verification service URL (optional), configured using the :kconfig:option:`CONFIG_TFM_ATTEST_VERIFICATION_SERVICE_URL` Kconfig option
• :ref:`tfm_secure_peripheral_partition` sample:
  • Updated documentation with information about how to access other TF-M partitions from the secure partition.

Thread samples

• :ref:`ot_cli_sample` sample:
  • Removed support for the nRF54H20 DK.

Zigbee samples

|no_changes_yet_note|

Wi-Fi samples

• :ref:`wifi_station_sample` sample:
  • Added an overlay-zperf.conf overlay for :ref:`performance benchmarking and memory footprint analysis <wifi_sta_performance_testing_memory_footprint>`.
• Radio test samples:
  • Added:
    • The :ref:`wifi_radio_test_sd` sample to demonstrate the Wi-Fi and Bluetooth LE radio test running on the application core.
  • Updated:
    • The :ref:`wifi_radio_test` sample is now moved to :zephyr_file:`samples/wifi/radio_test/multi_domain`.
• :ref:`wifi_shell_sample` sample:
  • Modified support for storing the nRF70 firmware patches in external flash using the :ref:`partition_manager`.

Other samples

• :ref:`coremark_sample` sample:

  • Added:

    • Support for the nRF54L05 and nRF54L10 SoCs (emulated on nRF54L15 DK).
    • FLPR core support for the :ref:`zephyr:nrf54l15dk_nrf54l15` and :ref:`zephyr:nrf54h20dk_nrf54h20` board targets.

  • Removed the following compiler options that were set in the :kconfig:option:`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.

• :ref:`caf_sensor_manager_sample` sample:

  • Added low power configuration for the :ref:`zephyr:nrf54h20dk_nrf54h20` board target.

Drivers

This section provides detailed lists of changes by :ref:`driver <drivers>`.

|no_changes_yet_note|

Wi-Fi drivers

|no_changes_yet_note|

Libraries

This section provides detailed lists of changes by :ref:`library <libraries>`.

Binary libraries

• :ref:`liblwm2m_carrier_readme` library:
  • Updated the glue to use the :ref:`lib_downloader` library instead of the deprecated :ref:`lib_download_client` library.

Bluetooth libraries and services

• :ref:`bt_fast_pair_readme` library:
  • Added:
    • A restriction on the :kconfig:option:`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 - :c:member:`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 :ref:`ug_bt_fast_pair_provisioning_register_firmware_update_intent` section in the Fast Pair integration guide.
  • Updated the automatically generated bt_fast_pair partition definition (located in the :file:`subsys/partition_manager/pm.yml.bt_fast_pair`) to work correctly when building with TF-M.
• :ref:`bt_mesh` library:
  • Fixed an issue in the :ref:`bt_mesh_light_ctrl_srv_readme` model to automatically resume the Lightness Controller after recalling a scene (NCSDK-30033 known issue).
• :ref:`bt_fast_pair_readme` library:
  • Updated the :c:func:`bt_fast_pair_info_cb_register` API to allow registration of multiple callbacks.

Common Application Framework

|no_changes_yet_note|

Debug libraries

|no_changes_yet_note|

DFU libraries

|no_changes_yet_note|

• :ref:`lib_fmfu_fdev`:
  • Regenerated the zcbor-generated code files using v0.9.0.

Gazell libraries

|no_changes_yet_note|

Security libraries

|no_changes_yet_note|

Modem libraries

• Deprecated the :ref:`at_params_readme` library.
• :ref:`pdn_readme` library:
  • Deprecated the :c:func:`pdn_dynamic_params_get` function. Use the new function :c:func:`pdn_dynamic_info_get` instead.
• :ref:`lte_lc_readme` 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.
• :ref:`modem_key_mgmt` library:
  • Added:
    • The :c:func:`modem_key_mgmt_digest` function that would retrieve the SHA1 digest of a credential from the modem.
    • The :c:func:`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 :c:func:`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 :c:func:`modem_key_mgmt_clear` function where +CMEE error notifications were not restored to their original state if the AT%CMNG AT command failed.
    • The :c:func:`modem_key_mgmt_clear` function to lock the shared scratch buffer.
• Updated the :ref:`nrf_modem_lib_lte_net_if` to automatically set the actual link :term:`Maximum Transmission Unit (MTU)` on the network interface when PDN connectivity is gained.
• :ref:`nrf_modem_lib_readme`:
  • Fixed a bug where various subsystems would be erroneously initialized during a failed initialization of the library.
• :ref:`lib_location` library:
  • Removed references to HERE location services.
• :ref:`lib_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 :kconfig:option:`CONFIG_LOG_BACKEND_UART` Kconfig option was set.
• :ref:`modem_info_readme` library:
  • Added:
    • The :c:enum:`modem_info_data_type` type for representing LTE link information data types.
    • The :c:func:`modem_info_data_type_get` function for requesting the data type of the current modem information type.
  • Deprecated the :c:func:`modem_info_type_get` function in favor of the :c:func:`modem_info_data_type_get` function.

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

• Added:
  • The :ref:`lib_downloader` library.
  • A backend for the :ref:`TLS Credentials Subsystem <zephyr:sockets_tls_credentials_subsys>` that stores the credentials in the modem, see :kconfig:option:`CONFIG_TLS_CREDENTIALS_BACKEND_NRF_MODEM`.
• Deprecated the :ref:`lib_download_client` library. See the :ref:`migration guide <migration_3.0_recommended>` for recommended changes.
• Updated the following libraries to use the :ref:`lib_downloader` library instead of the :ref:`lib_download_client` library:
  • :ref:`lib_nrf_cloud`
  • :ref:`lib_aws_fota`
  • :ref:`lib_azure_fota`
  • :ref:`lib_fota_download`
• :ref:`lib_nrf_cloud_pgps` library:
  • Fixed the warning due to missing https download protocol.
• :ref:`lib_downloader` library:
  • Updated to support Proxy-URI option and an authentication callback after connecting.
• :ref:`lib_fota_download` library:
  • Added error codes related to unsupported protocol, DFU failures, and invalid configuration.
  • Updated to use the :ref:`lib_downloader` library for CoAP downloads.
• :ref:`lib_nrf_cloud` library:
  • Added the :kconfig:option:`CONFIG_NRF_CLOUD` Kconfig option to prevent unintended inclusion of nRF Cloud Kconfig variables in non-nRF Cloud projects.
  • Updated to use the :ref:`lib_downloader` library for CoAP downloads.

Libraries for NFC

|no_changes_yet_note|

nRF RPC libraries

|no_changes_yet_note|

Other libraries

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

Security libraries

|no_changes_yet_note|

Shell libraries

|no_changes_yet_note|

Libraries for Zigbee

|no_changes_yet_note|

sdk-nrfxlib

See the changelog for each library in the :doc:`nrfxlib documentation <nrfxlib:README>` for additional information.

Scripts

This section provides detailed lists of changes by :ref:`script <scripts>`.

|no_changes_yet_note|

Integrations

This section provides detailed lists of changes by :ref:`integration <integrations>`.

Google Fast Pair integration

• Added:
  • Instructions on how to provision the Fast Pair data onto devices without the :ref:`partition_manager` support, specifically for the :ref:`zephyr:nrf54h20dk_nrf54h20`.
  • 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.

Edge Impulse integration

|no_changes_yet_note|

Memfault integration

• Added a new feature to automatically post coredumps to Memfault when network connectivity is available. To enable this feature, set the :kconfig:option:`CONFIG_MEMFAULT_NCS_POST_COREDUMP_ON_NETWORK_CONNECTED` Kconfig option to y. Only supported for nRF91 Series devices.

AVSystem integration

|no_changes_yet_note|

nRF Cloud integration

|no_changes_yet_note|

CoreMark integration

|no_changes_yet_note|

DULT integration

|no_changes_yet_note|

MCUboot

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

The code for integrating MCUboot into |NCS| is located in the :file:`ncs/nrf/modules/mcuboot` folder.

The following list summarizes both the main changes inherited from upstream MCUboot and the main changes applied to the |NCS| specific additions:

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

Zephyr

The Zephyr fork in |NCS| (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including fdeb7350171279d4637c536fcceaad3fbb775392, with some |NCS| 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 :file:`ncs/zephyr` repository (after running west update):

git log --oneline fdeb735017 ^beb733919d

For the list of |NCS| specific commits, including commits cherry-picked from upstream, run:

git log --oneline manifest-rev ^fdeb735017

The current |NCS| 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 :ref:`Zephyr release notes <zephyr_release_notes>`.

Additions specific to |NCS|

|no_changes_yet_note|

zcbor

|no_changes_yet_note|

Trusted Firmware-M

|no_changes_yet_note|

cJSON

|no_changes_yet_note|

Documentation

• Added:
  • New section :ref:`ug_custom_board`. This section includes the following pages:
    • :ref:`defining_custom_board` - Previously located under :ref:`app_boards`.
    • :ref:`programming_custom_board` - New page.
  • New page :ref:`thingy53_precompiled` under :ref:`ug_thingy53`. This page includes some of the information previously located on the standalone page for getting started with Nordic Thingy:53.
  • New page :ref:`add_new_led_example` under :ref:`configuring_devicetree`. This page includes information previously located in the |nRFVSC| documentation.
• Updated:
  • The :ref:`create_application` page with the :ref:`creating_add_on_index` section.
  • The :ref:`ug_nrf91` documentation to use `nRF Util`_ instead of nrfjprog.
  • The :ref:`dm-revisions` section of the :ref:`dm_code_base` page with information about the preview release tag, which replaces the development tag.
• Removed:
  • The standalone page for getting started with Nordic Thingy:53. The contents of this page have been moved to the :ref:`thingy53_precompiled` page and to the `Programmer app <Programming Nordic Thingy:53_>`_ documentation.
  • The standalone page for getting started with Nordic Thingy:91. The contents of this page are covered by the `Cellular IoT Fundamentals course`_ in the `Nordic Developer Academy`_. The part about connecting the prototyping platform to nRF Cloud is now a standalone :ref:`thingy91_connect_to_cloud` page in the :ref:`thingy91_ug_intro` section.
  • The standalone page for getting started with the nRF9160 DK. This page has been replaced by the `Quick Start app`_ that supports the nRF9160 DK. The part about connecting the DK to nRF Cloud is now a standalone :ref:`nrf9160_gs_connecting_dk_to_cloud` page in the :ref:`ug_nrf9160` section.