| commit | e0acfdf460574d39a67d3d13a9513599daff5962 | [log] [tgz] |
|---|---|---|
| author | shgutte <102281713+shgutte@users.noreply.github.com> | Mon Sep 08 18:16:45 2025 +0530 |
| committer | GitHub <noreply@github.com> | Mon Sep 08 12:46:45 2025 +0000 |
| tree | 8020712003156cf568fa0893f46658ea0d974fbf | |
| parent | 7c9b1260e3daa86aae0d41b894469b295eee70e8 [diff] |
[Silabs] [WiFi] Added changes for the 917 Wi-Fi multi-ota feature (#37611) * Added changes for the multi ota 917 soc * Added changes for the build errores * Added changes for 917 soc * Added changes for the name for 917 NCP * Deleted the 917 NCP file * Added fixed for 917 SoC build changes * Added changes for 917 SOC * Added changes for the 917 SOC build error * Added changes for the 917 SoC ota reset * Added changes for OTA 917 SoC script * Added changes for 917 build * Added debugging logs for the files * Removed the duplicate code * Added changes for the SoC Application * Added changes for builkd issue with EFR32 multi OTA * Added changes for the OTA 917 NCP * Added changes for the OTA tlv * Added changes for the comment * Added changes for the process block for WIfi * Removed the mWriteOffset in firmware processor * Removed unessory comment * Added changes for the ProcessInternal OTA WiFi * Added changes for WiFi OTA processor * Removed the unwanted line * Cleanup of the code * Corrected #ifdef comments * Removed unwanted comment * Added back the set_logger function * Applied suggestion * Added changes realted to comment * Discription for input command is updated * Added changes for build file of 917 SoC * Added changes for encryption * Adds changes for the multi-ota updated * Adds changes for the customProcessor * Refacred the code and removed the not required code * Adds change for script * Adds changes for the 917 NCP * Restyle done * Adds OTA_ENCRYPTION_ENABLE commnet * Added SL_STATUS_SI91X_FW_UPDATE_DONE directly * Removed the OTAImageTypex * Added comment for 917 NCP * Removed the comment * Changed the comment for SLI_SI91X_MCU_INTERFACE * Restyled by clang-format * 917 SoC reset has been moved to HandleApply instead of applyaction * Resolved review comments * Reverted multi-ota/build.gn changes * Remove commented code * Removed commented code * Cleanup the code * sl_si91x_soc_nvic_reset(); removed and added platform abstract reset API * Resolved CI build error * Cleanedup code * Removed iWx917/OTAWiFiFirmwareProcessor.h in multiimageprocessor as it not required * Update src/platform/silabs/multi-ota/OTATlvProcessor.h Co-authored-by: Rohan Sahay <103027015+rosahay-silabs@users.noreply.github.com> * Update src/platform/silabs/efr32/BUILD.gn Co-authored-by: Rohan Sahay <103027015+rosahay-silabs@users.noreply.github.com> * Update src/platform/silabs/multi-ota/SiWx917/OTAWiFiFirmwareProcessor.cpp Co-authored-by: Rohan Sahay <103027015+rosahay-silabs@users.noreply.github.com> * Update src/platform/silabs/multi-ota/SiWx917/OTAWiFiFirmwareProcessor.cpp Co-authored-by: Rohan Sahay <103027015+rosahay-silabs@users.noreply.github.com> * Removed extra logs and resolved review comments * Addressed review comments * Addressed review comments * Moved DataAccumulator Data and getthreashhold to protected block * Resolved review comments * Added BUILD.gn for multi-ota directory * Resolved re-review comments * Resolve merge conflicts * Resolve merge conflicts * Restored examples BUILD.gn changes as it is not required * Restored examples BUILD.gn changes as it is not required * Restored windows app BUILD.gn changes * Resolved merge conflicts due to ldscripts and matter-platform.slcp * Resolved review comments * Resolved build errors * Added wifi_sdk firmware_upgrade path in efr32_sdk.gni * Corrected naming schema in factorydata and fimware processors * Resolved review comments * Reverted the changes in OTADataAccumulator class * Reverted change in OTADataAccumulator class * Bring changes from matter_sdk * Bring changes from matter_sdk * Restyled by clang-format * Added custom TLV macros * Added refactored build.gn and added encrption changes also from matter_sdk * Modifie add arg for wifi input file as tai for --wifi_ta_input_file * Resolved merge conflicts * Resolved merge conflicts * multi-ota factory data upgrade fix added for 917 SoC * Reverted encryption related changes * Added app properties for EFR devices which is needed while creating .gbl file from .s37 file * Restyled by clang-format * Restyled by gn * Resolved review comments * Combined the sources and deps of efr and ncp of multi-ota by a condition * Restyler fix * Restyler fix * Resolved build errors when encryption enabled --------- Co-authored-by: Sergei Lissianoi <Sergei.Lissianoi@silabs.com> Co-authored-by: Restyled.io <commits@restyled.io> Co-authored-by: bhmanda <bhmanda@silabs.com> Co-authored-by: bhmanda-silabs <107180296+bhmanda-silabs@users.noreply.github.com> Co-authored-by: Rohan Sahay <103027015+rosahay-silabs@users.noreply.github.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.
