ESP8266 I2S WS2812 Driver

Provides more reliable WS2812 driving... And a nifty websockets-based interface for the ESP8266.
If you want to watch a video about this project, click the video link below.

Note: Most of the functionality is imported from a submodule (esp82xx). The submodule is more regularly updated and most of the technical description and troubleshooting advice is located there. You might want to cd esp82xx; git pull origin master; to fix (or sometimes introduce new) errors. The dev branch of both esp9266ws2812i2 and esp82xx might even be more cutting etch.

This project is based off of the Espressif I2S interface for an mp3 player

If you want more information about the build environment, etc. You should check out esp82xx.

This project is still jankey and needs some cleanup.
The way it currently works is to continuously send WS2812 frames and when new data comes in on port 7777, it just updates the frames.

I wanted to make it so it would stop doing all DMA proesses so it could save bus contention, but I couldn't figure out how to make that happen.
If I tried disabling and re-enabling, it seems to have caused the DMA to just freak out and turn off until chip reboot.

The WS2812 output is synthesized from the input buffer. Any time a 0 is to be transmitted, we need a .3us pulse high and .9us low.
If a 1, then we send a .9us high with a .3us low. The way we do this is we look at nibbles, i.e.:

0101 would convert into: 1000 1110 1000 1110 < bitstream that actually gets shipped out.

Unfortunately this does mean it takes up 4x the space in RAM to DMA the data... But, it is very fast and efficient.

Hardware Connection

Unfortunately the I2S Output pin is the same as RX1 (pin 25), which means if you are programming via the UART, it'll need to be unplugged any time you're testing. The positive side of this is that it is a pin that is exposed on most ESP8266 breakout boards.

Memory layout:

We use a bit of a modified take on the old memory layout since, while we support OTA upgrades, we do so in a different way than the normal way. Not that HTTP is limited on parts with <1M, and OTA flashing is not supported at all on parts with <512kB.