| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This adds to the ESP8266 tutorial instructions explaining which pins to
pull low to enter programming mode.
Commit made originally by @ARF1 in #2910.
Signed-off-by: Damien George <damien@micropython.org>
|
|
Show how to send an HTTP response code and content-type. Without the
response code Safari/iOS will fail. Without the content-type Lynx/Links
will fail.
|
|
|
|
|
|
|
|
With this commit there is now only one entry point into the whole
documentation, which describes the general MicroPython language, and then
from there there are links to information about specific platforms/ports.
This commit doesn't change content (almost, it does fix a few internal
links), it just reorganises things.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
At least, Sphinx 1.3.6.
|
|
This follows similar warnings in other parts of docs.
|
|
|
|
Give a clearly dissuading tone on end users trying 512KB version
- it has to many end-usery features lacking.
|
|
esptool 1.3 now supports both Python 2.7 and 3.4+.
Updated github link to now-official espressif repo.
|
|
|
|
|
|
Add a "Getting the firmware" section to better describe how to get hold of
the MicroPython firmware, especially if you have a 512kb module.
|
|
|
|
|
|
|
|
It used a standard BootROM programming algo and may be useful as a
fallback.
|
|
|
|
|
|
|
|
Tries to summarize most of the issues we've seen so far.
|
|
People tend to skip introductions (everyone knows what esp8266 is, right?),
so try to do A/B testing with a title inviting to read it.
|
|
Not all NodeMCU boards require it.
|
|
|
|
|
|
|
|
Fixes issue #2065.
|
|
The socket should either connect to `addr` or `addr_info[0][-1]`. Not to `addr[0][-1]`.
|
|
|
|
|
|
At http://micropython.org/webrepl .
|
|
|
|
|
|
|
|
|
