Replies: 5 comments 5 replies
-
What board support are you using? I don't have a RP2350 to test with, but the changes look pretty boiler plate. Try this branch and let me know if it works. |
Beta Was this translation helpful? Give feedback.
-
That branch worked great! All 12 Pio outputs working fine across all 3 Pio instances on a Raspberry Pi Pico 2. Thank you! |
Beta Was this translation helpful? Give feedback.
-
created a tracking issue and merged the changes into master for the next release |
Beta Was this translation helpful? Give feedback.
-
So, continuing on the pico PIO theme, what would be the best way to implement sending data to 8 strings at a time via a shift-register like a 74AHC595 chip? On a chip like the RP2350 with 12 state machines, you could send out data for a whopping 96 pixel strings all via PIO, so you'd hardly touch the main cores to drive the pixels. Could it be implemented within NPB? It's been done here, but in CircuitPython, as an example: https://learn.adafruit.com/neopio-drive-lots-of-leds-with-raspberry-pi-pico/overview I guess my end goal is take in UDP pixel data and send that out to the pixels via the state machines and shift-registers. |
Beta Was this translation helpful? Give feedback.
-
I just started a new project with a pico-2, any chance we could get a release containing the pico-2 support. And FYI, I think the constant got renamed I am testing the github head currently, but my strip stays dark (https://gist.github.com/ensonic/18c8205156b98affe5d1026a88910193). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks for adding support for the RP2040 as well as #873 adding support for 2 PIO instances. How hard would it be to add support for a 3rd PIO instance for the RP2350?
Beta Was this translation helpful? Give feedback.
All reactions