mayuresh bharmoria / Mbed OS mbed-os-example-wifi
Committer:
mayur098
Date:
Thu Jun 21 17:50:21 2018 +0000
Revision:
0:8f8e8f3cbd1c
first commit;

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mayur098 0:8f8e8f3cbd1c 1 # ESP8266 WiFi driver for Mbed OS
mayur098 0:8f8e8f3cbd1c 2
mayur098 0:8f8e8f3cbd1c 3 The Mbed OS driver for the ESP8266 WiFi module.
mayur098 0:8f8e8f3cbd1c 4
mayur098 0:8f8e8f3cbd1c 5 ## Firmware version
mayur098 0:8f8e8f3cbd1c 6
mayur098 0:8f8e8f3cbd1c 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).
mayur098 0:8f8e8f3cbd1c 8
mayur098 0:8f8e8f3cbd1c 9 ## Restrictions
mayur098 0:8f8e8f3cbd1c 10
mayur098 0:8f8e8f3cbd1c 11 - The ESP8266 WiFi module does not allow the TCP client to bind on a specific port.
mayur098 0:8f8e8f3cbd1c 12 - Setting up a UDP server is not possible.
mayur098 0:8f8e8f3cbd1c 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.