ESP32 S3 TFT_eSPI ili9486

Other Hardware Displays
1

I know this topic is all over the internet...but I've been reading all the links I can find and nothing seems to address my problem.

I've been using Bodmer's library with a 4" ILI9486 SPI screen and ESP32.
ESP32 DEV board works fine, display and touch...no problems!
Change to ESP32 S3 and it all goes pear shaped, as reported in many internet links.
I've created a simple prog just to test(same prog on both boards, ESP32 works and ESP32 S3 doesn't.

straight off the S3 continuously reboots.
regressed the Espressif board to 2.0.14 and reboot stops but screen is dead.
changed the SPI config to HSPI pins in 30 range with the define but screen is dead.

anybody got any further ideas??

//
//  ESP32 S3 DEV with ILI9486
//
#include "TFT_eSPI.h" // Hardware-specific library
//#include "SPI.h"

/*
                    set up for esp32 S3 dev in user_setup.h


 TFT_MISO 13		          // dont connect MISO pin to TFT miso if using touch
 TFT_MOSI 11		          // MOSI
 TFT_SCLK 12
 TFT_CS   10              // Chip select control pin
 TFT_DC   17              // Data Command control pin
 TFT_RST  16              // Reset pin (could connect to RST pin)
 TFT_LED  8

 T_clk    12
 T_CS     18              // Chip select pin (T_CS) of touch screen
 T_DIN    11              // MOSI
 T_dO     13              // MISO
*/

TFT_eSPI tft = TFT_eSPI(); // Invoke custom library with default width and height

void setup() 
{

//  Serial.begin(115200);
//  Serial.println("ESP32_SPI_9486_v1.1");
  
  tft.init();
  tft.setRotation(3);
  tft.fillScreen(TFT_BLACK);
  tft.setTextColor(TFT_WHITE);

 tft.setCursor(50,50);
 tft.setTextSize(2);
 tft.print("test at 50,50");
}

void loop() 
{   

}
ILI9488 con ESP32-S3 schermo bianco
How to remove Arduino IDE comletely! from my PC
2

Why did you change the board's level? Did you read somewhere that the S3 had a board 3 issue? If that is the case, you have two options. Wait until the library is fixed (or use a 'better' library) or pull a fork and fix it yourself.

3

Yes, the problem has been resolved by some by regressing. The problem goes back to 2020/22 but from continuous googling I don't think Bodmer, or anybody else has a fix. I may be wrong, and that is exactly why I have posted this. The regressing hasn't fixed it for me, and there are many comments to the effect that regressing shouldn't be the answer to fixing a problem.

I am reluctant to use another library as I do like Bodmer's library, but if nobody has solved this, and there is no update to the library, I suppose I will have to use a different library, one that works with S3.

creating a fork is well above my pay grade.

4

Have you looked at the Migration document to see if you are affected by the Board's 3.x issue? Have you looked at the Library Issues to see what has been reported and its current status, and if there is a fork that fixes it but may not be in GA status yet?

5

The crash problem has been reported to the developer many times over:

So I think that @vsl's workaround of downgrading their "esp32" boards platform installation to 2.0.14 is reasonable. I haven't read through the discussions in all those reports I linked above. It is possible the community has found an alternative workaround and described it in one of those, so it would be worth looking through them if you are unsatisfied with using the old version of the "esp32" platform.

For now, I would recommend focusing on the "screen is dead" problem @vsl is having now.

6

thanks for that...I had seen most of them, but the last one from May 25(stenliczz) I hadn't seen. I followed that advice but it didn't make any difference. The poster has asked for an update from Bodmer, but so far no reply.

I continue to fiddle.

7

I have same isuise. ESP-IDF v5.4.1
Iwill write one more bug report.
Do you have any idea how to work with ILI9486 and LVGL lib in ESP-IDF?

8

I'll be pleased to hear how you get on with the bug report.
I'm sorry but I don't have any experience of using the LVGL lib or esp-idf.

9

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.