-
Notifications
You must be signed in to change notification settings - Fork 340
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
rpi_ws281x not compatible with pi 5 #747
Comments
Yep, we're aware of it. Thanks. It doesn't sound like it will happen very soon. In the mean time, you might want to try out https://github.com/adafruit/Adafruit_CircuitPython_NeoPixel_SPI. |
@makermelissa I also faced a similar problem and tried SPI, as you suggested. See here |
Another option to try if you don't want to wait for the driver to be fixed, is to have use a NeoDriver (https://www.adafruit.com/product/5766) to separately control the lights. |
I bought an Arduino Uno instead for now |
Board Name
Raspberry Pi 5
Steps
Output of example from here- https://learn.adafruit.com/neopixels-on-raspberry-pi/python-usage:
File "/root/test.py", line 64, in
pixels.show()
File "/root/env/lib/python3.11/site-packages/adafruit_pixelbuf.py", line 204, in show
return self._transmit(self._post_brightness_buffer)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/env/lib/python3.11/site-packages/neopixel.py", line 180, in _transmit
neopixel_write(self.pin, buffer)
File "/root/env/lib/python3.11/site-packages/neopixel_write.py", line 42, in neopixel_write
return _neopixel.neopixel_write(gpio, buf)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/env/lib/python3.11/site-packages/adafruit_blinka/microcontroller/bcm283x/neopixel.py", line 83, in neopixel_write
raise RuntimeError(
RuntimeError: ws2811_init failed with code -3 (Hardware revision is not supported)
swig/python detected a memory leak of type 'ws2811_t *', no destructor found.
Description
The error appears to be from rpi_ws281x
The issue is currently being worked on:
jgarff/rpi_ws281x#528
Additional information
No response
The text was updated successfully, but these errors were encountered: