Library for the WS2812 LED Driver. Uses bit banging and nops for precise timing. Number of nops executed are configurable at run time.
This library uses bit banging to control the LED strip. Because the mbed platform doesn't have a timer standardized that doesn't have a resolution lower a microsecond, we have to use NOPs. Also, the time it takes to toggle a GPIO pin is not consistent across platforms and it does not correlate to the system clock in any way. It is completely dependent on the platform's implementation.
I have a found the timings for a few boards. They are currently listed on the example program page below.
When using this on a new platform, you'll need to use a logic analyzer to determine the timings.
Above is a screenshot from a Saleae logic analyzer. You'll notice that the "1" pulse is longer than the "0" pulse. The "Data low" pulses should be consistent. The timing requirements for these pulses can be found below (Source: http://wp.josh.com/2014/05/13/ws2812-neopixels-are-not-so-finicky-once-you-get-to-know-them/).
If you find timings for a new board you're using, please PM me or start a discussion below and I'll add it to this page!
For more on the timings and data format of the WS2812 drivers, you should read the datasheet and the article "NeoPixels Revealed: How to (not need to) generate precisely timed signals" listed below.
WS2812B Datasheet: https://www.adafruit.com/datasheets/WS2812B.pdf
"NeoPixels Revealed: How to (not need to) generate precisely timed signals": http://wp.josh.com/2014/05/13/ws2812-neopixels-are-not-so-finicky-once-you-get-to-know-them/
|1:aadbf08c62a2||2015-02-12||bridadan||Updated documentation and cleaned up code|
|0:0b79cafcb387||2015-02-12||bridadan||Driver for the WS2812 LED driver. Uses bit banging and relies on nops for timing. Number of nops can be varied to potentially accommodate different platforms. Currently tested on the K64F.|