-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Arduino-ESP32 version 3.0.0 does not compile with LilyGo T-display S3 and TFT_eSPI #3355
Comments
See this link for a workaround: #3346 |
Thanks for this suggestion!
Updated to version arduino-ESP32 version 3.0.1 .... The above mentioned compile error complaining about gpio_get_level is persistent in the new situation: This is NOT solving the problem! |
Try add it in TFT_eSPI_ESP32_S3.h. |
"Try add it in TFT_eSPI_ESP32_S3.h. Worked for me too. |
Yes, I can compile but the screen remains black. It worked before |
I have added // Processor ID reported by getSetup()
#define PROCESSOR_ID 0x32
// Include processor specific header
#include "soc/spi_reg.h"
#include "driver/spi_master.h"
#include "hal/gpio_ll.h"
#include "driver/gpio.h" I have tested this with arduino-ESP32 version 2.0.17 and the latest version: 3.0.1 Please include this in the next TFT_eSPI version! |
Board: LilyGo T-display S3 --> Board manager setting: "ESP32S3 Dev Module" with the right Tools settings
Arduino IDE version: 2.3.2; CLI Version: 0.35.3
TFT_eSPI version: 2.5.43; previous version: 2.5.34
Arduino-ESP32 version: 2.0.17
--> All my code compiles without problems and works fine with TFT_eSPI (versions 2.5.43 and 2.5.34) !!
After installing: Arduino-ESP32 version 3.0.0;
Compilation error: exit status 1
After re-installing Arduino-ESP32 version: 2.0.17 ---> NO Compilation error
Compliation Error is NOT dependent on the TFT_eSPI version. All my code works fine with TFT_eSPI and the LilyGo board of version 2.0.17 and previous
Our friends with Espressif have made changes (once again) that break up the TFT_eSPI library for this board (and others?).
The text was updated successfully, but these errors were encountered: