| commit | d35648481cd08a64a7a85e97c99baddb3537a9e3 | [log] [tgz] |
|---|---|---|
| author | Andrei Litvin <andy314@gmail.com> | Fri Jun 23 12:30:50 2023 -0400 |
| committer | GitHub <noreply@github.com> | Fri Jun 23 16:30:50 2023 +0000 |
| tree | 46257116469eae95f8aa08a5ed5398b0f94d5b07 | |
| parent | 3cdd5ee16a8f712496ee81d6902a6e302acf6644 [diff] |
Add a perfetto backend for tracing and enable it for chip-tool & light-app on linux (#27354) * Create varargs macros for tracing, including tests * Add matter trace scope macros * Add missing semicolon * Add labels to trace end * Restyled by whitespace * Restyled by clang-format * Restyled by gn * Add perfetto v35.0 as a submodule for linux and android * Start adding a perfetto backend * Enable perfetto and switch chip-tool C++ standard to 17 as we never compile it for embedded using other compilers * make library compile and link * GN format * Add a track event register, since this is what seems to be needed according to SDK guides * Add open/close support * Use a buildconfig header for tracing configuration * Fix missing include * Restyled by gn * Add a file path to perfetto command line argument tracing * Add a file path to perfetto command line argument tracing * Fix start/stop to setup tracing * Some minor reshuffling ... tracing not yet outputted * Tracing to file works now * Better tracing for dnssd stuff * better tracing * Better tracing logic - only enable perfetto tracing for chiptool * Minor update * more tracing ... shows active commissioning delegate calls are SLOOOW * Remove old MATTER_TRACE_EVENT_SCOPE * Remove trace.h include * Remove src/trace dependency * Minor change to kick re-builds * Restyled by clang-format * Restyled by gn * Restyled by prettier-markdown * Use a config variable to enable choice of perfetto enabling in tracing * Restyle * Fix logic for tracing enabling to use current_os instead of target os * Disable tracing by default, since building on linux or not is not sufficient ... many platforms build on linux * remove chip_build_pw_trace_lib flag * Switch linux default C++ standard to 17, to generally support perfetto everywhere * Restyle * Disable include check based since it is ifdef-guarded * Make perfetto and tokenization words in our wordlist * enable tracing on all linux apps by default and make perfetto the default linux backend * Restyle * Make only chip-tool use tracing for now - tracing backends require explicit configuration * Restyle * Use public header as a source set for macros_impl.h * Remove multiplexed trace begin/end/instant from perfetto_tracing since review comment was that this is a footgun * Multiplexed tracing is not thread safe. Assert lock held in all tracing locations * Revert "Multiplexed tracing is not thread safe. Assert lock held in all tracing locations" This reverts commit fd012030fffe354d4069f3092616845ede4a2548. * Add thread safety documentation * Allow shadow errors for perfetto compilation * Remove old tracing calls from jni code * Make esp32 compile with pw_rpc * Set perfetto to only apply to linux and android for now * Set perfetto to linux only after all ... once we have android build rules we can update * Undo cmakelist reformat * Undo pragmas warning disabled, use just void for now to make both gcc and clang happy * Restyle * make only chip-tool use C++17, since it is the only tracing/perfetto-enabled build * More update of defaults to make perfetto compile only for chip-tool for now * more changes to make the c++ version checks more generic * Restyle * more documentation * Restyle * Make file name be quoted * Fix typo * Enable trace support in generic linux examples, and explicitly enable it in the lighting app * Perfetto has its own scope method. use that instead of the custom implemented class for multiplexing * Use a buildconfig header for tracing command line arguments * Restyle * Restyle * Add nogncheck for ifdef-guarded file * Remove include path check for ifdef-guarded include * Split out perfetto initialization and file output logic, to allow inclusion separation * Ensure perfetto file output is closed at exit * Ensure TrackEvent registration is done * Another split, to ensure event storage is registered properly * Restyled by clang-format * Restyled by gn * Restyled by prettier-markdown * Fix conditional for perfetto tracing * Make tracing for android default-enabled * Restyled by clang-format * Restyled by gn * add perfetto repo for android * Debug odd load path failure for java codegen * Remove bootstrap cache for testing smoketest * Revert "Debug odd load path failure for java codegen" This reverts commit 13ec3ebba6690529f1f4007c77af28df7f79ab9c. * Revert "Remove bootstrap cache for testing smoketest" This reverts commit 3cfb7e48e655e734de6b3394d15fb8fc682f6660. * Force bootstrap cache refresh, because buggy cache * Switch to if instead of ifdef * Restyled by gn * Remove usage of vectors, turn more ifdefs into ifs * Fix removal of registered backends * Place the in list check in the register to avoid some code uglyness/duplication * Move the inlist check back to the registry, to have even smaller code changes * Fix logic errors regarding defined * Fix conditional for ifndef * Move trace setup to a class * Correct another ifdef * Fix a few more if/ifdef mismatches * Undo unintentional repo change * Restyled by clang-format * update dependency logic to use explicit targets for each of the none/multiplexed/perfetto * Add missing files * Fix paths and comments * Restyle * Remove invalid deps on perfetto from none and multiplexed * Bump up build time for python setup payload test because large build --------- Co-authored-by: Restyled.io <commits@restyled.io> Co-authored-by: Andrei Litvin <andreilitvin@google.com>
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.