Ncs 3.1.0 update (#41205) * [nrfconnect] Pulled patches from downstream fork Pulled bulk of commits including patches for nrfconnect platform present in downstream Nordic's fork. The list of pulled commits is the following: * [nrfconnect] Introduced Kconfigs to configure few params Introduced new Kconfig options to be able to configure the parameters related to persistent subscriptions re-establishment. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no> * Disable `chip_build_tools` for Zephyr Disable `chip_build_tools` when building for Zephyr as it enables `chip_with_nlfaultinjection` and increases RAM and FLASH usage. Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no> * [nrfconnect] Implement KMUKeyAllocator KMUKeyAllocator is used to overwrite PSAKeyAllocator for the specific use-cases of KMU driver. This feature is available only on the device which run Cracen. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no> * Add kconfig for Bootloader selection The new configs set bootloader implementation and select/imply all configs required by mcumgr and dfu_target. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no> * [nrfconnect] Don't select BOOTLOADER_MCUBOOT for nRF52840 Dongle Don't use `CHIP_BOOTLOADER_MCUBOOT` for dongle. Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no> * [nrfconnect] Reconfigure memory pool sizes With introduction of dedicated memory pools for nRF70 Wi-Fi driver, redistribute current heap size among the driver heap and kernel heap. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no> * Replace ReturnErrorCodeIf with VerifyOrReturnError Aligned to the Upstream change. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no> * [nrfconnect] Use default ICD poll intervals in tests Use default intervals to keep compatibility with tests. Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no> * [nrfconnect] Add Data Model target Add matter-data-model target for Data Model. Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no> * [nrfconnect] Replace POSIX_MAX_FDS with ZVFS_OPEN_MAX Replace deprecated Kconfig. Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no> * [nrfconnect] Remove config CHIP_OPENTHREAD_JOINER_ENABLED Remove CHIP_OPENTHREAD_JOINER_ENABLED Kconfig as it's no longer used. Signed-off-by: Adrian Gielniewski <adrian.gielniewski@nordicsemi.no> * Disable BLE SMP buffer scaling on nRF54L10 Disable automatic increase of the Bluetooth SMP MTU and RX buffers on the nRF54L10 SoC. Signed-off-by: Łukasz Duda <lukasz.duda@nordicsemi.no> * [nrfconnect] Added PSA_WANT_KEY_TYPE_SPAKE2P_KEY_PAIR_IMPORT Imply PSA_WANT_KEY_TYPE_SPAKE2P_KEY_PAIR_IMPORT when OBERON is used. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no> * [nrfconnect] Enable ACL Extensions for nRF Connect platform Re-enabled CHIP_CONFIG_ENABLE_ACL_EXTENSIONS for nRF Connect platform, because it was globally disabled. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no> * Replaced dependency for CHIP_USE_OPENTHREAD_ENDPOINT The CHIP_USE_OPENTHREAD_ENDPOINT depends on CHIP_WIFI, which is invalid, because this Kconfig is sourced from Kconfig.features. Replaced CHIP_WIFI with WIFI. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * Replaced deprecated openthread Zephyr mutex API Replaced deprecated openthread_api_mutex methods with a new openthread_mutex API. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * Added additional networking checks for memory profiling CHIP_MEMORY_PROFILING Kconfig selects several NET_ components that should not be selected if NETWORKING is not used. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [nrfconnect] Fixed Kconfig name for 7001 board Replaced obsolete BOARD_NRF7002DK_NRF7001_NRF5340_CPUAPP name with BOARD_NRF7002DK_NRF5340_CPUAPP_NRF7001 Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [nrfconnect] Remove redundant multithreding config in mcuboot Remove multithreading configuration from mcuboot where it is not needed. SPI/QSPI drivers do not require multithreading support anymore. Signed-off-by: Michal Kozikowski <michal.kozikowski@nordicsemi.no> * [nrfconnect] Changed the default ICD config values Changed values of a few ICD configs to optimize the devices behavior. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [nrfconnect] Fixed factory data cert generation Paths for the certificates are passed to factory data python script directly, and if the path contains cmake macro it is not expanded properly. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [nrfconnect] Align with Zephyr net_mgmt API changes The net_mgmt event representation changed from 32-bit to 64-bit value, therefore align with this change. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no> * Increased packet buffer pool size Increased default packet buffer pool size, as it was decreased some time ago and we can observe lack of available buffers in the load tests. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [zephyr] Changed Zephyr minor version in BLE Mgr check The check in BLEManagerImpl depending on Zephyr kernel minor version is not correct, as the code under check was present even before that. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [nrfconnect] Updated recommended NCS version to 3.1.0 Updated recommended version of nRF Connect SDK to 3.1.0. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [.github] Updated docker image version used in workflows Updated docker image number used in github workflows. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [nrfconnect] Disabled NFC for nRF52840 dongle Disable NFC for nRF52840 dongle to fix build error. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [nrfconnect] Disabled mcuboot for few apps to fix build Disabled mcuboot for few examples that does not support DFU. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * Restyled by clang-format * Restyled by gn * Fixed typos detected during gemini bot review Fixed typos in several comments. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> * [zephyr] Fixed zephyr versions used in platform checks Added a separate zephyr version check for nrfconnect target as unfortunately it was released with Zephyr 4.1.99 version, so it does not work with 4.1 and 4.2 checks. Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> --------- Signed-off-by: Kamil Kasperczyk <kamil.kasperczyk@nordicsemi.no> Co-authored-by: Restyled.io <commits@restyled.io>
Builds
Tests
Tools
Documentation
Matter (formerly Project CHIP) creates more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance.
Matter is a unified, open-source application-layer connectivity standard built to enable developers and device manufacturers to connect and build reliable, and secure ecosystems and increase compatibility among connected home devices. It is built with market-proven technologies using Internet Protocol (IP) and is compatible with Thread and Wi-Fi network transports. Matter was developed by a Working Group within the Connectivity Standards Alliance (Alliance). This Working Group develops and promotes the adoption of the Matter standard, a royalty-free connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet. The vision that led major industry players to come together to build Matter is that smart connectivity should be simple, reliable, and interoperable.
Matter simplifies development for manufacturers and increases compatibility for consumers.
The standard was built around a shared belief that smart home devices should be secure, reliable, and seamless to use. By building upon Internet Protocol (IP), Matter enables communication across smart home devices, mobile apps, and cloud services and defines a specific set of IP-based networking technologies for device certification.
The Matter specification details everything necessary to implement a Matter application and transport layer stack. It is intended to be used by implementers as a complete specification.
The Alliance officially opened the Matter Working Group on January 17, 2020, and the specification is available for adoption now.
Visit buildwithmatter.com to learn more and read the latest news and updates about the project.
Matter is developed with the following goals and principles in mind:
Unifying: Matter is built with and on top of market-tested, existing technologies.
Interoperable: The specification permits communication between any Matter-certified device, subject to users’ permission.
Secure: The specification leverages modern security practices and protocols.
User Control: The end user controls authorization for interaction with devices.
Federated: No single entity serves as a throttle or a single point of failure for root of trust.
Robust: The set of protocols specifies a complete lifecycle of a device — starting with the seamless out-of-box experience, through operational protocols, to device and system management specifications required for proper function in the presence of change.
Low Overhead: The protocols are practically implementable on low compute-resource devices, such as MCUs.
Pervasive: The protocols are broadly deployable and accessible, by leveraging IP and being implementable on low-capability devices.
Ecosystem-Flexible: The protocol is flexible enough to accommodate deployment in ecosystems with differing policies.
Easy to Use: The protocol provides smooth, cohesive, integrated provisioning and out-of-box experience.
Open: The Project’s design and technical processes are open and transparent to the general public, including non-members wherever possible.
Matter aims to build a universal IPv6-based communication protocol for smart home devices. The protocol defines the application layer that will be deployed on devices and the different link layers to help maintain interoperability. The following diagram illustrates the normal operational mode of the stack: 
The architecture is divided into layers to help separate the different responsibilities and introduce a good level of encapsulation among the various pieces of the protocol stack. The vast majority of interactions flow through the stack captured in the following Figure:
Security: An encoded action frame is then sent down to the Security Layer to encrypt and sign the payload to ensure that data is secured and authenticated by both sender and receiver of a packet.
Message Framing & Routing: With an interaction encrypted and signed, the Message Layer constructs the payload format with required and optional header fields; which specify the message's properties and some routing information.
Matter’s design and technical processes are intended to be open and transparent to the general public, including to Working Group non-members wherever possible. The availability of this GitHub repository and its source code under an Apache v2 license is an important and demonstrable step to achieving this commitment. Matter endeavors to bring together the best aspects of market-tested technologies and redeploy them as a unified and cohesive whole-system solution. The overall goal of this approach is to bring the benefits of Matter to consumers and manufacturers as quickly as possible. As a result, what you observe in this repository is an implementation-first approach to the technical specification, vetting integrations in practice. The Matter repository is growing and evolving to implement the overall architecture. The repository currently contains the security foundations, message framing and dispatch, and an implementation of the interaction model and data model. The code examples show simple interactions, and are supported on multiple transports -- Wi-Fi and Thread -- starting with resource-constrained (i.e., memory, processing) silicon platforms to help ensure Matter’s scalability.
We welcome your contributions to Matter. Read our contribution guidelines here.
Instructions about how to build Matter can be found here .
The Matter repository is structured as follows:
| File/Folder | Content |
|---|---|
| build | Build system support content and built output directories |
| build_overrides | Build system parameter customization for different platforms |
| config | Project configurations |
| credentials | Development and test credentials |
| docs | Documentation, including guides. Visit the Matter SDK documentation page to read it. |
| examples | Example firmware applications that demonstrate use of Matter |
| integrations | 3rd party integrations |
| scripts | Scripts needed to work with the Matter repository |
| src | Implementation of Matter |
| third_party | 3rd party code used by Matter |
| zzz_generated | ZAP generated template code - Revolving around cluster information |
| BUILD.gn | Build file for the GN build system |
| CODE_OF_CONDUCT.md | Code of conduct for Matter and contribution to it |
| CONTRIBUTING.md | Guidelines for contributing to Matter |
| LICENSE | Matter license file |
| REVIEWERS.md | PR reviewers |
| gn_build.sh | Build script for specific projects such as Android, EFR32, etc. |
| README.md | This file |
Matter is released under the Apache 2.0 license.
