nRF Connect SDK v2.6.99-cs1 Release Notes

nRF Connect SDK v2.6.99-cs1 is a customer sampling release, tailored exclusively for participants in the nRF54L15 customer sampling program. Do not use this release of nRF Connect SDK if you are not participating in the program.

The release is not part of the regular release cycle and is specifically designed to support early adopters working with the nRF54L15 device. It is intended to provide early access to the latest developments for nRF54L15, enabling participants to experiment with new features and provide feedback.

The scope of this release is intentionally narrow, concentrating solely on the nRF54L15 device. You can use the latest stable release of nRF Connect SDK to work with other boards.

All functionality related to nRF54L15 is considered experimental.

Changelog

The following sections provide detailed lists of changes by component.

Peripherals support

  • Added experimental support for the following peripherals on the nRF54L15 PDK:

    • GPIO

    • SPIM

    • UART

    • TWIM

    • SAADC

    • WDT

    • GRTC

    • QDEC

    • I2S

    • PWM

Working with nRF54L Series

Protocols

This section provides detailed lists of changes by protocol. See Samples for lists of changes for the protocol-related samples.

Amazon Sidewalk

  • Added support for the nRF54L15 PDK in the following configurations:

    • Bluetooth® LE only

    • DFU over Bluetooth LE

Enhanced ShockBurst (ESB)

Applications

This section provides detailed lists of changes by application.

nRF Desktop

  • Added:

    • Support for the nRF54L15 PDK with build targets nrf54l15pdk_nrf54l15_cpuapp and nrf54l15pdk_nrf54l15_cpuapp@0.3.0. The PDK can act as a sample mouse or keyboard. It supports the Bluetooth LE HID data transport and uses SoftDevice Link Layer with Low Latency Packet Mode (LLPM) enabled. The PDK uses MCUboot bootloader built in the direct-xip mode (MCUBOOT+XIP) and supports firmware updates using the Device Firmware Upgrade module.

    • The nrfdesktop-wheel-qdec DT alias support to Wheel module. You must use the alias to specify the QDEC instance used for scroll wheel, if your board supports multiple QDEC instances (for example nrf54l15pdk_nrf54l15_cpuapp). You need not define the alias if your board supports only one QDEC instance, because in that case, the wheel module can rely on the qdec DT label provided by the board.

Samples

This section provides detailed lists of changes by sample.

Bluetooth samples

Cryptography samples

  • Added support for the nRF54L15 PDK in all cryptography samples:

    • Samples Crypto: Persistent key storage and Crypto: PSA TLS support the nRF54L15 PDK with the nrf54l15pdk_nrf54l15_cpuapp build target.

    • All other crypto samples support the nRF54L15 PDK with both nrf54l15pdk_nrf54l15_cpuapp and nrf54l15pdk_nrf54l15_cpuapp_ns build targets.

ESB samples

Matter samples

NFC samples

Peripheral samples

Thread samples

Trusted Firmware-M (TF-M) samples

Other samples

  • Added the CoreMark sample that demonstrates how to measure a performance of the supported SoCs by running the Embedded Microprocessor Benchmark Consortium (EEMBC) CoreMark benchmark. Included support for the nRF54L15 PDK.

Libraries

This section provides detailed lists of changes by library.

Security libraries

MCUboot

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

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

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

  • Added experimental support for MCUboot-based DFU on the nRF54L15 PDK.

Zephyr

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including 0051731a41fa2c9057f360dc9b819e47b2484be5, 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 0051731a41 ^23cf38934c

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

git log --oneline manifest-rev ^0051731a41

The current nRF Connect SDK main branch is based on revision 0051731a41 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.

Zephyr samples

Current nRF54L15 PDK Limitations

General

  • The v0.2.1 revision of the nRF54L15 PDK has Button 3 and Button 4 connected to GPIO port 2 that does not support interrupts. An example of software workaround for this issue is implemented in the DK Buttons and LEDs library. The workaround is enabled by default with the CONFIG_DK_LIBRARY_BUTTON_NO_ISR Kconfig option, but it increases the overall power consumption of the system.

Amazon Sidewalk

  • LoRa/FSK is not supported.

  • After a successful image transfer, the DFU image swap for the Hello World application takes almost 80 seconds.

  • After an auto-connect, the first sent message contains corrupted data. A workaround for this issue is to disable the auto-connect or set up the connection manually before sending the uplink message.

Matter

  • The Device Firmware Update (DFU) is available only for the internal RAM memory space and for the release build configuration.

  • External flash memory is not supported.

  • A crash might occur when the Matter thread and Openthread thread are using PSA API concurrently. Such crash might be observed during the commissioning process to the next Matter fabric when the device is already connected to a Matter fabric.

Thread

  • Link Metrics is not supported.

  • Thread commissioning fails since EC J-PAKE is not supported.

Documentation