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.
*[X-NUCLEO-IDS01A4](https://github.com/ARMmbed/stm-spirit1-rf-driver) (*a.k.a.* Spirit1) radio shields. Check instructions for compilation [here](#compile-configuration-for-spirit1)
68
+
*[X-NUCLEO-IDS01A4](https://github.com/ARMmbed/stm-spirit1-rf-driver) (*a.k.a.* Spirit1) radio shields. Check instructions for compilation [here](#compile-configuration-for-spirit1).
69
69
70
70
To select the radio shield make sure that the `mbed_app.json` file points to the correct radio driver type:
71
71
@@ -128,7 +128,7 @@ For sub-GHz shields ([Spirit1](https://github.com/ARMmbed/stm-spirit1-rf-driver)
128
128
129
129
For more information about the radio shields, see [the related documentation](docs/radio_module_identify.md).
130
130
131
-
=======
131
+
132
132
#### Supported combinations of board and shields
133
133
134
134
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.
@@ -156,6 +156,7 @@ With Thread, you can change the operating mode of the client from the default ro
156
156
* UBLOX_EVK_ODIN_W2. Check instructions for compilation [here](#compile-configuration-for-odin-wifi).
157
157
* K64F + GROVE SEEED shield using [ESP8266](https://en.wikipedia.org/wiki/ESP8266) WiFi module.
158
158
* NUCLEO_F429ZI + GROVE SEEED shield using [ESP8266](https://en.wikipedia.org/wiki/ESP8266) WiFi module.
To run this application using ESP8266 WiFi Interface, you need:
161
162
@@ -167,8 +168,8 @@ To run this application using ESP8266 WiFi Interface, you need:
167
168
168
169
```json
169
170
"network-interface": {
170
-
"help": "options are ETHERNET,WIFI,MESH_LOWPAN_ND,MESH_THREAD.",
171
-
"value": "WIFI"
171
+
"help": "options are ETHERNET,WIFI_ESP8266,WIFI_IDW0XX1,WIFI_ODIN,MESH_LOWPAN_ND,MESH_THREAD.",
172
+
"value": "WIFI_ESP8266"
172
173
}
173
174
```
174
175
@@ -202,14 +203,43 @@ For example, NUCLEO_F401RE requires a different serial connection:
202
203
203
204
#### Compile configuration for ODIN WiFi
204
205
205
-
To compile ODIN 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.
206
+
To compile ODIN WiFi configuration, you need to tell mbed NOT to compile mesh files for example. To do that, set up a `.mbedignore` file. An example file is available in the `configs` folder.
206
207
207
208
This should resolve the issue:
208
209
209
-
```
210
+
```bash
211
+
cp configs/wifi_odin_v4.json mbed_app.json
212
+
<use your favourite editor to modify mbed_app.json for WiFi details>
210
213
cp configs/eth-wifi-mbedignore ./.mbedignore
211
-
```
212
-
214
+
```
215
+
216
+
#### Compile configuration for Nucleo F401RE and X-Nucleo WiFi
217
+
218
+
To compile Nucleo X WiFi configuration, you need to tell mbed NOT to compile mesh files for example. To do that, set up a `.mbedignore` file. An example file is available in the `configs` folder.
219
+
220
+
This should resolve the issue:
221
+
222
+
```bash
223
+
cp configs/wifi_idw01m1_v4.json mbed_app.json
224
+
<use your favourite editor to modify mbed_app.json for WiFi details>
225
+
cp configs/wifi-idw0xx1-mbedignore ./.mbedignore
226
+
```
227
+
228
+
Depending on which Wifi-module you have, you might have to change the module type in the `.json`file `target-overrides` section.
229
+
230
+
```json
231
+
"idw0x11": {
232
+
"expansion.board": "IDW01M1"
233
+
}
234
+
```
235
+
Options are: `IDW01M1` is the Morph form-factor board and `IDW04A1` is the Arduino form-factor board. The label is clearly printed on the PCB.
236
+
237
+
If you have issues with the `IDW04A1` board you might have to define also a macro `IDW04A1_WIFI_HW_BUG_WA`. This can be added to the same `.json`file to the `macros:` section.
238
+
239
+
```json
240
+
"macros": [...,"IDW04A1_WIFI_HW_BUG_WA"],
241
+
```
242
+
213
243
### Non listed board support
214
244
215
245
Apart from the listed configurations, this example can work on other mbed OS supported hardware boards which support any of the given network interface including Ethernet, WiFi, Mesh (6LoWPAN) or Thread, provided the configuration fulfills condition that the target hardware has TLS entropy implemented for it. On devices where hardware entropy is not present, TLS is disabled by default. This would result in compile time failures or linking failures.
@@ -268,7 +298,7 @@ Possible socket types per connection:
268
298
| Network interface | UDP | TCP |
269
299
| ------------------------------|:-----:|:-----:|
270
300
| Ethernet (IPv4) | X | X |
271
-
| Ethernet (IPv6) | X ||
301
+
| Ethernet (IPv6) | X |X|
272
302
| Wifi (IPv4) | X | X |
273
303
| Wifi (IPv6) - Not supported |||
274
304
| 6LoWPAN/Thread (IPv6) | X ||
@@ -388,9 +418,3 @@ To learn how to get notifications when resource 1 changes, or how to use resourc
388
418
389
419
## Known issues
390
420
391
-
### mbed OS 5.4
392
-
393
-
* [UBLOX_EVK_ODIN_W2]: This example is not compiling with IAR. See [#194](https://github.com/ARMmbed/mbed-os-example-client/issues/194)
394
-
* [NUCLEO_F429ZI]: This example is not compiling with IAR. See [#194](https://github.com/ARMmbed/mbed-os-example-client/issues/194)
395
-
396
-
Fix for those issues coming via; [mbed-os PR 3920] (https://github.com/ARMmbed/mbed-os/pull/3920)
0 commit comments