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
{{ message }}
This repository was archived by the owner on Apr 24, 2019. It is now read-only.
Remove the known issues, they were all fixed already.
Insert a table of supported boards/network connectivity, easier to read.
Now, once we insert the "NANOSTACK" feature to the `*.json`s, we do not
need the extra compilation instructions either.
*[UBLOX_EVK_ODIN_W2](https://developer.mbed.org/platforms/ublox-EVK-ODIN-W2/) (use the supplied `configs/eth_v4.json`)
43
-
*[REALTEK RTL8195AM](https://developer.mbed.org/platforms/REALTEK-RTL8195AM/) (use the supplied `configs/wifi_realtek_v4.json`, remember to update [DAPLINK](https://developer.mbed.org/platforms/REALTEK-RTL8195AM/#daplink-firmware-update).)
48
+
* K64F + GROVE SEEED shield using [ESP8266](https://en.wikipedia.org/wiki/ESP8266) WiFi module.
49
+
* NUCLEO_F429ZI + GROVE SEEED shield using [ESP8266](https://en.wikipedia.org/wiki/ESP8266) WiFi module.
50
+
* UBLOX_EVK_ODIN_W2 with built-in WiFi.
51
+
* REALTEK RTL8195AM with built-in WiFi.
52
+
53
+
To run this application using ESP8266 WiFi Interface, you need:
54
+
55
+
1. An [ESP8266](https://en.wikipedia.org/wiki/ESP8266) WiFi module.
1. Mount the WiFi module onto [K64F Grove Shield v2](https://developer.mbed.org/platforms/FRDM-K64F/#supported-seeed-studio-grove-extension).
58
+
1. Attach the shield on your board.
59
+
1. In the `mbed_app.json` file, change `network-interface` parameter to match your WiFi, for example for ESP8266:
60
+
61
+
```json
62
+
"network-interface": {
63
+
"help": "options are ETHERNET, WIFI_ESP8266, WIFI_ODIN, WIFI_RTW, MESH_LOWPAN_ND,MESH_THREAD.",
64
+
"value": "WIFI_ESP8266"
65
+
}
66
+
```
67
+
You can use values `WIFI_ODIN` for ODIN UBLOX EVK W2 and `WIFI_RTW` for Realtek RTL8195AM.
68
+
69
+
Provide your WiFi SSID and password here and leave `\"` in the beginning and end of your SSID and password (as shown in the example below). Otherwise, the example cannot pick up the SSID and password in correct format.
70
+
71
+
```json
72
+
"wifi-ssid": {
73
+
"help": "WiFi SSID",
74
+
"value": "\"SSID\""
75
+
},
76
+
"wifi-password": {
77
+
"help": "WiFi Password",
78
+
"value": "\"Password\""
79
+
}
80
+
```
81
+
82
+
<spanclass="notes">**Note:** Some devices do not support the Grove Shield or use the primary UART for USB communication. On such devices, modify the `mbed_app.json` to use the serial pins connected to the ESP8266.</span>
44
83
45
-
For running the example application using Ethernet, you need:
84
+
For example, NUCLEO_F401RE requires a different serial connection:
85
+
86
+
```json
87
+
"wifi-tx": {
88
+
"help": "TX pin for serial connection to external device",
89
+
"value": "PA_11"
90
+
},
91
+
"wifi-rx": {
92
+
"help": "RX pin for serial connection to external device",
93
+
"value": "PA_12"
94
+
}
95
+
```
46
96
47
-
- An Ethernet cable.
48
-
- An Ethernet connection to the internet.
49
97
50
98
### Mesh
51
99
@@ -128,7 +176,7 @@ For sub-GHz shields ([Spirit1](https://github.com/ARMmbed/stm-spirit1-rf-driver)
128
176
129
177
For more information about the radio shields, see [the related documentation](docs/radio_module_identify.md).
130
178
131
-
=======
179
+
132
180
#### Supported combinations of board and shields
133
181
134
182
See Mesh-minimal's [Notes on different hardware](https://github.com/ARMmbed/mbed-os-example-mesh-minimal/blob/master/Hardware.md) for known combinations of development boards and RF shields that have been tested with mesh networking stack.
@@ -149,68 +197,6 @@ With Thread, you can change the operating mode of the client from the default ro
1. Mount the WiFi module onto [K64F Grove Shield v2](https://developer.mbed.org/platforms/FRDM-K64F/#supported-seeed-studio-grove-extension).
166
-
1. Attach the shield on your board.
167
-
1. In the `mbed_app.json` file, change `network-interface` parameter to match your WiFi, for example for ESP8266:
168
-
169
-
```json
170
-
"network-interface": {
171
-
"help": "options are ETHERNET, WIFI_ESP8266, WIFI_ODIN, WIFI_REALTEK, MESH_LOWPAN_ND,MESH_THREAD.",
172
-
"value": "WIFI_ESP8266"
173
-
}
174
-
```
175
-
You can use values `WIFI_ODIN` for ODIN UBLOX EVK W2 and `WIFI_REALTEK` for Realtek RTL8195AM.
176
-
177
-
Provide your WiFi SSID and password here and leave `\"` in the beginning and end of your SSID and password (as shown in the example below). Otherwise, the example cannot pick up the SSID and password in correct format.
178
-
179
-
```json
180
-
"wifi-ssid": {
181
-
"help": "WiFi SSID",
182
-
"value": "\"SSID\""
183
-
},
184
-
"wifi-password": {
185
-
"help": "WiFi Password",
186
-
"value": "\"Password\""
187
-
}
188
-
```
189
-
190
-
<spanclass="notes">**Note:** Some devices do not support the Grove Shield or use the primary UART for USB communication. On such devices, modify the `mbed_app.json` to use the serial pins connected to the ESP8266.</span>
191
-
192
-
For example, NUCLEO_F401RE requires a different serial connection:
193
-
194
-
```json
195
-
"wifi-tx": {
196
-
"help": "TX pin for serial connection to external device",
197
-
"value": "PA_11"
198
-
},
199
-
"wifi-rx": {
200
-
"help": "RX pin for serial connection to external device",
201
-
"value": "PA_12"
202
-
}
203
-
```
204
-
205
-
#### Compile configuration for ODIN and Realtek WiFi
206
-
207
-
To compile ODIN and Realtek WiFi configuration, you need to tell mbed NOT to compile the related files. To do that, set up a `.mbedignore` file. An example file is available in the `configs` folder.
208
-
209
-
This should resolve the issue:
210
-
211
-
```bash
212
-
cp configs/eth-wifi-mbedignore ./.mbedignore
213
-
```
214
200
215
201
216
202
### Non listed board support
@@ -295,17 +281,7 @@ To build the example using mbed CLI:
0 commit comments