| commit | 97afd9235f154105451174da8e097a0730a0167b | [log] [tgz] |
|---|---|---|
| author | jby-nxp <113013617+jby-nxp@users.noreply.github.com> | Thu Oct 17 15:29:18 2024 +0200 |
| committer | GitHub <noreply@github.com> | Thu Oct 17 13:29:18 2024 +0000 |
| tree | 2278a8593c2132a325ccb96b68d2e378733d62ab | |
| parent | 1a38286a552f0b41d9f0147bc73fc9e7fa232c6c [diff] |
NXP : Add support of RT1060 and RT1170 boards (#35842) * [NXP][rt1170] Matter enablement on RT1170 It includes: - Matter port files for RT1170 - example files for Laundry-washer, thermostat and all-cluster-app - documentations Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com> [border router][rt1170] RT1170 platform and README updates to support OTBR with new OT stack version (cherry picked from commit f97d5c58c866774c787ec4417bca075ce45eece0) [platform][rt1170] Enable lwip and ephemeral key CLI addons (cherry picked from commit fb3320eabd3c3f6c8c75c4094d6426fcc0cfed57) [2.16][rt1170] SDK 2.16 rt1170 API name changed Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com> (cherry picked from commit 67f183263466267bc1c7da6fd3a05743fd268ea2) Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com> [examples][rt1170] Enable Disgnostic log for thermostat app Signed-off-by: Martin Girardot <martin.girardot@nxp.com> (cherry picked from commit cce6267446d035e7966c7f5f17d112fb5f1557c5) [platform][rt1170] Rename rt_nvm_component to nxp_nvm_component Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com> (cherry picked from commit f5fb5f4e8b2be45fc97c2a7c7a2d5a453adf9b34) [doc][rt1170] update OTA guidelines to generate mcuboot binary (cherry picked from commit 27f58810a07343234d0d884f385eb407998a9220) * [NXP][rt1060] Adding RT1060 Matter support It includes following changes: - Matter port files for RT1060 - examples support for Laundry-washer, thermostat and all-cluster-app - Support for configurations: RT1060 evkb+8801, RT1060 evkb+IW416, RT1060 evkc+IW612 and RT1060 evkb+k32w0 Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com> [platform][rt1060] Rename rt_nvm_component to nxp_nvm_component Signed-off-by: Dina Benamar <dina.benamarelmaaroufi@nxp.com> (cherry picked from commit 316450da02b365aa61bcb53a0dc6b50512fb6435) [border router][rt1060] RT1060 platform and README updates to support OTBR with new OT stack version (cherry picked from commit 231a4c15c4abca40d5759194fb61b9636c8f67e8) [platform][rt1060] Enable lwip and ephemeral key CLI addons (cherry picked from commit 463749a12abcc68fc5f6569f98c27b574b3516bd) [2.16][rt1060] SDK 2.16 rt1060 API name changed Signed-off-by: Gatien Chapon <gatien.chapon@nxp.com> (cherry picked from commit 42f7d8771329172aaeedfde1b2bab86b1799f6d9) [examples][rt1060] Enable Diagnostic log for thermostat app Signed-off-by: Martin Girardot <martin.girardot@nxp.com> (cherry picked from commit 7c4cbeb41d3a00ec90525bb084f7bc278d5ecb8e) * [NXP][rt1060][doc] Update WiFi build instructions * [NXP][border router][rt1060] Platform updates to support TBR cluster and secondary nwk if A new gn variable was created, chip_enable_secondary_nwk_if, to enable or disable Thread as secondary network commissioning interface when building with BR support. * [NXP][border router][rt1170] Platform updates to support TBR cluster and secondary nwk if A new gn variable was created, chip_enable_secondary_nwk_if, to enable or disable Thread as secondary network commissioning interface when building with BR support. * [NXP] Add targets RT1060 and RT1170 to NXP builds * [NXP][OTA][doc] update OTA doc for RTs boards * [NXP][border router][rt1060] fix compilation issue * [NXP][border router][rt1170] fix compilation issue * [NXP][doc][rt1060] minor changes * [NXP] [rt1060] OTA requestor enablement on RT1060-EVKC+Firecrest * [NXP] Add OTA variant to RT1060 and RT1170 builds * [NXP][doc][rt] changes since workflow feedback * [NXP][examples][rt1060] Update empty button registration path Signed-off-by: marius-alex-tache <marius.tache@nxp.com> * [NXP][examples][rt1170] Update empty button registration path Signed-off-by: marius-alex-tache <marius.tache@nxp.com> * [NXP] [gn] Restyle gn files * [NXP][doc] Restyle md files * [NXP] Restyle build scripts * [NXP][RT] fix OTBR compile issue * [NXP][RT][doc] rework documentation * [NXP] Reduce and collapse NXP targets list * [NXP] filter which target to be build on PR * [NXP] [rt1170] remove useless flag * [NXP] [rt1060] remove useless flag * [NXP] [doc] fix path to referenced docs since NXP documentation moved --------- Signed-off-by: marius-alex-tache <marius.tache@nxp.com> Co-authored-by: Gatien Chapon <gatien.chapon@nxp.com> Co-authored-by: Mihai Ignat <mihai.ignat@nxp.com> Co-authored-by: Marius Preda <marius.preda@nxp.com> Co-authored-by: marius-alex-tache <marius.tache@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.
