RTC auf true

Committer:
kevman
Date:
Wed Mar 13 11:03:24 2019 +0000
Revision:
2:7aab896b1a3b
2019-03-13

Who changed what in which revision?

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