-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
Wrong PIN for RGB LED on board lolin_s3_mini #9037
Comments
hello, i get similar warnings when loading code, but the code is running In the pin definition for LOLIN S3mini, i made the proposed changes of @mp-se and the warning have disapeared. |
The change has already been implemented for the esp32s3 board here https://github.com/espressif/arduino-esp32/blob/master/variants/esp32s3/pins_arduino.h. So it has partly been implemented for some of the s3 boards but this should apply for all boards based on the s3 variant. |
I believe the colour order is different too? The example sketch
Indeed,
|
This has been fixed for the Arduino Core 3.0.0 |
We are close to release Arduino 2.0.15. |
PR #9381 will add/backport all changes to 2.0.15 |
Fixed by #9381 |
Board
lolin_s3_mini
Device Description
Its not possible to control the RGB led on this board with the neopixelWrite() function since the PIN number is wrong in the pins_arduino.h
The pin definition for this board is
#define RGB_BUILTIN LED_BUILTIN
In neopixelWrite the following operation is done
So the for this to work the definition for this board needs to be
#define RGB_BUILTIN LED_BUILTIN+SOC_GPIO_PIN_COUNT
Not sure if the macro or the LED_BUILTIN constant should be changed so I put it as a bug report instead of PR.
If this is changed its possible to change the rgb led color on this board.
Hardware Configuration
Just plain board not connections
Version
v2.0.14
IDE Name
PlatformIO
Operating System
Windows 11
Flash frequency
40
PSRAM enabled
yes
Upload speed
115200
Description
It should be possible to control the RGB led with neopixel on this board.
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: