Changelog for nRF Connect SDK v2.0.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.0.0 for the list of issues valid for the latest release.

Changelog

The following sections provide detailed lists of changes by component.

Application development

Protocols

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

Bluetooth mesh

No changes since the latest nRF Connect SDK release.

See Bluetooth mesh samples for the list of changes for the Bluetooth mesh samples.

Matter

  • Removed the low-power configuration build type from all Matter samples.

See Matter samples for the list of changes for the Matter samples.

Matter fork

The Matter fork in the nRF Connect SDK (sdk-connectedhomeip) contains all commits from the upstream Matter repository up to, and including, 25e241ebcbf11b1f63dbe25546b1f10219866ad0.

The following list summarizes the most important changes inherited from the upstream Matter:

No changes since the latest nRF Connect SDK release.

Thread

  • Added information about Synchronized Sleepy End Device (SSED) and SED vs SSED activity in the Device types documentation.

  • Multiprotocol support was removed from overlay-cert.config and moved to overlay-multiprotocol.conf.

See Thread samples for the list of changes for the Thread samples.

Zigbee

  • Updated:

    • Enabled the PAN ID conflict resolution in applications that uses Zigbee application utilities library. For details, see Libraries for Zigbee.

    • Changed the default entropy source of Zigbee samples and unit tests to Cryptocell for SoCs that have Cryptocell.

See Zigbee samples for the list of changes for the Zigbee samples.

ESB

  • Fixed the update_radio_crc() function in order to correctly configure the CRC’s registers (8 bits, 16 bits, or none).

RF Front-End Modules

  • Fixed a build error that occurred when building an application for nRF53 SoCs with Simple GPIO Front-End Module support enabled.

Applications

This section provides detailed lists of changes by application.

nRF9160: Asset Tracker v2

  • Removed:

    • CONFIG_APP_REQUEST_GNSS_ON_INITIAL_SAMPLING option.

    • CONFIG_APP_REQUEST_NEIGHBOR_CELLS_DATA option.

  • Updated:

  • Fixed:

    • An issue that reports GNSS altitude, accuracy, and speed incorrectly when using LwM2M engine.

    • An issue that caused modem FOTA jobs to be reported as not validated to nRF Cloud.

nRF9160: Serial LTE modem

  • Updated:

    • AT response and the URC sent when the application enters and exits data mode.

  • Added:

    • URC for GNSS sleep and wakeup events.

    • Selected flags support in #XRECV and #XRECVFROM commands.

    • Multi-PDN support in the Socket service.

nRF5340 Audio

nRF Machine Learning (Edge Impulse)

No changes since the latest nRF Connect SDK release.

nRF Desktop

  • nRF Desktop peripherals no longer automatically send security request immediately after Bluetooth LE connection is established. The feature can be turned on using CONFIG_CAF_BLE_STATE_SECURITY_REQ.

  • nRF Desktop dongles start peripheral discovery immediately after Bluetooth LE connection is established. The dongles no longer wait until the connection is secured.

No changes since the latest nRF Connect SDK release.

Thingy:53 Zigbee weather station

No changes since the latest nRF Connect SDK release.

Samples

This section provides detailed lists of changes by sample, including protocol-related samples. For lists of protocol-specific changes, see Protocols.

Bluetooth samples

Bluetooth mesh samples

No changes since the latest nRF Connect SDK release.

nRF9160 samples

  • Added nRF9160: Modem trace backend sample, demonstrating how to add a custom modem trace backend. The custom backend prints the amount of trace data received in bytes, trace data throughput, and CPU load.

  • nRF9160: LwM2M Client sample:

    • Fixed:

      • Default configuration conforms to the LwM2M specification v1.0 instead of v1.1. For enabling v1.1 there is already an overlay file.

      • Bootstrap is not TLV only anymore. With v1.1, preferred content format is sent in the bootstrap request. SenML CBOR takes precedence over SenML JSON and OMA TLV, when enabled.

    • Added:

      • CoAP max message size is set to 1280 by default.

      • Number of SenML CBOR records is set to a higher value to cope with data exchange after registration with Coiote server.

  • nRF9160: Modem Shell sample:

    • Added:

      • nRF9160 DK overlays for enabling BT support. When running this configuration, you can perform BT scanning and advertising using the bt command.

      • Support for injecting GNSS reference altitude for low accuracy mode. For a position fix using only three satellites, GNSS module must have a reference altitude that can now be injected using the gnss agps ref_altitude command.

Thread samples

No changes since the latest nRF Connect SDK release.

Matter samples

NFC samples

No changes since the latest nRF Connect SDK release.

nRF5340 samples

No changes since the latest nRF Connect SDK release.

Gazell samples

No changes since the latest nRF Connect SDK release.

Zigbee samples

  • Zigbee: Light switch sample:

    • Fixed an issue where a buffer would not be freed after a failure occurred when sending a Match Descriptor request.

Other samples

No changes since the latest nRF Connect SDK release.

Drivers

This section provides detailed lists of changes by driver.

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

Bootloader libraries

No changes since the latest nRF Connect SDK release.

Modem libraries

Libraries for networking

  • Updated:

    • nRF Cloud library:

      • Fixed:

        • An issue that caused the application to receive multiple disconnect events.

      • Added:

        • nrf_cloud_fota_pending_job_validate() function that enables an application to validate a pending FOTA job before initializing the nRF Cloud library.

        • Handling for new nRF Cloud REST error code 40499. Moved the error log from the nrf_cloud_parse_rest_error() function into the calling function.

Libraries for NFC

No changes since the latest nRF Connect SDK release.

Other libraries

Common Application Framework (CAF)

No changes since the latest nRF Connect SDK release.

Shell libraries

No changes since the latest nRF Connect SDK release.

Libraries for Zigbee

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.

Unity

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 e86f575f68fdac2cab1898e0a893c8c6d8fd0fa1, plus 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 53fbf40227de087423620822feedde6c98f3d631, plus 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 53fbf40227 ^45ef0d2

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

git log --oneline manifest-rev ^53fbf40227

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

zcbor

The zcbor module has been updated from version 0.3.0 to 0.4.0. Release notes for 0.4.0 can be found in ncs/nrf/modules/lib/zcbor/RELEASE_NOTES.md.

The following major changes have been implemented:

  • No changes since the latest nRF Connect SDK release.

Trusted Firmware-M

  • Fixed:

    • No changes since the latest nRF Connect SDK release.

cJSON

  • No changes since the latest nRF Connect SDK release.

Documentation