Damien George
7e1f580910
|
9 years ago | |
---|---|---|
.. | ||
scripts | 9 years ago | |
Makefile | 9 years ago | |
README.md | 9 years ago | |
axtls_helpers.c | 9 years ago | |
eagle.rom.addr.v6.ld | 9 years ago | |
esp8266.ld | 9 years ago | |
esp_mphal.c | 9 years ago | |
esp_mphal.h | 9 years ago | |
espneopixel.c | 9 years ago | |
espneopixel.h | 9 years ago | |
esponewire.c | 9 years ago | |
esponewire.h | 9 years ago | |
esppwm.c | 9 years ago | |
esppwm.h | 9 years ago | |
ets_alt_task.c | 9 years ago | |
ets_alt_task.h | 9 years ago | |
etshal.h | 9 years ago | |
fatfs_port.c | 9 years ago | |
gccollect.c | 9 years ago | |
gccollect.h | 10 years ago | |
gchelper.s | 10 years ago | |
help.c | 9 years ago | |
intr.c | 9 years ago | |
lexerstr32.c | 9 years ago | |
main.c | 9 years ago | |
makeimg.py | 9 years ago | |
modesp.c | 9 years ago | |
modmachine.c | 9 years ago | |
modnetwork.c | 9 years ago | |
modonewire.c | 9 years ago | |
modpyb.c | 9 years ago | |
modpyb.h | 9 years ago | |
modpybadc.c | 9 years ago | |
modpybpin.c | 9 years ago | |
modpybpwm.c | 9 years ago | |
modpybrtc.c | 9 years ago | |
modpybrtc.h | 9 years ago | |
modpybspi.c | 9 years ago | |
modpybuart.c | 9 years ago | |
moduos.c | 9 years ago | |
modutime.c | 9 years ago | |
mpconfigport.h | 9 years ago | |
qstrdefsport.h | 9 years ago | |
strtoll.c | 10 years ago | |
uart.c | 9 years ago | |
uart.h | 9 years ago | |
uart_register.h | 10 years ago | |
user_config.h | 10 years ago |
README.md
MicroPython port to ESP8266
This is a highly experimental port of MicroPython for the WiFi modules based on Espressif ESP8266 chip.
WARNING: The port is highly experimental and any APIs are subject to change.
Currently implemented features include:
- REPL (Python prompt) over UART0.
- Garbage collector, exceptions.
- Unicode support.
- Builtin modules: gc, array, collections, io, struct, sys, esp, network, many more.
- Arbitrary-precision long integers and 30-bit precision floats.
- WiFi support.
- Sockets using modlwip.
- GPIO and bit-banging I2C, SPI support.
- 1-Wire and WS2812 (aka Neopixel) protocols support.
- Internal filesystem using the flash.
- WebREPL over WiFi from a browser (clients at https://github.com/micropython/webrepl).
Work-in-progress documentation is available at http://docs.micropython.org/en/latest/esp8266/ .
Build instructions
The tool chain required for the build is the OpenSource ESP SDK, which can be
found at https://github.com/pfalcon/esp-open-sdk. Clone this repository and
run make
in its directory to build and install the SDK locally. Make sure
to add toolchain bin directory to your PATH. Read esp-open-sdk's README for
additional important information on toolchain setup.
Add the external dependencies to the MicroPython repository checkout:
$ git submodule update --init
See the README in the repository root for more information about external dependencies.
Then, to build MicroPython for the ESP8266, just run:
$ cd esp8266
$ make axtls
$ make
This will produce binary images in the build/
subdirectory. If you install
MicroPython to your module for the first time, or after installing any other
firmware, you should erase flash completely:
esptool.py --port /dev/ttyXXX erase_flash
Erase flash also as a troubleshooting measure, if a module doesn't behave as expected.
To flash MicroPython image to your ESP8266, use:
$ make deploy
This will use the esptool.py
script to download the images. You must have
your ESP module in the bootloader mode, and connected to a serial port on your PC.
The default serial port is /dev/ttyACM0
. To specify another, use, eg:
$ make PORT=/dev/ttyUSB0 deploy
The image produced is firmware-combined.bin
, to be flashed at 0x00000.
Troubleshooting
While the port is still in alpha, it's known to be generally stable. If you experience strange bootloops, crashes, lockups, here's a list to check against:
- You didn't erase flash before programming MicroPython firmware.
- Firmware can be occasionally flashed incorrectly. Just retry. Recent esptool.py versions have --verify option.
- Power supply you use doesn't provide enough power for ESP8266 or isn't stable enough.
- A module/flash may be defective (not unheard of for cheap modules).
Please consult dedicated ESP8266 forums/resources for hardware-related problems.