This PR reflects @nurikk / @nurikk-sa ftdi development without the jointup of the SPI and ftdi device code (see #1595).
The PR introduces ftdilib1 led device implementation. FTDI chips are common usb2serial/spi/whatever chips, and are available for 5-10$ from Chinese website as various breakout boards.
My wiring is following:
FTDI | APA102
AD0 -> CLOCK
AD1 -> DATA
AD3 -> CS (active low) // can be used to drive logic shifter OE pins
FTDI | WS2812 or SK6812
AD1 -> DATA
AD3 -> CS (active low) // can be used to drive logic shifter OE pins
What kind of change does this PR introduce? (check at least one)
[ ] Bugfix
[X] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Build-related changes
[ ] Other, please describe:
If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
[ ] Yes
[X] No
If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:
[ ] When resolving a specific issue, it's referenced in the PR's body (e.g. Fixes: #xxx[,#xxx], where "xxx" is the issue number)
If adding a new feature, the PR's description includes:
[X] A convincing reason for adding this feature
[ ] Related documents have been updated (docs/docs/en)
[ ] Related tests have been updated
PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD
[ ] Yes, CHANGELOG.md is also updated
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Summary
This PR reflects @nurikk / @nurikk-sa ftdi development without the jointup of the SPI and ftdi device code (see #1595).
The PR introduces
ftdilib1
led device implementation. FTDI chips are common usb2serial/spi/whatever chips, and are available for 5-10$ from Chinese website as various breakout boards.My wiring is following:
What kind of change does this PR introduce? (check at least one)
If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:
Fixes: #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: