summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorPaul Sokolovsky <pfalcon@users.sourceforge.net>2017-04-07 10:52:50 +0300
committerPaul Sokolovsky <pfalcon@users.sourceforge.net>2017-04-07 10:52:50 +0300
commite5278b98fe2aad840d58e33a0c06af2e2b55cbde (patch)
tree7df7e14e75e4be26b636b49f23bb4bdf958e1d19
parentd7310fabc22ebf45aedcaade1c531ece96c33bf0 (diff)
downloadmicropython-e5278b98fe2aad840d58e33a0c06af2e2b55cbde.tar.gz
micropython-e5278b98fe2aad840d58e33a0c06af2e2b55cbde.zip
docs/esp8266/general: Start explicit "Known Issues", mentioned RTC inaccuracy.
-rw-r--r--docs/esp8266/general.rst10
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/esp8266/general.rst b/docs/esp8266/general.rst
index cd659f80a9..47df80d7ba 100644
--- a/docs/esp8266/general.rst
+++ b/docs/esp8266/general.rst
@@ -107,8 +107,16 @@ This will allow to keep the structure of your application clear, as well as
allow to install multiple applications on a board, and switch among them.
+Known Issues
+------------
+
Real-time clock
----------------
+~~~~~~~~~~~~~~~
+
+RTC in ESP8266 has very bad accuracy, drift may be seconds per minute. As
+a workaround, to measure short enough intervals you can use
+``utime.time()``, etc. functions, and for wall clock time, synchronize from
+the net using included ``ntpdate.py`` module.
Due to limitations of the ESP8266 chip the internal real-time clock (RTC)
will overflow every 7:45h. If a long-term working RTC time is required then