Closed tinker2much closed 4 years ago
The pixels don't require precise timing or anything, so software SPI is fine. And if you are doing a Christmas project using two GPIO pins, why not use pins 12 and 25 to mark the date? A kind of Christmas Easter Egg.
I missed the Easter egg (hangs head).
I may have some further questions. Would you be willing to hear them, and if so would you prefer to do this in direct emails like this one, in the issue on GitHub, or on the raspberry forum where I’ve had a thread going for a while?
On Jan 7, 2020, at 11:22 AM, Ben Nuttall notifications@github.com wrote:
The pixels don't require precise timing or anything, so software SPI is fine. And if you are doing a Christmas project using two GPIO pins, why not use pins 12 and 25 to mark the date? A kind of Christmas Easter Egg.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
This is more a request for information than an issue. I just wonder why you're not using the actual SPI pins, 19 and 23. I've heard of "hardware SPI" versus "bit banging", and it seems you're doing the latter? - physical pin 22 == GPIO 25 (used for clock? ) physical pin 32 == GPIO 12 (used for data? )
Could you please provide the thinking behind your approach?