From 4e373a5249844acf8cf0c82eb234dec683b06864 Mon Sep 17 00:00:00 2001 From: Biridaraju Vishwanath Date: Thu, 8 Sep 2022 14:24:00 +0000 Subject: [PATCH] Pull request #80: WIFI documentation update Merge in WMN_TOOLS/matter from wifi_docs_update_sep8 to silabs Squashed commit of the following: commit e4a89e2a30f3b431f8c8d79e98fc07a806e8c71d Author: riwaghe Date: Thu Sep 8 19:21:54 2022 +0530 WiFi document update commit c653f9a7f9bfa15d1173d85d84745374c05e94ce Author: riwaghe Date: Thu Sep 8 19:14:26 2022 +0530 WiFi document update commit 05d21a9a636405c856cc704eaf86a586938ac5e1 Author: riwaghe Date: Thu Sep 8 17:11:43 2022 +0530 WiFi document update SW_SETUP commit 926a6056b7c49a965d20323f6156d037955a0ddf Author: riwaghe Date: Thu Sep 8 17:08:57 2022 +0530 WiFi document update SW_SETUP commit 4371fbc8031215f79c1dd9dcb2d1c7b2cfb6c5bf Author: riwaghe Date: Thu Sep 8 17:06:49 2022 +0530 WiFi document update SW_SETUP commit d6de83e8d3d62b67406d9b742bb3a8a648021a6b Author: riwaghe Date: Thu Sep 8 17:05:32 2022 +0530 WiFi document update SW_SETUP commit cb3c7f8fdef4086e7f19c964d0b67ebff6ce6773 Author: riwaghe Date: Thu Sep 8 17:03:12 2022 +0530 WiFi document update SW_SETUP commit 00eab5fd6fd72f4ef70b808ad5180e32f5327aa7 Author: riwaghe Date: Thu Sep 8 16:57:11 2022 +0530 WiFi document update overview commit b1b49433816debb3a47c2bfd0f949667fd144b5a Author: riwaghe Date: Thu Sep 8 16:53:39 2022 +0530 WiFi document update overview commit 97df973853bdb58ba59daf345777a3c861879a5a Author: riwaghe Date: Thu Sep 8 16:38:59 2022 +0530 WiFi document update readme commit 257a1b8e8231fae358e74d3d1b8f8142cbd1e780 Author: riwaghe Date: Thu Sep 8 15:09:31 2022 +0530 WiFi document update --- docs/silabs/README.md | 6 +- docs/silabs/wifi/BUILD_CHIP_ENV.md | 155 ++--------------------------- docs/silabs/wifi/BUILD_PI_ENV.md | 75 +++++++------- docs/silabs/wifi/DEMO_OVERVIEW.md | 49 +++------ docs/silabs/wifi/FAQ.md | 20 ++-- docs/silabs/wifi/RUN_DEMO.md | 2 +- docs/silabs/wifi/SW_SETUP.md | 84 ++++++++++------ docs/silabs/wifi/WIFI_PREREQS.md | 22 ++-- 8 files changed, 141 insertions(+), 272 deletions(-) diff --git a/docs/silabs/README.md b/docs/silabs/README.md index 85111892d06d06..865002ee9ddd23 100644 --- a/docs/silabs/README.md +++ b/docs/silabs/README.md @@ -15,13 +15,11 @@ 4. [Creating a Thread Matter End Device](thread/BUILD_FLASH_MAD.md) 5. [Using the Chip-Tool](thread/CHIP_TOOL.md)

-4. [Matter over Wi-Fi](wifi/WIFI.md) +4. Matter over Wi-Fi 1. [Matter Wi-Fi Demo Overview](wifi/DEMO_OVERVIEW.md) - 2. [Building A Matter Wi-Fi End Device](wifi/BUILD_CHIP_ENV.md) + 2. [Building A Matter Wi-Fi End Device](wifi/SW_SETUP.md) 3. [Running Matter Demo over Wi-Fi](wifi/RUN_DEMO.md) - 4. [optional] - [Running Matter Demo over Wi-Fi using Android](wifi/WIFI_ANDROID.md)

