diff --git a/sld120-matter-wifi-getting-started/04-light-switch-step-by-step-example.md b/sld120-matter-wifi-getting-started/04-light-switch-step-by-step-example.md index 0786e13..f54c30b 100644 --- a/sld120-matter-wifi-getting-started/04-light-switch-step-by-step-example.md +++ b/sld120-matter-wifi-getting-started/04-light-switch-step-by-step-example.md @@ -21,7 +21,7 @@ This procedure prepares the Raspberry Pi 4B (RPi4B) to become a Matter Hub. You 4. Use PuTTY to connect to RPi4B. 1. The first time connecting to RPi4B, PuTTY will warn about a new host key or key fingerprint. Accept the key. - 2. The credentials (username: password) are the same given Step 1. + 2. The credentials (username: password) are the same as those given in Step 1. 3. Switch to root mode and navigate to path "/home/ubuntu/connectedhomeip/out/standalone" to find the chip-tool. Matter hub/chip-tool are ready and working. Keep the PuTTY session open for the following steps. @@ -92,8 +92,8 @@ Now two Matter accessory devices (MADs) are on the network and ready to be used. 1. In a PuTTY session to the Matter hub, use the chip-tool to test the Matter light device. - 1. Control the light status of the light MAD Using `./chip-tool onoff on nodeID 1`. You can also use `chip-tool onoff off` and `chip-tool toggle`. - 2. For dev board with buttons available, you can use BTN1 to toggle the light status locally. + 1. Control the light status of the light MAD using `./chip-tool onoff on nodeID 1`. You can also use `chip-tool onoff off` and `chip-tool toggle`. + 2. For dev boards with buttons available, you can use BTN1 to toggle the light status locally. 2. In a PuTTY session to the Matter hub, use the chip-tool to bind the light_switch MAD to the light MAD, thus allowing the switch to control the light. diff --git a/sld120-matter-wifi-getting-started/07-next-steps-other-resources.md b/sld120-matter-wifi-getting-started/07-next-steps-other-resources.md index 932dd2e..50dad7a 100644 --- a/sld120-matter-wifi-getting-started/07-next-steps-other-resources.md +++ b/sld120-matter-wifi-getting-started/07-next-steps-other-resources.md @@ -1,6 +1,6 @@ # Next Steps -Now that you have gotten a sense of what goes into making a Matter network, you can begin to customize MADs and other features for your own purposes. The [Developers' Guide](/matter/{build-docspace-version}/matter-developers-guide-overview) contains more detail than was provided in this Quick-Start guide, and also contains information on a number of special development topics. Your Matter Extension package contains a number of other Matter examples that you can use as a starting point, the first two of which were used in this example. +Now that you have gotten a sense of what goes into making a Matter network, you can begin to customize MADs and other features for your own purposes. The [Developers' Guide](/matter/{build-docspace-version}/matter-developers-guide-overview) contains more detail than was provided in this Quick-Start guide, and also contains information on a number of special development topics. Your Matter Extension package contains a number of other Matter examples that you can use as a starting point, the first two of which were used in this example: - Matter SoC Light over Wi-Fi diff --git a/sld246-matter-faq/wifi-faq.md b/sld246-matter-faq/wifi-faq.md index f769693..a4409cd 100644 --- a/sld246-matter-faq/wifi-faq.md +++ b/sld246-matter-faq/wifi-faq.md @@ -184,7 +184,7 @@ When this happens, perform the following steps to run the OTA Update successfull 1. Disconnect the WF200 Expansion Board from the EFR32MG24. -2. Go To the Simplicity Commander's folder path in the command prompt and run this command: +2. Go to the Simplicity Commander's folder path in the command prompt and run this command: ```shell commander.exe extflash read --range 0x00:+ diff --git a/sld247-matter-overview/index.md b/sld247-matter-overview/index.md index ef878e3..945ed2d 100644 --- a/sld247-matter-overview/index.md +++ b/sld247-matter-overview/index.md @@ -77,7 +77,7 @@ Pre-built images for the SiWx917 connectivity firmware are available per the ins **Simplicity Commander**: [Simplicity Commander](/matter/{build-docspace-version}/matter-references/flash-silabs-device#simplicity-commander) is a utility that provides GUI and command line access to the debug features of an EFM32 device. It allows you to flash firmware, update the kit firmware, and lock or unlock debug access. -**Tera Term**: [Tera Term](https://osdn.net/projects/ttssh2/releases/) is the terminal emulator for Microsoft Windows that supports serial port, telnet, and SSH connections. +**Tera Term**: [Tera Term](https://github.com/TeraTermProject/osdn-download) is the terminal emulator for Microsoft Windows that supports serial port, telnet, and SSH connections. **Silicon Labs Matter SiSDK Extension**: Once Simplicity Studio 5 is installed, you will be prompted to install the Simplicity SDK, formerly released as Gecko SDK (GSDK). Here you should also install the Matter Enablement Package by making sure the extension is checked, as shown. @@ -85,7 +85,7 @@ Pre-built images for the SiWx917 connectivity firmware are available per the ins **Installation of Wi-Fi SDK and WiSeConnect Packages**: The following packages will be installed during the installation of Simplicity Studio. Refer to [Package Installation](/matter/{build-docspace-version}/matter-wifi-getting-started-example/software-installation). -**Matter Hub Raspberry Pi Image**: A copy of the pre-built image from the Silicon Labs web services can be downloaded in this [zipfile](https://www.silabs.com/documents/public/software/SilabsMatterPi_2.5.0-1.4-extension.zip). **Note** this is a large file and will take some time to download. +**Matter Hub Raspberry Pi Image**: A copy of the pre-built image from the Silicon Labs web services can be downloaded in this [zipfile](https://www.silabs.com/documents/public/software/SilabsMatterPi_2.6.0-1.4-extension.zip). **Note** this is a large file and will take some time to download. >**Note:** The Matter hub for Matter over Thread requires an additional device, a radio co-processor. See [the introduction to the Matter over Thread demo](/matter/{build-docspace-version}/matter-light-switch-example/02-thread-light-switch-example) for more information. diff --git a/sld248-matter-overview-guides/code-size-savings.md b/sld248-matter-overview-guides/code-size-savings.md index 69c668e..393f403 100644 --- a/sld248-matter-overview-guides/code-size-savings.md +++ b/sld248-matter-overview-guides/code-size-savings.md @@ -4,7 +4,7 @@ Silicon Labs' Matter example applications come out of the box with various ease- To reduce the total size of your application's image while still maintaining basic core Matter functionality, you can take a few steps: -1. Remove optional components in from the Matter Project in Studio that may not be needed for a certain application. For example, removing the components Matter Display and Matter QR Code Display will save flash by disabling the LCD screen. +1. Remove optional components from the Matter Project in Studio that may not be needed for a certain application. For example, removing the components Matter Display and Matter QR Code Display will save flash by disabling the LCD screen. 2. Remove any excess printing from the application. In practice, this can include removing the Matter Shell component and RTT Logging from the Matter device. 3. Install the `matter_no_debug` and/or `matter_no_lcd_shell` components. This will automatically take care of removing these extra features (`matter_no_lcd_shell`) as well as implement the defines and configuration values (`matter_no_debug`) to achieve optimal image size reduction at the click of a button. 4. Remove clusters from the zap configuration. Example applications have clusters enabled to support both Thread and Wi-Fi transport layers such as the Diagnostics clusters. It is important to note that certain device types require different Matter Clusters. Be sure to check the [Matter Specifications](https://csa-iot.org/developer-resource/specifications-download-request/) to confirm which Matter Clusters are required for your device type. diff --git a/sld248-matter-overview-guides/matter-icd.md b/sld248-matter-overview-guides/matter-icd.md index 0339e56..9aabf06 100644 --- a/sld248-matter-overview-guides/matter-icd.md +++ b/sld248-matter-overview-guides/matter-icd.md @@ -73,9 +73,9 @@ These configurations are independent from the underlying transport configuration These configurations can be changed by modifying the configuration of the `ICD Server Configuration` component or directly by setting values in `sl_matter_icd_config.h`. ```cpp - #define SL_IDLE_MODE_DURATION_S = 600 // 10min Idle Mode Interval - #define SL_ACTIVE_MODE_INTERVAL = 1000 // 1s Active Mode Interval - #define SL_ACTIVE_MODE_THRESHOLD = 500 // 500ms Active Mode Threshold + #define SL_IDLE_MODE_DURATION_S 600 // 10min Idle Mode Interval + #define SL_ACTIVE_MODE_INTERVAL 1000 // 1s Active Mode Interval + #define SL_ACTIVE_MODE_THRESHOLD 500 // 500ms Active Mode Threshold ``` ### ICD Check-In Protocol Use-Case @@ -305,9 +305,9 @@ The recommended configurations are likely to change with the Matter 1.4 release. Configuration parameters of the ICD Server Configuration component (sl_matter_icd_config.h): ```cpp - #define SL_IDLE_MODE_DURATION_S = 600 // 10min Idle Mode Interval - #define SL_ACTIVE_MODE_INTERVAL = 10000 // 10s Active Mode Interval - #define SL_ACTIVE_MODE_THRESHOLD = 1000 // 1s Active Mode Threshold + #define SL_IDLE_MODE_DURATION_S 600 // 10min Idle Mode Interval + #define SL_ACTIVE_MODE_INTERVAL 10000 // 10s Active Mode Interval + #define SL_ACTIVE_MODE_THRESHOLD 1000 // 1s Active Mode Threshold ``` **Openthread Configuration flags** @@ -370,9 +370,9 @@ The last three parameters are configuration parameters in the Matter Core Compon Configuration parameters of the ICD Server Configuration component (`sl_matter_icd_config.h`): ```cpp - #define SL_IDLE_MODE_DURATION_S = 3600 // 60min Idle Mode Interval - #define SL_ACTIVE_MODE_INTERVAL = 0 // 0s Active Mode Interval - #define SL_ACTIVE_MODE_THRESHOLD = 5000 // 5s Active Mode Threshold + #define SL_IDLE_MODE_DURATION_S 3600 // 60min Idle Mode Interval + #define SL_ACTIVE_MODE_INTERVAL 0 // 0s Active Mode Interval + #define SL_ACTIVE_MODE_THRESHOLD 5000 // 5s Active Mode Threshold ``` **Openthread Configuration flags** diff --git a/sld249-matter-prerequisites/hardware-requirements.md b/sld249-matter-prerequisites/hardware-requirements.md index c717dc5..b49d78e 100644 --- a/sld249-matter-prerequisites/hardware-requirements.md +++ b/sld249-matter-prerequisites/hardware-requirements.md @@ -28,10 +28,20 @@ Over 60 Silicon Labs boards support running the RCP firmware. To build an image - BRD4187C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm - [XG24-RB4187C](https://www.silabs.com/development-tools/wireless/xg24-rb4187c-efr32xg24-wireless-gecko-radio-board) +- **MGM24 boards:** + - BRD4316A / SLWSTK6006A / Wireless Start Kit / 2.4GHz@10dBm - xGM240-RB4316A + - BRD4317A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm - xGM240-RB4317A + - BRD4318A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm - xGM240-RB4318A + - BRD4319A (Rev A00 only) / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm + - BRD2704A / Sparkfun Thing Plus MGM240P + - BRD4337A / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm - xGM240-RB4337A + - **MG26 boards:** - BRD4116A / 2.4GHz@10dBm - BRD4117A / 2.4GHz@20dBm - BRD4118A / 2.4GHz@20dBm + - BRD4120A + - BRD4121A - BRD2608A - BRD2709A @@ -53,19 +63,22 @@ The Matter Accessory Device (MAD) is the actual device that the Matter applicati - BRD2703A / MG24 Explorer Kit - BRD2601B / MG24 Explorer Kit - [XG24-DK2601B](https://www.silabs.com/development-tools/wireless/efr32xg24-dev-kit?tab=overview) - - BRD4319A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm - - **Note**: Only the A00 revision of this board is supported, other revisions do not have enough RAM to run Matter. + - - BRD4316A / SLWSTK6006A / Wireless Start Kit / 2.4GHz@10dBm - - [XGM240-RB4316A](https://www.silabs.com/development-tools/wireless/xgm240-rb4316a-xgm240p-module-radio-board?tab=overview) - - BRD4317A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm - - [XGM240-RB4317A](https://www.silabs.com/development-tools/wireless/xgm240-rb4317a-xgm240p-module-radio-board?tab=overview) +- **MGM24 boards:** + - BRD4316A / SLWSTK6006A / Wireless Start Kit / 2.4GHz@10dBm - xGM240-RB4316A + - BRD4317A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm - xGM240-RB4317A + - BRD4318A / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm - xGM240-RB4318A + - BRD4319A (Rev A00 only) / SLWSTK6006A / Wireless Starter Kit/ 2.4GHz@20dBm + - BRD2704A / Sparkfun Thing Plus MGM240P + - BRD4337A / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm - xGM240-RB4337A - **MG26 boards** - BRD4116A / 2.4GHz@10dBm - BRD4117A / 2.4GHz@20dBm - BRD4118A / 2.4GHz@20dBm + - BRD4120A + - BRD4121A - BRD2608A - BRD2709A @@ -73,6 +86,11 @@ The Matter Accessory Device (MAD) is the actual device that the Matter applicati - BRD4350A - BRD4351A +- **MGM301 boards:** + - BRD2719A + - BRD4407A + - BRD4408A + ## Matter Over Wi-Fi Accessory Device Requirements ### Matter Over Wi-Fi Accessory Device Requirements for NCP Mode @@ -112,7 +130,6 @@ The following boards are supported for the Matter over Wi-Fi demos and developme - WF200 / Single Band Wi-Fi Expansion Board / 2.4GHz - [SLEXP8023A](https://www.silabs.com/development-tools/wireless/wi-fi/wfm200-wifi-expansion-kit) - Interconnect board (included in the Wi-Fi kits) -- Interconnect board (included in the Wi-Fi kits) - SPI Cable (included in the RS9116 kit) - Jumper Cables (included in the RS9116 kit) diff --git a/sld249-matter-prerequisites/matter-artifacts.md b/sld249-matter-prerequisites/matter-artifacts.md index 4a29850..ceb821c 100644 --- a/sld249-matter-prerequisites/matter-artifacts.md +++ b/sld249-matter-prerequisites/matter-artifacts.md @@ -4,7 +4,7 @@ This page provides links to pre-built software image "artifacts" that can be use Images for the items listed below are available under the "Assets" section at the bottom of this page: -https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.0 +https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.1 ## Matter Hub Raspberry Pi Image @@ -16,25 +16,25 @@ https://www.silabs.com/documents/public/software/SilabsMatterPi_2.5.0-1.4-extens The Radio Co-Processor firmware is used to turn an EFR into an RCP that can be used with a Raspberry Pi to allow the Raspberry Pi's Open Thread Border Router to access the Thread network. Radio Co-Processor (RCP) images are available in the Assets section of this page: -https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/ot-rcp-binaries-2.6.0-1.4.zip +https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/ot-rcp-binaries-2.6.1-1.4.zip ## Matter Accessory Device Images The Matter Accessory Device Images are used to turn an EFR into a Matter device. These are pre-built binary images for the Matter Demo. Matter Accessory Device Images are located in the Assets section of this page: -https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/matter-accessory-device-images_2.6.0-1.4.zip +https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/matter-accessory-device-images_2.6.1-1.4.zip ## Matter Bootloader Binaries All Silicon Labs board supporting Matter require that a bootloader binary is flashed to the device along with the application image. Bootloader binaries for all of the Matter supported devices are available here: -https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/bootloader_binaries_matter_extension_v2.6.0-1.4.zip +https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/bootloader_binaries_matter_extension_v2.6.1-1.4.zip ## RS9116 Firmware The RS9116 firmware (`rs9116_firmware_files_with_rev.zip`) is used to update the RS9116 which can be found in the Assets section of this page: -https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/rs9116_firmware_files_with_rev_2.6.0-1.4.zip +https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/rs9116_firmware_files_with_rev_2.6.1-1.4.zip **Note**: RS9116 chip/module needs to be flashed with proper firmware as mentioned below: @@ -46,11 +46,11 @@ RS9116 chip/module needs to be flashed with proper firmware as mentioned below: The SiWx917 firmware(SiWx917_firmware_files.zip) is used to update the SiWN917 NCP and SiWG917 SOC which can be found in the Assets section of this page: -https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/SiWx917_firmware_files_2.6.0-1.4.zip +https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/SiWx917_firmware_files_2.6.1-1.4.zip **Note**: -- SiWN917 NCP board need to be flashed with proper firmware as mentioned below: +- SiWN917 NCP boards need to be flashed with proper firmware as mentioned below: - `SiWG917-B.2.x.X.X.X.rps - This firmware image is valid for BRD8045A (B0 Expansion v2.0) board` @@ -58,16 +58,18 @@ https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/SiWx917 - `SiWG917-B.2.x.X.X.X.rps - This firmware image is valid for BRD4338A(B0 common flash v2.0) board` +[Both the points in the Note refer to the same file]: # + ## Matter SiWx917 RCP Linux app and Configuration file The SiWx917 RCP folder (siwx917_rcp_files.zip) contains the Matter Linux all-cluster-app, which can be run on a Raspberry Pi, and the wfx-sdio-overlay.dts file, a Device Tree Source file used to configure the SDIO interface on the Raspberry Pi to detect and communicate with the SiWx917 RCP. -https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/siwx917_rcp_files.zip +https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/siwx917_rcp_files.zip ## SiWx917 SoC Configuration Files For JLink RTT Logging To check device logs on JLink RTT for the Matter Application on the SiWx917 SoC, the **JLink RTT** must be configured for the SiWx917 SoC device by following the instructions on the [JLink RTT SOC Support](/matter/{build-docspace-version}/matter-wifi-enabling-features/jlink-soc-setup) for SiWx917 SoC. -The [JLinkDevices.xml](https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/JLinkDevices.xml.zip) and [RS9117_SF_4MB_42bsp.elf](https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/RS9117_SF_4MB_42bsp.elf.zip) files referenced in the instructions may be found in the Assets section of this page. +The [JLinkDevices.xml](https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/JLinkDevices.xml.zip) and [RS9117_SF_4MB_42bsp.elf](https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.1/RS9117_SF_4MB_42bsp.elf.zip) files referenced in the instructions may be found in the Assets section of this page. >**Note**: For EFR32MG2x devices, JLink RTT Logging support is already enabled. diff --git a/sld250-matter-references/custom-matter-device.md b/sld250-matter-references/custom-matter-device.md index 8a92246..1d515e5 100644 --- a/sld250-matter-references/custom-matter-device.md +++ b/sld250-matter-references/custom-matter-device.md @@ -120,7 +120,7 @@ $ mattertool levelcontrol move-to-level {desired_level} 0 1 1 {node_ID} 1 $ mattertool levelcontrol read current-level 1 1 // Returns 10 ``` -For more information on running a Silicon Labs lighting example on a Thunderboard Sense 2 see you can view documentation in the Silicon Labs Matter GitHub Repo. +For more information on running a Silicon Labs lighting example on a Thunderboard Sense 2 you can view documentation in the Silicon Labs Matter GitHub Repo. ## Defining a Custom Cluster diff --git a/sld250-matter-references/find-raspi.md b/sld250-matter-references/find-raspi.md index 7ef4327..d69c475 100644 --- a/sld250-matter-references/find-raspi.md +++ b/sld250-matter-references/find-raspi.md @@ -17,7 +17,7 @@ Use nmap with the following command: $ sudo nmap -sn .0/24` ``` -Example: `sudo nmap -sn 1-.4.148.0/24`, Among other returned values, you will see something: +Example: `sudo nmap -sn 10.4.148.0/24`, Among other returned values, you will see something: ```shell $ Nmap scan report for ubuntu.silabs.com (10.4.148.44) @@ -37,7 +37,7 @@ Alternatively, use Arp with the following command: ### Windows -In the command prompt, use `nslookup` to fnd your Raspberry Pi. +In the command prompt, use `nslookup` to find your Raspberry Pi. Example: `nslookup ubuntu` diff --git a/sld250-matter-references/flash-silabs-device.md b/sld250-matter-references/flash-silabs-device.md index 4eb7f2c..391d909 100644 --- a/sld250-matter-references/flash-silabs-device.md +++ b/sld250-matter-references/flash-silabs-device.md @@ -7,10 +7,10 @@ Once you have an image built, you can flash it onto your EFR or SiWx917 device ( Simplicity Studio is a complete development environment and tool suite. It has the ability to discover USB-connected development boards and flash them. - [Download Simplicity Studio](https://www.silabs.com/developers/simplicity-studio). -- Building application Using Simplicity Studio: +- Building Application Using Simplicity Studio: - [Build Application for EFR32](/matter/{build-docspace-version}/matter-wifi-run-demo/build-efx32-application-using-studio) - [Build Application for SoC](/matter/{build-docspace-version}/matter-wifi-run-demo/build-soc-application-using-studio) -- Flash application Using Simplicity Studio: +- Flash Application Using Simplicity Studio: - [Build Application for EFR32 Step 9](/matter/{build-docspace-version}/matter-wifi-run-demo/build-efx32-application-using-studio) - [Build Application for SoC Step 9](/matter/{build-docspace-version}/matter-wifi-run-demo/build-soc-application-using-studio) - [Simplicity Studio Reference Guide](https://docs.silabs.com/simplicity-studio-5-users-guide/latest/ss-5-users-guide-building-and-flashing/flashing) diff --git a/sld250-matter-references/matter-gatt.md b/sld250-matter-references/matter-gatt.md index 27b8b79..acd9345 100644 --- a/sld250-matter-references/matter-gatt.md +++ b/sld250-matter-references/matter-gatt.md @@ -27,7 +27,7 @@ follows: In the top menu of your project navigate to `Configuration Tools > Bluetooth GATT Configurator` -4. Change your GATT settings as you wish for your project. +4. Change your GATT settings as you wish for your project More information on using the [BLE GATT Configurator is provided here.](https://docs.silabs.com/simplicity-studio-5-users-guide/latest/ss-5-users-guide-developing-with-project-configurator/bluetooth-gatt-configurator) @@ -37,7 +37,7 @@ follows: 6. BLE GATT database is stored in the `autogen` folder in your project directory -7. Move the BLE GATT db into your Matter project. +7. Move the BLE GATT db into your Matter project Copy the BLE GATT db header files out of your project and into the Matter project. BLE GATT db header and `.c` files are located in diff --git a/sld250-matter-references/matter-pintool.md b/sld250-matter-references/matter-pintool.md index 33b2088..1b52b32 100644 --- a/sld250-matter-references/matter-pintool.md +++ b/sld250-matter-references/matter-pintool.md @@ -25,9 +25,9 @@ When creating a configuration for a custom board do the following: to start the project wizard. Choose your development board type, and the latest Gecko SDK you'll be working from. Click **Next**. -1. Select the `Empty C++ Project` example and click **Next**. +2. Select the `Empty C++ Project` example and click **Next**. -1. Click **Finish** to create your project. +3. Click **Finish** to create your project. ## 3. Customize your Components and Pin configuration in Simplicity Studio diff --git a/sld250-matter-references/using-studio.md b/sld250-matter-references/using-studio.md index 4adcfb5..c0334db 100644 --- a/sld250-matter-references/using-studio.md +++ b/sld250-matter-references/using-studio.md @@ -4,7 +4,7 @@ Simplicity Studio contains a number of integrated tools that you can use with pr ## Bluetooth GATT Configurator -The Simplicity Studio Bluetooth LE (BLE) GATT Configurator is an Advanced Configurator within the Simplicity Studio Project Configuration suite. you can add the BLE GATT configuration by adding the `Bluetooth > GATT > Configuration` component to your project. This will enable the BLE GATT Configurator under `Configuration Tools > Bluetooth GATT Configurator`. See the Simplicity Studio v5 User's Guide for more information on using the [BLE GATT Configurator](https://docs.silabs.com/simplicity-studio-5-users-guide/latest/ss-5-users-guide-developing-with-project-configurator/bluetooth-gatt-configurator). +The Simplicity Studio Bluetooth LE (BLE) GATT Configurator is an Advanced Configurator within the Simplicity Studio Project Configuration suite. You can add the BLE GATT configuration by adding the `Bluetooth > GATT > Configuration` component to your project. This will enable the BLE GATT Configurator under `Configuration Tools > Bluetooth GATT Configurator`. See the Simplicity Studio v5 User's Guide for more information on using the [BLE GATT Configurator](https://docs.silabs.com/simplicity-studio-5-users-guide/latest/ss-5-users-guide-developing-with-project-configurator/bluetooth-gatt-configurator). ## Energy Profiler @@ -15,4 +15,4 @@ Complete documentation on using the Simplicity Studio Energy Profiler is provide ## Custom Hardware Configuration -At some point during product development you may need to move your project over to your custom hardware. In this case, you will likely need to change the pinout and hardware configuration in the example project to reflect your own custom project. You can do this using the Pin Tool. The Simplicity Studio 5 User's Guide contains full documentation using the [Pin Tool](https://docs.silabs.com/simplicity-studio-5-users-guide/latest/ss-5-users-guide-developing-with-project-configurator/pin-tool). +At some point during product development you may need to move your project over to your custom hardware. In this case, you will likely need to change the pinout and hardware configuration in the example project to reflect your own custom project. You can do this using the Pin Tool. The Simplicity Studio 5 User's Guide contains full documentation on using the [Pin Tool](https://docs.silabs.com/simplicity-studio-5-users-guide/latest/ss-5-users-guide-developing-with-project-configurator/pin-tool). diff --git a/sld250-matter-references/versioning-release-maintenance.md b/sld250-matter-references/versioning-release-maintenance.md index 1b36aeb..cf7aaf2 100644 --- a/sld250-matter-references/versioning-release-maintenance.md +++ b/sld250-matter-references/versioning-release-maintenance.md @@ -70,4 +70,5 @@ Update digits based on the following criteria: | v2.5.0-1.4 | 18-Dec-24 | 2024.12.0 | v3.4.0 | 1.4 | Obsolete | | v2.5.1-1.4 | 12-Feb-25 | 2024.12.1 | v3.4.1 | 1.4 | Obsolete | | v2.5.2-1.4 | 10-Apr-25 | 2024.12.2 | v3.4.2 | 1.4 | Maintained | -| v2.6.0-1.4 | 18-Jun-25 | 2025.6.0 | v3.5.0 | 1.4 | Active | +| v2.6.0-1.4 | 18-Jun-25 | 2025.6.0 | v3.5.0 | 1.4 | Maintained | +| v2.6.1-1.4 | 23-Jul-25 | 2025.6.1 | v3.5.1 | 1.4 | Active | diff --git a/sld251-matter-thread/build-flash-mad.md b/sld251-matter-thread/build-flash-mad.md index a07e47d..44678c2 100644 --- a/sld251-matter-thread/build-flash-mad.md +++ b/sld251-matter-thread/build-flash-mad.md @@ -36,7 +36,7 @@ If you are coming from Simplicity Studio, you may have already installed the dem There are two ways to build a Matter Accessory Device image file. You can build it using the Silicon Labs Matter GitHub Repo or you can build it using Simplicity Studio. The entire build process for Simplicity Studio is covered in the [Matter Over Thread Quick Start Guide](/matter/{build-docspace-version}/matter-light-switch-example/02-thread-light-switch-example). There are two ways to build a Matter Accessory Device image file. You can build it using the Silicon Labs Matter GitHub Repo or you can build it using Simplicity Studio. The entire build process for Simplicity Studio is covered in the [Matter Over Thread Quick Start Guide](/matter/{build-docspace-version}/matter-light-switch-example/02-thread-light-switch-example). -- [Build Using the Matter GitHub Repo](https://github.com/SiliconLabs/matter/blob/latest/examples/lighting-app/silabs/efr32/README.md) +- [Build Using the Matter GitHub Repo](https://github.com/project-chip/connectedhomeip/tree/master/examples/lighting-app/silabs) - [Build Using Simplicity Studio](/matter/{build-docspace-version}/matter-light-switch-example/02-thread-light-switch-example) ## Step 2: Flash the Matter Accessory Device diff --git a/sld255-matter-dev-guide-overview/index.md b/sld255-matter-dev-guide-overview/index.md index c9a3b18..3d3ea17 100644 --- a/sld255-matter-dev-guide-overview/index.md +++ b/sld255-matter-dev-guide-overview/index.md @@ -5,6 +5,6 @@ as well as other topics of interest. - [**Prerequisites**](/matter/{build-docspace-version}/matter-prerequisites) provides a more extensive list of hardware options as well as additional detail on software prerequisites. - The [**Matter over Thread Example**](/matter/{build-docspace-version}/matter-thread) and [**Matter over Wi-Fi Example**](/matter/{build-docspace-version}/matter-wifi) provide much more detail than the quick-start guides. -- The [**Matter Ecosystems**](/matter/{build-docspace-version}/matter-ecosystems) displays information on various IoT ecoystems and how Silicon Labs' Matter enabled applications integrate within them. +- The [**Matter Ecosystems**](/matter/{build-docspace-version}/matter-ecosystems) displays information on various IoT ecosystems and how Silicon Labs' Matter enabled applications integrate within them. - [**Detailed Development Topics**](/matter/{build-docspace-version}/matter-overview-guides) cover a number of other topics of interest to developers, including commissioning, security, and over-the-air update. diff --git a/sld288-matter-fundamentals-data-model/index.md b/sld288-matter-fundamentals-data-model/index.md index c9e43d2..5bed87b 100644 --- a/sld288-matter-fundamentals-data-model/index.md +++ b/sld288-matter-fundamentals-data-model/index.md @@ -4,7 +4,7 @@ The Data Model in Matter describes a hierarchical encapsulation of data elements A single physical Matter device, such as a light, switch, or door lock, can be represented by one or more nodes. An environment where multiple Matter nodes interoperate is referred to as a Matter fabric. These nodes share a common root of trust. On each separate fabric, a physical Matter device is represented by a node. Every node has a unique network address (Operational Node ID) that makes it uniquely identifiable in the fabric it is on. For example, in the following figure a Matter Lighting device on an Apple HomePod fabric (blue) has an operational node ID unique to the HomePod fabric and a Matter Switch device on a separate Samsung SmartThings Station fabric (red) in the same home has an operational node ID unique to the SmartThings fabric. These IDs may be the same or different; they are independent of each other because they are on two different fabrics. -A Matter device may also be part of more than one fabric and thus is represented on each different fabric by a different node. In following figure, a Matter Door Lock device is on both the HomePod and SmartThings fabrics. Thus, the Door Lock is represented by two different nodes; one for the HomePod fabric and another for the SmartThings fabric. The operational node IDs for the two nodes representing the device may be the same or different; the IDs are independent of each other because the nodes are on two different fabrics. +A Matter device may also be part of more than one fabric and thus is represented on each different fabric by a different node. In the following figure, a Matter Door Lock device is on both the HomePod and SmartThings fabrics. Thus, the Door Lock is represented by two different nodes; one for the HomePod fabric and another for the SmartThings fabric. The operational node IDs for the two nodes representing the device may be the same or different; the IDs are independent of each other because the nodes are on two different fabrics. ![Devices and their fabrics](resources/devices-fabrics.png) diff --git a/sld289-matter-fundamentals-interaction-model/index.md b/sld289-matter-fundamentals-interaction-model/index.md index 00c2bf4..f6f6705 100644 --- a/sld289-matter-fundamentals-interaction-model/index.md +++ b/sld289-matter-fundamentals-interaction-model/index.md @@ -92,7 +92,7 @@ A Timed Write Transaction consists of the following sequence of actions: ### Untimed Write Transactions -An Untimed Write Transaction requires only the Write Request Action and the Write Response Action Timed Write Transaction since there is no time interval that needs to be set or confirmed. +An Untimed Write Transaction requires only the Write Request Action, unlike a Timed Write Transaction since there is no time interval that needs to be set or confirmed. ### Write Transaction Restrictions diff --git a/sld290-matter-wifi-getting-started-example/build-chip-tool.md b/sld290-matter-wifi-getting-started-example/build-chip-tool.md index 5852a8b..750f7eb 100644 --- a/sld290-matter-wifi-getting-started-example/build-chip-tool.md +++ b/sld290-matter-wifi-getting-started-example/build-chip-tool.md @@ -1,6 +1,6 @@ # Building the Chip-Tool -NOTE: The chip-tool binary is a part of the mattertool utility provided with the Silicon Labs Matter Hub RapberryPi image. It is not necessary to build chip-tool from scratch if using Matter Hub. +NOTE: The chip-tool binary is a part of the mattertool utility provided with the Silicon Labs Matter Hub Raspberry Pi image. It is not necessary to build chip-tool from scratch if using Matter Hub. This page covers: diff --git a/sld290-matter-wifi-getting-started-example/getting-started-efx32-ncp.md b/sld290-matter-wifi-getting-started-example/getting-started-efx32-ncp.md index 560519a..2bb2035 100644 --- a/sld290-matter-wifi-getting-started-example/getting-started-efx32-ncp.md +++ b/sld290-matter-wifi-getting-started-example/getting-started-efx32-ncp.md @@ -38,7 +38,7 @@ The following hardware devices are required for executing Matter over Wi-Fi: - [RS9116X-SB-EVK2](https://www.silabs.com/development-tools/wireless/wi-fi/rs9116x-sb-evk2-development-kit) - DB-EVK1 / Dual Band Wi-Fi Development Kit / 2.4GHz & 5GHz - [RS9116X-DB-EVK1](https://www.silabs.com/development-tools/wireless/wi-fi/rs9116x-db-evk-development-kit) - **Note:** Matter only supported over 2.4GHz on this Dev kit. + **Note:** Matter is only supported over 2.4GHz on this Dev kit. - **SiWx917** - SiWx917 NCP Mode / Wi-Fi Expansion Board / 2.4GHz - BRD8045A (B0 Expansion v2.0) @@ -65,7 +65,7 @@ Below are the software tools, packages, and images required for executing Matter - Simplicity Commander for flashing bootloader on EFR32 Boards and Siwx917 NCP. - Tera Term for flashing firmware on EFR32 NCP Boards. - Simplicity Studio -- Putty for controlling EFR32 hardware using chip-tool controller +- PuTTY for controlling EFR32 hardware using chip-tool controller - Ozone Debugger for logging and debugging (Optional) - JLink RTT for logging only (Optional) diff --git a/sld290-matter-wifi-getting-started-example/getting-started-siwx917-rcp.md b/sld290-matter-wifi-getting-started-example/getting-started-siwx917-rcp.md index 579c8e3..c7bf58d 100644 --- a/sld290-matter-wifi-getting-started-example/getting-started-siwx917-rcp.md +++ b/sld290-matter-wifi-getting-started-example/getting-started-siwx917-rcp.md @@ -80,7 +80,7 @@ The following hardware devices are required for this example: # Enable Silabs Wi-Fi (only one bus may be enabled at a time) # Notes: - # -SDIO frequency is limited to 25MHz to ensure compatiblity with all + # -SDIO frequency is limited to 25MHz to ensure compatibility with all # Raspberry Pi versions # -If using a Raspberry Pi 4B with SPI, please limit frequency to 25000000 # -For more information, please contact Silabs support diff --git a/sld290-matter-wifi-getting-started-example/getting-started-with-soc.md b/sld290-matter-wifi-getting-started-example/getting-started-with-soc.md index 8c0994c..4479df2 100644 --- a/sld290-matter-wifi-getting-started-example/getting-started-with-soc.md +++ b/sld290-matter-wifi-getting-started-example/getting-started-with-soc.md @@ -31,7 +31,7 @@ Below are the software tools, packages, and images required for executing Matter - Simplicity Commander for flashing firmware/binary - Tera Term - Simplicity Studio -- Putty for controlling EFR32 hardware using chip-tool controller +- PuTTY for controlling EFR32 hardware using chip-tool controller - JLink RTT for logging only ### Software Packages @@ -49,7 +49,7 @@ Below are the software tools, packages, and images required for executing Matter Refer to the [Wi-Fi Software Installation page](./software-installation). -## Connect SiWx917 SOC to Computer +## Connect SiWx917 SoC to Computer 1. Mount the SiWx917 radio board onto the SiWx917 WSTK board. diff --git a/sld290-matter-wifi-getting-started-example/index.md b/sld290-matter-wifi-getting-started-example/index.md index 77ea5fa..04be159 100644 --- a/sld290-matter-wifi-getting-started-example/index.md +++ b/sld290-matter-wifi-getting-started-example/index.md @@ -8,7 +8,7 @@ To get started with Matter over Wi-Fi, download the latest version of Simplicity ## Setting up the Matter over Wi-Fi Development Environment -Refer to the [Release Notes](https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.0) to know more about the latest releases from Silicon Labs. +Refer to the [Release Notes](https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.1) to know more about the latest releases from Silicon Labs. To control the Matter Accessory Device, a controller is required which is termed as **chip-tool**. The chip-tool can be set up in two ways: diff --git a/sld291-matter-wifi-run-demo/build-efx32-application-using-studio.md b/sld291-matter-wifi-run-demo/build-efx32-application-using-studio.md index cd524cc..a86c5fe 100644 --- a/sld291-matter-wifi-run-demo/build-efx32-application-using-studio.md +++ b/sld291-matter-wifi-run-demo/build-efx32-application-using-studio.md @@ -1,6 +1,6 @@ # Create a Project for an EFR32 Application -This page provides a detailed description on how to create an Wi-Fi NCP project for EFR32 boards. +This page provides a detailed description on how to create a Wi-Fi NCP project for EFR32 boards. 1. [Download](https://www.silabs.com/developers/simplicity-studio) and Install Simplicity Studio. diff --git a/sld291-matter-wifi-run-demo/build-pi-env.md b/sld291-matter-wifi-run-demo/build-pi-env.md index 2ffb458..4a0070c 100644 --- a/sld291-matter-wifi-run-demo/build-pi-env.md +++ b/sld291-matter-wifi-run-demo/build-pi-env.md @@ -12,7 +12,7 @@ When using a Raspberry Pi as a controller in your Matter network, you have two o 1. Insert the flashed SD card (directly or using a card reader) into the laptop/PC that will run the Raspberry Pi Imager tool. 2. Launch the Raspberry Pi 4 Imager. -3. Flash the Pi image using any one of the following procedure: +3. Flash the Pi image using any one of the following procedures: - Click **Choose OS > Other General-purpose OS > Ubuntu >Ubuntu xx.xx 64-bit server OS**. @@ -44,7 +44,7 @@ On powering up the board, the red and green lights should start blinking. Password: ubuntu 4. Switch to root mode and navigate to path _/home/ubuntu/connectedhomeip/out/standalone_ to find the chip-tool. On the pre-built Matter Hub image, the chip-tool will be ready and working. Keep the PuTTY session open for the further steps. -5. If you are building the chip-tool from scratch, update the latest packages by running following commands in the terminal: +5. If you are building the chip-tool from scratch, update the latest packages by running the following commands in the terminal: ```shell $ sudo apt update diff --git a/sld291-matter-wifi-run-demo/flashing-using-commander.md b/sld291-matter-wifi-run-demo/flashing-using-commander.md index 2612801..04f5dcd 100644 --- a/sld291-matter-wifi-run-demo/flashing-using-commander.md +++ b/sld291-matter-wifi-run-demo/flashing-using-commander.md @@ -1,6 +1,6 @@ # Flashing the Matter Binaries Using Simplicity Commander -To flash the application for EFR32 and SiWx917 SOC Board Simplicity Commander software will be used. +To flash the application for EFR32 and SiWx917 SoC Board Simplicity Commander software will be used. Before flashing the application for EFR32 Boards, flash **bootloader images** as per board variants: @@ -61,7 +61,7 @@ Bootloader binaries are available in the respective path of codebase **third_par ## Flashing the SiWx917 SOC Matter Binary using Simplicity Commander -SiWx917 SoC device support is available in the latest [Simplicity Commander](https://community.silabs.com/s/article/simplicity-commander?language=en_US). Download can be found [here](/matter/{build-docspace-version}/matter-references/flash-silabs-device#simplicity-commander) The SiWx917 SOC board will support **.rps** as the only file to flash. Follow these steps to create and flash the **.rps** file using **.s37**. +SiWx917 SoC device support is available in the latest [Simplicity Commander](https://community.silabs.com/s/article/simplicity-commander?language=en_US). Download can be found [here](/matter/{build-docspace-version}/matter-references/flash-silabs-device#simplicity-commander) The SiWx917 SoC board will support **.rps** as the only file to flash. Follow these steps to create and flash the **.rps** file using **.s37**. 1. Locate Simplicity Commander on your PC/Laptop where it is installed through command prompt(cmd). diff --git a/sld291-matter-wifi-run-demo/using-mattertool.md b/sld291-matter-wifi-run-demo/using-mattertool.md index 44e15bd..587eb96 100644 --- a/sld291-matter-wifi-run-demo/using-mattertool.md +++ b/sld291-matter-wifi-run-demo/using-mattertool.md @@ -37,7 +37,7 @@ $ mattertool levelcontrol read current-level 106 1 | **Command** | **Description** | | ------------ | ------------------------------------------------------------------------------------------------- | | help | Prints help options | -| bleWifi | For Matter Bluetooth LE Wi-FI commissioning with 917 SoC device | +| bleWifi | For Matter Bluetooth LE Wi-Fi commissioning with 917 SoC device | | buildCT | Clean build of the chip-tool | | cleanVars | Erase every Set variable used in the script. They will be set back to default or randomized value | | off | Turn off the Light on the already-commissioned 917 SoC device | diff --git a/sld292-matter-wifi-enabling-features/wifi-sleepy-end-device.md b/sld292-matter-wifi-enabling-features/wifi-sleepy-end-device.md index 26e8fa6..02ca4c9 100644 --- a/sld292-matter-wifi-enabling-features/wifi-sleepy-end-device.md +++ b/sld292-matter-wifi-enabling-features/wifi-sleepy-end-device.md @@ -33,7 +33,7 @@ In the Legacy power save mode, when the Wi-Fi station receives a beacon with its The AP acknowledges the PS-Poll frame and responds with a single buffered frame. In this mode, the Wi-Fi station stays active and retrieves a single buffered frame at a time. The AP also indicates that there are more buffered frames for the station using the More Data subfield. -The Wi-Fi station continues to retrieve buffered frames using the PS-Poll frame until there are no more buffered frames and the More Data subfield is set to 0. The Wi-Fi station goes back into the sleep afterwards. +The Wi-Fi station continues to retrieve buffered frames using the PS-Poll frame until there are no more buffered frames and the More Data subfield is set to 0. The Wi-Fi station goes back into sleep afterwards. A Wi-Fi station can enter sleep mode after sending a Null frame to the AP with the power management (PM) bit set. From then on, the AP will store all packets destined to the Wi-Fi station in a per-device queue and sets the TIM field in the beacon frame to indicate that packets destined for the Wi-Fi station have been queued. @@ -68,7 +68,7 @@ To enable ICD functionality for Wi-Fi, the `ICD Management` cluster/component ne ### EFR32 + RS9116 Setup for ICDs (Sleepy Devices) - The following GPIO pins should be connected for 9116 and Host handshakes. -pin 7 and 9 to UULP_2 and UULP_0 respectively. +pin 7 and pin 9 to UULP_2 and UULP_0 respectively. ![Power measurement GPIO pin connection for 9116](./images/wifi-9116-gpio-connections.png) diff --git a/sld295-matter-api-reference/datamodeltypes.md b/sld295-matter-api-reference/datamodeltypes.md index 599fa80..43008cd 100644 --- a/sld295-matter-api-reference/datamodeltypes.md +++ b/sld295-matter-api-reference/datamodeltypes.md @@ -1,6 +1,6 @@ # Data Models -The Data Model defines namespaces for endpoints, clusters, and attributes in the application. From a developper standpoint, this is handled by the ZAP tool. For Multi-Fabric devices, the data model is shared between the Fabrics. +The Data Model defines namespaces for endpoints, clusters, and attributes in the application. From a developer standpoint, this is handled by the ZAP tool. For Multi-Fabric devices, the data model is shared between the Fabrics. For a review of what the Matter Data Model is and how it is used, see the [Matter Data Model](../sld288-matter-fundamentals-data-model/index.md). diff --git a/sld295-matter-api-reference/index.md b/sld295-matter-api-reference/index.md index cfa90ff..b8c604a 100644 --- a/sld295-matter-api-reference/index.md +++ b/sld295-matter-api-reference/index.md @@ -1,6 +1,6 @@ # Matter API Reference -This section covers the various Application Programming Interfaces (APIs) that a developper might use when developing a new Matter Application. +This section covers the various Application Programming Interfaces (APIs) that a developer might use when developing a new Matter Application. - [**DataModel**](./datamodeltypes.md) - [**Attributes**](./attributes.md) @@ -11,7 +11,7 @@ This section covers the various Application Programming Interfaces (APIs) that a ## Application APIs -### Initializaton +### Initialization The application 'Init' sequence lives in the ```AppTask.cpp``` file, and is called at the beginning of the application to ensure that all components are properly initialized and ready to operate. It sets up necessary callbacks, initializes hardware components, and handles any errors that may occur during the process. This function is crucial for the stable operation of the application. diff --git a/sld296-matter-ecosystems/apple-ecosystem-setup.md b/sld296-matter-ecosystems/apple-ecosystem-setup.md index 5c76133..b105926 100644 --- a/sld296-matter-ecosystems/apple-ecosystem-setup.md +++ b/sld296-matter-ecosystems/apple-ecosystem-setup.md @@ -11,7 +11,7 @@ For the Hardware required for an Apple EcoSystem, refer to the [Ecosystem overvi - Apple Account - Apple Home App on Smartphone -**Note:** Apple only has Matter support with IOS version-16.1 or higher. +**Note:** Apple only has Matter support within iOS version-16.1 or higher. ## Set Up Apple HomePod and Apple Phone diff --git a/sld296-matter-ecosystems/google-ecosystem-setup.md b/sld296-matter-ecosystems/google-ecosystem-setup.md index d578839..f1b2a90 100644 --- a/sld296-matter-ecosystems/google-ecosystem-setup.md +++ b/sld296-matter-ecosystems/google-ecosystem-setup.md @@ -43,7 +43,7 @@ Having finished the above, the only step left to have your setup ready is to ope 2. Connect board to a computer. - For Wi-Fi NCP Mode Boards, see [Connect EFR32 Board to Computer](/matter/{build-docspace-version}/matter-wifi-getting-started-example/getting-started-efx32-ncp#connect-the-efx32-boards-to-a-computer). - - For Wi-Fi SOC Mode Boards, see [Connect SiWx917 SOC to Computer](/matter/{build-docspace-version}/matter-wifi-getting-started-example/getting-started-with-soc#connect-siwx917-soc-to-computer). + - For Wi-Fi SoC Mode Boards, see [Connect SiWx917 SoC to Computer](/matter/{build-docspace-version}/matter-wifi-getting-started-example/getting-started-with-soc#connect-siwx917-soc-to-computer). 3. Flash the bootloader binary for your device along with the application (for example, lighting, lock, thermostat, window covering, or light-switch) using [Simplicity Commander](/matter/{build-docspace-version}/matter-wifi-run-demo/flashing-using-commander). diff --git a/sld297-matter-wifi-dic/aws-configuration-registration.md b/sld297-matter-wifi-dic/aws-configuration-registration.md index e46865e..33424cd 100644 --- a/sld297-matter-wifi-dic/aws-configuration-registration.md +++ b/sld297-matter-wifi-dic/aws-configuration-registration.md @@ -2,7 +2,7 @@ Amazon Web Services offers reliable, scalable, and inexpensive cloud computing services. Refer to [AWS Documentation](https://aws.amazon.com/what-is-aws/) for more details. -## AWS CA Certitifcate Registration +## AWS CA Certificate Registration 1. Create a CA certificate, a CA verification certificate, a client certificate, and a client key using the [Openssl Certificate Creation](./openssl-certificate-creation.md) documentation. 2. Open [AWS](https://aws.amazon.com/). diff --git a/sld297-matter-wifi-dic/index.md b/sld297-matter-wifi-dic/index.md index 17be471..f113ef8 100644 --- a/sld297-matter-wifi-dic/index.md +++ b/sld297-matter-wifi-dic/index.md @@ -1,6 +1,6 @@ # Matter Wi-Fi Direct Internet Connectivity -Direct Internet Connectivity (DIC) is a Silicon Labs-only feature to connect Matter devices to proprietary cloud solutions (eg, AWS, GCP, Apple) directly. As such, a Matter Wi-Fi device must support connecting locally on the Matter Fabric, via IPv6, and connecting to the Internet via IPv4. +Direct Internet Connectivity (DIC) is a Silicon Labs-only feature to connect Matter devices to proprietary cloud solutions (e.g., AWS, GCP, Apple) directly. As such, a Matter Wi-Fi device must support connecting locally on the Matter Fabric, via IPv6, and connecting to the Internet via IPv4. - Matter devices can be controlled by chip-tool or controller, and the respective status of the attribute modified will be published to the cloud. - Remote users can install the cloud-specific application to get the notifications on the attribute status and to control the device. diff --git a/sld297-matter-wifi-dic/mqtt-explorer-setup.md b/sld297-matter-wifi-dic/mqtt-explorer-setup.md index bac029d..0ec81af 100644 --- a/sld297-matter-wifi-dic/mqtt-explorer-setup.md +++ b/sld297-matter-wifi-dic/mqtt-explorer-setup.md @@ -38,7 +38,7 @@ Download and install the MQTT Explorer from https://mqtt-explorer.com/. ### Connecting to Mosquitto Connection -- Host : Your Mosquitto ip address +- Host : Your Mosquitto IP address - Port : 8883 - Make sure you enable Validate Certificate and Encryption - Click **Advanced Settings** diff --git a/sld297-matter-wifi-dic/openssl-certificate-creation.md b/sld297-matter-wifi-dic/openssl-certificate-creation.md index 42e48cd..7364fdc 100644 --- a/sld297-matter-wifi-dic/openssl-certificate-creation.md +++ b/sld297-matter-wifi-dic/openssl-certificate-creation.md @@ -1,10 +1,10 @@ -# Openssl Certificate Creation +# OpenSSL Certificate Creation An SSL certificate is an important way to secure user information and protect against hackers. -## Openssl Installation (In ubuntu) +## OpenSSL Installation (In ubuntu) -1. To install openssl, run `sudo apt install openssl`. +1. To install OpenSSL, run `sudo apt install openssl`. ## Certificates Creation @@ -22,12 +22,12 @@ The following commands are used to generate certificates: - `openssl ecparam -name prime256v1 -genkey -noout -out device.key` -4. To generate Client certificate (ex: `device.crt` and `device.key`) using CA certficate: +4. To generate Client certificate (ex: `device.crt` and `device.key`) using CA certificate: - `openssl req -new -out device.csr -key device.key` - `openssl x509 -req -in device.csr -CA CA.crt -CAkey CA.key -CAcreateserial -out device.crt -days 360` -5. To generate CA verification certification key: +5. To generate CA verification certificate key: - `openssl genrsa -out verification_cert.key 2048` diff --git a/sld388-matter-new-features/index.md b/sld388-matter-new-features/index.md index 34e659c..581072b 100644 --- a/sld388-matter-new-features/index.md +++ b/sld388-matter-new-features/index.md @@ -1,5 +1,12 @@ # New Features +## New Features for v2.6.1-1.4 + +- Quality-tested Matter 1.4.1 solution for Thread MG24 / MG26, Wi-Fi SiWx917 SoC and NCP mode, Wi-Fi MG24/WF200 and Wi-Fi MG24/RS9116 (non-sleepy). + - For Wi-Fi SiWx917 SoC and NCP mode, there are known timeout issues in certain stress test conditions, which have not been observed with ecosystems under normal conditions. For details see the Known Issues section of the [Release Notes](https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.1). +- Works with Simplicity SDK v2025.6.1 and WiSeConnect SDK v3.5.1 +- Miscellaneous bug fixes and improvements. + ## New Features for v2.6.0-1.4 - Quality-tested Matter 1.4.1 solution for Thread MG24 / MG26, Wi-Fi SiWx917 SoC and NCP mode, Wi-Fi MG24/WF200 and Wi-Fi MG24/RS9116 (non-sleepy). diff --git a/sld405-matter-fundamentals-security/index.md b/sld405-matter-fundamentals-security/index.md index a2f1b34..e4cbd29 100644 --- a/sld405-matter-fundamentals-security/index.md +++ b/sld405-matter-fundamentals-security/index.md @@ -1,6 +1,6 @@ # Matter Security -Matter raises the bar on security to a new level beyond simply guaranteeing the communication pipe is secure. Now, the end device must be proven to be authentic. The Matter Node Security will likely raise over time. As threats evolve, the SHOULDs will become SHALLs. Creating Secure Identities and injecting them securely in your manufacturing process is not trivial and can be costly. Silicon Labs has the hardware, software, and services to get your secure Matter products to market quickly and cost effectively. +Matter raises the bar on security to a new level beyond simply guaranteeing the communication pipe is secure. Now, the end device must be proven to be authentic. The Matter Node Security will likely increase over time. As threats evolve, the SHOULDs will become SHALLs. Creating Secure Identities and injecting them securely in your manufacturing process is not trivial and can be costly. Silicon Labs has the hardware, software, and services to get your secure Matter products to market quickly and cost effectively. Register at [Silicon Labs Tech Talks](https://www.silabs.com/about-us/events/tech-talks-wireless-technology-training/matter) to watch a detailed on-demand discussion of Matter Security, along with other tech talks as part of the Interactive Matter Training Series. @@ -158,7 +158,7 @@ The Matter PKI for Device Attestation is comprised of: #### Certification Declaration -Another data construct that is necessary for Device Attestation is the Certification Declaration (CD), which is cryptographically signed by the Connectivity Standards Alliance and contains the Vender and Device information as well as the PAA of the device. The CD must be put into the Device during manufacturing to be used during the Device Attestation process. The Commissioner will ask for the stored CD during the commissioning of the Node. +Another data construct that is necessary for Device Attestation is the Certification Declaration (CD), which is cryptographically signed by the Connectivity Standards Alliance and contains the Vendor and Device information as well as the PAA of the device. The CD must be put into the Device during manufacturing to be used during the Device Attestation process. The Commissioner will ask for the stored CD during the commissioning of the Node. ![Certification Declaration](resources/matter-certification-declaration-example.png) diff --git a/sld407-matter-ota/02-ota-software-update.md b/sld407-matter-ota/02-ota-software-update.md index 913fcc6..4d00ff3 100644 --- a/sld407-matter-ota/02-ota-software-update.md +++ b/sld407-matter-ota/02-ota-software-update.md @@ -1,6 +1,6 @@ # Matter OTA Software Update with Silicon Labs Example Applications -This page outlines the steps for a scenario that demonstrates the The Over The Air (OTA) Software Update functionality in Matter. +This page outlines the steps for a scenario that demonstrates the Over The Air (OTA) Software Update functionality in Matter. The Over The Air (OTA) Software Update functionality is enabled by default for all Silicon Labs example applications. Its inclusion in an application is controlled by the OTA Requestor component in a Matter project in Simplicity Studio. @@ -42,7 +42,7 @@ The chip-ota-provider-app binary for a Raspberry Pi is a part of the Artifacts p The running image and the update image are regular Matter application images and are built using the standard procedure. The only additional configuration required is the use of a higher software version in the update image. The software version is configured in a Studio Matter project by navigating to Software Components -> Silicon Labs Matter -> Stack -> Matter Core Components, clicking "Configure" and setting the "Device software version" and "Device software version string" parameters. -See the following page for detailed steps: [build OTA application using studio](./05-build-ota-application-using-studio.md). +See the following page for detailed steps: [build OTA application using studio](./04-build-ota-application-using-studio.md). ### Obtaining the Bootloader binary @@ -138,7 +138,7 @@ Installing the Lower Power Mode component in the project's Software Components t Disabling logging in the configuration of the Matter Core Components component also helps to reduce the image size. -Using LZMA compression when building the .gbl file ( passing `--compress lzma` parameter to the `commander gbl create` command) further reduces the downloaded image size. +Using LZMA compression when building the .gbl file (passing `--compress lzma` parameter to the `commander gbl create` command) further reduces the downloaded image size. When building an internal storage bootloader, the two key configuration parameters are the Slot Start Address and Slot Size in the Bootloader Storage Slot component. The storage slot must not overlap with the running image and the NVM section of the flash. In other words, the slot start address must be greater than the end of the running image address and the sum of the start address and the slot size must be less than the address of the NVM section. The simplest way to get the relevant addresses for the running image and NVM is by using the Silicon Labs `Simplicity Commander` (**Device Info > Main Flash > Flash Map**). @@ -174,17 +174,18 @@ For more information, see the documentation for the ota-provider-app example in ## Multi-Chip OTA Images -Multi-Chip OTA is implemented for EFR32 and SiWx917 NCP/SoC devices. Multi-chip OTA uses an enhanced script, ota_multi_image_tool.py, which creates .ota files that contain additional TLV headers. These TLV headers describe the binaries to be sent over the air. The enhanced script is located here. It is a wrapper to the original src/app/ota_image_tool.py. Multiple binaries can be packaged in the .ota file. Some tags are reserved for specific Silicon Labs binaries, and other tags are available to be used for arbitrary TLVs. The payloads can be encrypted. +Multi-Chip OTA is implemented for EFR32 and SiWx917 NCP/SoC devices. Multi-Chip OTA uses an enhanced script, ota_multi_image_tool.py, which creates .ota files that contain additional TLV headers. These TLV headers describe the binaries to be sent over the air. The enhanced script is located here. It is a wrapper to the original src/app/ota_image_tool.py. Multiple binaries can be packaged in the .ota file. Some tags are reserved for specific Silicon Labs binaries, and other tags are available to be used for arbitrary TLVs. The payloads can be encrypted. The script can be obtained from the Matter Extension github repository. -For more information on creating a Multi-Chip .ota file, see the [README.md](https://github.com/SiliconLabs/matter/blob/latest/scripts/tools/silabs/ota/README.md). +For more information on creating a Multi-Chip .ota file, see the [README.md](https://github.com/project-chip/connectedhomeip/blob/master/scripts/tools/silabs/ota/README.md). -Applications must be built with the OTA Multi Image Requestor component added to the project in Simplicity Studio to enable them to process the TLVs. +Applications must be built with the Multi-Chip OTA Image Requestor component added to the project in Simplicity Studio to enable them to process the TLVs. -The OTA Multi Image Requestor Encryption component should be added to the project if the requestor is meant to process encrypted payloads. +The Multi-Chip OTA Image Requestor Encryption component should be added to the project if the requestor is meant to process encrypted payloads. -**Combined OTA images are also supported:** +**Combined OTA Images in Regular and Multi-Chip OTA Implementations:** +Combined OTA images are supported in both regular OTA and Multi-Chip OTA implementations. These images can contain the bootloader, application, or both, depending on your upgrade scenario. 1. Bootloader + application upgrade. This requires a combined image. @@ -237,7 +238,7 @@ BootloaderInformation_t info Then, in the beginning of [OTAImageProcessorImpl::IsFirstImageRun](https://github.com/SiliconLabsSoftware/matter_sdk/blob/01a2d4aafaa0b124123caac067831809a1a86720/src/platform/silabs/efr32/OTAImageProcessorImpl.cpp#L115), add: ```c++ -bootloader_getInfo(&info); // LINE ADDED: for Multi-OTA test +bootloader_getInfo(&info); // LINE ADDED: for Multi-Chip OTA test ChipLogProgress(SoftwareUpdate, "Bootloader version: 0x%lx\n", info.version); ChipLogProgress(SoftwareUpdate, "Bootloader type: %d\n", info.type); ``` diff --git a/sld407-matter-ota/03-firmware-upgrades.md b/sld407-matter-ota/03-firmware-upgrades.md deleted file mode 100644 index 69b3b3b..0000000 --- a/sld407-matter-ota/03-firmware-upgrades.md +++ /dev/null @@ -1,134 +0,0 @@ -# Firmware Upgrades with Matter applications - -The Over The Air (OTA) Software Update functionality provides WiFi firmware upgrades within the matter environment. - -## Hardware Requirements - -- To run matter ota on Silicon Labs Platform, refer [Hardware Requirements](/matter/{build-docspace-version}/matter-prerequisites/hardware-requirements). - -## Software Requirements - -- To run matter ota on Silicon Labs Platform, refer [Software Requirements](/matter/{build-docspace-version}/matter-prerequisites/software-requirements). - -## Setting up OTA Environment - -- To run OTA on Matter over Wi-Fi, Need to build two different application below: - - **OTA-A** is a normal application with default or older software version. It acts as **ota-requestor** where it needs to update latest software version. - - **OTA-B is** a normal application with updated software version. - - **Chip-tool** is a controller for sending commands to ota-requestor to update the software version and receving commands from device. - - **OTA-Provider** is the server who has the latest software version and from which ota-requestor will download the updated software. - -### Setting up Chip-tool Controller - -If you have not downloaded or cloned this repository, you can run the following -commands on a Linux terminal running on either Linux machine, WSL or Virtual -Machine to clone the repository and run bootstrap to prepare to build the sample -application images. - -1. To download the [SiliconLabs Matter codebase](https://github.com/SiliconLabs/matter.git) run the following commands. - - ```shell - $ git clone https://github.com/SiliconLabs/matter.git - ``` - -2. Bootstrapping: - - ```shell - $ cd matter - $ ./scripts/checkout_submodules.py --shallow --recursive --platform efr32 - $ . scripts/bootstrap.sh - # Create a directory where binaries will be updated/compiled called `out` - $ mkdir out - ``` - - To control the Wi-Fi Matter Accessory Device you will have to compile and run the chip-tool on either a Linux, Mac or Raspberry Pi. The chip-tool builds faster on the Mac and Linux machines so that is recommended, but if you have access to a Raspberry Pi that will work as well. - -3. Build the chip-tool - - ```shell - $ ./scripts/examples/gn_build_example.sh examples/chip-tool out/standalone - ``` - -This will build chip-tool in `out/standalone`. - -### Setting up OTA-Provider - -- To Build OTA-Provider app in Linux Platform, Run below command in matter repository. - -```shell - scripts/examples/gn_build_example.sh examples/ota-provider-app/linux out/debug chip_config_network_layer_ble=false -``` - -### Building OTA Images Using Simplicity Studio - -- To create and build matter OTA using Simplicity studio, refer following link [build OTA application using studio](./05-build-ota-application-using-studio.md). - -## Executing OTA Scenario - -### Generating the OTA image - -1. Locate Simplicity Commander Path via **Command Prompt Terminal**. -2. Create a bootable image file by running below command in commander terminal(using the Lighting application image as an -example): - - ```shell - commander gbl create chip-efr32-lighting-example.gbl --compress lzma --app chip-efr32-lighting-example.s37 - ``` - - **Note**: Using LZMA compression when building the .gbl file ( passing `--compress lzma` parameter to the `commander gbl create` command) further reduces the downloaded image size. - -3. Create the Matter OTA file by running below command in **${WORKSPCAE_DIR}/matter** path: - -```shell - ./src/app/ota_image_tool.py create -v 0xFFF1 -p 0x8005 -vn 2 -vs "2.0" -da sha256 chip-efr32-lighting-example.gbl chip-efr32-lighting-example.ota -``` - -**Note**: Modify **-vn** to **CHIP_DEVICE_CONFIG_DEVICE_SOFTWARE_VERSION** and **-vs** to **CHIP_DEVICE_CONFIG_DEVICE_SOFTWARE_VERSION** as per OTA-B application Building Step 10 in [Build OTA Images](./05-build-ota-application-using-studio.md). - -### Running OTA Provider - -- Locate **ota-provider** terminal start the Provider app passing to it the path to the Matter OTA file created in the previous step: - -```shell - rm -r /tmp/chip_* - ./out/debug/chip-ota-provider-app -f chip-efr32-lighting-example.ota -``` - -### Setting up OTA-Requestor - -- Before running **ota-requestor** app flash the bootloader binary images for Silicon Labs Devices. - -#### Flash Bootloader Images - -- Bootloader binaries will be flashed using Simplicity Commander only. It will support EFR32 NCP Boards only. -- Silicon Labs Devices will supports below Bootloader variants for EFR32 Boards. - - Internal Storage Bootloader - - External Storage Bootloader -- To Flash the Bootloader Binary along with the application for Silicon Labs Device, refer [Flashing Binaries](/matter/{build-docspace-version}/matter-wifi-run-demo/flashing-using-commander.md). - -### Running OTA-Requestor - -1. In a separate terminal, locate the chip-tool and ota-requestor and run the chip-tool commands to provision the Provider: - - ```shell - ./out/chip-tool pairing onnetwork 1 20202021 - ./out/chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": null, "targets": null}]' 1 0 - ``` - -2. If the application device had been previously commissioned hold Button 0 for six seconds to factory-reset the device. - -3. In the chip-tool terminal, commission the Device by passing below command: - - ```shell - ./out/chip-tool pairing ble-wifi "node_id" "SSID" "PSK" 20202021 3840 - ``` - - where SSID and PSK are AP username and password. - -4. Once the commissioning process completes in the same terminal, run below requestor command to start downloading the image: - -```shell - ./out/chip-tool otasoftwareupdaterequestor announce-ota-provider 1 0 0 0 2 0 -``` - -- The application device will connect to the Provider and start the image download. Once the image is downloaded the device will reboot into the downloaded image. diff --git a/sld407-matter-ota/04-ota-software-update-soc.md b/sld407-matter-ota/03-ota-software-update-soc.md similarity index 93% rename from sld407-matter-ota/04-ota-software-update-soc.md rename to sld407-matter-ota/03-ota-software-update-soc.md index 7bbb52b..0aae2f6 100644 --- a/sld407-matter-ota/04-ota-software-update-soc.md +++ b/sld407-matter-ota/03-ota-software-update-soc.md @@ -1,14 +1,14 @@ -# Matter OTA For SiWx917 SOC +# Matter OTA For SiWx917 SoC The scope of this page describes the Matter OTA upgrade on SiWx917 SoC mode for combined image(TA+M4), application(M4) alone, and Wi-Fi(TA) alone image upgrade. ## Hardware Requirements -- To run matter OTA on Silicon Labs Platform, refer to [Hardware Requirements](/matter/{build-docspace-version}/matter-prerequisites/hardware-requirements). +- To run Matter OTA on Silicon Labs Platform, refer to [Hardware Requirements](/matter/{build-docspace-version}/matter-prerequisites/hardware-requirements). ## Software Requirements -- To run matter OTA on Silicon Labs Platform, refer to [Software Requirements](/matter/{build-docspace-version}/matter-prerequisites/software-requirements). +- To run Matter OTA on Silicon Labs Platform, refer to [Software Requirements](/matter/{build-docspace-version}/matter-prerequisites/software-requirements). ## Setting up OTA Environment @@ -33,7 +33,7 @@ To run OTA on Matter over Wi-Fi, you need to build two different applications be ### Building OTA Application -To create and build Matter OTA using Simplicity Studio For SiWx917 SOC, refer to [build OTA application using Simplicity Studio](./05-build-ota-application-using-studio.md). +To create and build Matter OTA using Simplicity Studio For SiWx917 SoC, refer to [build OTA application using Simplicity Studio](./04-build-ota-application-using-studio.md). ### Creating Images @@ -143,15 +143,15 @@ Before running **ota-requestor** app, flash the **OTA-A** application(M4) and Wi ./chip-tool basicinformation read software-version 1 0 ``` -### Multi-OTA images for SiWx917 NCP/SoC +### Multi-Chip OTA images for SiWx917 NCP/SoC -Multi-OTA images can be created using `ota_multi_image_tool.py` which creates .ota files that contain additional TLV headers. +Multi-Chip OTA images can be created using `ota_multi_image_tool.py` which creates .ota files that contain additional TLV headers. >**Note**: SiWN917 NCP uses TLV tag 4 for Wi-Fi(TA) image upgrade. -#### Multi-OTA image creation on SiWN917 NCP +#### Multi-Chip OTA image creation on SiWN917 NCP -Multi-OTA on SiWN917 NCP supports application image upgrade, Wi-Fi(TA) image upgrade and combined image upgrade. +Multi-Chip OTA on SiWN917 NCP supports application image upgrade, Wi-Fi(TA) image upgrade and combined image upgrade. **Application Image Upgrade** @@ -177,7 +177,7 @@ commander gbl create SiWx917-lock-example.gbl --app SiWx917-lock-example.s37 --c ./scripts/tools/silabs/ota/ota_multi_image_tool.py create -v 0xFFF1 -p 0x8005 -vn 2 -vs "2.0" -da sha256 --app-input-file SiWx917-lock-example.gbl --wifi_ta_input_file SiWG917-B.2.14.5.0.0.10.rps combined_image.ota ``` -#### Multi-OTA image creation on SiWG917 SoC +#### Multi-Chip OTA image creation on SiWG917 SoC >**Note**: SiWG917 SoC uses TLV tag 1 for all image upgrades M4 alone, TA alone and combined image upgrade. diff --git a/sld407-matter-ota/05-build-ota-application-using-studio.md b/sld407-matter-ota/04-build-ota-application-using-studio.md similarity index 98% rename from sld407-matter-ota/05-build-ota-application-using-studio.md rename to sld407-matter-ota/04-build-ota-application-using-studio.md index a418a09..b472877 100644 --- a/sld407-matter-ota/05-build-ota-application-using-studio.md +++ b/sld407-matter-ota/04-build-ota-application-using-studio.md @@ -1,4 +1,4 @@ -# Building Matter applications for OTA Software Update +# Getting Started with OTA Updates in Matter Applications Using Simplicity Studio In the Matter OTA Software Update scenario, the running image (OTA-A) and the update image (OTA-B) are regular Matter application images and are built using the standard procedure. The only additional configuration required is the use of a higher software version in the update image. This page provides information about creation of OTA-A and OTA-B application for EFR32 and SiWx917 SOC Boards. diff --git a/sld407-matter-ota/index.md b/sld407-matter-ota/index.md index 437a1f8..67faa6a 100644 --- a/sld407-matter-ota/index.md +++ b/sld407-matter-ota/index.md @@ -4,5 +4,5 @@ The Over The Air (OTA) Software Update functionality is enabled by default for a - [**Matter OTA Bootloader**](./01-ota-bootloader.md) - [**Matter OTA Software Update**](./02-ota-software-update.md) -- [**Matter 917 SOC OTA Software Update**](./04-ota-software-update-soc.md) -- [**Matter OTA WiFi Project**](./05-build-ota-application-using-studio.md) +- [**Matter 917 SOC OTA Software Update**](./03-ota-software-update-soc.md) +- [**Matter OTA Project in Simplicity Studio**](./04-build-ota-application-using-studio.md) diff --git a/sld417-matter-dcl/index.md b/sld417-matter-dcl/index.md index 83c0bba..95b7f50 100644 --- a/sld417-matter-dcl/index.md +++ b/sld417-matter-dcl/index.md @@ -30,7 +30,7 @@ Below are the DCL Schemas that can be stored in the DCL and who is responsible f ## Access DCL -The Connectivity Standards Alliance offers two ways to access the DCL. You can access via a Web UI that can be found at [https://webui.dcl.csa-iot.org/](https://webui.dcl.csa-iot.org/), or you can install the latest version and use the CLI Client, [https://github.com/zigbee-alliance/distributed-compliance-ledger/releases](https://github.com/zigbee-alliance/distributed-compliance-ledger/releases). Note that the CLI Client is platform specific to either Linux or Mac OSX. +The Connectivity Standards Alliance offers two ways to access the DCL. You can access via a Web UI that can be found at [https://webui.dcl.csa-iot.org/](https://webui.dcl.csa-iot.org/), or you can install the latest version and use the CLI Client, [https://github.com/zigbee-alliance/distributed-compliance-ledger/releases](https://github.com/zigbee-alliance/distributed-compliance-ledger/releases). Note that the CLI Client is platform specific to either Linux or Mac OS. You will need to create an account with the DCL and wait for Connectivity Standards Alliance approval. Once approved for Vendor level access, you can enter your vendor information and add product information. **Silicon Labs recommends that you create a DCL Account sometime before Matter Certification Process is complete.** diff --git a/sld461-matter-secure-manufacturing/index.md b/sld461-matter-secure-manufacturing/index.md index d2ee96d..ffd9d02 100644 --- a/sld461-matter-secure-manufacturing/index.md +++ b/sld461-matter-secure-manufacturing/index.md @@ -9,7 +9,7 @@ When manufacturing a Matter product you must follow the Matter Security Requirem What should your Matter device include? - Device Attestation Credential (DAC) and private key unique to your device. This private key must be protected from unauthorized access. -- Onboarding Payload (Vendor ID (VID), and Product ID (PID) discriminator and passcode) +- Onboarding Payload (Vendor ID (VID), Product ID (PID), discriminator, and passcode) - Certification Declaration (CD) - Product Attestation Intermediate (PAI) diff --git a/sld464-matter-smg-migration-guide/index.md b/sld464-matter-smg-migration-guide/index.md index 79fe48e..0e14cb1 100644 --- a/sld464-matter-smg-migration-guide/index.md +++ b/sld464-matter-smg-migration-guide/index.md @@ -9,7 +9,7 @@ When manufacturing a Matter product you must follow the Matter Security Requirem What should your Matter device include? - Device Attestation Credential (DAC) and private key unique to your device. This private key must be protected from unauthorized access. -- Onboarding Payload (Vendor ID (VID), and Product ID (PID) discriminator and passcode) +- Onboarding Payload (Vendor ID (VID), Product ID (PID), discriminator, and passcode) - Certification Declaration (CD) - Product Attestation Intermediate (PAI) diff --git a/sld477-matter-quick-start-demo/01-wifi-quick-start-demo.md b/sld477-matter-quick-start-demo/01-wifi-quick-start-demo.md index bf10711..4529068 100644 --- a/sld477-matter-quick-start-demo/01-wifi-quick-start-demo.md +++ b/sld477-matter-quick-start-demo/01-wifi-quick-start-demo.md @@ -4,7 +4,7 @@ This Quick-Start Guide will demo the out-of-box experience for adding an SiWx917 ## Software Requirements -- Simplicity Studio v5 with SiSDK - 2025.6.0 + Silicon Labs Matter - 2.6.0 + WiSeConnect - 3.5.0 +- Simplicity Studio v5 with SiSDK - 2025.6.1 + Silicon Labs Matter - 2.6.1 + WiSeConnect - 3.5.1 - Simplicity Connect mobile App on Smartphone ## Hardware Requirements diff --git a/sld477-matter-quick-start-demo/02-thread-quick-start-demo.md b/sld477-matter-quick-start-demo/02-thread-quick-start-demo.md index 136fada..90e6e25 100644 --- a/sld477-matter-quick-start-demo/02-thread-quick-start-demo.md +++ b/sld477-matter-quick-start-demo/02-thread-quick-start-demo.md @@ -4,7 +4,7 @@ This Quick-Start Guide will demo the out-of-box experience for adding an EFR32MG ## Software Requirements -- Simplicity Studio v5 with SiSDK - 2025.6.0 + Silicon Labs Matter - 2.6.0 +- Simplicity Studio v5 with SiSDK - 2025.6.1 + Silicon Labs Matter - 2.6.1 - Simplicity Connect mobile App on Smartphone ## Hardware Requirements diff --git a/sld5257-matter-provisioning/matter-provisioning.md b/sld5257-matter-provisioning/matter-provisioning.md index 57a94c4..0442461 100644 --- a/sld5257-matter-provisioning/matter-provisioning.md +++ b/sld5257-matter-provisioning/matter-provisioning.md @@ -11,7 +11,7 @@ Matter defines three interfaces to access the provisioned data during runtime: - [CommissionableDataProvider](https://github.com/SiliconLabs/matter_extension/blob/main/third_party/matter_sdk/src/include/platform/CommissionableDataProvider.h) - [DeviceAttestationCredentialsProvider](https://github.com/SiliconLabs/matter_extension/blob/main/third_party/matter_sdk/src/credentials/DeviceAttestationCredsProvider.h) -In Silicon Labs devices, all three interfaces are implemented by the [ProvisionStorage](https://github.com/SiliconLabs/matter_extension/blob/main/third_party/matter_sdk/src/platform/silabs/provision/ProvisionStorage.h). +In Silicon Labs devices, all three interfaces are implemented by the [ProvisionStorage](https://github.com/SiliconLabs/matter_extension/blob/main/third_party/matter_support/provision/headers/ProvisionStorage.h). The provisioning script on this folder now supercedes the following tools: @@ -55,16 +55,14 @@ The GFW performs the following tasks: - Stores the Attestation Data on the main flash (CD, PAI, DAC) - Stores the size and offsets used to store the Attestation Data, along with the KeyId used to store the private-key. -The provisioning code resides under `extension/matter_extension` in the SiSDK directory tree for the SDK used in your Studio project, for example `SimplicityStudio/SDKs/sisdk_release_2/extension/matter_extension/provision`. +The provisioning code resides under `extension/matter_extension` in the SiSDK directory tree for the SDK used in your Studio project, for example `SimplicityStudio/SDKs/sisdk_release/extension/matter_extension/provision`. -The main source code of the GFW is located under `./generator`, while the board support is located under `./support`. -Pre-compiled images for the supported chips can be found in `./images`. +The board support is located under `./support`. Pre-compiled images for the supported chips can be found in `./images`. Backwards-compatibility script files are stored under `./modules/vX_Y` where X.Y matches the targeted version. The directory structure is as follows: - provision - - generator - images - modules - v1_0 diff --git a/sld57-matter-landing-page/index.md b/sld57-matter-landing-page/index.md index 2064f23..bb18010 100644 --- a/sld57-matter-landing-page/index.md +++ b/sld57-matter-landing-page/index.md @@ -8,7 +8,7 @@ Silicon Labs supports Matter on both 802.15.4 (Thread) and 802.11 (Wi-Fi) transp Device: SiWx917 SoC -![Silicon Labs - SiWx917 soc](resources/silabs-matter-siwx917.png) +![Silicon Labs - SiWx917 SoC](resources/silabs-matter-siwx917.png) ## Path for Development @@ -20,7 +20,7 @@ The [Silicon Labs Matter GitHub repo](https://github.com/SiliconLabs/matter) wil ## Other Resources -**To see release notes** containing a list of features and known issues, go to [Matter Release Notes on Silicon Labs Matter Extension](https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.0). +**To see release notes** containing a list of features and known issues, go to [Matter Release Notes on Silicon Labs Matter Extension](https://github.com/SiliconLabs/matter_extension/releases/tag/v2.6.1). **If you are new to Matter** or would like more information about Silicon Labs Matter-based products, see the [Matter content on silabs.com](https://www.silabs.com/wireless/matter). diff --git a/sld601-matter-application-development/index.md b/sld601-matter-application-development/index.md index 9c4450a..4685964 100644 --- a/sld601-matter-application-development/index.md +++ b/sld601-matter-application-development/index.md @@ -1,6 +1,6 @@ # Introduction -This section covers application development topics. Silicon Labs will build out this section over time. For Matter v2.6.0, we provide: +This section covers application development topics. Silicon Labs will build out this section over time. For Matter v2.6.1, we provide: - [Matter Scenes Quick Start Guide](./matter-scenes-quick-start-guide) - [Matter Event and Timer Guide](./matter-event-timer-guide.md)