Oh that looks complex. ![:)]( "Smile")
That amount of complexity isn't a good fit for PIO. An interesting programming challenge, but can't really be held up as an example to follow. It's like trying to BeagleBone PRU things with a PIO. But the latter is best used for state machine use cases running program fragments, and higher level operations are best orchestrated using one of the cores. So no surprise that folks are not jumping in quickly to analyze the code.
I'm too much of a PIO novice to recommend anything, but am interested to know how the program can be improved upon.
I think you can save one instruction for the WS2812 off tx with:
And maybe a redundant set pins.
That amount of complexity isn't a good fit for PIO. An interesting programming challenge, but can't really be held up as an example to follow. It's like trying to BeagleBone PRU things with a PIO. But the latter is best used for state machine use cases running program fragments, and higher level operations are best orchestrated using one of the cores. So no surprise that folks are not jumping in quickly to analyze the code.I'm too much of a PIO novice to recommend anything, but am interested to know how the program can be improved upon.
I think you can save one instruction for the WS2812 off tx with:
Code:
set pins 1 [1] ; mov pins x [3]Statistics: Posted by katak255 — Sat Jan 03, 2026 9:16 am