conflict with neopixelWrite or GPIO48 on ESP32S3? #3119
Unanswered
Sisyphos0
asked this question in
Q&A - General
Replies: 1 comment
-
This sounds like a resource conflist. I suspect the Neopixel driver is using the SPI resource to drive the serial signal to the LED. Check your Neopixel library requirements. Maybe allocating a different SPI port will fix this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using this great lib already on a multitude of projects with a multitude of TFTs (most on ESP8266 and ESP32). Thanks a lot Bodmer for this great work!
I now switched to ESP32S3 in a project where I'm using the build-in RGB-Led on GPIO 48.
I connected an ILI9341 and everything is working fine.
But after calling
tft.init()
theneopixelWrite()
function isn't working anymore, sketch is not hanging or crashing but the RGB-Led is no more responding to theneopixelWrite()
commands... (function still working before callingtft.init()
)Already checked in TFT_eSPI.h/.cpp, TFT_config.h, TFT_Drivers,Processors but could not find anything wich is obviously conflicting with neopixel functions or GPIO48.
As the TFT doesn't have a MISO output I tried with TFT_MISO 12, -1 and #undef, -, no changes.
Using:
bblanchon/ArduinoJson@^6.21.5
me-no-dev/ESP Async WebServer@^1.2.3
sv-zanshin/DS3231M@^1.0.8
bodmer/TFT_eSPI@^2.5.43
What am I missing? Did anyone had the same problem?
Beta Was this translation helpful? Give feedback.
All reactions