-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support GRB neopixels as well as RGB as the status indicator #8469
Comments
You don't need a ESP32-S3-Zero board to test it, any board with an on-board neopixel should work, you will just verify that the colors are swapped. |
I have added support for this to my fork: (and a Disclaimer: I am definitely out my element in C as those are the first lines I've ever written in it. Initially I tried adding: I didn't submit this as a PR yet as its part of my ESP32-S3-Zero board support PR which currently has the wrong USB PID. I'm waiting for Waveshare to get back to me if they'll sort out a USB PID or if I should try to do so myself |
That sounds like a good approach! Thanks for the update. |
Fixed by #8497. |
The Waveshare ESP32-S3-Zero board (#8468) uses a Neopixel with different color order than RGB as the status LED, which means that it blinks green on error, and red on success. This is confusing for the users.
It would be nice to be able to specify a variable in the
mpconfigboard.h
for that board to swap the colors, so the errors are red and success is green.I think the easiest way to do that is to add an ifdef in the
supervisor/shared/status_leds.c
file around line 257-259 (https://github.com/adafruit/circuitpython/blob/main/supervisor/shared/status_leds.c#L257-L259) with an alternate color order.I could submit a PR for this, but it seems to be a good first issue, so maybe someone wants to take it.
The text was updated successfully, but these errors were encountered: