@@ -11,8 +11,10 @@ An example showing the use of CHIP on the Silicon Labs EFR32 MG12 and MG24.
1111 - [ Mac OS X] ( #mac-os-x )
1212 - [ Flashing the Application] ( #flashing-the-application )
1313 - [ Viewing Logging Output] ( #viewing-logging-output )
14- - [ SeggerRTT] ( #segger-rtt )
15- - [ Serial Console] ( #console-log )
14+ - [ SEGGER RTT] ( #segger-rtt )
15+ - [ Console Log] ( #console-log )
16+ - [ Configuring the VCOM] ( #configuring-the-vcom )
17+ - [ Using the console] ( #using-the-console )
1618 - [ Running the Complete Example] ( #running-the-complete-example )
1719 - [ Notes] ( #notes )
1820 - [ On Border Router:] ( #on-border-router )
@@ -32,7 +34,7 @@ An example showing the use of CHIP on the Silicon Labs EFR32 MG12 and MG24.
3234> frequent releases thoroughly tested and validated. Developers looking to
3335> develop matter products with silabs hardware are encouraged to use our latest
3436> release with added tools and documentation.
35- > [ Silabs Matter Github] ( https://github.com/SiliconLabs/matter/releases )
37+ > [ Silabs matter_sdk Github] ( https://github.com/SiliconLabsSoftware/matter_sdk/tags )
3638
3739## Introduction
3840
@@ -78,8 +80,8 @@ the Silicon Labs platform.
7880- Supported hardware:
7981
8082 - > For the latest supported hardware please refer to the
81- > [ Hardware Requirements] ( https://github. com/SiliconLabs/ matter/blob/ latest/docs/silabs/general/HARDWARE_REQUIREMENTS.md )
82- > in the Silicon Labs Matter Github Repo
83+ > [ Hardware Requirements] ( https://docs.silabs. com/matter/latest/matter-prerequisites/hardware-requirements )
84+ > in the Silicon Labs Matter Documentation
8385
8486 MG21 boards: Currently not supported due to RAM limitation.
8587
@@ -103,52 +105,52 @@ the Silicon Labs platform.
103105
104106* Build the example application:
105107
106- cd ~/connectedhomeip
107- ./scripts/examples/gn_silabs_example.sh ./examples/air-quality-sensor-app/silabs/ ./out/air-quality-sensor-app BRD4187C
108+ cd ~/connectedhomeip
109+ ./scripts/examples/gn_silabs_example.sh ./examples/air-quality-sensor-app/silabs/ ./out/air-quality-sensor-app BRD4187C
108110
109111- To delete generated executable, libraries and object files use:
110112
111- $ cd ~/connectedhomeip
112- $ rm -rf ./out/
113+ $ cd ~/connectedhomeip
114+ $ rm -rf ./out/
113115
114116 OR use GN/Ninja directly
115117
116- $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
117- $ git submodule update --init
118- $ source third_party/connectedhomeip/scripts/activate.sh
119- $ export SILABS_BOARD=BRD4187C
120- $ gn gen out/debug
121- $ ninja -C out/debug
118+ $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
119+ $ git submodule update --init
120+ $ source third_party/connectedhomeip/scripts/activate.sh
121+ $ export SILABS_BOARD=BRD4187C
122+ $ gn gen out/debug
123+ $ ninja -C out/debug
122124
123125- To delete generated executable, libraries and object files use:
124126
125- $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
126- $ rm -rf out/
127+ $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
128+ $ rm -rf out/
127129
128130* Build the example with Matter shell
129131
130- ./scripts/examples/gn_silabs_example.sh examples/air-quality-sensor-app/silabs/ out/air-quality-sensor-app-app BRD4187C chip_build_libshell=true
132+ ./scripts/examples/gn_silabs_example.sh examples/air-quality-sensor-app/silabs/ out/air-quality-sensor-app-app BRD4187C chip_build_libshell=true
131133
132134* Build the example as Intermittently Connected Device (ICD)
133135
134- $ ./scripts/examples/gn_silabs_example.sh ./examples/air-quality-sensor-app/silabs/ ./out/air-quality-sensor-app-app_ICD BRD4187C --icd
136+ $ ./scripts/examples/gn_silabs_example.sh ./examples/air-quality-sensor-app/silabs/ ./out/air-quality-sensor-app-app_ICD BRD4187C --icd
135137
136138 or use gn as previously mentioned but adding the following arguments:
137139
138- $ gn gen out/debug '--args=SILABS_BOARD="BRD4187C" enable_sleepy_device=true chip_openthread_ftd=false chip_build_libshell=true'
140+ $ gn gen out/debug '--args=SILABS_BOARD="BRD4187C" enable_sleepy_device=true chip_openthread_ftd=false chip_build_libshell=true'
139141
140142* Build the example with pigweed RCP
141143
142- $ ./scripts/examples/gn_silabs_example.sh examples/air-quality-sensor-app/silabs/ out/air-quality-sensor-app-app_rpc BRD4187C 'import("//with_pw_rpc.gni")'
144+ $ ./scripts/examples/gn_silabs_example.sh examples/air-quality-sensor-app/silabs/ out/air-quality-sensor-app-app_rpc BRD4187C 'import("//with_pw_rpc.gni")'
143145
144146 or use GN/Ninja Directly
145147
146- $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
147- $ git submodule update --init
148- $ source third_party/connectedhomeip/scripts/activate.sh
149- $ export SILABS_BOARD=BRD4187C
150- $ gn gen out/debug --args='import("//with_pw_rpc.gni")'
151- $ ninja -C out/debug
148+ $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
149+ $ git submodule update --init
150+ $ source third_party/connectedhomeip/scripts/activate.sh
151+ $ export SILABS_BOARD=BRD4187C
152+ $ gn gen out/debug --args='import("//with_pw_rpc.gni")'
153+ $ ninja -C out/debug
152154
153155For more build options, help is provided when running the build script without
154156arguments
@@ -159,15 +161,14 @@ arguments
159161
160162- On the command line:
161163
162- $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
163- $ python3 out/debug/matter-silabs-air-quality-sensor-app-switch-example.flash.py
164+ $ cd ~/connectedhomeip/examples/air-quality-sensor-app/silabs
165+ $ python3 out/debug/matter-silabs-air-quality-sensor-app-switch-example.flash.py
164166
165167- Or with the Ozone debugger, just load the .out file.
166168
167169All EFR32 boards require a bootloader, see Silicon Labs documentation for more
168- info. Pre-built bootloader binaries are available in the Assets section of the
169- Releases page on
170- [ Silabs Matter Github] ( https://github.com/SiliconLabs/matter/releases ) .
170+ info. Pre-built bootloader binaries are available on the
171+ [ Matter Software Artifacts page] ( https://docs.silabs.com/matter/latest/matter-prerequisites/matter-artifacts#matter-bootloader-binaries ) .
171172
172173## Viewing Logging Output
173174
@@ -193,14 +194,14 @@ after flashing the .out file.
193194
194195* Install the J-Link software
195196
196- $ cd ~/Downloads
197- $ sudo dpkg -i JLink_Linux_V*_x86_64.deb
197+ $ cd ~/Downloads
198+ $ sudo dpkg -i JLink_Linux_V*_x86_64.deb
198199
199200* In Linux, grant the logged in user the ability to talk to the development
200201 hardware via the linux tty device (/dev/ttyACMx) by adding them to the
201202 dialout group.
202203
203- $ sudo usermod -a -G dialout ${USER}
204+ $ sudo usermod -a -G dialout ${USER}
204205
205206Once the above is complete, log output can be viewed using the JLinkExe tool in
206207combination with JLinkRTTClient as follows:
@@ -209,15 +210,15 @@ combination with JLinkRTTClient as follows:
209210
210211 For MG12 use:
211212
212- $ JLinkExe -device EFR32MG12PXXXF1024 -if JTAG -speed 4000 -autoconnect 1
213+ $ JLinkExe -device EFR32MG12PXXXF1024 -if JTAG -speed 4000 -autoconnect 1
213214
214215 For MG21 use:
215216
216- $ JLinkExe -device EFR32MG21AXXXF1024 -if SWD -speed 4000 -autoconnect 1
217+ $ JLinkExe -device EFR32MG21AXXXF1024 -if SWD -speed 4000 -autoconnect 1
217218
218219- In a second terminal, run the JLinkRTTClient to view logs:
219220
220- $ JLinkRTTClient
221+ $ JLinkRTTClient
221222
222223### Console Log
223224
@@ -263,41 +264,41 @@ With any serial terminal application such as screen, putty, minicom etc.
263264 Code is be scanned by the CHIP Tool app For the Rendez-vous procedure over
264265 BLE
265266
266- * On devices that do not have or support the LCD Display like the BRD4166A Thunderboard Sense 2,
267- a URL can be found in the RTT logs.
267+ * On devices that do not have or support the LCD Display like the BRD4166A Thunderboard Sense 2,
268+ a URL can be found in the RTT logs.
268269
269- <info > [SVR] Copy/paste the below URL in a browser to see the QR Code:
270- <info > [SVR] https://project-chip.github.io/connectedhomeip/qrcode.html?data=CH%3AI34NM%20-00%200C9SS0
270+ <info > [SVR] Copy/paste the below URL in a browser to see the QR Code:
271+ <info > [SVR] https://project-chip.github.io/connectedhomeip/qrcode.html?data=CH%3AI34NM%20-00%200C9SS0
271272
272273 **LED 0** shows the overall state of the device and its connectivity. The
273274 following states are possible:
274275
275- - Short Flash On (50 ms on/950 ms off): The device is in the
276- unprovisioned (unpaired) state and is waiting for a commissioning
277- application to connect.
276+ - Short Flash On (50 ms on/950 ms off): The device is in the
277+ unprovisioned (unpaired) state and is waiting for a commissioning
278+ application to connect.
278279
279- - Rapid Even Flashing (100 ms on/100 ms off): The device is in the
280- unprovisioned state and a commissioning application is connected through
281- Bluetooth LE.
280+ - Rapid Even Flashing (100 ms on/100 ms off): The device is in the
281+ unprovisioned state and a commissioning application is connected through
282+ Bluetooth LE.
282283
283- - Short Flash Off (950ms on/50ms off): The device is fully
284- provisioned, but does not yet have full Thread network or service
285- connectivity.
284+ - Short Flash Off (950ms on/50ms off): The device is fully
285+ provisioned, but does not yet have full Thread network or service
286+ connectivity.
286287
287- - Solid On: The device is fully provisioned and has full Thread
288- network and service connectivity.
288+ - Solid On: The device is fully provisioned and has full Thread
289+ network and service connectivity.
289290
290291 **Push Button 0**
291292
292- - _Press and Release_ : Start, or restart, BLE advertisement in fast mode. It will advertise in this mode
293- for 30 seconds. The device will then switch to a slower interval advertisement.
294- After 15 minutes, the advertisement stops.
295- Additionally, it will cycle through the QR code, application status screen and device status screen, respectively.
293+ - _Press and Release_ : Start, or restart, BLE advertisement in fast mode. It will advertise in this mode
294+ for 30 seconds. The device will then switch to a slower interval advertisement.
295+ After 15 minutes, the advertisement stops.
296+ Additionally, it will cycle through the QR code, application status screen and device status screen, respectively.
296297
297- - _Pressed and hold for 6 s_ : Initiates the factory reset of the device.
298- Releasing the button within the 6-second window cancels the factory reset
299- procedure. **LEDs** blink in unison when the factory reset procedure is
300- initiated.
298+ - _Pressed and hold for 6 s_ : Initiates the factory reset of the device.
299+ Releasing the button within the 6-second window cancels the factory reset
300+ procedure. **LEDs** blink in unison when the factory reset procedure is
301+ initiated.
301302
302303* You can provision and control the Chip device using the python controller,
303304 [CHIPTool](https://github.com/project-chip/connectedhomeip/blob/master/examples/chip-tool/README.md)
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?v=4&size=40){kind=avatar}
0 commit comments