-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Good day.
My team and I are working on a small project that utilizes the RP2040 Nano Connect. Part of this project requires us to light some NeoPixels, yet we've had a heck of a time getting them to work.
After some hours debugging, we realized that for this controller, the NeoPixel library requires the GPIO pin rather than the Arduino pin. So, as an example: for this controller, we have D7 connected but had to provide GPIO 19 to the library to see output.
I'm not aware if this is documented anywhere and it certainly gave me a run for my money as, for example, on the Nano 33 IoT--which we swapped for the RP2040 to test our code to make sure we weren't blockheads as it has the exact same pinout--specifying D7 worked just fine and everything lit.
As this behavior is not standardized between controllers, I personally believe it would be best to update the library to handle this conversion internally. However, if this is too tall a task, then at least a documentation change somewhere would be better than none at all as it currently appears to be.
For an MRE: we couldn't get the strandtest example to work until we specified 19
for the pin, so feel free to use that.
We're using version 1.12.4.