5. Development using VS Code diff --git a/docs/silabs/wifi/BUILD_CHIP_ENV.md b/docs/silabs/wifi/BUILD_CHIP_ENV.md index 8251161b63e942..0583414ff5ae0d 100644 --- a/docs/silabs/wifi/BUILD_CHIP_ENV.md +++ b/docs/silabs/wifi/BUILD_CHIP_ENV.md @@ -1,8 +1,8 @@ # Building Your Wi-Fi Matter End Device and the Chip-Tool -# Build Environment using Linux +# Build Environment for Linux -This section will go through the steps required to build the demo using Linux. +This section will go through the steps required to build the chip-tool for Linux. > **Do not execute any commands on this page as ROOT (no _su_ required), unless > specified** @@ -17,7 +17,6 @@ Update the latest packages by typing following commands in terminal: $ sudo apt update $ sudo apt install ``` -
## Prerequisites for Matter (CHIP) project on Linux @@ -27,156 +26,18 @@ $ sudo apt install - Open the Linux terminal from Start menu - Install required packages on Ubuntu Laptop/PC using the following commands: - ```shell - $ sudo apt 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: - - - Download the - [Matter codebase](https://github.com/SiliconLabs/matter.git) from here - as follows: - - `$ git clone https://github.com/SiliconLabs/matter.git` - -- Sync submodules by running the following commands: - ```shell - $ cd matter - $ ./scripts/checkout_submodules.py --shallow --platform efr32 + $ sudo apt 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. Building Enviorment -- Environment Builds - - - Activate environment builds: - - `$ . scripts/bootstrap.sh` - - - Create a directory where binaries will be updated: - - `$ mkdir out` - -- **[Optional:** Increasing stack size **]**
  Navigate to - `git/matter` 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. - -> Please change the board referenced in the build command to your specific board -> before running the command. - -Build command for RS911x + EFR32MG12: - -`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx --wifi rs911x |& tee out/rs911x_lighting.log` - -Build command for WF200 + EFR32MG12: - -`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/wf200_lighting BRD41xxx is_debug=false --wifi wf200 |& tee out/wf200_lighting.log` - -Build command for RS911x + EFR32MG24: - -`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx disable_lcd=true show_qr_code=false use_external_flash=false --wifi rs911x` - -Build command for WF200 + EFR32MG24: - -`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/wf200_lighting BRD41xxx disable_lcd=true show_qr_code=false use_external_flash=false chip_build_libshell=false --wifi wf200` - -MG12 Boards: - -``` -BRD4161A, BRD4163A, BRD4164A -``` - -MG24 Boards: - -``` -BRD4186C, BRD4187C -``` - -By using the following flags we can enable or disable the features of lighting -application. - -1. `rs91x_wpa3_only` : To use rs91x wifi in wpa3 enable this flag while - building. - - ```shell - $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx rs91x_wpa3_only=true --wifi rs911x |& tee out/rs911x_lighting.log - ``` - -2. `chip_enable_wifi_ipv4` : To enable ipv4 of device add this flag while - building the application. - - ```shell - $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx chip_enable_wifi_ipv4=true --wifi rs911x |& tee out/rs911x_lighting.log - ``` - -3. `To enable different options for WPA/WPA2` : - - 1)Get the router address by entering `route -n` or ifconfig of ipconfig. - - 2)Enter router address in the browser and enter the appropriate username and - password. - - 3)Select appropriate band. - - 4)In security, select type. - - > Note: It is enabled by default for the rs911x, wf200. - -4. `Flag to get the complete logs without truncation` : - - ```shell - $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx segger_rtt_buffer_size_up=2068 --wifi rs911x |& tee out/rs911x_lighting.log - ``` - -Run the following: - -```shell -$ cd matter -$ -``` - -
