The use of nmap on the Mac may require a software download.
Use nmap with the following command:
`sudo nmap -sn
Example: `sudo nmap -sn 1-.4.148.0/24`
Among other returned values, you will see:
`Nmap scan report for ubuntu.silabs.com (10.4.148.44)`
`Host is up (0.00025s latency).`
`MAC Address: E4:5F:01:7B:CD:12 (Raspberry Pi Trading)`
And this is the Raspberry Pi at 10.4.148.44
***Arp***
Alternatively, use Arp with the following command:
`arp -a \| grep -i "b8:27:eb\|dc:a6:32"` | +| Windows | In the command prompt, use `nslookup` to fnd your Raspberry Pi.
Example: `nslookup ubuntu` | + +
+ +## Connecting to your Raspberry Pi over SSH + +| Platform | Strategy | +| -------- | -------- | +| Mac / Linux / Windows | Once you have found your Raspberry Pi's IP address, you can use Secure Shell (SSH) to connect to it over the command line with the following command:
`ssh
Example:
`ssh ubuntu@10.4.148.44`
`password: raspberrypi`
When prompted provide the raspberry pi's password, in the case of the Silicon Labs Matter Hub image the username is ***ubuntu*** and the password is ***raspberrypi*** | diff --git a/docs/silabs/general/FLASH_SILABS_DEVICE.md b/docs/silabs/general/FLASH_SILABS_DEVICE.md new file mode 100644 index 00000000000000..00aba6bb0557e5 --- /dev/null +++ b/docs/silabs/general/FLASH_SILABS_DEVICE.md @@ -0,0 +1,16 @@ +[<< Back to TOC](../README.md) + +# How to Flash a Silicon Labs Device + +Once you have an image built, you can flash it onto your EFR device (either a EFR32 development board or the Thunderboard Sense 2) over USB connected to your development machine. This can be done using either Simplicity Studio or the standalone Simplicity Commander. + +
+ +## Simplicity Commander +A link to download Simplicity Commander's standalone version is located along with documentation in the + - [Simplicity Commander Reference Guide](https://www.silabs.com/documents/public/user-guides/ug162-simplicity-commander-reference-guide.pdf) + +## Simplicity Studio: +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) +- [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/docs/silabs/general/ZAP.md b/docs/silabs/general/ZAP.md new file mode 100644 index 00000000000000..9fee9d54b20f4d --- /dev/null +++ b/docs/silabs/general/ZAP.md @@ -0,0 +1,161 @@ +[<< Back to TOC](../README.md) + +# ZCL Advanced Platform (ZAP) Tool for Matter + +## Overview + +EFR32 example applications provide a baseline demonstration of a lock device, +built using the Matter SDK and the Silicon Labs GeckoSDK. It can be controlled +by a CHIP controller over Openthread network. + +The EFR32 device can be commissioned over Bluetooth Low Energy (BLE) where the +device and the CHIP controller will exchange security information with the +Rendez-vous procedure. Thread Network credentials are provided to the EFR32 +device which will then join the network. + +The LCD on the Silicon Labs WSTK shows a QR Code containing the needed +commissioning information for the BLE connection and starting the Rendez-vous +procedure. + +The lock example is intended to serve both as a means to explore the workings of +CHIP, and a template for creating real products on the Silicon Labs platform. + +Each Matter application consists of the following layers: + +- Matter SDK: Source code necessary to communicate through the Matter network + over Thread or Wifi +- Data model layer in the form of clusters. There are two types of clusters: + - Utility Clusters: + - They represent common management and diagnostic features of a Matter + endpoint + - Identify cluster is an example of a Utility Cluster. Given a Node + ID, it can be used to Blink LED0 to the corresponding Silicon Labs + WSTK + - Application Clusters: + - These clusters represent functionalities specific to a given + application + - Door Lock Cluster is an example of an Application specific cluster. + This cluster contains commands to lock and unlock a door(door-lock + is represented by an LED), with options to set passwords and lock + schedules + +
+ +## Clusters + +Every Matter Application uses multiple clusters leveraged from the Zigbee +Cluster Library(ZCL). A cluster can be seen as a building block for the Data +Model of a Matter application. Clusters contains attributes, commands, and +events. Attributes are customizable variables specified by the Zigbee Advanced +Platform(ZAP) tool. Commands are sent to the application, which may respond with +data, LED flickering, lock actuation, etc. Events are notifications sent out by +the server. + +An application can have multiple Matter endpoints. Application endpoints +generally refer to one device, and inherits its information from the "cluster" +it belongs to. Utility clusters are required to be on the endpoint with ID 0. +Application clusters are assigned to endpoints with IDs 1 and higher. + +Some applications have callbacks that are left to be implemented by the device +manufacturer. For example, the storage and mangement of users and credentials in +the lock-app is left up to the application developer. + +
+ +## ZAP Tool + +The ZAP tool is built and maintained by Silicon Labs and developers in the ZAP opensource community. It inherits its name and +features from the Zigbee Cluster Library, which was the starting point for the Matter data model. ZAP is used +for generating code for Matter applications based on the Zigbee Cluster +Library and associated Matter code templates. + +The ZAP tool can be cloned using the following git command. This will create a +root level matter folder in your current directory. All following commands +should be run from the matter folder. + +> `$ git clone https://github.com/SiliconLabs/matter.git` + +The `run_zaptool.sh` script can be invoked +without arguments, or, you can provide the path to a ZAP file to be opened upon +launch. + +In the following examples, the ZAP file for the lock-app has been chosen. + +> `$ ./scripts/tools/zap/run_zaptool.sh ($PATH_TO_ZAP_FILE)` + +This shows the output of the run_zaptool script with no arguments. To load a new +zap file, click the application menu for Electron (Upper left corner of the +screen for macs), then click "Open File". Then navigate to the desired .zap +file. + + + +This shows the output of the run_zaptool script with a zap file given as an +argument, or after a .zap file has been opened in the ZAP UI. An Electron +application will open, pre-loaded with the information from the .zap file +provided as a command line argument. + + + +The Out of the box(OOB) example lock application has 2 endpoints. Endpoint 0 is +called the root node. It contains all Service and Device management clusters. In +general, any cluster or feature that is not specific to a device type belongs in +Endpoint 0. Examples of clusters one might find in Endpoint 0: Device Descriptor +cluster, Network Diagnostics cluster. + +Endpoint 1 contains information specific to the device type. Conveniently, the +ZAP tool offers a Door lock cluster, which contains Commands(lock, unlock, set +credential, etc..) and Attributes(Lock state, Require PIN) that a standard door +lock application might use. + +More endpoints can be added. Each endpoint acts like a port on a network interface. + +Endpoints contain clusters which are bundles of device functionality. Clusters have both a Client and a Server interface. In general the Client interface sends commands and the Server interface receives them. For instance a Light would implement the Server side of the on/off clusters. A Switch would implement the Client side of the same cluster. + +Click on Endpoint 1 on the left hand side of the application. The door lock +cluster should already be enabled as "Server". + + + +
+ +## Attributes + +Attributes are analogous to member variables of a class. Each attribute is +provided with generated setter/getter code from the ZAP tool. They can be +enabled or disabled for each cluster on a Matter endpoint. Some attributes are +required to be enabled, else the application will not function properly. There +is an option to add attributes to either the server code or client code. The ZAP +tool also allows you choose a storage space for attributes. Attributes can be +stored in standard RAM, Non-volatile memory or external memory. Each attribute +has a type, some are standard C types and some have specially defined enums. +Each attribute can be provided with a default starting value value. + +Click the settings wheel to enable/disable, choose a storage option, and choose +a default value for attributes, commands and events for Endpoint 1. + + + +
+ +## Commands + +Commands can be enabled/disabled like attributes. Some commands are required for +an application to function properly. Many of the functions run when a command is +received are implemented on the server side. But some of these are left up to +the application to define. In the EFR32 lock example, the set/get user and +credential functions are customizable as each implementation of a lock might +store these differently. + + + +
+ +## Generation of Code + +Once desirable cluster options are chosen for an application, one must save the +current zap configuration using the application menu in the upper left corner. +Then click generate in the top menu bar. The user will be prompted to choose a +save location for the generated ZAP code. In the Silicon Labs Matter repository, +the lock-app generated files belong in +matter/zzz_generated/lock-app/zap-generated . diff --git a/docs/silabs/general/images/zap_attributes.png b/docs/silabs/general/images/zap_attributes.png new file mode 100644 index 00000000000000..07d1f9ed0c1c98 Binary files /dev/null and b/docs/silabs/general/images/zap_attributes.png differ diff --git a/docs/silabs/general/images/zap_commands.png b/docs/silabs/general/images/zap_commands.png new file mode 100644 index 00000000000000..6e7e959758a9ef Binary files /dev/null and b/docs/silabs/general/images/zap_commands.png differ diff --git a/docs/silabs/general/images/zap_endpoint.png b/docs/silabs/general/images/zap_endpoint.png new file mode 100644 index 00000000000000..9f46e85883a2ad Binary files /dev/null and b/docs/silabs/general/images/zap_endpoint.png differ diff --git a/docs/silabs/general/images/zap_endpoint_1.png b/docs/silabs/general/images/zap_endpoint_1.png new file mode 100644 index 00000000000000..56d55137f09e72 Binary files /dev/null and b/docs/silabs/general/images/zap_endpoint_1.png differ diff --git a/docs/silabs/general/images/zap_intro.png b/docs/silabs/general/images/zap_intro.png new file mode 100644 index 00000000000000..f391a5a93ca041 Binary files /dev/null and b/docs/silabs/general/images/zap_intro.png differ diff --git a/docs/silabs/thread/BUILD_FLASH_MAD.md b/docs/silabs/thread/BUILD_FLASH_MAD.md new file mode 100644 index 00000000000000..6fab52e7226c1a --- /dev/null +++ b/docs/silabs/thread/BUILD_FLASH_MAD.md @@ -0,0 +1,70 @@ +[<< Back to TOC](../README.md) + +# How to Build and Flash the Matter Accessory Device (MAD) + +The Matter Accessory Device, such as the lighting-app, is the actual Matter +device that you will commission onto the Matter network and control using the +Chip-Tool. + +## Step 1: Get the Image File to Flash the MAD + +We have provided two ways to get the required image to flash the MAD. You can +use one of the following options: + +1. Using the pre-built image file +2. Building the image file from the '`connectedhomeip`' repository + +
+ +### **Using the Pre-Built Image File** + +All of the Matter Accessory Device image files are accessible through the +[Matter Artifacts Page](../general/ARTIFACTS.md). If you are using the pre-built +image file, you can skip forward to Step #2: Flashing the MAD. + +
+ +### **Building the Matter Image File from the Repository** + +**1. Clone the Silicon Labs Matter repository** + + Since you are reading this documentation it is assumed that you have already cloned the Silicon Labs Matter GitHub repository and have the right branch. If you have not you can follow the directions below. + +The Silicon Labs Matter repo is located in Github here: +https://github.com/SiliconLabs/matter. + +In order to clone the Matter repo you'll need to have Git installed on your +local machine. Once you have Git installed you can use the following command: + +> `$ git clone https://github.com/SiliconLabs/matter.git` + +Once you have cloned the repo, enter the repo and sync all the submodules with +the following command: + +> `$ cd matter`
`$ git submodule update --init --recursive` + +
+ +**2. Build the Matter Accessory Device** + +The Matter Accessory Device (lighting-app) can be built out of this repo. Documentation on how to build and use the lighting-app Matter Accessory Device is provided in this [README.md](../../../examples/lighting-app/efr32/README.md) + +Please note that you only need to build a single device for +the demo such as the lighting-app. If you wish to build other examples such as +the sleepy end device you are welcome to it is just not necessary for the demo. + +The build process puts all image files in the following location: + +> \
+ +## Step 2: Flash the Matter Accessory Device + +For more information on how to flash your Silabs development platform consider +the following instructions: +[How to Flash a Silicon Labs Device](../general/FLASH_SILABS_DEVICE.md) + +Once your Matter Accessory Device has been flashed it should show a QR code on +the LCD. If no QR Code is present it may be that you need to add a bootloader to +your device. diff --git a/docs/silabs/thread/CHIP_TOOL.md b/docs/silabs/thread/CHIP_TOOL.md new file mode 100644 index 00000000000000..5cabcca2b09908 --- /dev/null +++ b/docs/silabs/thread/CHIP_TOOL.md @@ -0,0 +1,180 @@ +[<< Back to TOC](../README.md) + +# Using the ChipTool + +The following commands show how to start a new Thread network from the local +OTBR, commission an EFR32 Matter End Device (Matter Accessory Device), and then +send the on/off commands with the `mattertool` automated script. + +| **Command** | **Usage** | +| ------------------------ | ------------------------------------------------------------------------- | +| `mattertool startThread` | Starts the thread network on the OTBR | +| `mattertool bleThread` | Starts commissioning of a Matter Accessory Device using the ChipTool | +| `mattertool on` | Sends the _on_ command to the Matter Accessory Device using the ChipTool | +| `mattertool off` | Sends the _off_ command to the Matter Accessory Device using the ChipTool | + +You can also use the full ChipTool command as usual (still using mattertool) + +> `$ mattertool levelcontrol read current-level 106 1` + +
+ +## Informational Section [Optional] + +### Image tree + +- home + - ubuntu (you are here) + - connectedhomeip (git repo: + https://github.com/project-chip/connectedhomeip.git) + - . + - ot-br-posix (git repo: + https://github.com/openthread/ot-br-posix.git) + - . + - scripts (in-house scripts) + - configurations.sh + - matterTool.sh + - setupOTBR.sh + +
+ +### Open Thread Border Router (OTBR) + +For information on what commits to use for the OTBR and RCP, please consult the +[Matter Repositories and Commit Hashes page](../general/COMMIT_HASHES.md) + +The pre-installed OTBR is configured for the infrastructure interface eth0. + +Bash script to modify, reinstall or update the OTBR: + +> `otbrsetup` + +This bash script centralizes and simplifies the local OTBR installation. + +Available commands: + +| **Command** | **Description** | +| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- | +| -h, --help | Prints help options | +| -if, --interface
+ +#### Usage: + +
+ +Change infrastructure to wlan0: `$ otbrsetup -if wlan0 -s`
Rerun full +install for eth0 interface: `$ otbrsetup -i` + +Change OTBR commit reference/version + +> `$ cd /home/ubuntu/ot-br-posix`
+ +> `$ git fetch`
+ +> `$ git checkout
+ +> `$ otbrsetup -u` + +
+ +### Matter - ChipTool + +For more information on the commit hashes used for this demo please consult the +following page: +[Matter Repositories and Commit Hashes](../general/COMMIT_HASHES.md) + +To change the ChipTool commit reference/version, follow these steps: + +> `$ cd /home/ubuntu/connectedhomeip`
+ +> `$ git fetch`
+ +> `$ git checkout
+ +> `$ mattertool buildCT` + +The mattertool script centralizes and simplifies the use of ChipTool and +starting a clean thread network. + +
+ +Available commands: + +| **Command** | **Description** | +| ------------ | ------------------------------------------------------------------------------------------------------------- | +| help | Prints help options | +| startThread | Start a new thread network and store the operational thread dataset for the commissioning purpose (bleThread) | +| bleThread | For Matter Ble thread commissioning with an EFR32 device | +| bleWifi | For Matter Ble WiFI commissioning with an EFR32 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 EFR32 device | +| on | Turn on the Light on the already commissioned EFR32 device | +| toggle | Toggle the Light on the already commissioned EFR32 device | +| parsePayload | Parse the given Payload (QrCode string) | +| rebuildCT | Rebuild the chip-tool | +| vars | Print the Variables in use by the script | + +
+ +Some options/arguments can be added to the command to update the values of the +variables used by the script. + +
+ +Available commands: + +| **Command** | **Description** | +| ------------------------ | ---------------------------------------------------- | +| -h, --help | Prints help options | +| -n, --nodeId DIGIT | Specify the Nodeid you are trying to reach | +| -e, --endpoint DIGIT | Specify an endpoint for the desired cluster | +| -d, --dataset HEX_STRING | Thread Operation Dataset to be provisioned | +| -s, --ssid STRING | WiFi AP SSID that the end devices need to connect to | +| -p, --password STRING | WiFi AP password | + +> These configurations are held until overwritten, cleared with cleanVars or +> when Raspberry Pi reboots. + +
+ +Active variables used by mattertool: + +| **Variable** | **Value** | +| --------------- | ----------------------------------------------------- | +| MATTER_ROOT | /home/ubuntu/connectedhomeip | +| CHIPTOOL_PATH | /home/ubuntu/connectedhomeip/out/standalone/chip-tool | +| NODE_ID | 31354 | +| THREAD_DATA_SET | \
+ +### Scripts Alias + +The commands presented above are linked to scripts. You can edit **_.bashrc_** +and rename the following alias to your liking. + +> `$ alias mattertool=‘source $HOME/scripts/matterTool.sh’`
+ +> `$ alias otbrsetup=‘source $HOME/scripts/setupOTBR.sh’` diff --git a/docs/silabs/thread/DEMO_OVERVIEW.md b/docs/silabs/thread/DEMO_OVERVIEW.md new file mode 100644 index 00000000000000..427811f8049ae6 --- /dev/null +++ b/docs/silabs/thread/DEMO_OVERVIEW.md @@ -0,0 +1,71 @@ +[<< Back to TOC](../README.md) + +# Matter Demo over Thread Overview + +This guide goes through the steps for running an example lighting-app for Matter +over Thread. Please look at [this](THREAD.md) file for an introduction to the +Matter over Thread setup. + +At a high level, we will walk through starting a thread network, commissioning a +new device to the thread network using BLE, and finally sending a basic OnOff +command to the end device. + +
+ +## Step 0: Prerequisites + +Before beginning your Matter project, consider the +[Matter Hardware and Software Prerequisites](./THREAD_PREREQS.md). Here you will find all the information you need on Silicon Labs hardware supported for Matter development. + +
+ +## Step 1: Setting up the Matter Hub (Raspberry Pi) + +The Matter Hub consists of the OTBR and the ChipTool running on a Raspberry Pi. +Silicon Labs has developed a Raspberry Pi image which can be downloaded and +flashed onto an SD Card that is then to be inserted into the Raspberry Pi. + +The Matter Controller sends IPv6 packets to the OTBR, which converts the IPv6 +packets into Thread packets. The Thread packets are then routed to the Silicon +Labs end device. + +Please refer to this guide for the setup: +[How to use Matter Hub \(Raspberry Pi\) Image](./RASPI_IMG.md) + +
+ +## Step 2: Build and Flash the RCP + +The Radio Co-Processor (RCP) is a thread device that connects to the Raspberry +Pi via USB. First, to flash the RCP, it should be connected to your laptop via +USB. Thereafter, it should be connected to the Raspberry Pi via USB as well. + +Information on building and flashing the RCP is located here: +[How To Build and Flash the RCP](RCP.md) + +
+ +## Step 3: Build and Flash the MAD + +The Matter Accessory Device (MAD) is the actual Matter device that will be +commissioned onto the Matter network and control using the ChipTool. + +Information on how to build and flash the Matter Accessory device is located +here: [How To Build and Flash the Matter Accessory Device](./MATTER_DEVICE.md) + +
+ +## Step 4: Commission and Control the MAD + +Once the Matter Accessory device has been flashed onto your hardware you can +commission it from the Matter Hub using the commands provided in the Raspberry +Pi image: + +| Command | Usage | +| ---------------------- | -------------------------------------------------- | +| mattertool startThread | Starts the thread network on the OTBR | +| mattertool bleThread | Starts commissioning of a MAD using ChipTool | +| mattertool on | Sends an **on** command to the MAD using ChipTool | +| mattertool off | Sends an **off** command to the MAD using ChipTool | + +
diff --git a/docs/silabs/thread/FAQ.md b/docs/silabs/thread/FAQ.md new file mode 100644 index 00000000000000..c84b2dc8374d0c --- /dev/null +++ b/docs/silabs/thread/FAQ.md @@ -0,0 +1,33 @@ +[<< Back to TOC](../README.md) + + + +# Frequently Asked Questions for Matter over Thread + +## Demo + +- Why are the `mattertool` commands not working after all the steps? + + - You should check if the Radio Co-Processor (RCP) image was build and/or + flashed correctly to the device + - Make sure you see a QR code on the display of the Matter Accessory + Device (MAD) + - Make sure the images being used to flash the Raspberry Pi, RCP and MAD + are correct + +
+ +- How can I find the IP address of my Raspberry Pi? + + - First, make sure the Raspberry Pi is connected to a network (ethernet or + wifi). This page has more information on the same: + [Setting up the Matter Hub (Raspberry Pi)](RASPI_IMG.md) + - Refer to this page for general questions on finding the Raspberry Pi on + your network: [Finding your Raspberry Pi](../general/FIND_RASPI.md) + - For more detailed information, please refer to this page: + [Raspberry Pi Remote Access](https://www.raspberrypi.com/documentation/computers/remote-access.html) + +
diff --git a/docs/silabs/thread/RASPI_IMG.md b/docs/silabs/thread/RASPI_IMG.md new file mode 100644 index 00000000000000..7d2aca86dac730 --- /dev/null +++ b/docs/silabs/thread/RASPI_IMG.md @@ -0,0 +1,72 @@ +[<< Back to TOC](../README.md) + +# Setting up the Matter Hub (Raspberry Pi) + +The Matter Hub consists of the Open Thread Border Router and the ChipTool +running on a Raspberry Pi. Silicon Labs has developed a Raspberry Pi image which +can be downloaded and flashed onto an SD Card for the Raspberry Pi. + +In short, the Matter Controller sends IPv6 packets to the OTBR, which converts +the IPv6 packets into Thread packets. The Thread packets are then routed to the +Silicon Labs end device. + +
+ +## How to use the Silicon Labs Matter Raspberry Pi Image (Matter Hub) + +
+ +The Raspberry Pi should be connected to a network - this could be ethernet or a +Wifi network. + +Please refer to this page on how to connect your Raspberry Pi to a wifi network: +[Connecting Raspberry Pi to Wifi](https://www.raspberrypi.com/documentation/computers/configuration.html#configuring-networking) + +
+ +### Step 1. Raspberry Pi Image Download + +The provided Raspberry Pi image is used as a Matter Controller with the OTBR. + +The image can be downloaded from the +[Matter Artifacts page](../general/ARTIFACTS.md) + +
+ +### Step 2. Flashing your Raspberry Pi + +[Raspberry Pi Disk Imager](https://www.raspberrypi.com/software/) can be used to +flash the SD Card which contains the operating system for the Raspberry Pi. + +Alternatively, a tool like [balenaEtcher](https://www.balena.io/etcher/) can be +used to flash the image to a micro SD card. + +> After flashing the SD card, insert it into the Raspberry Pi and reset the +> Raspberry Pi. Then, wait at least 10 seconds for it to come up and start the +> SSH server. + +
+ +### Step 3. Finding your Raspberry Pi on the Network + +Please see the [Finding Your Raspberry Pi page](../general/FIND_RASPI.md) for +more information on finding the Raspberry Pi on the local network. + +##### Raspberry Pi Login Credentials + +- user: **ubuntu** +- password: **raspberrypi** + +> When you log into the Raspberry Pi for the first time over SSH you may receive +> a warning regarding a 'key fingerprint' - this is normal and expected. You can +> get past this by just typing '_yes_' at the prompt. + +
+ +### Step 4: Using the Matter Hub + +The ChipTool, also referred to as the `mattertool`, is provided as a pre-built +application inside the Raspberry Pi image. + +Please refer to the ChipTool page for information on using the Matter Hub with +`mattertool` commands: [ChipTool page](./CHIP_TOOL.md) diff --git a/docs/silabs/thread/RCP.md b/docs/silabs/thread/RCP.md new file mode 100644 index 00000000000000..72f6bbd0eb9594 --- /dev/null +++ b/docs/silabs/thread/RCP.md @@ -0,0 +1,91 @@ +[<< Back to TOC](../README.md) + +# How to Build and Flash the Radio Co-Processor (RCP) + +The Radio Co-Processor is a 15.4 stack image flashed onto a Silicon Labs +development kit or Thunderboard Sense 2. The 15.4 stack on the development kit +communicates with the higher layers of the Thread stack running on the Raspberry +Pi over a USB connection. + +First, in order to flash the RCP, it should be connected to your laptop directly +over USB. + + + +
+ +## Step 1: Get or Build the Image File to Flash the RCP + +We have provided two ways to get the required image to flash the RCP. You can +use one of the following options: + +1. Using the pre-built image `ot-rcp` image file +2. Building the image file from the '`ot-efr32`' repository which is listed on + the [Matter Repositories and Commit Hashes page](../general/COMMIT_HASHES.md) + +
+ +### **Using the Pre-built Image File** + +All of the RCP image files are accessible through the +[Matter Artifacts Page](../general/ARTIFACTS.md). If you are using the pre-built +image file, you can skip forward to Step #2: Flashing the RCP. + +
+ +### **Building the Image File from the Repository** + +**1. Clone the ot-efr32 repository** + +The ot-efr32 repo is located in Github here: +https://github.com/SiliconLabs/ot-efr32. + +In order to clone the ot-efr32 repo, you'll need to have Git installed on your +local machine. Once you have Git installed you can use the following command: + +> `$ git clone https://github.com/SiliconLabs/ot-efr32.git` + +Once you have cloned the repo, enter the repo and sync all the submodules with +the following command: + +> `$ cd ot-efr32`
> `$ git submodule update --init --recursive` + +After updating the submodules you can checkout the correct branch or commit hash +for the system. Check the current branch and commit hash used here: +[Matter Branches and Commit Hashes](../general/COMMIT_HASHES.md) + +> `$ git checkout
+ +**2. Build the RCP** + +Once you have checked out the correct hash, follow the instructions here: +https://github.com/SiliconLabs/ot-efr32/blob/main/src/README.md to build the RCP +image for your EFR platform. + +This process will build several images for your board. The filename of the image +to be flashed onto the board to create an RCP is '`ot-rcp.s37`'. + +The output of the build process puts all the image files in the following +location: `
+ +## Step 2: Flash the RCP + +Once you get the RCP image '`ot-rcp.s37`' after either downloading it from the +link provided above, or building the image file from the repo as documented +above, you can flash it onto your device which will become the RCP attached to +your Raspberry Pi. Flashing of the device is done directly from your laptop and +not through the Raspberry Pi, so make sure that the device is connected directly +over USB to your laptop. Further information on flashing a Silicon Labs device +is located here: +[How to Flash a Silicon Labs Device](../general/FLASH_SILABS_DEVICE.md) + +Once you have flashed your RCP device you can disconnect it from you laptop and +connect it via USB to the Raspberry Pi. + +The Raspberry Pi's Open Thread Border Router can then use the RCP to communicate +with the Thread network. diff --git a/docs/silabs/thread/THREAD.md b/docs/silabs/thread/THREAD.md new file mode 100644 index 00000000000000..04be35a7d09a1c --- /dev/null +++ b/docs/silabs/thread/THREAD.md @@ -0,0 +1,40 @@ +[<< Back to TOC](../README.md) + +# Introduction + +**Matter 15.4 Setup**  + +A typical simple Matter 15.4 (Thread) network is setup as shown in the image +above. It consists of the following 4 elements: + +1. A **Controller** such as an app running on a phone or the ChipTool running + on a Linux box or Raspberry PI +2. An Open Thread Border Router (**OTBR**) running on a Linux box or Raspberry + Pi +3. A Radio Co-Processor (**RCP**) which the OTBR uses to communicate with + Thread network +4. An End Device such as a light or switch, which is the Matter Accessory + Device (**MAD**) + +The flow of the setup described above is as follows: + +1. The controller commissions the End Device directly over Bluetooth – this + makes the End Device join the Thread network and the CHIP fabric. +2. After commissioning, the Bluetooth connection is terminated and all further + communication is done over Matter. +3. The controller sends ZCL commands, such as the OnOff Toggle, and the End + Device performs the corresponding action; in the case of the OnOff Toggle, + this would turn the LED of the End Device on or off + +
+ +There are a few different ways that a Matter network can be built using a +combination of Silicon Labs hardware, a Raspberry Pi, and any external +controller(Macbook, Ubuntu, Android, etc.) + +The suggested method involves using a Raspberry Pi to function as both, the +controller, and the OTBR, with a Silicon Labs device as the MAD. + +An alternate configuration would be using a Macbook as the controller, a +Raspberry Pi as the OTBR, with a Silicon Labs Device as the MAD. This requires +additional routing between the controller and OTBR. diff --git a/docs/silabs/thread/THREAD_PREREQS.md b/docs/silabs/thread/THREAD_PREREQS.md new file mode 100644 index 00000000000000..d26a1d5b40ebc2 --- /dev/null +++ b/docs/silabs/thread/THREAD_PREREQS.md @@ -0,0 +1,95 @@ +[<< Back to TOC](../README.md) + +# Matter 15.4 Hardware and Software Prerequisites + +## Software Requirements + +### System Agnostic Software Requirements (Mac/ Linux/ Windows): + +1. SSH Client ([Putty](https://www.putty.org/) or similar): + > SSH client is used to communicate with the Raspberry Pi over a secure + > shell +1. [Raspberry Pi Disk Imager](https://www.raspberrypi.com/software/) + > Raspberry Pi Disk Imager is used to flash the SD Card which contains the + > operating system for the Raspberry Pi +1. [Flash tool](../general/FLASH_SILABS_DEVICE.md) + > Simplicity Commander standalone or Simplicity Studio is used to flash + > Silicon Labs hardware with firmware images for the RCP and the Matter + > Accessory Device +1. Git [Required for building images and development] + > Make sure Git is installed on the local machine that will be used to flash + > the devices to that the necessary repositories can be cloned locally and + > used as needed. + +
+ +### Windows-Specific Software Requirements + + These are requirements in addition to those mentioned above, if using a +Windows machine.
+ + A Unix-like command line: + +- [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/about) + **OR** +- [VirtualBox](https://www.virtualbox.org/) with + [Ubuntu 20.04.x LTS](https://ubuntu.com/download/desktop) + + > WSL or Virtual Box are used to emulate a virtual Linux machine, which is + > useful for accessing the Linux command line tools + +
+ +## Hardware Requirements + +1. Matter Hub (OTBR + ChipTool) + + Raspberry Pi 4 with an SD card with storage $\geq$ 64 GB + + > The Raspberry Pi 4 is used to run the Open Thread Border Router and the + > Chip Tool. In this documentation the combination of this software on the + > Raspberry Pi is also called the 'Matter Hub' + +
+ +2. Radio Co-Processor (RCP) + + The RCP is a Silicon Labs development board or ThunderBoard Sense 2 running + the Radio Co-Processor firmware for Thread. The following Silicon Labs + devices are supported: + + - EFR32MG based on EFR32 Mighty Gecko Wireless Starter Kit + - [EFR32MG12 Development Kit](https://www.silabs.com/development-tools/wireless/zigbee/efr32mg12-dual-band-starter-kit) + + **or** + + - Silicon Labs Thunderboard Sense 2 + - [Thunderboard Sense 2](https://www.silabs.com/development-tools/thunderboard/thunderboard-sense-two-kit) + +
+ +3. Matter Accessory Device (MAD) + + The following Silicon Labs devices are supported to function as a MAD: + + - **MG12 boards:** + + - [EFR32MG12 Development Kit](https://www.silabs.com/development-tools/wireless/zigbee/efr32mg12-dual-band-starter-kit) + - BRD4161A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm + - [SLWRB4161A](https://www.silabs.com/development-tools/wireless/zigbee/slwrb4161a-efr32mg12-radio-board) + - BRD4163A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm + - [SLWRB4163A](https://www.silabs.com/development-tools/wireless/zigbee/slwrb4163a-efr32mg12-radio-board) + - BRD4164A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm + - [SLWRB4164A](https://www.silabs.com/development-tools/wireless/zigbee/slwrb4164a-efr32mg12-radio-board) + - BRD4166A / SLTB004A / Thunderboard Sense 2 / 2.4GHz@10dBm + - [Thunderboard Sense 2](https://www.silabs.com/development-tools/thunderboard/thunderboard-sense-two-kit) + - BRD4170A / SLWSTK6000B / Multiband Wireless Starter Kit / + 2.4GHz@19dBm, 915MHz@19dBm + - [SLWRB4170A](https://www.silabs.com/development-tools/wireless/zigbee/slwrb4170a-efr32mg12-radio-board) +
+ + - **MG24 boards:** + - BRD4186C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@10dBm + - [XG24-RB4186C](https://www.silabs.com/development-tools/wireless/xg24-rb4186c-efr32xg24-wireless-gecko-radio-board) + - BRD4187C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm + - [XG24-RB4187C](https://www.silabs.com/development-tools/wireless/xg24-rb4187c-efr32xg24-wireless-gecko-radio-board) diff --git a/docs/silabs/thread/images/thread_overview.png b/docs/silabs/thread/images/thread_overview.png new file mode 100644 index 00000000000000..c20a9c5efd0cde Binary files /dev/null and b/docs/silabs/thread/images/thread_overview.png differ diff --git a/docs/silabs/wifi/BUILD_CHIP_ENV.md b/docs/silabs/wifi/BUILD_CHIP_ENV.md new file mode 100644 index 00000000000000..f28ea7f2d5717c --- /dev/null +++ b/docs/silabs/wifi/BUILD_CHIP_ENV.md @@ -0,0 +1,116 @@ +[<< Back to TOC](../README.md) + +# Build Environment using Linux + +This section will go through the steps required to build the demo using Linux. + +> **Do not execute any commands on this page as ROOT (no _su_ required), unless +> specified** + +
+ +## Prepare Linux Packages + +Update the latest packages by typing following commands in terminal: + +> `$ sudo apt update` + +> `$ sudo apt install` + +
+ +## Prerequisites for CHIP project on Linux + +### 1. Installing packages on Ubuntu Laptop/PC + +- Open the Linux terminal from Start menu +- Install required packages on Ubuntu Laptop/PC using the following commands: + + > `$ sudo apt-get install git gcc g++ pkg-config libssl-dev libdbus-1-dev \ + libglib2.0-dev libavahi-client-dev ninja-build python3-venv python3-dev \ + python3-pip unzip libgirepository1.0-dev libcairo2-dev libreadline-dev`
+ + +
+ +### 2. Matter codebase + +- Check out Matter codebase from GitHub: + + - Create a working directory - we will name it `matter` as part of this + example: + + > `$ mkdir matter` + + > `$ cd matter` + + > `$ MATTER_WORKDIR=pwd` + + --> We will use $MATTER_WORKDIR later + + - Download the + [Matter codebase](https://github.com/project-chip/connectedhomeip.git) + from here as follows: + > `$ git clone https://github.com/project-chip/connectedhomeip.git` + +- Sync submodules by running the following commands: + + > `$ cd connectedhomeip` + + > `$ git submodule update --init --recursive` + +- Environment Builds + + - Activate environment builds: + > `$ . scripts/bootstrap.sh` + - Create a directory where binaries will be updated: + > `$ mkdir out` + +- **[Optional:** Increasing stack size **]**
Navigate to + `matter/connectedhomeip` and open the file in the path + `examples/lighting-app/efr32/include/FreeRTOSConfig.h`. Find the macro: + \``configMINIMAL_STACK_SIZE`\`, and change the macro value from `140` to + **`320`**. + +
+ +### 3. Compiling the Lighting-app + +The following commands are for building the example. Depending on which device +you are using, select the appropriate build command to run. + +Build command for RS911x: +`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD4161A --wifi rs911x |& tee out/rs911x_lighting.out` + +Build command for WF200: +`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/wf200_lighting BRD4161A is_debug=false --wifi wf200 |& tee out/rs911x_lighting.out` + +Run the following: + +> `$ cd connectedhomeip` + +> `$
+ +> Look for build problems in `out/*.out`, which is the log file that was +> generated by the above command + +The generated software can be found in `out/rs911x_xxx/BRD4161A/*.out`. + +This is what you will burn into the EFR32. + +
+ +## Compiling ChipTool + +- Build the ChipTool on a laptop which has Wifi and BLE +- Run the following commands: + + > `$ cd $MATTER_WORKDIR/connectedhomeip`
+ + > `$ ./scripts/examples/gn_build_example.sh examples/chip-tool out/standalone` + + This will build chiptool in `out/standalone` + +Now, you will have all the binaries to flash onto MG12 platform. diff --git a/docs/silabs/wifi/BUILD_PI_ENV.md b/docs/silabs/wifi/BUILD_PI_ENV.md new file mode 100644 index 00000000000000..e5da598d1e68b8 --- /dev/null +++ b/docs/silabs/wifi/BUILD_PI_ENV.md @@ -0,0 +1,74 @@ +[<< Back to TOC](../README.md) + +# Building Environment using Raspberry Pi 4 + +1. Flash the Ubuntu OS onto the SD card +2. Insert the flashed SD card (directly or using a card reader) into the + laptop/PC that will run the Raspberry Pi Imager tool +3. Launch Raspberry Pi 4 Imager +4. Click on 'Choose OS' --> 'Other General-purpose OS' --> 'Ubuntu' --> 'Ubuntu 22.04 64-bit server OS' +5. Click 'Storage' and select the 'SD card detect' +6. This Raspberry Pi 4's console can be accessed in multiple ways, refer to: + https://www.raspberrypi.com/documentation/computers/remote-access.html +7. In this guide, Raspberru Pi 4 is being accessed using Putty. Enter the + details like User name, Password, SSID and it's password to connect to + network. Then, click 'Save' +8. Click 'Write' and then 'Yes' when you are asked for permission to erase data + on the SD card. It will then start flashing the OS onto the SD card +9. When it is done, click 'Continue' +10. Remove the SD card from the reader and insert it into the Raspberry Pi as + shown below: + + +
+
+11. On powering up the board, the red and green lights should start blinking
+12. Use this reference to find the IP address of your Raspberry Pi: [Finding Your Raspberry Pi](../general/FIND_RASPI.md)
+13. Once you find the IP address, launch Putty, select 'Session', enter the IP
+ address of the Raspberry Pi, and click 'Open'
+14. Enter the username and password given at the time of flashing and click
+ 'Enter'
+ If you don't give username and password default is user account "ubuntu" and password "ubuntu",
+
+15. Update the latest packages by running following commands in the terminal:
+
+ > `$ sudo apt update`
+
+ > `$ sudo apt install`
+
+16. Install required packages using the following commands:
+
+ > `$ sudo apt-get install git gcc g++ pkg-config libssl-dev libdbus-1-dev \
+ libglib2.0-dev libavahi-client-dev ninja-build python3-venv python3-dev \
+ python3-pip unzip libgirepository1.0-dev libcairo2-dev libreadline-dev'
+
+ + > If you see any popups between installs, you can select 'Ok' or 'Continue' + +## Installing prerequisites on Raspberry Pi 4 + Finally, install some Raspberry Pi specific dependencies + + refer this link : https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/BUILDING.md + In above link follow section "Installing prerequisites on Raspberry Pi 4". + +## Bluetooth setup + Make sure BLE is up and running on Raspberry-Pi. + Raspberry pi internally has some issue in BLE and sometimes it crash in middle, BLE is used for + commissioning purpose on Matter So make sure BLE is running. + + Use below commands to turn on or restart bluetooth on Raspberry - Pi. + + To stop BLE if it is already running. + `$ sudo systemctl stop bluetooth.service` + + To restart the Bluetooth service, we need to enable it first as we did before. Hence, we have been using the same systemctl command with a one word change e.g. enable. + `$ sudo systemctl enable bluetooth.service` + + When you check the status of a Bluetooth service, you will find it inactive because we haven’t restarted the service yet. + `$ sudo systemctl status bluetooth.service` + + So, one needs to restart the Bluetooth service to make it active and running. So we have executed the query below. + `$ sudo systemctl restart bluetooth.service` + + After this command, when we have checked the status of the Bluetooth service, we found it active and running. + `$ sudo systemctl status bluetooth.service` diff --git a/docs/silabs/wifi/DEMO_OVERVIEW.md b/docs/silabs/wifi/DEMO_OVERVIEW.md new file mode 100644 index 00000000000000..72082af46c5a18 --- /dev/null +++ b/docs/silabs/wifi/DEMO_OVERVIEW.md @@ -0,0 +1,60 @@ +[<< Back to TOC](../README.md) + +# Matter over Wifi Demo Overview + +This document walks through the steps to build Matter Lighting-app project using +EFR32 BRD4161A + RS911X and EFR32 BRD4161A + WF200. Silicon Labs has two +families of WiFi adatpers (1. RS911X 2. WF200). Both are supported in this WiFi +port of Matter. + +
+ +## Setup Overview + + + +## EFR32MG12 + WF200 Connection + + + +
+ + + +This document walks through the steps to build the Matter Lighting-app project +using EFR32 BRD4161A + RS911X and EFR32 BRD4161A + WF200. + +Follow this sequence if you are setting up for the first time: + +1. [Matter Wifi Prerequisites](WIFI_PREREQS.md) + + This page goes through the hardware and software (host side) required for + the demo - make sure you have all the necessary hardware available before + continuing. + +2. [Build Linux Environment](BUILD_CHIP_ENV.md) + + This part gives you steps to setup the build environment on a Linux machine. + The instructions gives you build steps for the application and the ChipTool. + +3. [Build Raspberry-Pi Environment](BUILD_PI_ENV.md) + + This section documents steps to setup the build environment on the Raspberry + Pi. + +4. [Software Setup](SW_SETUP.md) + + This part gives you steps to build the Lighting-app over Wifi. Two separate + build commands are mentioned for RS911x and WF200 adapters to use + accordingly. + +5. [Running Matter Demo over Wifi using Linux](RUN_DEMO.md) + + This part give you steps to run the Matter Wifi demo using ChipTool running + on a Linux Machine (either Laptop or Raspberry Pi) - follow this after + successfully executing the above steps. + +6. [optional] [Running Matter Demo over Wifi using Android](WIFI_ANDROID.md) + + This part give you steps to run the Matter Wifi demo using ChipTool running + on an Android phone (either Laptop or Raspberry Pi). diff --git a/docs/silabs/wifi/FAQ.md b/docs/silabs/wifi/FAQ.md new file mode 100644 index 00000000000000..765811ec0777d1 --- /dev/null +++ b/docs/silabs/wifi/FAQ.md @@ -0,0 +1,3 @@ +[<< Back to TOC](../README.md) + +# Frequently Asked Questions for Matter over Wifi diff --git a/docs/silabs/wifi/RUN_DEMO.md b/docs/silabs/wifi/RUN_DEMO.md new file mode 100644 index 00000000000000..deb82f3b82b1ef --- /dev/null +++ b/docs/silabs/wifi/RUN_DEMO.md @@ -0,0 +1,115 @@ +[<< Back to TOC](../README.md) + +# Runing the Matter Demo over Wifi + +## Flashing images/binaries on MG12 platform using Ozone + +1. Plug in the WSTK and EFR into the laptop + +2. Launch Ozone - this will display a GUI + +3. In 'New Project Wizard': + + 1. Click the three-dots on the 'Device' tab and select 'Manufacturer' as + '`Silicon Labs`' + 2. Select 'Device' as '`EFR32MG12PXXF1024`' + 3. Click 'OK' + 4. The 'Register set' tab will get filled automatically + 5. 'Peripherals' tab need not be changed as it is optional + +4. Click 'Next' - the window that is displayed will contain: + + - Serial Number: Read from device + - Target Interface: JTAG + - Speed: 4MHz + - Host Interface: USB + - There will be one product in the 'Emulators connected via USB' tab - + select this and click 'Next' + +5. Click on the 'Silicon Labs device' detected, and then click 'Next' + +6. You will be asked to select the image/binary to be loaded: click on the + three-dots on that tab and navigate to '`out/rs911x_lighting/BRD4161A`' + through 'Browse', select the file named `chip-efr32-lighting-example.out` and + click 'Next', this is the same image which we built in previous step. + +7. Make sure the next screen has 'Initial PC' selected as 'ELF Entry Point' - + click 'Finish' + + > Ignore Diagnostics warning about 'FreeRTOS' detected - click 'Continue' + +8. Select 'Download and Reset Program' in the dropdown next to the Power button + on the top left of the page + + > The EFR32MG12 will be erased and programmed + +9. Run the image by clicking the 'Play' button on the top left (or press the F5 + key) + + > The output of the EFR32 can be viewed on the console of the Ozone GUI + +10. **[Optional]** This step is for when the device has already been flashed and + is being used for testing/debug purposes: + + > If you are restarting the device and do not need to re-flash the EFR + > firmware then you can use these commands (JLinkExe & JLinRTTClient). The + > following commands will provide you with a serial cossole of the EFR32 + >
+ + > `$ konsole -e JLinkExe -device EFR32MG12PXXXF1024 -if JTAG -speed 4000 -autoconnect 1 &` + > (Put it in the background) + + > `$ sleep 3` + + > `$ konsole -e JLinkRTTClient &` + + > You may need to press
+ +## Demo Execution - Commissioning a Wifi Device using ChipTool for Linux + +> Commissioning can also be done using ChipTool running either on +> Linux/Raspberry Pi + +1. Get the SSID and PSK of the Wifi network (WPA2 - Security) you are connected + to +2. Position the hardware near the laptop as the BLE antenna on the BRD4161A is + slightly weak +3. Run the following: + + > `$ cd $MATTER_WORKDIR/connectedhomeip` + + ### Commissioning Command: + + > `$ out/standalone/chip-tool pairing ble-wifi 1122 $SSID $PSK 20202021 3840` + + > The node ID used here is 1122. This will be used in future comands. + > '\$SSID' is a placeholder for your Wifi SSID and '\$PSK' is a placeholder + > for the password of your Wifi network. + +4. Turning **on** the LED on the EFR32MG12:
+ `$ out/standalone/chip-tool onoff on 1122 1` +5. Turning **off** the LED on the EFR32MG12:
+ `$ out/standalone/chip-tool onoff off 1122 1` + +> If there are any failures, run the following command and then re-run the +> ChipTool command: `$ rm -rf /tmp/chip_*` + +> As the device remembers the Access Point credentials given for commissioning, +> if you want to run the demo multiple times, do a factory reset by pressing the +> BTN0 on EFR32 MG12 for about 6-7seconds, you will observe the LED0 and LED1 +> flashes 3 times and QR code appears again on the LCD screen. + +
+ +The commissioning command mentioned above does the following: + +- ChipTool scans BLE and located the SiLabs device that uses the specified + discriminator +- Sends the Wifi SSID and Passkey +- The SiLabs device will join the Wifi network and get an IPv4 address. It + then starts providing mDNS records on IPv4 and IPv6 +- ChipTool then locates the SiLabs device over Wifi and establishes + operational certificates +- Future communications (tests) will then happen over Wifi diff --git a/docs/silabs/wifi/SW_SETUP.md b/docs/silabs/wifi/SW_SETUP.md new file mode 100644 index 00000000000000..0737c1371a6be8 --- /dev/null +++ b/docs/silabs/wifi/SW_SETUP.md @@ -0,0 +1,92 @@ +[<< Back to TOC](../README.md) + +# Software Setup and Preliminaries + +## Software Setup + +Run below commands on a Linux terminal running on either Linux machine, WSL or +Virtual Machine. + +1. To download the + [Matter codebase](https://github.com/project-chip/connectedhomeip.git) run + the following commands. Create a working directory - we will name it `matter` + as part of this example flow: + + > `$ mkdir matter` + + > `$ cd matter` + + > `$ MATTER_WORKDIR=pwd` --> We will use $MATTER_WORKDIR later + + > `$ git clone https://github.com/project-chip/connectedhomeip.git` + +2. Bootstrapping: + + > `$ cd connectedhomeip` + + > `$ git submodule update --init --recursive` + + > `$ . scripts/bootstrap.sh` + + Create a directory where binaries will be updated/compiled. We will call it + `out` in this example: + + > `$ mkdir out` + +
+ +## Building Software + +The following commands are for building the example. Depending on which device +you are using, select the appropriate build command to run. + +Build command for RS911x: +`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD4161A --wifi rs911x |& tee out/rs911x_lighting.out` + +Build command for WF200: +`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/wf200_lighting BRD4161A is_debug=false --wifi wf200 |& tee out/rs911x_lighting.out` + +Run the following: + +> `$ cd connectedhomeip` + +> `$
+ +## Software + +- Ozone to flash the images generated + - Windows: [Download Ozone](https://www.segger.com/downloads/jlink/) + > Search for "Ozone - The J-Link Debugger" and download the latest + > Windows installer depending on 32/64bit and install it. + - Linux: + [Download Ozone](https://www.segger.com/downloads/jlink/Ozone_Linux_x86_64.deb) + and install it +- [otional] ChipTool Android mobile application: + [Download](https://confluence.silabs.com/download/attachments/240625466/chip-app.zip?version=1&modificationDate=1647837891300&api=v2), + extract, and install to the Android mobile; [TODO: the link is a confluence + link!] +- Raspberry Pi imager tool: [Download](https://www.raspberrypi.com/software/) +- Upgrade firmware on RS9116 EVK: + [Reference](http://draft-docs.suds.silabs.net/rs9116-wiseconnect/2.5/wifibt-wc-getting-started-with-pc/update-evk-firmware) + +
+ +## RS9116: Steps to Update Firmware + +Pre-Built Rs9116 firmware is available on the +[Matter Artifacts page](../general/ARTIFACTS.md) + +1. [Setting up TeraTerm](https://docs.silabs.com/rs9116/wiseconnect/2.0/tera-term-setup) +2. [Updating the RS9116 Firmware](https://docs.silabs.com/rs9116/wiseconnect/2.0/update-evk-firmware) diff --git a/docs/silabs/wifi/images/MG12_WF200.jpg b/docs/silabs/wifi/images/MG12_WF200.jpg new file mode 100644 index 00000000000000..db1c0b53fc2322 Binary files /dev/null and b/docs/silabs/wifi/images/MG12_WF200.jpg differ diff --git a/docs/silabs/wifi/images/sd_into_pi.png b/docs/silabs/wifi/images/sd_into_pi.png new file mode 100644 index 00000000000000..dfe023cdc17d47 Binary files /dev/null and b/docs/silabs/wifi/images/sd_into_pi.png differ diff --git a/docs/silabs/wifi/images/wifi_code_edit.png b/docs/silabs/wifi/images/wifi_code_edit.png new file mode 100644 index 00000000000000..5670f3a82e3864 Binary files /dev/null and b/docs/silabs/wifi/images/wifi_code_edit.png differ diff --git a/docs/silabs/wifi/images/wifi_setup.png b/docs/silabs/wifi/images/wifi_setup.png new file mode 100644 index 00000000000000..4ca47f9b40e78f Binary files /dev/null and b/docs/silabs/wifi/images/wifi_setup.png differ