kwyn
Tessel2 incompatibility
This library specifies 'Tessel' as if all hardware works, but in reality only Tessel1 (not Tessel2) is compatible. This is due to:
npx/lib/npx.js: var hw = process.binding('hw');
...since Tessel2 does not implement the hw library.
Hi Michaesc
Did you ever find a solution to this issue, since I am struggling with it too?
There is no easy solution to this, and nothing has been implemented to make WS2812B work with Tessel2. As far as I know (please confirm this with other Tessel devs) the Tessel1 had only a microcontroller (fast enough IO to drive WS2812B) and connected directly to the GPIO breakout circuit. The Tessel2 has a microcontroller as well, but a separate microprocessor is what runs the OS and is connected to both UART CPLD (for USB connections) and the GPIO ten pin headers (for peripheral I/O.) I'm not even sure what role the microcontroller plays in the Tessel2, but it seems that it has no direct access to the GPIO pins.
To make WS2812B ICs work on the Tessel2 we need a leap of faith and design both new hardware and software from scratch to work around the architecture difference described above.
Disclaimer: I'm writing this from the gut, trying to remember information I've learned over time. It's possible I've misunderstood or poorly described the situation, so please get a second opinion if you want to start working on the problem.
MODULES!
Coincidentally, my ten pin Neopixel modules just arrived from the PCB printers. I haven't bothered to populate the boards with WS2812B ICs yet, but welcome discussion about this topic.
I haven't advertised the fact that I made Neopixel modules anywhere, and I just have a few boards.