Changelog for nRF Connect SDK v3.0.0-preview1

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

Known issues

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

Changelog

The following sections provide detailed lists of changes by component.

IDE, OS, and tool support

• Updated:

  • The required SEGGER J-Link version to v8.10f.

  • The Install prerequisites section on the Installation page with the Windows-only requirement to install SEGGER USB Driver for J-Link.

Board support

No changes since the latest nRF Connect SDK release.

Build and configuration system

• Removed support for the deprecated multi-image builds (parent-child images) functionality. All nRF Connect SDK projects must now use Sysbuild (System build). See Migrating from multi-image builds to sysbuild for an overview of differences with parent-child image and how to migrate.

Bootloaders and DFU

No changes since the latest nRF Connect SDK release.

Developing with nRF91 Series

No changes since the latest nRF Connect SDK release.

Developing with nRF70 Series

• Firmware patches in the external memory

  • Removed support for storing the nRF70 firmware patches in external flash without the Partition Manager.

Working with nRF54H Series

• Removed the note on installing SEGGER USB Driver for J-Link on Windows from the Getting started with the nRF54H20 DK 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 Install prerequisites section on the Installation page.

Developing with nRF54L Series

• Added HMAC SHA-256 with a 128-bit key type to KMU, as detailed in the Key types that can be stored in the KMU documentation section.

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

• Added support for the following:

  • nRF21540 Front-End Module in GPIO mode for the nRF54L Series devices.

Developing with PMICs

No changes since the latest nRF Connect SDK release.

Security

• Added:

  • Support for HKDF-Expand and HKDF-Extract in CRACEN.

  • Support for Ed25519ph(HashEdDSA) to CRACEN.

• Updated the Managing access port protection 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.

• Moved the Processing environments in the nRF Connect SDK documentation page under Security from the Application development section.

Protocols

No changes since the latest nRF Connect SDK release.

Amazon Sidewalk

No changes since the latest nRF Connect SDK release.

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 Bluetooth Low Energy Remote Procedure Call configuration) did not work on the nRF54H20 devices due to incorrect memory mapping.

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

Bluetooth Mesh

No changes since the latest nRF Connect SDK release.

DECT NR+

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst (ESB)

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

Gazell

No changes since the latest nRF Connect SDK release.

Matter

• Added:

  • A new documentation page Matter Group Communication in the Matter overview.

  • A new section Creating manufacturer-specific clusters in Matter application in the Adding clusters to Matter application page.

  • A description for the new zap-append command within the Matter west commands page.

  • New arguments to the zap-gui command to provide a custom cache directory and add new clusters to Matter Data Model.

  • Matter debug snippet (matter-debug).

• Disabled the Multiprotocol Service Layer before performing factory reset to speed up the process.

Matter fork

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

No changes since the latest nRF Connect SDK release.

Zigbee

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

Wi-Fi

No changes since the latest nRF Connect SDK release.

Applications

This section provides detailed lists of changes by application.

Machine learning

• Updated the application to enable the Zephyr Memory Storage (ZMS) file system for the nRF54H20 DK board.

Asset Tracker v2

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

Connectivity Bridge

No changes since the latest nRF Connect SDK release.

IPC radio firmware

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

Matter Bridge

• Enabled SUIT DFU support for the Matter bridge application. Currently, only the Matter OTA protocol is fully supported for SUIT DFU purposes.

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

nRF5340 Audio

No changes since the latest nRF Connect SDK release.

nRF Desktop

