Google Git
Sign in
pigweed / third_party / github / project-chip / connectedhomeip / 23644a530437cbaed95411afa51fcfa66fb6cb78
commit23644a530437cbaed95411afa51fcfa66fb6cb78[log] [tgz]
authorRohan Sahay <Rohan.Sahay@silabs.com>Fri Jun 23 07:43:33 2023 +0530
committerGitHub <noreply@github.com>Fri Jun 23 02:13:33 2023 +0000
treee12659025b199a0838f91d6d1de226246cf326bf
parent21cb7a3996751fbd8fbf2c4c3aecd5f750e2b703 [diff]
[Silabs] Adds SPI multiplex changes for rs911x (#26238)

* SPI multiplex changes for rs911x

* Adds intermediate changes with cleanup

* Adds additional macro checks

* Adds updated working logic for multiplexing expansion header and LCD

* Adds missing ;

* Adds fix for WF200 baudrate on SPI

* Adds fix for third_party

* Adds updated log statements

* Adds fix for log statement

* Adds conditional use of semaphore

* Adds conditional EFR32MG24 semaphore logic

* Adds fix for err usage

* Refactor SPIDRV_ReInit

* Adds SPIDRV_ReInit for EUSART

* Added error logs

* Added logs

* Revert submodule update

* Aligned the macros

* Restyled

* Aligned the MACRO

* Adds cosmetic changes

* Removes debug log

* Adds sl_wfx_host_post_bootloader_spi_transfer in relevant failure outcomes

* Adds re factored local function updateDisplay(void)

* Removes spi_multiplex.c

* Removes development debug trace and log

* Renamed conflicting variable

* Adds comment for technical debt and understanding

* Adds changes for updateDisplay function

* Adds checks for semaphore used for sync peripherals

* Clean up of unreachable code due to portMAX_DELAY

* Adds fix for comment alignment

* Changes SPIDRV_ReInit to SPIDRV_SetBaudrate

* Removes unused error variable

* Clean up logs

* Clean up of logs

* Replace magic number

* Added tickets for tracking additional rework

* Clean up additional logs

* Adds fix for print statements

* Adds fix for MACRO

* Adds fix for MATTER-1904

* Adds partial fix for MATTER-1907

* Adds for fix code compilation

* Adds code to clean up MACROs

* Restyled by clang-format

* Removes debug log

* Adds fix for MATTER-1907

* Adds use of the ECODE_EMDRV_SPIDRV status instead of generic ECODE

* Adds comment for declaring the current supported family.

---------

Co-authored-by: shasaicha <shsaicha@silabs.com>
Co-authored-by: Restyled.io <commits@restyled.io>
11 files changed
tree: e12659025b199a0838f91d6d1de226246cf326bf
  1. .devcontainer/
  2. .githooks/
  3. .github/
  4. .vscode/
  5. build/
  6. build_overrides/
  7. config/
  8. credentials/
  9. docs/
  10. examples/
  11. integrations/
  12. scripts/
  13. src/
  14. third_party/
  15. zzz_generated/
  16. .clang-format
  17. .clang-tidy
  18. .default-version.min
  19. .dir-locals.el
  20. .editorconfig
  21. .flake8
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .gn
  26. .isort.cfg
  27. .mergify.yml
  28. .prettierrc.json
  29. .pullapprove.yml
  30. .restyled.yaml
  31. .shellcheck_tree
  32. .spellcheck.yml
  33. BUILD.gn
  34. CODE_OF_CONDUCT.md
  35. CONTRIBUTING.md
  36. gn_build.sh
  37. lgtm.yml
  38. LICENSE
  39. NOTICE
  40. README.md
  41. REVIEWERS.md
README.md

Matter

Builds

Builds

Android Ameba ASR BouffaloLab Darwin TI CC26X2X7 TI CC32XX EFR32 ESP32 Infineon i.MX Linux K32W with SE051 Linux ARM Linux Standalone Linux Standalone Mbed OS MW320 nRF Connect SDK Open IoT SDK QPG Telink Tizen

Tests

Unit / Integration Tests Cirque QEMU

Tools

ZAP Templates

Documentation

Documentation Build

About

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.

What is Matter?

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.

Project Overview

Development Goals

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.

Architecture Overview

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: Matter Architecture Overview

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:

Matter Stack Architecture

  1. Application: High-order business logic of a device. For example, an application that is focused on lighting might contain logic to handle turning on/off the bulb as well as its color characteristics.
  1. Data Model: The data layer corresponds to the data and verb elements that help support the functionality of the application. The Application operates on these data structures when there is an intent to interact with the device.
  1. Interaction Model: The Interaction Model layer defines a set of interactions that can be performed between a client and server device. For example, reading or writing attributes on a server device would correspond to application behavior on the device. These interactions operate on the elements defined at the data model layer.
  1. Action Framing: Once an action is constructed using the Interaction Model, it is serialized into a prescribed packed binary format to encode for network transmission.

  1. 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.

  2. 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.

  1. IP Framing & Transport Management: After the final payload has been constructed, it is sent to the underlying transport protocol for IP management of the data.

Current Status of Matter

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.

How to Contribute

We welcome your contributions to Matter. Read our contribution guidelines here.

Building and Developing in Matter

Instructions about how to build Matter can be found here .

Directory Structure

The Matter repository is structured as follows:

File/FolderContent
buildBuild system support content and built output directories
build_overridesBuild system parameter customization for different platforms
configProject configurations
credentialsDevelopment and test credentials
docsDocumentation, including guides. Visit the Matter SDK documentation page to read it.
examplesExample firmware applications that demonstrate use of Matter
integrations3rd Party integrations
scriptsScripts needed to work with the Matter repository
srcImplementation of Matter
third_party3rd party code used by Matter
zzz_generatedzap generated template code - Revolving around cluster information
BUILD.gnBuild file for the gn build system
CODE_OF_CONDUCT.mdCode of conduct for Matter and contribution to it
CONTRIBUTING.mdGuidelines for contributing to Matter
LICENSEMatter license file
REVIEWERS.mdPR reviewers
gn_build.shBuild script for specific projects such as Android, EFR32, etc.
README.mdThis File

License

Matter is released under the Apache 2.0 license.