Software Setup and Preliminaries

Software Setup

If you have not downloaded or cloned this repository, you can run the following commands on a Linux terminal running on either Linux machine, WSL or Virtual Machine to clone the repository and run bootstrap to prepare to build the sample application images.

  1. To download the SiliconLabs Matter codebase run the following commands.

     $ git clone https://github.com/SiliconLabs/matter.git

  2. Bootstrapping:

    $ cd matter
$ ./scripts/checkout_submodules.py --shallow --recursive --platform efr32
$ . scripts/bootstrap.sh
# Create a directory where binaries will be updated/compiled called `out`
$ mkdir out

Compiling the chip-tool

In order to control the Wi-Fi Matter Accessory Device you will have to compile and run the chip-tool on either a Linux, Mac or Raspberry Pi. The chip-tool builds faster on the Mac and Linux machines so that is recommended, but if you have access to a Raspberry Pi that will work as well.

  1. Build the chip-tool

    $ ./scripts/examples/gn_build_example.sh examples/chip-tool out/standalone

    This will build chip-tool in out/standalone.

Using the Matter Accessory Device (MAD) Pre-Built Binaries

If you are just running the Matter demo, and are not interested in building the Matter Accessory Device images from scratch, you can download the MAD images for Wi-Fi from this software release on the Matter Artifacts Page

Note: A pre-built image is not available for SiWx917 in SoC mode. It must be built from scratch in this release. Pre-built images will be provided in the next release.

Once you have downloaded the image you require for your device, you can skip forward to the instructions for running the demo.

If you are planning to build the Wi-Fi images from scratch, continue with this documentation.

Building the Matter Application

The following commands are for building the Matter application. Depending on which device you are using, select the appropriate command to build.

Note:

  1. The build commands given below are for the following applications: lighting-app, lock-app, light-switch-app, window-app

  2. In order to build applications other than those mentioned in # 1, (such as thermostat-app), substitute the appropriate application name & substitute /silabs/efr32/ with /efr32/ after the application name.

  3. Additional examples (such as onoff-plug-app) are provided in the /examples or /silabs_examples directory.

  4. In order to build applications from /silabs_examples (such as onoff-plug-app), substitute examples with silabs_examples.

  5. To build for EFR32MG24 host processors, substitute BRD41xxx in the build command with the appropriate MG24 board number from the Hardware Requirements Page.

Run the following:

$ cd matter
$ <run_appropriate_build_command_from_below>

Note: The image size currently exceeds the available flash with CHIP logging enabled.

Build command for EFR32MG24 + RS9116:

$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32 out/rs911x_lighting BRD41xxx disable_lcd=true use_external_flash=false chip_enable_ble_rs911x=true --wifi rs9116 |& tee out/rs911x_lighting.log

Build command for EFR32MG24 + SiWx917:

$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32 out/siwx917_lighting BRD41xxx disable_lcd=true use_external_flash=false chip_enable_ble_rs911x=true --wifi SiWx917 |& tee out/siwx917_lighting.log

Build command for EFR32MG24 + WF200:

$ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32 out/wf200_lighting BRD41xxx chip_build_libshell=false --wifi wf200 |& tee out/wf200_lighting.log

Build command for SiWx917 SoC processor:

./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/SiWx917 out/SiWx917_lighting BRD4325B |& tee out/soc_lighting.out

Note:

  1. LED and button features are enabled for SiWx917 SoC.

  2. LCD and QR code features are not enabled for SiWx917 SoC.

  3. Before building for SiWx917 SoC, you must first obtain the WiseMCU Combo SDK package and install it. See the Software Requirements page.

A complete list of hardware supported is included on the Hardware Requirements page.

Enable or disable the lighting application’s features using the following flags.

  1. rs91x_wpa3_only : Use this flag while building to enable wpa3 mode in rs91x wifi chip.

    $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32/ out/rs911x_lighting BRD41xxx rs91x_wpa3_only=true --wifi rs9116 |& 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

  1. segger_rtt_buffer_size_up : Flag to get the complete logs without truncation.

    $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32/ out/rs911x_lighting BRD41xxx segger_rtt_buffer_size_up=2068 --wifi rs9116 |& tee out/rs911x_lighting.log

  2. show_qr_code=false : Use this flag while building to disable QR code.

    $ ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32/ out/rs911x_lighting BRD41xxx show_qr_code=false --wifi rs9116 |& tee out/rs911x_lighting.log

Note:

  1. QR code is enabled by default for all except MG24

  2. QR code is disabled for MG24 because of lcd disable. It cannot be enabled using the flag.

  1. chip_enable_wifi_ipv4 : Use this flag while building to enable IPV4 (disabled by default).

    ./scripts/examples/gn_efr32_example.sh examples/lighting-app/silabs/efr32/ out/rs911x_lighting BRD41xxx chip_enable_wifi_ipv4=true --wifi rs9116 |& tee out/rs911x_lighting.log

The generated software can be found in out/rs911x_xxx/BRD41xxx/*.out for the RS9116, in out/siwx917_xxx/BRD41xxx/*.out for the SiWx917 and in out/wf200_xxx/BRD41xxx/*.out for the WF200.

This is what you will flash onto the EFR32 device or SiWx917 SoC device. For more information on flashing:

[Optional: Increasing stack size ]

Navigate to matter and open the file in the path examples/platform/silabs/efr32/FreeRTOSConfig.h. Find the macro: `configMINIMAL_STACK_SIZE`, and change the macro value from 140 to 320.