
A quick example of a simple WiFi application using the WiFi and network-socket APIs that is provided as a part of mbed-os.
The program brings up the WiFi and the underlying network interface, and uses it to scans available networks, connects to a network, prints interface and connection details and performs simple HTTP operation.
Supported hardware:
- UBLOX Odin board built-in WiFi module
- REALTEK_RTL8195AM built-in WiFi module
- NUCLEO_F401RE with X-NUCLEO-IDW01M1 WiFi expansion board using pins D8 D2
- NUCLEO_F429ZI with ESP8266-01 module using pins D1 D0
- NUCLEO_L476RG with ESP8266-01 module using pins D8 D2
- Other mbed targets with ESP8266 module or X-NUCLEO-IDW01M1 expansion board
Not that the mbed target board the WiFi shield gets connected to shouldn't have any other network interface e.g. Ethernet.
ESP8266 is a fallback option and will be used if the build is for unsupported platform.
Diff: mbed_app_idw01m1.json
- Revision:
- 82:122bb3ae6de5
- Parent:
- 44:63be19b7a3db
- Child:
- 86:92e4be20dc8b
diff -r b620d7cac9a2 -r 122bb3ae6de5 mbed_app_idw01m1.json --- a/mbed_app_idw01m1.json Wed Oct 10 14:15:03 2018 +0100 +++ b/mbed_app_idw01m1.json Fri Oct 12 11:45:02 2018 +0100 @@ -1,9 +1,5 @@ { "config": { - "wifi-shield": { - "help": "Options are internal, WIFI_ESP8266, WIFI_IDW0XX1", - "value": "WIFI_IDW0XX1" - }, "wifi-ssid": { "help": "WiFi SSID", "value": "\"SSID\"" @@ -25,8 +21,9 @@ "*": { "platform.stdio-convert-newlines": true, "idw0xx1.expansion-board": "IDW01M1", - "drivers.uart-serial-txbuf-size": 730, - "drivers.uart-serial-rxbuf-size": 730 + "idw0xx1.provide-default": true, + "drivers.uart-serial-txbuf-size": 730, + "drivers.uart-serial-rxbuf-size": 730 }, "UBLOX_EVK_ODIN_W2": { "target.device_has": ["EMAC"]