wifi test

Dependencies:   X_NUCLEO_IKS01A2 mbed-http

Committer:
JMF
Date:
Wed Sep 05 14:28:24 2018 +0000
Revision:
0:24d3eb812fd4
Initial commit

Who changed what in which revision?

UserRevisionLine numberNew contents of line
JMF 0:24d3eb812fd4 1 # ESP8266 WiFi driver for Mbed OS
JMF 0:24d3eb812fd4 2
JMF 0:24d3eb812fd4 3 The Mbed OS driver for the ESP8266 WiFi module.
JMF 0:24d3eb812fd4 4
JMF 0:24d3eb812fd4 5 ## Firmware version
JMF 0:24d3eb812fd4 6
JMF 0:24d3eb812fd4 7 ESP8266 modules come in different shapes and formats, but the most important factor is the firmware version in it. To make sure that the firmware in your module is compatible with Mbed OS, follow the [Update guide](https://developer.mbed.org/teams/ESP8266/wiki/Firmware-Update).
JMF 0:24d3eb812fd4 8
JMF 0:24d3eb812fd4 9 ## Restrictions
JMF 0:24d3eb812fd4 10
JMF 0:24d3eb812fd4 11 - The ESP8266 WiFi module does not allow the TCP client to bind on a specific port.
JMF 0:24d3eb812fd4 12 - Setting up a UDP server is not possible.
JMF 0:24d3eb812fd4 13 - The serial port does not have hardware flow control enabled. The AT command set does not either have a way to limit the download rate. Therefore, downloading anything larger than the serial port input buffer is unreliable. An application should be able to read fast enough to stay ahead of the network. This affects mostly the TCP protocol where data would be lost with no notification. On UDP, this would lead to only packet losses which the higher layer protocol should recover from.