Dependencies:
MMA7660
LM75B
easy-connect/esp8266-driver/README.md@0:119624335925, 2018-06-30 (annotated)
- Committer:
- MACRUM
- Date:
- Sat Jun 30 01:40:30 2018 +0000
- Revision:
- 0:119624335925
Initial commit
Who changed what in which revision?
| User | Revision | Line number | New contents of line |
|---|
| MACRUM |
0:119624335925
|
1
|
# The ESP8266 WiFi driver for mbed-os
|
| MACRUM |
0:119624335925
|
2
|
The mbed OS driver for the ESP8266 WiFi module
|
| MACRUM |
0:119624335925
|
3
|
|
| MACRUM |
0:119624335925
|
4
|
## Firmware version
|
| MACRUM |
0:119624335925
|
5
|
ESP8266 modules come in different shapes and forms, but most important difference is which firmware version it is programmed with. To make sure that your module has mbed-os compatible firmware follow update guide: https://developer.mbed.org/teams/ESP8266/wiki/Firmware-Update
|
| MACRUM |
0:119624335925
|
6
|
|
| MACRUM |
0:119624335925
|
7
|
## Restrictions
|
| MACRUM |
0:119624335925
|
8
|
- The ESP8266 WiFi module does not allow TCP client to bind on a specific port
|
| MACRUM |
0:119624335925
|
9
|
- Setting up an UDP server is not possible
|
| MACRUM |
0:119624335925
|
10
|
- Serial port does not have hardware flow control enabled. Also AT-command set does not have any way to limit download rate. Therefore downloading anything larger that serial port input buffer is unreliable. 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.
|