Changelog

All the notable changes to this project are documented on this page.

nRF Connect SDK v2.7.99 

Enabled zcbor’s stop_on_error flag before decoding the CBOR payload of an nRF RPC packet. When this flag is set, zcbor stops decoding subsequent data items in the case of decoding failure unless the error is explicitly cleared with the zcbor_pop_error() function.

Fixed an issue where the nrf_rpc_cbor_cmd_rsp() function decodes only the first response element.

All the notable changes added to the nRF Connect SDK v2.2.0 release are documented in this section.

Added the CONFIG_NRF_RPC_ZCBOR_BACKUPS Kconfig option for setting up the number of zcbor backups.

Enabled independent initialization of transport in each group. This makes RPC available for the groups that are ready, even though initialization of others may have failed.

All the notable changes added to the nRF Connect SDK v2.1.0 release are documented in this section.

Added support for multi-instance transport. Each group can use a different transport instance, or groups can share a single transport instance.
Added support for the nRF RPC protocol versioning.

All the notable changes added to the nRF Connect SDK v2.0.0 release are documented in this section.

No changes in this release.

All the notable changes added to the nRF Connect SDK v1.8.0 release are documented in this section.

All the notable changes added to the nRF Connect SDK v1.7.0 release are documented in this section.

All the notable changes added to the nRF Connect SDK v1.6.0 release are documented in this section.

All the notable changes added to the nRF Connect SDK v1.5.0 release are documented in this section.

All the notable changes added to the nRF Connect SDK v1.4.0 release are documented in this section.

Initial release.