| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The simple NTP client module is named "ntptime.py".
|
|
|
|
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.
|
|
|
|
With warnings of need to close files, sockets, etc.
|
|
|
|
Add a "Getting the firmware" section to better describe how to get hold of
the MicroPython firmware, especially if you have a 512kb module.
|
|
|
|
|
|
|
|
Consistency and formatting.
|
|
SPI(1) is not used for hardware SPI. Few more details are provided.
|
|
|
|
|
|
Use the `SPI` factory function in the examples, and use
proper baud rate of 80 000 000.
|
|
This module uses ESP8266's SPI hardware, which allows much higher
speeds. It uses a library from
https://github.com/MetalPhreak/ESP8266_SPI_Driver
|
|
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.
|
|
|
|
|
|
|
|
|
|
WebREPL is much more stable now.
|
