| commit | 9c5af692ec02881cecd5e674a99025ed3ac3a054 | [log] [tgz] |
|---|---|---|
| author | dinabenamar <108664279+dinabenamar@users.noreply.github.com> | Thu Apr 17 18:28:03 2025 +0200 |
| committer | GitHub <noreply@github.com> | Thu Apr 17 16:28:03 2025 +0000 |
| tree | 9f013bbe6d8708abcb737eb0b79689fe1d33d608 | |
| parent | 88bff3127bc9dd391862b7496fde09ce8ac597a3 [diff] |
[NXP] Updates in NXP platform files and switch to SDK 25.03.00 (#38431)
* [NXP][platform][rw61x] Small reworks to support building Matter-over-Thread with cmake as part of the "chip" module
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[rw61x] use wifi osa to register idle function in MoT as well
Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com>
* [NXP][platform][rt1170] Small reworks to support building Matter-over-Thread with cmake as part of the "chip" module
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][rt1170] Switching spinel GN options to nxp prefix
Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com>
[rt1170] Enabling session resumption which is now supported
Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com>
[rt1170] use wifi osa to register idle function in MoT as well
* [NXP][platform][rt1060] Small reworks to support building Matter-over-Thread with cmake as part of the "chip" module
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][rt1060] Switching spinel GN options to nxp prefix
Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com>
[rt1060] use wifi osa to register idle function in MoT as well
* [NXP][platform][common] Updating NXP platform code to support cmake build
Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com>
[platform][common] Updating legacy factory data file to support cmake build
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][common] refactor icd configs
Signed-off-by: Doru Gucea <doru-cristian.gucea@nxp.com>
[platform][common][ble] Remove BLE Host Task functions/queues and use SDK ones
Signed-off-by: Andrei Menzopol <andrei.menzopol@nxp.com>
[platform][common] Update include in src/platform/nxp/common/factory_data/legacy/FactoryDataProvider.cpp to use public header
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][common] Adding missing CHIP configs to be set with Kconfig values
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][common] Make sure to check if CHIP_DEVICE_CONFIG_ENABLE_SED is defined
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][common] Use "ifdef" around Kconfig that may not be defined for all platforms
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][platform][mcxw71_k32w1] Updates and reworks in platform files for CMake build support and improvements
[platform][mcxw71_k32w1] Reworks to use CHIP config and app config generation with Kconfig
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][mcxw71_k32w1] Adding compile options to compile MoT with cmake
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][mcxw71_k32w1] Moving factory data source files to be added within the platform target
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][mcxw71] refactor icd configs
Signed-off-by: Doru Gucea <doru-cristian.gucea@nxp.com>
[platform][mcxw71_k32w1] Remove BLE Host Task function declarations
* Functions from SDK will be used instead.
Signed-off-by: Andrei Menzopol <andrei.menzopol@nxp.com>
[platform][mcxw71_k32w1] Adding dependency on "src/credentials:credentials_header" which is required to build factory data files
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][mcxw71_k32w1] Moving some CHIP configs under CHIPDevicePlatformConfig.h to replace CHIPProjectConfig.h with Kconfig generation
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][mcxw71_k32w1] Set CHIP_CONFIG_MAX_FABRICS to 5
Signed-off-by: Andrei Menzopol <andrei.menzopol@nxp.com>
[platform][mcxw71_k32w1] Add ifndef around CHIP_DEVICE_CONFIG_KVS_WEAR_STATS to make sure it's not redefined
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[platform][mcxw71_k32w1] Add ifndef condition to avoid redefinition of CHIP macros
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][platform][k32w0] refactor icd configs
Signed-off-by: Doru Gucea <doru-cristian.gucea@nxp.com>
* [NXP][examples][common] Updating NXP example code to support cmake build
Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com>
[examples][common] Updates in examples files to align with CMake reworks
[examples][common] Updating contact-sensor-app and lighting-app applications by adding "vApplicationStackOverflowHook" to the main.cpp
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[examples][common] Moving BleZephyrManagerApp.cpp from thermostat folder to be common under "examples/platform/nxp/common"
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][examples][rt1060] Updates in examples files to align with CMake reworks
[examples][rt1060] keep empty implementation for button
[examples][rt1060] Update path to BleZephyrManagerApp.cpp in GN file
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][examples][rt1170] Update path to BleZephyrManagerApp.cpp in GN file
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][examples][rw61x] Update path to BleZephyrManagerApp.cpp in GN file
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][examples][mcxw71_k32w1] Moving factory data source files to be added within the platform target
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
[examples][mcxw71_k32w1] Updating platform AppFactoryDataExample.cpp to support building with cmake
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][examples][zephyr] Update thermostat CMakeLists.txt with the new path of BleZephyrManagerApp.cpp
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][examples][rt1060][ota] fix flash size for RT1060-EVKC on gn build
* [NXP][platform][rt1060] Remove include fsl_adapter_rng.h which is not necessary
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][platform][rw61x] Remove include fsl_adapter_rng.h which is not necessary
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP][rt1060][cmake][FileSystem] switch to NVS FileSystem
* [NXP][rt1170][cmake][FileSystem] switch to NVS FileSystem
* [NXP] Update copyrights year date
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP] Update nxp_matter_support submodule
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP] Update docker image version to use for building NXP examples
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* [NXP] Update platform BUILD.gn to align with latest updates
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
* Restyled by whitespace
* Restyled by gn
---------
Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com>
Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com>
Signed-off-by: Doru Gucea <doru-cristian.gucea@nxp.com>
Co-authored-by: Doru Gucea <doru-cristian.gucea@nxp.com>
Co-authored-by: Gatien Chapon <gatien.chapon@nxp.com>
Co-authored-by: Jaafar BEN YOUNES <jaafar.benyounes@nxp.com>
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.