• Updated:

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

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

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

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

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

    • Disabled Bluetooth long workqueue (CONFIG_BT_LONG_WQ).

    • Limited the number of key slots in the PSA Crypto core to 10 (CONFIG_MBEDTLS_PSA_KEY_SLOT_COUNT).

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

    • The system workqueue thread stack (CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE).

    • The CAF settings loader thread stack (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.

• Added:

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

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

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

nRF Machine Learning (Edge Impulse)

No changes since the latest nRF Connect SDK release.

Serial LTE modem

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

• Updated the application to use the Downloader library instead of the deprecated 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 sample.

Amazon Sidewalk samples

No changes since the latest nRF Connect SDK release.

Bluetooth samples

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

  • Bluetooth: Central HIDS

  • Bluetooth: 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:

    • Bluetooth: Central HIDS

    • Bluetooth: Peripheral HIDS keyboard

    • Bluetooth: 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 (CONFIG_MAIN_STACK_SIZE) to prevent stack overflows:

    • Bluetooth: Central HIDS

    • Bluetooth: Peripheral HIDS keyboard

    • Bluetooth: Peripheral HIDS mouse

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

• Bluetooth: 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.

• Bluetooth: Central UART sample:

  • Added reconnection to bonded devices based on their address.

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 (CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE).

    • The Bluetooth receiving thread stack (CONFIG_BT_RX_STACK_SIZE).

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

• Bluetooth Fast Pair: Locator tag sample:

  • Added support for the nRF54H20 DK board target.

  • 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:

    • Bluetooth Mesh NLC: HVAC Integration (Sensor observer)

    • Bluetooth Mesh NLC: Ambient Light Sensor/Occupancy Sensor

    • Bluetooth Mesh: Coexistence with other LE services

    • Bluetooth Mesh: Chat

    • Bluetooth Mesh: Light switch

    • Bluetooth Mesh: Silvair EnOcean

    • Bluetooth Mesh NLC: Dimming Control/Scene Selector

    • Bluetooth Mesh: Light

    • Bluetooth Mesh: Device Firmware Update (DFU) target

    • Bluetooth Mesh NLC: Lightness Controller/Energy Monitor

    • Bluetooth Mesh: Device Firmware Update (DFU) distributor

  • Support for nRF54L05 in the following samples:

    • Bluetooth Mesh NLC: HVAC Integration (Sensor observer)

    • Bluetooth Mesh NLC: Ambient Light Sensor/Occupancy Sensor

    • Bluetooth Mesh: Coexistence with other LE services

    • Bluetooth Mesh: Chat

    • Bluetooth Mesh: Light switch

    • Bluetooth Mesh: Silvair EnOcean

    • Bluetooth Mesh NLC: Dimming Control/Scene Selector

    • Bluetooth Mesh: Light

    • Bluetooth Mesh NLC: Lightness Controller/Energy Monitor

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

  • Bluetooth Mesh: Device Firmware Update (DFU) distributor

  • Bluetooth Mesh: Device Firmware Update (DFU) target

Cellular samples

• Updated the following samples to use the Downloader library instead of the Download client library:

  • Cellular: HTTP application update

  • Cellular: HTTP modem delta update

  • Cellular: HTTP full modem update

  • Cellular: Location

  • Cellular: LwM2M carrier

  • Cellular: LwM2M Client

  • Cellular: Modem Shell

  • nRF Cloud multi-service

  • nRF Cloud REST FOTA sample

• Cellular: Modem Shell sample:

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

• nRF Cloud multi-service sample:

  • Fixed:

    • Wrong header naming in provisioning_support.h that was causing build errors when sample_reboot.h was included in other source files.

    • An issue with an uninitialized variable in the handle_at_cmd_requests() function.

    • An issue with the too small CONFIG_COAP_EXTENDED_OPTIONS_LEN_VALUE Kconfig value in the 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.

• LTE Sensor Gateway sample:

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

• Cellular: PDN sample:

  • Added dynamic PDN information.

Cryptography samples

No changes since the latest nRF Connect SDK release.

Debug samples

No changes since the latest nRF Connect SDK release.

DECT NR+ samples

No changes since the latest nRF Connect SDK release.

Edge Impulse samples

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst samples

No changes since the latest nRF Connect SDK release.

Gazell samples

No changes since the latest nRF Connect SDK release.

Keys samples

No changes since the latest nRF Connect SDK release.

Matter samples

• Updated the Matter: Template sample document with the 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 MRAM only.

• Enabled SUIT DFU support for the Matter: Door lock, and Matter: Template samples. Currently, only the Matter OTA protocol is fully supported for SUIT DFU purposes.

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

Networking samples

• Updated:

  • The 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 Downloader library instead of the Download client library:

    • AWS IoT

    • Azure IoT Hub

    • Download

NFC samples

No changes since the latest nRF Connect SDK release.

nRF5340 samples

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

Peripheral samples

• Radio test (short-range) sample:

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

PMIC samples

• nPM1300: Fuel gauge sample:

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

No changes since the latest nRF Connect SDK release.

Protocol serialization samples

No changes since the latest nRF Connect SDK release.

SDFW samples

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

Sensor samples

No changes since the latest nRF Connect SDK release.

SUIT samples

No changes since the latest nRF Connect SDK release.

Trusted Firmware-M (TF-M) samples

• TF-M: PSA template sample:

  • Added support for the following attestation token fields:

    • Profile definition

    • PSA certificate reference (optional), configured using the SB_CONFIG_TFM_OTP_PSA_CERTIFICATE_REFERENCE sysbuild Kconfig option

    • Verification service URL (optional), configured using the CONFIG_TFM_ATTEST_VERIFICATION_SERVICE_URL Kconfig option

Thread samples

No changes since the latest nRF Connect SDK release.

Zigbee samples

No changes since the latest nRF Connect SDK release.

Wi-Fi samples

• Wi-Fi: Station sample:

  • Added an overlay-zperf.conf overlay for performance benchmarking and memory footprint analysis.

• Radio test samples:

  • Added:

    • The Wi-Fi: Bluetooth LE Wi-Fi Radio test (Single domain) sample to demonstrate the Wi-Fi and Bluetooth LE radio test running on the application core.

  • Updated:

    • The Wi-Fi: Radio test (Multi domain) sample is now moved to samples/wifi/radio_test/multi_domain.

• Wi-Fi: Shell sample:

  • Modified support for storing the nRF70 firmware patches in external flash using the Partition Manager.

Other samples

• CoreMark sample:

  • Added:

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

    • FLPR core support for the nRF54L15 DK board target.

Drivers

This section provides detailed lists of changes by driver.

No changes since the latest nRF Connect SDK release.

Wi-Fi drivers

No changes since the latest nRF Connect SDK release.

Libraries

This section provides detailed lists of changes by library.

Binary libraries

• LwM2M carrier library:

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

Bluetooth libraries and services

• Google Fast Pair Service (GFPS) library:

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

  • Updated the automatically generated bt_fast_pair partition definition (located in the subsys/partition_manager/pm.yml.bt_fast_pair) to work correctly when building with TF-M.

• Bluetooth Mesh libraries library:

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

• Google Fast Pair Service (GFPS) library:

  • Updated the bt_fast_pair_info_cb_register() API to allow registration of multiple callbacks.

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.

• Full modem firmware update from flash device:

  • Regenerated the zcbor-generated code files using v0.9.0.

Gazell libraries

No changes since the latest nRF Connect SDK release.

Security libraries

No changes since the latest nRF Connect SDK release.

Modem libraries

• Deprecated the AT parameters library.

• PDN library:

  • Deprecated the pdn_dynamic_params_get() function. Use the new function pdn_dynamic_info_get() instead.

• LTE link control library:

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

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

• Modem key management library:

  • Added:

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

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

  • Fixed:

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

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

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

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

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

• Modem library integration layer:

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

• Location library:

  • Removed references to HERE location services.

• AT Host library:

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

• Modem information library:

  • Added:

    • The modem_info_data_type type for representing LTE link information data types.

    • The modem_info_data_type_get() function for requesting the data type of the current modem information type.

  • Deprecated the modem_info_type_get() function in favor of the modem_info_data_type_get() function.

Multiprotocol Service Layer libraries

No changes since the latest nRF Connect SDK release.

Libraries for networking

• Added:

  • The Downloader library.

  • A backend for the TLS Credentials Subsystem that stores the credentials in the modem, see CONFIG_TLS_CREDENTIALS_BACKEND_NRF_MODEM.

• Deprecated the Download client library. See the migration guide for recommended changes.

• Updated the following libraries to use the Downloader library instead of the Download client library:

  • nRF Cloud

  • AWS FOTA

  • Azure FOTA

  • FOTA download

• nRF Cloud P-GPS library:

  • Fixed the warning due to missing https download protocol.

• Downloader library:

  • Updated to support Proxy-URI option and an authentication callback after connecting.

• FOTA download library:

  • Added error codes related to unsupported protocol, DFU failures, and invalid configuration.

  • Updated to use the Downloader library for CoAP downloads.

• nRF Cloud library:

  • Added the CONFIG_NRF_CLOUD Kconfig option to prevent unintended inclusion of nRF Cloud Kconfig variables in non-nRF Cloud projects.

  • Updated to use the Downloader library for CoAP downloads.

Libraries for NFC

No changes since the latest nRF Connect SDK release.

nRF RPC libraries

No changes since the latest nRF Connect SDK release.

Other libraries

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

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.

No changes since the latest nRF Connect SDK release.

Integrations

This section provides detailed lists of changes by integration.

Google Fast Pair integration

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

Edge Impulse integration

No changes since the latest nRF Connect SDK release.

Memfault integration

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

AVSystem integration

No changes since the latest nRF Connect SDK release.

nRF Cloud integration

No changes since the latest nRF Connect SDK release.

CoreMark integration

No changes since the latest nRF Connect SDK release.

DULT integration

No changes since the latest nRF Connect SDK release.

MCUboot

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

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

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

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

Zephyr

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

For the list of upstream Zephyr commits (not including cherry-picked commits) incorporated into nRF Connect SDK since the most recent release, run the following command from the ncs/zephyr repository (after running west update):

git log --oneline fdeb735017 ^beb733919d

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

git log --oneline manifest-rev ^fdeb735017

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

Note

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

Additions specific to nRF Connect SDK

No changes since the latest nRF Connect SDK release.

zcbor

No changes since the latest nRF Connect SDK release.

Trusted Firmware-M

No changes since the latest nRF Connect SDK release.

cJSON

No changes since the latest nRF Connect SDK release.

Documentation

• Added:

  • New section Developing with custom boards. This section includes the following pages:

    • Defining custom board - Previously located under Board support.

    • Connecting custom boards for programming - New page.

  • New page Preloaded and precompiled Thingy:53 firmware under Developing with Thingy:53. This page includes some of the information previously located on the standalone page for getting started with Nordic Thingy:53.

  • New page Adding a dimmable LED node under Configuring devicetree. This page includes information previously located in the nRF Connect for VS Code documentation.

• Updated:

  • The Creating an application page with the Creating application from add-ons section.

  • The Developing with nRF91 Series documentation to use nRF Util instead of nrfjprog.

  • The Versions and revisions section of the nRF Connect SDK 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 Preloaded and precompiled Thingy:53 firmware page and to the Programming Nordic Thingy:53 section in the Programmer app documentation.