summaryrefslogtreecommitdiffstatshomepage
path: root/docs/esp8266/tutorial/intro.rst
diff options
context:
space:
mode:
authorPaul Sokolovsky <pfalcon@users.sourceforge.net>2017-04-14 01:12:04 +0300
committerPaul Sokolovsky <pfalcon@users.sourceforge.net>2017-04-14 01:12:04 +0300
commita1c39ffb69d711858e47e172d4ca8d98990d2bf9 (patch)
treeece1bc4e08c73874fa7025d77888877441bc7b47 /docs/esp8266/tutorial/intro.rst
parentfbe7a81e30906b7e2c991cf76cf10d582fd2e012 (diff)
downloadmicropython-a1c39ffb69d711858e47e172d4ca8d98990d2bf9.tar.gz
micropython-a1c39ffb69d711858e47e172d4ca8d98990d2bf9.zip
docs/esp8266/tutorial/intro: Reword section on flash size requirement.
Give a clearly dissuading tone on end users trying 512KB version - it has to many end-usery features lacking.
Diffstat (limited to 'docs/esp8266/tutorial/intro.rst')
-rw-r--r--docs/esp8266/tutorial/intro.rst9
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/esp8266/tutorial/intro.rst b/docs/esp8266/tutorial/intro.rst
index e7a38d3e5b..67ed0ba67c 100644
--- a/docs/esp8266/tutorial/intro.rst
+++ b/docs/esp8266/tutorial/intro.rst
@@ -20,9 +20,12 @@ characteristic of a board is how much flash it has, how the GPIO pins are
connected to the outside world, and whether it includes a built-in USB-serial
convertor to make the UART available to your PC.
-The minimum requirement for flash size is 512k. A board with this amount of
-flash will not have room for a filesystem, but otherwise is fully functional.
-If your board has 1Mbyte or more of flash then it will support a filesystem.
+The minimum requirement for flash size is 1Mbyte. There is also a special
+build for boards with 512KB, but it is highly limited comparing to the
+normal build: there is no support for filesystem, and thus features which
+depend on it won't work (WebREPL, upip, etc.). As such, 512KB build will
+be more interesting for users who build from source and fine-tune parameters
+for their particular application.
Names of pins will be given in this tutorial using the chip names (eg GPIO0)
and it should be straightforward to find which pin this corresponds to on your