| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
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.
|
|
|
|
Using remote image causes problems with tools (partly because the image
is semi-firewalled and can't be accessed by arbitrary tools).
|
|
|
|
|
|
APA102 is a new "smart LED", similar to WS2812 aka "Neopixel".
|
|
Since the ``stop`` parameter has been dropped.
|
|
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 .
|
|
|
|
|
|
|
|
|
|
Link to vendor forum with datasheets, etc. is provided, as well as inline
TTX.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
