Nuvoton / Mbed OS NuMaker-mbed-OS-6-AWS-IoT-example

NuMaker connection with AWS IoT thru MQTT/HTTPS (Mbed OS 6)

Dependencies:   MQTT

Diff: README.md

Revision:
6:7ef096085ca7
Parent:
5:2a70e217325f
Child:
19:b8191f21eeaf
--- a/README.md	Fri Jan 12 11:16:13 2018 +0800
+++ b/README.md	Thu Feb 01 17:39:19 2018 +0800
@@ -316,8 +316,9 @@
     due to bad network status and fails these commands.
     These commands must be OK for ESP8266 F/W to reset connection state correctly.
     If that happens, try enlarging [ESP8266 driver's](https://github.com/ARMmbed/esp8266-driver) timeout configuration.
-    For example, enlarge `ESP8266_MISC_TIMEOUT` (defined in [ESP8266Interface.cpp](https://github.com/ARMmbed/esp8266-driver/blob/master/ESP8266Interface.cpp))
-    to 5000 ms (through `mbed_app.json`).
+    For example, enlarge `ESP8266_SEND_TIMEOUT`/`ESP8266_RECV_TIMEOUT`/`ESP8266_MISC_TIMEOUT` (defined in
+    [ESP8266Interface.cpp](https://github.com/ARMmbed/esp8266-driver/blob/master/ESP8266Interface.cpp))
+    to 5000/5000/5000 ms respectively (through `mbed_app.json`).
     <pre>
     {
         "macros": [
@@ -325,6 +326,8 @@
             "MBEDTLS_USER_CONFIG_FILE=\"mbedtls_user_config.h\"",
             "MBED_HEAP_STATS_ENABLED=1",
             "MBED_MEM_TRACING_ENABLED=1",
+            <b>"ESP8266_SEND_TIMEOUT=5000",</b>
+            <b>"ESP8266_RECV_TIMEOUT=5000",</b>
             <b>"ESP8266_MISC_TIMEOUT=5000"</b>
         ],
         "config": {