For the SPIBladePtr<>, do you have a complete list per-board of what pins can be used for the data pin and clock pin? The name of the blade made me think at first perhaps only certain combos could be used. Like for example on a PB3 blade3Pin for data, and blade5Pin (which are listed as MOSI1 and SCK1 respectively), however the POD says that any of the bladeXPins can be used… along with saying potentially others might work depending on the board?
Does that mean that any pin that would work for driving a WS281X strip would work for either of those pads, or what? (Not sure what the software/driver backend looks like and what’s required)
SPIBladePtr<> currently uses pure software for output, so any GPIO-capable pins will work. It’s not particularly efficient, but not a lot of people use it, and those who do usually use it for fairly short strings of LEDs.
Future implementations might make use of SPI hardware to output data, which could potentially be much faster and more efficient, but would require that you use one of the MOSI/SCK pins to work.
1 Like
Awesome, thanks for the clarification!
@profezzorn As a follow-up on this, does that mean you can use a SPIBladePtr on pads that share a timer with other data lines and still drive dumb LEDs (or other things) via PWM with them?
Yes. SPIBlade currently doesn’t use any timers at all.
If there is a need, I can probably add some code so that it will use the actual SPI hardware if you specify the right pins. (Which still wouldn’t use any timers.)
1 Like
Awesome, thanks!
I don’t have a need… I’m just researching things to ensure I’m understanding correctly for ProffieConfig V2 development, so that I make as few mistakes and oversights as possible (there’ll be plenty as it stands I’m sure 
)