You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sld246-matter-faq/wifi-faq.md
+10-68Lines changed: 10 additions & 68 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,77 +80,31 @@ Where `mySSID` is **your AP's SSID** and `mypassword` is **your AP's password**.
80
80
81
81
- Issue the commissioning command
82
82
83
-
### 3. WLAN connection fails from RS9116 during commissioning when channel 13 is selected on the AP
83
+
### 3. Apple HomePod associated failures
84
84
85
-
**Note:** RS9116 is deprecated and no longer supported on Matter.
85
+
If there is an Apple HomePod on the network paired with a Thread device, and a commissioning failure is seen with error 3000001:
86
86
87
-
The required channel becomes available for connection when the WLAN connection region is configured during compilation to one that supports the channel, such as for Japan for channel 13.
87
+
- Remove the Apple HomePod from the network or unpair it from all Thread devices.
88
+
- Retry commissioning
88
89
89
-
In order to use the desired channel, before building, make sure the WLAN connection region is configured correctly by reviewing/modifying the following lines in**/examples/platform/silabs/efr32/rs911x/rsi_wlan_config.h**:
90
-
91
-
```c
92
-
//Make sure this is set to RSI_ENABLE
93
-
#define RSI_SET_REGION_SUPPORT RSI_ENABLE
94
-
95
-
// Note that the channels available for WLAN connection depend on the region selected
96
-
// Make sure this is set to 1 to configure from RSI_REGION_CODE value below
97
-
// 0: region configurations taken from beacon
98
-
// 1: region configurations taken from user
99
-
#define RSI_SET_REGION_FROM_USER_OR_BEACON 1
100
-
101
-
// 0 : Default Region domain
102
-
// 1 : US
103
-
// 2 : EUROPE
104
-
// 3 : JAPAN
105
-
#define RSI_REGION_CODE 3
106
-
```
107
-
108
-
### 4. Incorrect firmware version
109
-
110
-
```shell
111
-
cd ./third_party/silabs/wiseconnect-wifi-bt-sdk/firmware
112
-
```
113
-
114
-
You will get appropriate firmware in the above mentioned path.
115
-
116
-
Note:
117
-
118
-
1. How to check the current firmware version?
119
-
120
-
> You can find the currently used firmware version in the DUT log.
121
-
122
-
2. How to check whether you are using correct firmware version or not?
123
-
124
-
> Compare last 5 digits of firmware version mentioned in the above path with the currently used firmware version.
125
-
126
-
### 5. Apple HomePod associated failures
127
-
128
-
If there is an Apple HomePod on the network paired with a Thread device, and a commissioning failure is seen with error `3000001`:
129
-
130
-
> Either remove the Apple HomePod from the network, or unpair it from all Thread devices, before re-trying the commissioning.
131
-
132
-
### 6. Commissioning failure at step 18
90
+
### 4. Commissioning failure at step 18
133
91
134
92
1. Verify router configuration specifically related to IPV6 SLAAC, Internet Group Management Protocol (IGMP) snooping.
135
93
2. Delete all the files of chip-tool /tmp folder. (`rm -rf /tmp/chip_*`)
136
94
3. After checking the router configuration, factory-reset your access point.
137
95
138
-
### 7. Commissioning failure at step 16
96
+
### 5. Commissioning failure at step 16
139
97
140
98
Verify the access point settings, SSID, PSK, security type, REGION, CHANNEL.
141
99
142
-
### 8. Inconsistent logs
143
-
144
-
Verify external power is supplied to rs911x
145
-
146
-
### 9. To enable different security options on AP/Router
100
+
### 6. To enable different security options on AP/Router
147
101
148
102
1. Get the router address by entering `route -n` or ifconfig of ipconfig.
149
103
2. Enter the router address in the browser and enter the appropriate username and password.
150
104
3. Select the appropriate band.
151
105
4. In security, selecttype (WPA / WPA2 / WPA3).
152
106
153
-
### 10. CHIP Logs are not available on MG12 + WF200 due to image size constraints
107
+
### 7. CHIP Logs are not available on MG12 + WF200 due to image size constraints
154
108
155
109
Due to apps taking up more space than available flash on the MG12 + WF200 device combination, `chip_logging=false` needs to be included on the command line while building the app image, to disable CHIP logs and thereby reduce the image size.
156
110
@@ -168,19 +122,7 @@ Disable LCD and enable CHIP Logging:
### 11. MG24 device sometimes loses its connection to Ozone during OTA Update with RS9116
172
-
173
-
**Note:** RS9116 is deprecated and no longer supported on Matter.
174
-
175
-
While performing an OTA Update with the EFR32MG24 + RS9116 device combination, when the device is reset and bootloading begins with the new image, the Ozone Debugger sometimes loses its connection.
176
-
177
-
There are two possible workarounds to this:
178
-
179
-
1. Immediately re-attach the device to the console when the connection is lost.
180
-
181
-
2. Download the RTT Viewer application instead and use it to view the logs during OTA Update.
182
-
183
-
### 12. MG24 device sometimes fails to bootload with the new image during OTA Update with WF200
125
+
### 8. MG24 device sometimes fails to bootload with the new image during OTA Update with WF200
184
126
185
127
While performing an OTA Update with the EFR32MG24 + WF200 device combination using the external flash, when the device is reset and bootloading begins with the new image, the device sometimes starts up with the existing image instead of the newly downloaded one.
186
128
@@ -198,7 +140,7 @@ When this happens, perform the following steps to run the OTA Update successfull
198
140
199
141
4. Re-run the OTA Update process from the beginning.
200
142
201
-
### 13. Connectivity Issues with SiWX917 SoC with Low-Power Applications while flashing firmware/application image
143
+
### 9. Connectivity Issues with SiWX917 SoC with Low-Power Applications while flashing firmware/application image
202
144
203
145
Sometimes, firmware/application updates fail while flashing, and the logs display "Could not connect debugger. Could not connect to target device," indicating that the application processor is in a low power state with no flash access. Try one of the following solutions, then retry the firmware/application update:
Copy file name to clipboardExpand all lines: sld247-matter-overview/index.md
+1-11Lines changed: 1 addition & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ two EFR32MG24-based development boards, and a Raspberry Pi used as a Matter hub.
26
26
27
27
**Matter Over Wi-Fi Accessory Device Requirements for NCP Mode**
28
28
29
-
The Silicon Labs Matter over Wi-Fi NCP mode demo and development requires two boards: the Silicon Labs EFR32 Radio board to run the Matter code and either the RS9116, SiWx917, or WF200 to run the Wi-Fi protocol stack.
29
+
The Silicon Labs Matter over Wi-Fi NCP mode demo and development requires two boards: the Silicon Labs EFR32 Radio board to run the Matter code and either the SiWx917 or WF200 to run the Wi-Fi protocol stack.
30
30
31
31
The following boards are supported for the Matter over Wi-Fi demos and development:
32
32
@@ -38,14 +38,6 @@ The following boards are supported for the Matter over Wi-Fi demos and developme
Copy file name to clipboardExpand all lines: sld249-matter-prerequisites/hardware-requirements.md
+1-14Lines changed: 1 addition & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ The Matter Accessory Device (MAD) is the actual device that the Matter applicati
95
95
96
96
### Matter Over Wi-Fi Accessory Device Requirements for NCP Mode
97
97
98
-
The Silicon Labs Matter over Wi-Fi NCP mode demo and development requires two boards: the Silicon Labs EFR32 Radio board to run the Matter code and either the RS9116, SiWx917, or WF200 to run the Wi-Fi protocol stack. Pre-built images for the EFR32, and also for SiWx917 or RS9116 connectivity firmware, are provided on the [Matter Artifacts page](./matter-artifacts.md).
98
+
The Silicon Labs Matter over Wi-Fi NCP mode demo and development requires two boards: the Silicon Labs EFR32 Radio board to run the Matter code and either the SiWx917 or WF200 to run the Wi-Fi protocol stack. Pre-built images for the EFR32, and also for SiWx917 connectivity firmware, are provided on the [Matter Artifacts page](./matter-artifacts.md).
99
99
100
100
**Notes:**
101
101
@@ -114,13 +114,6 @@ The following boards are supported for the Matter over Wi-Fi demos and developme
114
114
- MG24 with WSTK : [xG24-PK6010A](https://www.silabs.com/development-tools/wireless/efr32xg24-pro-kit-20-dbm?tab=overview)
115
115
116
116
-**Wi-Fi NCP Dev Kits & boards**
117
-
-**RS9116**
118
-
- SB-EVK1 / Single Band Wi-Fi Development Kit / 2.4GHz
RS9116 chip/module needs to be flashed with proper firmware as mentioned below:
43
-
44
-
-`RS916.x.x.x.x.x.rps - This firmware image is valid for RS9116 1.5 revision chip/module`
45
-
-`RS9116.x.x.x.x.x.rps - This firmware image is valid for RS9116 1.4/1.3 revision chip/module`
46
-
47
33
## SiWx917 Firmware for SiWN917 NCP and SiWG917 SOC
48
34
49
35
The SiWx917 firmware(SiWx917_firmware_files.zip) is used to update the SiWN917 NCP and SiWG917 SOC which can be found in the Assets section of this page:
Copy file name to clipboardExpand all lines: sld249-matter-prerequisites/software-requirements.md
+2-10Lines changed: 2 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,17 +34,9 @@ Below are the software tools both optional and required for developing Matter ov
34
34
35
35
1.[SiSDK package](/matter/{build-docspace-version}/matter-wifi-getting-started-example/software-installation#installation-of-gecko-sdk-extension), which can be installed as part of the Simplicity Studio tool installation.
36
36
37
-
2.[WiSeConnect SDK v2.x for RS9116 NCP](/matter/{build-docspace-version}/matter-wifi-getting-started-example/software-installation#installation-of-wiseconnect-sdk-v2x-or-v3x-extension), which can be installed as part of the Simplicity Studio tool installation.
37
+
2.[WiSeConnect SDK v3.x for SiWx917 NCP](/matter/{build-docspace-version}/matter-wifi-getting-started-example/software-installation#installation-of-wiseconnect-sdk-v2x-or-v3x-extension), which can be installed as part of the Simplicity Studio tool installation.
38
38
39
-
**Note:** RS9116 is deprecated and no longer supported on Matter.
40
-
41
-
3.[WiSeConnect SDK v3.x for SiWx917 NCP](/matter/{build-docspace-version}/matter-wifi-getting-started-example/software-installation#installation-of-wiseconnect-sdk-v2x-or-v3x-extension), which can be installed as part of the Simplicity Studio tool installation.
42
-
43
-
4.[Firmware for RS9116 NCP](./matter-artifacts.md#rs9116-firmware)
44
-
45
-
**Note:** RS9116 is deprecated and no longer supported on Matter.
46
-
47
-
5.[Firmware for SiWx917 NCP](./matter-artifacts.md#siwx917-firmware-for-siwn917-ncp-and-siwg917-soc)
39
+
3.[Firmware for SiWx917 NCP](./matter-artifacts.md#siwx917-firmware-for-siwn917-ncp-and-siwg917-soc)
48
40
49
41
## Software Packages Required for Wi-Fi SiWx917 SoC Devices
0 commit comments