nRF Connect SDK v2.7.99-cs1 Release Notes

nRF Connect SDK v2.7.99-cs1 is a customer sampling release, tailored exclusively for participants in the nRF54H20 SoC 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 nRF54H20 SoC. It is intended to provide early access to the latest developments for nRF54H20 SoC, enabling participants to experiment with new features and provide feedback.

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

All functionality related to nRF54H20 SoC is considered experimental.

Highlights

Added the following features as experimental:

  • Power management with support for System On All Idle power state.

  • Clock control API.

  • New peripheral driver SAADC.

Release tag

The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v2.7.99-cs1. Check the west.yml file for the corresponding tags in the project repositories.

To use this release, check out the tag in the manifest repository and run west update. See Get the nRF Connect SDK code and Updating the repositories for more information.

For information on the included repositories and revisions, see Repositories and revisions for v2.7.99-cs1.

IDE and tool support

nRF Connect extension for Visual Studio Code is the recommended IDE for nRF Connect SDK v2.7.99-cs1. See the Installation section for more information about supported operating systems and toolchain.

Note

Because of the significant, potentially breaking changes introduced in the nRF Connect SDK v2.7.0, the support for v2.7.99-cs1 in the nRF Connect for VS Code extension is experimental in the following areas:

  • sysbuild - During the extension stabilization period, manually edit and verify Kconfig option values instead of using the nRF Kconfig GUI.

  • Hardware Model v2 - During the extension stabilization period, edit devicetree files manually instead of using the Devicetree Visual Editor. Moreover, custom boards added in the extension will follow the Zephyr’s Hardware Model v1.

The extension users that need v2.7.99-cs1 should switch to the pre-release version of the extension.

Migration notes

See the Migration notes for nRF Connect SDK v2.7.99-cs1 and the nRF54H20 DK for the changes required or recommended when migrating your environment to the nRF Connect SDK v2.7.99-cs1.

Changelog

The following sections provide detailed lists of changes by component.

Zephyr

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including 28b6861211d2d9f54411ff60357a42d84a253600, 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 28b6861211 ^25e90e7bb0

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

git log --oneline manifest-rev ^28b6861211

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

Documentation