ESP32 V3.0.0 doesn't support LCD8, LCD16 and RGBPanel anymore - what can i do now?
Posted: Sun Jun 02, 2024 5:00 pm
the problem is this:
i own a ESP32-S3 with a display on it (JC8048W550). In the ESP32 V2.0.x i used the RGBPanel function everything works. Now i have a ESP32-C6 and installed V3.0.0 because that is the only version which includes ESP32-C6. If i now try to compile the old program for the
ESP32-S3 there are many errors because RGBPanel is no longer supported by Espressif.
Why ost this really a pain? If iwant to compile with Arduino 2.3.2 i have to choose ESP V2.0.x for ESP32-S3 and than change it to ESP V3.0.0 if i want to compile with ESP32-C6. All precompiled librarys are gone after i change this and the compile needs more than 15 minutes to end! There is no way to install 2 versions of Arduino.
I don't really understand why this was done (eliminate the LCD8, LCD16, RGBPanle functionallity).
Any explanation or idea to get around this problem with V3.0.0 would be very appriciated.
hape
i own a ESP32-S3 with a display on it (JC8048W550). In the ESP32 V2.0.x i used the RGBPanel function everything works. Now i have a ESP32-C6 and installed V3.0.0 because that is the only version which includes ESP32-C6. If i now try to compile the old program for the
ESP32-S3 there are many errors because RGBPanel is no longer supported by Espressif.
Why is that no longer supported because now V2.0.x is incompatible with V3.0.0 .Arduino_ESP32RGBPanel *rgbpanel = new Arduino_ESP32RGBPanel(
^~~~~~~~~~~~~~~~~~~~~
Arduino_ESP32SPIDMA
Arduino_GFX_dev_device.h:185:1: error: 'Arduino_RGB_Display' does not name a type
Why ost this really a pain? If iwant to compile with Arduino 2.3.2 i have to choose ESP V2.0.x for ESP32-S3 and than change it to ESP V3.0.0 if i want to compile with ESP32-C6. All precompiled librarys are gone after i change this and the compile needs more than 15 minutes to end! There is no way to install 2 versions of Arduino.
I don't really understand why this was done (eliminate the LCD8, LCD16, RGBPanle functionallity).
Any explanation or idea to get around this problem with V3.0.0 would be very appriciated.
hape