- -> Look for build problems in `out/*.log`, which is the log file that was -> generated by the above command - -The generated software can be found in `out/rs911x_xxx/BRD4161A/*.log`. - -This is what you will flash into the EFR32. +- To build enviorment follow the `Software setup` and `Compiling chip-tool` steps given in [SW_SETUP](./SW_SETUP.md),
-## Compiling Chip-Tool - -- Build the ChipTool on a laptop which has Wi-Fi and Bluetooth LE -- Run the following commands: - - ```shell - $ cd $MATTER_WORKDIR/matter - $ ./scripts/examples/gn_build_example.sh examples/chip-tool out/standalone - ``` - - This will build chiptool in `out/standalone` - -For more information on how to flash a Silicon Labs device please consult the -[Flashing Silicon Labs Device](../general/FLASH_SILABS_DEVICE.md) page. - --- [Table of Contents](../README.md) | [Thread Demo](../thread/DEMO_OVERVIEW.md) | diff --git a/docs/silabs/wifi/BUILD_PI_ENV.md b/docs/silabs/wifi/BUILD_PI_ENV.md index ee32d26a0a854f..98a17e4287eef8 100644 --- a/docs/silabs/wifi/BUILD_PI_ENV.md +++ b/docs/silabs/wifi/BUILD_PI_ENV.md @@ -5,17 +5,19 @@ options # Building Environment using Raspberry Pi 4 -To flash the Ubuntu OS onto the SD card: +## To flash the Ubuntu OS onto the SD card: 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 Raspberry Pi 4 Imager 3. Click 'Choose OS' --> 'Other General-purpose OS' --> 'Ubuntu' --> 'Ubuntu - 22.04 64-bit server OS' + xx.xx 64-bit server OS' + > Note: Flash the latest version of Ubnutu Server (64-bit server OS for arm64 architecture) + 4. Click 'Storage' and select the 'SD card detect' -5. This Raspberry Pi 4's console can be accessed in multiple ways, refer to: - https://www.raspberrypi.com/documentation/computers/remote-access.html In - this guide, Raspberry Pi 4 is being accessed using Putty. +5. This Raspberry Pi 4's console can be accessed in multiple ways. + In [this guide](https://www.raspberrypi.com/documentation/computers/remote-access.html) + Raspberry Pi 4 is being accessed using Putty. 6. Enter the details like User name, Password, SSID and its password to connect to network. Click 'Save' 7. Click 'Write' and then 'Yes' when you are asked for permission to erase data @@ -27,69 +29,72 @@ To flash the Ubuntu OS onto the SD card: Inserting SD into Pi -On powering up the board, the red and green lights should start blinking. To -start using the Raspberry Pi: +On powering up the board, the red and green lights should start blinking. -1. Use this reference to find the IP address of your Raspberry Pi: - [Finding Your Raspberry Pi](../general/FIND_RASPI.md) -2. Once you find the IP address, launch Putty, select 'Session', enter the IP - address of the Raspberry Pi, and click 'Open' -3. 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", +## To start using the Raspberry Pi: +1. Use this [reference](../general/FIND_RASPI.md) to find the IP address of your Raspberry Pi. + +2. Once you find the IP address, launch Putty, select `Session`, enter the IP + address of the Raspberry Pi, and click `Open` +3. Enter the username and password given at the time of flashing and click + `Enter` + + > Note: If username and password not provided while flashing then by default + Username: ubuntu + Password: ubuntu + 4. Update the latest packages by running following commands in the terminal: - - > `$ sudo apt update` - - > `$ sudo apt install` - + ```shell + $ sudo apt update + $ sudo apt install + ``` 5. Install required packages using the following commands: + ```shell + $ 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 + ``` - > `$ 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: + > If you see any popups between installs, you can select 'Ok' or 'Continue' +## Build Environment +1. Installing prerequisites on Raspberry Pi 4 Follow the instructions in [the Project CHIP GitHub Site](https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/BUILDING.md), in the section "Installing prerequisites on Raspberry Pi 4". +2. To build enviorment follow the `Software setup` and `Compiling chip-tool` steps given in [Software setup](./SW_SETUP.md), + ## Bluetooth Setup Make sure Bluetooth LE (BLE) is up and running on Raspberry Pi. Raspberry Pi internally has some issues with BLE that may cause it to crash. Because BLE is used for commissioning on Matter, make sure BLE is running. -> `$ sudo systemctl status bluetooth.service` +`$ sudo systemctl status bluetooth.service` To stop BLE if it is already running: -> `$ sudo systemctl stop bluetooth.service` +`$ sudo systemctl stop bluetooth.service` To restart the Bluetooth service, first enable it: -> `$ sudo systemctl enable bluetooth.service` +`$ sudo systemctl enable bluetooth.service` When you check the status of the Bluetooth service, it will be inactive because it has been enabled but not restarted: -> `$ sudo systemctl status bluetooth.service` +`$ sudo systemctl status bluetooth.service` Restart the service: -> `$ sudo systemctl restart bluetooth.service` +`$ sudo systemctl restart bluetooth.service` Now the status of the service should be active and running: -> `$ sudo systemctl status bluetooth.service` +`$ sudo systemctl status bluetooth.service` --- diff --git a/docs/silabs/wifi/DEMO_OVERVIEW.md b/docs/silabs/wifi/DEMO_OVERVIEW.md index 3f86498bee2548..375116c16af8c5 100644 --- a/docs/silabs/wifi/DEMO_OVERVIEW.md +++ b/docs/silabs/wifi/DEMO_OVERVIEW.md @@ -1,14 +1,13 @@ # Matter over Wi-Fi Demo Overview -This document walks through the steps to build the Matter Lighting-app project -using +This document walks through the steps to build the Matter application i.e lighting, thermostat, door-lock for
+EFR32MG12 boards:
+`BRD4161A, BRD4163A, BRD4164A` -`EFR32 BRD4161A, BRD4163A, or BRD4164A + RS911X and EFR32 BRD4161A, BRD4163A, or BRD4164A + WF200`, +EFR32MG24 boards:
+`BRD4186C, BRD4187C` -`EFR32 BRD4186C, BRD4187C + RS911X, or EFR32 BRD4186C, BRD4187C + WF200`. - -Silicon Labs has two families of Wi-Fi adapters (1. RS911X 2. WF200). Both are -supported in this Wi-Fi port of Matter. +Silicon Labs has two families of Wi-Fi adapters (1.RS911X 2.WF200). Both are supported in this Wi-Fi port of Matter. ## Step 1: Matter Wi-Fi Prerequisites @@ -18,9 +17,6 @@ use case. 1. [Matter Wi-Fi Prerequisites](WIFI_PREREQS.md) - This page goes through the hardware and software (host side) required for - the demo. - ## Step 2: Building the Chip-Tool for Wi-Fi In order to run the Matter Wi-Fi demo you will need to run the Chip-Tool on one @@ -28,40 +24,21 @@ of two platforms, either Linux/Mac or Raspberry Pi. 1. [Build Linux Environment](BUILD_CHIP_ENV.md) - This page contains instructions to set up the build environment on a Linux - machine. The instructions provide build steps for the application and the - ChipTool. - -1. [Build Raspberry-Pi Environment](BUILD_PI_ENV.md) - - This page contains instructions to set up the build environment on the - Raspberry Pi. This is an alternative if you do not have a Linux machine. +2. [Build Raspberry-Pi Environment](BUILD_PI_ENV.md) ## Step 3: Building the Matter Accessory Device (MAD) for Wi-Fi -If you are running the demo, you can simply download the proper image for your -Matter Accessory Device from the -[Matter Software Artifacts Page](../general/ARTIFACTS.md). Otherwise if you wish -to build your Matter Accessory Device from scratch, you can begin with the -[Software Setup](SW_SETUP.md): +Follow the steps in [Software Setup](SW_SETUP.md) -1. [Software Setup](SW_SETUP.md) - - This page contains instructions to build the Lighting-app over Wi-Fi. Build - commands are provided for both the RS911x and WF200 adapters. +Build commands are provided for both the RS911x and WF200 adapters. ## Step 4: Running the Demo -1. [Running Matter Demo over Wi-Fi using Linux](RUN_DEMO.md) - - This contains instructions to run the Matter Wi-Fi demo using ChipTool - running on a Linux Machine (either Laptop or Raspberry Pi) - follow this - after successfully executing the above steps. - -1. [optional] [Running Matter Demo over Wi-Fi using Android](WIFI_ANDROID.md) +[Running Matter Demo over Wi-Fi using Linux](RUN_DEMO.md) - This part give you steps to run the Matter Wi-Fi demo using ChipTool running - on an Android phone (either Laptop or Raspberry Pi). +This contains instructions to run the Matter Wi-Fi demo using ChipTool +running on a Linux Machine (either Laptop or Raspberry Pi) - follow this +after successfully executing the above steps. --- diff --git a/docs/silabs/wifi/FAQ.md b/docs/silabs/wifi/FAQ.md index 884113809df3e6..47177da65fa2e4 100644 --- a/docs/silabs/wifi/FAQ.md +++ b/docs/silabs/wifi/FAQ.md @@ -6,14 +6,11 @@ ### 1. Bluetooth connection fails when trying to commission the system through the ChipTool: -
- **Command leading to error:** `$ out/standalone/chip-tool pairing ble-wifi 1122 mySSID myPassword 20202021 3840` -> Where `mySSID` is **your AP's SSID** and `mypassword` is **your AP's -> password**. +Where `mySSID` is **your AP's SSID** and `mypassword` is **your AP's password**.
@@ -57,7 +54,7 @@ > Where `mySSID` is **your AP's SSID** and `mypassword` is **your AP's > password**. -

+
### 2. Unsupported certificate format Error: @@ -180,7 +177,18 @@ network)
+### 9 . To enable different security options on AP/Router + +1. Get the router address by entering `route -n` or ifconfig of ipconfig. + +2. Enter router address in the browser and enter the appropriate username and + password. + +3. Select appropriate band. + +4. In security, select type(WPA/WPA2/WPA3). + --- [Table of Contents](../README.md) | [Thread Demo](../thread/DEMO_OVERVIEW.md) | -[Wi-Fi Demo](./DEMO_OVERVIEW.md) +[Wi-Fi Demo](./DEMO_OVERVIEW.md) \ No newline at end of file diff --git a/docs/silabs/wifi/RUN_DEMO.md b/docs/silabs/wifi/RUN_DEMO.md index cf0ff9dd436c64..b65a8d5761d23c 100644 --- a/docs/silabs/wifi/RUN_DEMO.md +++ b/docs/silabs/wifi/RUN_DEMO.md @@ -113,7 +113,7 @@ must be on the same Wi-Fi network as your RS9116 or WF200 and there cannot be another network interface on the device that is running the Chip-Tool. For instance, if you have an Ethernet connection as well as a Wi-Fi connection, you need to unplug the Ethernet connection and try running the Chip-Tool as in step -#3 above. +#2 above. 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 diff --git a/docs/silabs/wifi/SW_SETUP.md b/docs/silabs/wifi/SW_SETUP.md index 090225284abac2..87182091555f47 100644 --- a/docs/silabs/wifi/SW_SETUP.md +++ b/docs/silabs/wifi/SW_SETUP.md @@ -37,13 +37,34 @@ application images. # Create a directory where binaries will be updated/compiled called `out` $ mkdir out ``` +
+ +## Compiling the ChipTool + +In order to control the Wi-Fi Matter Accessory Device you will have to compile +and run the ChipTool on either a Linux, Mac or Raspberry Pi. The ChipTool 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. + +1. Build the Chip-Tool + + `$ ./scripts/examples/gn_build_example.sh examples/chip-tool out/standalone` + This will build chiptool in `out/standalone`.
-## Building Software -The following commands are for building the example. Depending on which device -you are using, select the appropriate build command to run. +## Building Matter Application + +The following commands are for building the Matter application. Depending on which device +you are using, select the appropriate command to build. + +Run the following: + +```shell +$ cd matter +$ +``` Build command for EFR32MG12 + RS911x: @@ -53,28 +74,40 @@ Build command for EFR32MG12 + WF200: `$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32 out/wf200_lighting_app BRD41xxx is_debug=false --wifi wf200 |& tee out/wf200_lighting.log` -In above command BRD41xxx represent the MG12 boards +In above command BRD41xxx represent the EFR32MG12 boards -> `BRD4161A, BRD4163A, BRD4164A` +`BRD4161A, BRD4163A, BRD4164A` Build command for EFR32MG24 + RS911x: -`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx disable_lcd=true show_qr_code=false use_external_flash=false --wifi rs911x` +`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx disable_lcd=true use_external_flash=false --wifi rs911x` Build command for EFR32MG24 + WF200: -`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/wf200_lighting BRD41xxx disable_lcd=true show_qr_code=false use_external_flash=false chip_build_libshell=false --wifi wf200` +`$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/wf200_lighting BRD41xxx disable_lcd=true use_external_flash=false chip_build_libshell=false --wifi wf200` -In above command BRD41xxx represent the MG24 boards +In above command BRD41xxx represent the EFR32MG24 boards -> `BRD4186C, BRD4187C` +`BRD4186C, BRD4187C` + +By using the following flags we can enable or disable the features of lighting application. + +1. `rs91x_wpa3_only` : Use this flag while building to enable wpa3 mode in rs91x wifi chip. + + ```shell + $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx rs91x_wpa3_only=true --wifi rs911x |& tee out/rs911x_lighting.log + ``` + Note: + 1. WPA/WPA2 is enabled by default for the rs911x + 2. Enabling WPA3 will disable WPA and WPA2 support + +2. `segger_rtt_buffer_size_up` : Flag to get the complete logs without truncation. + + ```shell + $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/efr32/ out/rs911x_lighting BRD41xxx segger_rtt_buffer_size_up=2068 --wifi rs911x |& tee out/rs911x_lighting.log + ``` -Run the following: -```shell -$ cd matter -$ -``` The generated software can be found in `out/rs911x_xxx/BRD4161A/*.out` for the RS9116 and in `out/wf200_xxx/BRD4161A/*.out` for the WF200. @@ -83,24 +116,15 @@ This is what you will flash onto the EFR32. For more information on how to flash the EFR32 please check out the page on [Flashing a Silicon Labs Device](../general/FLASH_SILABS_DEVICE.md) -## Compiling the ChipTool - -In order to control the Wi-Fi Matter Accessory Device you will have to compile -and run the ChipTool on either a Linux, Mac or Raspberry Pi. The ChipTool 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. - -1. Build the Chip-Tool - - `$ ./scripts/examples/gn_build_example.sh examples/chip-tool out/standalone` - - This will build chiptool in `out/standalone`. +
- After this, follow the steps on the page - '[Running the Matter Demo over Wi-Fi](RUN_DEMO.md)' to flash the binaries - and execute the demo. +**[Optional:** Increasing stack size **]**
  Navigate to + `matter` and open the file in the path + `examples/platform/efr32/FreeRTOSConfig.h`. Find the macro: + \``configMINIMAL_STACK_SIZE`\`, and change the macro value from `140` to + **`320`**. ---- +
[Table of Contents](../README.md) | [Thread Demo](../thread/DEMO_OVERVIEW.md) | [Wi-Fi Demo](./DEMO_OVERVIEW.md) diff --git a/docs/silabs/wifi/WIFI_PREREQS.md b/docs/silabs/wifi/WIFI_PREREQS.md index 5e792106fdba37..c5a22de08b0e89 100644 --- a/docs/silabs/wifi/WIFI_PREREQS.md +++ b/docs/silabs/wifi/WIFI_PREREQS.md @@ -20,32 +20,28 @@ follows: ![Overview](./images/wifi_setup.png) -> Note : For EFR32MG24 + RS911x hardware overview will be looking like same -> which is shown in the above diagram, only EFR32MG24 board need to change. +>Note: For EFR32MG24 + RS911x hardware overview will be looking like same which is shown in the above diagram, only MG12 >board need to replace with MG24. ## EFR32MG12 + WF200 Hardware Overview ![EFR32MG12 + WF200 connection ](./images/MG12_WF200.jpg) -
- -> Note : For EFR32MG24 + WF200 hardware overview also looking like same which is -> shown in the above diagram. Only EFR32MG24 board need to change. - +> Note : +> 1. For EFR32MG24 + WF200 hardware overview also looking like same which is shown in the above diagram. Only EFR32MG24 >board need to change. +> 2. Make sure on wf200 board interface slide button should in SPI mode and other slide button should be in "ON BOARD LDO" ## Hardware - Linux PC/Laptop **or** Raspberry Pi 4 (This is for running the ChipTool to commission and control the device) - Kits/Boards: - SLWSTK6000B Wireless Starter Kit main board - - BRD4161A/BRD4163A/BRD4164A/BRD4186C/BRD4187C daughter boards are - supported + - BRD4161A/BRD4163A/BRD4164A/BRD4186C/BRD4187C daughter boards are supported - [SLWRB4161A](https://www.silabs.com/development-tools/wireless/zigbee/slwrb4161a-efr32mg12-radio-board) - [SLWRB4163A](https://www.silabs.com/development-tools/wireless/zigbee/slwrb4163a-efr32mg12-radio-board) - [SLWRB4164A](https://www.silabs.com/development-tools/wireless/zigbee/slwrb4164a-efr32mg12-radio-board) - [XG24-RB4186C](https://www.silabs.com/development-tools/wireless/xg24-rb4186c-efr32xg24-wireless-gecko-radio-board) - [XG24-RB4187C](https://www.silabs.com/development-tools/wireless/xg24-rb4187c-efr32xg24-wireless-gecko-radio-board) - > BLE and Matter code run here + > BLE and Matter code run here - Wi-Fi Dev Kit, either [RS9116X-SB-EVK1](https://www.silabs.com/development-tools/wireless/wi-fi/rs9116x-sb-evk-development-kit) **or** @@ -55,7 +51,6 @@ follows: - Jumper Cables (included in the RS9116 kit) - Access point with Internet access - microSD card (32GB) (if using Raspberry Pi) -- **[Optional]** Android Mobile phone (If using the ChipTool on Android)
@@ -90,8 +85,9 @@ follows: 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) +1. Connect rs911x `USB-CDC` port to host machine. +2. [Setting up TeraTerm](https://docs.silabs.com/rs9116/wiseconnect/2.0/tera-term-setup) +3. [Updating the RS9116 Firmware](https://docs.silabs.com/rs9116/wiseconnect/2.0/update-evk-firmware) ---