[Telink] Zephyr 3.3 & 3.7 support (#37582) * [Telink] Zephyr v3.7 update changes Adopted changes for Telink B9x board series for upcoming update of Zephyr version. Fixed err output from InitChipStack in mainCommon. Tested advertisement tested manually. * [Telink] Manual Zephyr SDK update to check CI jobs * [Telink] Fix build errors: - STREAM_FLASH_ERASE has direct dependencies STREAM_FLASH - GETOPT_LONG multiple definition error * [Telink] CONFIG_BOOT_MAX_IMG_SECTORS_AUTO used * [Telink] Fix build errors * [Telink] Reduce mcuboot partition size to 60Kb - Apply change for flash overlays <=2Mb - Possible after reducing CONFIG_BOOT_MAX_IMG_SECTORS * [Telink] Reduce NET_BUF_*_COUNT (to be tested) * [Telink] avoid using NEWLIB_LIBC (use PICOLIB) * Restyled by whitespace * Restyled by clang-format * [Telink] Update Zephyr revision & SDK * [Telink] Adopt TL3218 to latest Zephyr version * [Telink] Use 4mb flash for (B92) Light Switch App target build * [Telink] Fix W91 target build * [Telink] Fix B91 Mars target build * [Telink] Use correct if SOC_RISCV_TELINK_TL321X * [Telink] Fix retention target builds * [Telink] fixed W91 WiFi interface init reverted GetWifiInterface in InetUtils changes, added syntax fixes to Kconfigs.default * [Telink] Update to latest zephyr (develop_new_matter_fixes) hash * [Telink] memory layout and default config changes Reduced mcuboot partition by 0x1000 and removed two other partitions getting 0x3000 to distribute 0x4000 between slot0 and slot 1. Kconfig.defaults changes to reduce ROM usage on B92 lighting OTA. To be improved [Telink] reduced MCUboot partition for most targets increase of slot0,1, bootloader config changes [Telink] Fixed B9x platform startup Lack of MBEDTLS_ZEPHYR_ENTROPY config in defaults which led to InitChipStack 172 error. As result entropy failed in src/platform/Zephyr/PlatformManagerImpl.cpp [Telink] fixed B9x commissioning Reverted network buffers configs [Telink] TL3218 commissioning fixes Changes to fix TLx commissioning on new Zephyr [Telink] Zephyr revision update After merge updates. Kconfig change to fix TL3218 commissioning Reduced RAM usage to build TL3218 by COMMON_LIBC_MALLOC_ARENA_SIZE changing [Telink] zephyr version change, cleanup Changed MCUBOOT logs config, same for LZMA * [Telink] W91 OTA, Factory data commissioning fix Fixes full config target commissioning for W91. Been failing on `SendAttestationRequest` step, finished with `general error 0x01`. Tested manually with chip-tool on RPi on tlsr9118bdk40d * [Telink] W91 stacks increase Increased NET_MGMT_EVENT_STACK_SIZE by 122 B and IPC_SERVICE_BACKEND_ICMSG_WQ_STACK_SIZE by 256 B so that net_mgmt and icmsg_workq stack were used <90%. Jenkins reported thread analyzer warnings on that. * [Telink] review changes draft Reverted NET_BUF_RX/TX_COUNT * [Telink] Add tl7218 board. * [Telink] Fix compilation warnings. * [Telink] Fix config option. * [Telink] Cleanup MbedTLS configuration. * [Telink] Update tl721x default Kconfig - update the default values for BT_RX_STACK_SIZE and COMMON_LIBC_MALLOC_ARENA_SIZE for TL721X Signed-off-by: Jinmiao Yu <jinmiao.yu@telink-semi.com> * [Telink] Remove unused files * [Telink] Update Zephyr revision * [Telink] Clean config types * [Telink] Update Zephyr revision * [Telink] Increase BLE_CTRL_THREAD_STACK_SIZE (B92 SoC retention test) * [Telink] Fix compilation warninig * [Telink] TL7218 upgrade to support version A2 * [Telink] Remove unused file after resolve merge conflict * [Telink] Add tl7218_retention target * riscv: telink: seperate ram for tl3218x . - use retention mode to seperate ram. - reserve more ram for ilm. Signed-off-by: Haiwen Xia <haiwen.xia@telink-semi.com> * [Telink] Fix broken GitHub CI after adding tl721x target * [Telink] remove temporary LZMA for tl321x due to bug * [Telink] Fix TELINK_TLX_MATTER_RETENTION_LAYOUT typo for BOARD_TL3218 * [Telink] Add GPIO/PWM required for TL721X https://github.com/telink-semi/hal_telink/commit/62edeab7cde786a1403cb062e7cef7d13edae520 * [Telink] Temporary disable B95 OTA failed build B95 will be removed fully in next commits * [Telink] Add missed clean out build output step * [Telink] adopt WiFi driver * [Telink] remove b95 SoC / TLSR9258a board (replaced by TL721x) * [Telink] Revert InetUtils.cpp Telink dependency * [Telink] zephyr versions compatibility changes (#382) * [Telink] zephyr versions compatibility changes * [Telink] Change Window Covering App default SoC W91 doesn't support PM * [Telink] Update Zephyr revision * [Telink] sync B92 flash layout * [Telink] Remove temp b92 4mb change * [Telink] Avoid main stack owerflow for w91 * [Telink] Update Zephyr revision * [Telink] manual sync after merge master * [Telink] Increase Main Stack size for W91 Update Zephyr revision * [Telink] Zephyr 3.3 backward compatibility support * riscv: telink: fix insufficient RAM when config LZMA (#384) - adjust the zephyr hash to 930b6d4 . Signed-off-by: Fengtai Xie <fengtai.xie@telink-semi.com> * riscv: telink: add retention mode for buteo (#385) * riscv: telink: Update Zephyr hash - adjust the zephyr hash to 9e39d9f . - add tl3218x_retention target . Signed-off-by: Fengtai Xie <fengtai.xie@telink-semi.com> * riscv: telink: remove retention build target for buteo Signed-off-by: Fengtai Xie <fengtai.xie@telink-semi.com> * [Telink] Add comment --------- Signed-off-by: Fengtai Xie <fengtai.xie@telink-semi.com> Co-authored-by: Alex Tsitsiura <s07641069@gmail.com> * [Telink] Fix commisioning issue due to missed MbedTLS module TODO: fix compilation warnings * telink: tl7218x: fix tercel retention (Update Zephyr hash) * [Telink] Optimize add MbedTLS definitions for Zephyr 3.3 without warnings * [Telink] Use latest hash for Zephyr 3.3 * [Telink] Disable debug part --------- Signed-off-by: Jinmiao Yu <jinmiao.yu@telink-semi.com> Signed-off-by: Haiwen Xia <haiwen.xia@telink-semi.com> Signed-off-by: Fengtai Xie <fengtai.xie@telink-semi.com> Co-authored-by: interfer <diman1436@gmail.com> Co-authored-by: Restyled.io <commits@restyled.io> Co-authored-by: Dmytro Huz <75682372+interfer@users.noreply.github.com> Co-authored-by: Andrii Bilynskyi <andrii.bilynskyi@telink-semi.com> Co-authored-by: Haiwen Xia <haiwen.xia@telink-semi.com> Co-authored-by: Serhii Salamakha <serhii.salamakha@gmail.com> Co-authored-by: fengtai-telink <fengtai.xie@telink-semi.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.