WS2812 / NeoPixel addressable LED strips for PyMCU — compiled to native machine code, with no interpreter on the chip.
pymcu install neopixelWhich one you get depends on the stdlib layer your project declares. The import is
always neopixel.
Native (stdlib unset):
from neopixel import NeoPixel
strip = NeoPixel("PD6", 8)
strip[0] = (255, 0, 0)
strip.show()MicroPython (stdlib = ["micropython"]) — a MicroPython script, unchanged:
from machine import Pin
from neopixel import NeoPixel
np = NeoPixel(Pin(6), 8)
np[0] = (255, 0, 0)
np.write()CircuitPython (stdlib = ["circuitpython"]) — a CircuitPython script, unchanged:
import board
import neopixel
pixels = neopixel.NeoPixel(board.D6, 8, auto_write=False)
pixels.fill((0, 32, 0))
pixels.show()None of those three files contains a single conditional: the layer adapters are plain
Python written against each API as it is documented upstream. Everything that has to
know about a chip lives in one private module, _neopixel.core, and the compiler folds
it away.
Colours live in a per-strip SRAM framebuffer, 3 bytes per pixel in WS2812 wire order —
24 bytes for a strip of 8, and nothing else. Every method is @inline, so no object is
allocated on the device and no method call survives compilation.
Measured figures per chip are published in the library index, and the flash cost of every example in this repo is in docs/Getting-started.md.
WS2812 / WS2812B / NeoPixel strips on AVR (ATmega328P and friends) at 16 MHz, on
pins PB0-PB5 and PD2-PD7. show() / write() disables interrupts for the
duration of the transmission and restores them afterwards, since WS2812 bit timing has
no clock line to resynchronize against — see
docs/How-it-works.md.
Bit timing (750 ns / 437.5 ns high pulses, inside both the WS2812 and WS2812B
datasheet windows) is verified by tests/test_timing.py, which compiles a probe
program and measures it cycle-by-cycle on the avr8sharp AVR emulator — not yet
verified against a real strip on a logic analyzer. One pin, PB0, is not yet covered
by this fix and should be avoided until it is. See
docs/How-it-works.md
for the measured numbers, the PB0 gap, and how the numbers were obtained.
Other architectures raise a compile-time error rather than returning something that
looks like it worked. Ports are welcome: _neopixel/avr.py is the whole contract —
see docs/Porting-to-a-new-architecture.md.
Five complete, buildable PyMCU projects live under
examples/: the native,
MicroPython and CircuitPython APIs doing the same fill-and-blink, plus a per-pixel
colour wipe and an auto_write demo. See
docs/Getting-started.md for how to build them and their
measured flash cost.
- docs/Home.md — start here
- docs/Getting-started.md
- docs/The-three-APIs.md
- docs/How-it-works.md
- docs/Porting-to-a-new-architecture.md
- docs/Troubleshooting.md
MIT.