SiliconLabsSoftware · silabs-vm · Jul 23, 2025 · Jul 7, 2025 · Jul 7, 2025 · Jul 7, 2025
@@ -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.
 

@@ -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
 

@@ -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:+<total size to read>

@@ -77,15 +77,15 @@ 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.
 
 ![Installing the Matter Extension](./resources/install-package-advanced-device.png)
 
 **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.
 

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

@@ -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**

@@ -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,26 +63,34 @@ 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
 
 - **MGM26 boards:**
   - 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)
 

@@ -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,28 +46,30 @@ 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`
 
 - SiWG917 SoC 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 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.
@@ -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
 

@@ -17,7 +17,7 @@ Use nmap with the following command:
     $ sudo nmap -sn <subnet>.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`
 

@@ -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)