-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can this be used on SBCs other than the rpi? #338
Comments
SPI might work - the other methods won’t |
Thank you for replying so quickly. Unfortunately, I am using SPI for this project. Do you know of any similar projects that might work for me? I can't think of anything else other than using an Arduino as an interface to the neopixels rather than connecting directly to the SBC. |
SPI might work - it should work if the rock64 has a well written kernel with SPI DMA support |
But I'm already using SPI for something else. Can I share SPI with something like this? |
Maybe - Linux on Pi (and I presume rock64) supports multiple devices with separate slave select signals. You’d need some logic to hide the data line from the leds when slave select is inactive. Does your other SPI device use slave select ? |
It looks like it doesn’t use slave select. Check out the PDF below. I
wonder if I could bitbang this.
https://github.com/SeeedDocument/ReSpeaker-4-Mic-Array-for-Raspberry-Pi/blob/master/src/ReSpeaker%204-Mic%20Array%20for%20Raspberry%20Pi%20%20v1.0.pdf
…On November 25, 2018 at 4:57:04 AM, penfold42 ***@***.***) wrote:
Maybe - Linux on Pi (and I presume rock64) supports multiple devices with
separate slave select signals.
You’d need some logic to hide the data line from the leds when slave
select is inactive.
Does your other SPI device use slave select ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#338 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOm5KJWrm-AMdRU2dOB9lc5j2wLDrTl4ks5uymlwgaJpZM4YxuSE>
.
|
It won't work because the driver modes are hardcoded based on the pin layout of the raspberry pi. See Lines 647 to 673 in a8441f6
Lines 675 to 733 in a8441f6
|
Hi! Can you esteem how big effort would be to port this library to odroid c2 if it's feasible at all? If not, what do you think, what would be the best approach to drive a NeoPixel strip from an odroid c2? I'm thinking about using an ESP8266 as a "driver IC" which would receive data over UART/I2C and would translate it and send to the strip, but it is a rather excessive solution. |
You can already drive neopixels with an esp, or Arduino, or teensy, or trinket or whatever. Just connect it to the odroid via usb, i2c, or uart and send commands directly to it. You might need a level shifter if you aren't using USB to communicate with it. Serial and USB are the easiest methods. |
I would like to use this on a rock64. (My pi blew up and I'm in a time crunch.). Is this possible?
The text was updated successfully, but these errors were encountered: