Universal Display Driver for ST7701 in ESP32-4848S040

[ameeuw]

Hi everyone, another day another ESP32-S3 display device.

The device in question is the ESP32-4848S040 which hosts a 480x480 LCD driven by a ST7701 controller via RGB interface.

I have not found any approaches to using the Universal Display Driver so I have started by myself but I seem to be very stuck. As a start here is my approach and what I have so far:

Step 1: What information do we have?

The manufacturer (I assume) provides a zip with a bunch of files about the device.

Pinout

The pins line up with a table describing the pin description:

IO4		DB1(B)
IO5		DB2(B)
IO6		DB3(B)
IO7		DB4(B)
IO15		DB5(B)
IO16		HSYNC
IO17	U1TXD	VSYNC
IO18	U1RXD	DE
IO8		DB6(G)
IO3	JTAG	DB8(G)
IO46	log	DB9(G)
IO9		DB10(G)
IO10	SPICS0	DB11(G)
IO11	SPID	DB13(R)
IO12	SPICLK	DB14(R)
IO13	SPIQ	DB15(R)
IO14		DB16(R)
IO43	U0TXD	TX
IO44	U0RXD	RX
IO1		I2S-BCLK/L3
IO2		I2S-LRCLK/L2
IO42		TF(D3)
IO41		TF(D1)
IO40		IS2-DIN/L1
IO39		LCD_CS
IO38		BL_C
IO37
IO36
IO35
IO0	BOOT	DB17(R)
IO45	VSPI	TP_SCL
IO48	SPICLK_N	TF(SCK)
IO47	SPICLK_P	TF(SDA)
IO21		PCLK
IO20	USB_D+	DB7(G)
IO19	USB_D-	TP_SDA

Example

An example which uses the ArduinoGFX library and instantiates the panel as follows:

Arduino_ESP32RGBPanel *bus = new Arduino_ESP32RGBPanel(
    39 /* CS */, 48 /* SCK */, 47 /* SDA */,
    18 /* DE */, 17 /* VSYNC */, 16 /* HSYNC */, 21 /* PCLK */,
    11 /* R0 */, 12 /* R1 */, 13 /* R2 */, 14 /* R3 */, 0 /* R4 */,
    8 /* G0 */, 20 /* G1 */, 3 /* G2 */, 46 /* G3 */, 9 /* G4 */, 10 /* G5 */,
    4 /* B0 */, 5 /* B1 */, 6 /* B2 */, 7 /* B3 */, 15 /* B4 */
);
Arduino_ST7701_RGBPanel *gfx = new Arduino_ST7701_RGBPanel(
    bus, GFX_NOT_DEFINED /* RST */, 0 /* rotation */,
    true /* IPS */, 480 /* width */, 480 /* height */,
    st7701_type1_init_operations, sizeof(st7701_type1_init_operations), true /* BGR */,
    10 /* hsync_front_porch */, 8 /* hsync_pulse_width */, 50 /* hsync_back_porch */,
    10 /* vsync_front_porch */, 8 /* vsync_pulse_width */, 20 /* vsync_back_porch */);

The initialisation sequence used is in the ArduinoGFX library:

static const uint8_t st7701_type1_init_operations[] = {
    BEGIN_WRITE,
    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x10,

    WRITE_C8_D16, 0xC0, 0x3B, 0x00,
    WRITE_C8_D16, 0xC1, 0x0D, 0x02,
    WRITE_C8_D16, 0xC2, 0x31, 0x05,
    WRITE_C8_D8, 0xCD, 0x00,//0x08

    WRITE_COMMAND_8, 0xB0, // Positive Voltage Gamma Control
    WRITE_BYTES, 16,
    0x00, 0x11, 0x18, 0x0E,
    0x11, 0x06, 0x07, 0x08,
    0x07, 0x22, 0x04, 0x12,
    0x0F, 0xAA, 0x31, 0x18,

    WRITE_COMMAND_8, 0xB1, // Negative Voltage Gamma Control
    WRITE_BYTES, 16,
    0x00, 0x11, 0x19, 0x0E,
    0x12, 0x07, 0x08, 0x08,
    0x08, 0x22, 0x04, 0x11,
    0x11, 0xA9, 0x32, 0x18,

    // PAGE1
    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x11,

    WRITE_C8_D8, 0xB0, 0x60, // Vop=4.7375v
    WRITE_C8_D8, 0xB1, 0x32, // VCOM=32
    WRITE_C8_D8, 0xB2, 0x07, // VGH=15v
    WRITE_C8_D8, 0xB3, 0x80,
    WRITE_C8_D8, 0xB5, 0x49, // VGL=-10.17v
    WRITE_C8_D8, 0xB7, 0x85,
    WRITE_C8_D8, 0xB8, 0x21, // AVDD=6.6 & AVCL=-4.6
    WRITE_C8_D8, 0xC1, 0x78,
    WRITE_C8_D8, 0xC2, 0x78,

    WRITE_COMMAND_8, 0xE0,
    WRITE_BYTES, 3, 0x00, 0x1B, 0x02,

    WRITE_COMMAND_8, 0xE1,
    WRITE_BYTES, 11,
    0x08, 0xA0, 0x00, 0x00,
    0x07, 0xA0, 0x00, 0x00,
    0x00, 0x44, 0x44,

    WRITE_COMMAND_8, 0xE2,
    WRITE_BYTES, 12,
    0x11, 0x11, 0x44, 0x44,
    0xED, 0xA0, 0x00, 0x00,
    0xEC, 0xA0, 0x00, 0x00,

    WRITE_COMMAND_8, 0xE3,
    WRITE_BYTES, 4, 0x00, 0x00, 0x11, 0x11,

    WRITE_C8_D16, 0xE4, 0x44, 0x44,

    WRITE_COMMAND_8, 0xE5,
    WRITE_BYTES, 16,
    0x0A, 0xE9, 0xD8, 0xA0,
    0x0C, 0xEB, 0xD8, 0xA0,
    0x0E, 0xED, 0xD8, 0xA0,
    0x10, 0xEF, 0xD8, 0xA0,

    WRITE_COMMAND_8, 0xE6,
    WRITE_BYTES, 4, 0x00, 0x00, 0x11, 0x11,

    WRITE_C8_D16, 0xE7, 0x44, 0x44,

    WRITE_COMMAND_8, 0xE8,
    WRITE_BYTES, 16,
    0x09, 0xE8, 0xD8, 0xA0,
    0x0B, 0xEA, 0xD8, 0xA0,
    0x0D, 0xEC, 0xD8, 0xA0,
    0x0F, 0xEE, 0xD8, 0xA0,

    WRITE_COMMAND_8, 0xEB,
    WRITE_BYTES, 7,
    0x02, 0x00, 0xE4, 0xE4,
    0x88, 0x00, 0x40,

    WRITE_C8_D16, 0xEC, 0x3C, 0x00,

    WRITE_COMMAND_8, 0xED,
    WRITE_BYTES, 16,
    0xAB, 0x89, 0x76, 0x54,
    0x02, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0x20,
    0x45, 0x67, 0x98, 0xBA,

    //-----------VAP & VAN---------------
    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x13,

    WRITE_C8_D8, 0xE5, 0xE4,

    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x00,

    WRITE_C8_D8, 0x3A, 0x60, // 0x70 RGB888, 0x60 RGB666, 0x50 RGB565

    //WRITE_COMMAND_8, 0x21,0X00,
    //END_WRITE,
     
    DELAY, 10,
    WRITE_COMMAND_8, 0x11, // Sleep Out
    END_WRITE,

    DELAY, 120,

    BEGIN_WRITE,
    WRITE_COMMAND_8, 0x29, // Display On

    END_WRITE};

Start porting

I have now started a display.ini and the following things are clear:

• Header
• Video signal
• Touch interface

:H,ST7701,480,480,16,RGB,18,17,16,21,38,4,5,6,7,15,8,20,3,46,9,10,11,12,13,14,0,14
:V,1,10,8,50,1,10,8,20,0
:TI1,5d,45,19,-1,-1

However, I have hit a barrier when trying to embed the information of CS, SCK, and SDA of the display controller in order to send the initialisation sequence commands, which I have transcribed from the above sequence as such:

:I
FF,5,77,01,00,00,10
C0,2,3B,00
C1,2,0D,02
C2,2,31,05
CD,1,00
B0,16,00,11,18,0E,11,06,07,08,07,22,04,12,0F,AA,31,18
B1,16,00,11,19,0E,12,07,08,08,08,22,04,11,11,A9,32,18
FF,5,77,01,00,00,11
B0,1,60
B1,1,32
B2,1,07
B3,1,80
B5,1,49
B7,1,85
B8,1,21
C1,1,78
C2,1,78
E0,3,00,1B,02
E1,11,08,A0,00,00,07,A0,00,00,00,44,44
E2,12,11,11,44,44,ED,A0,00,00,EC,A0,00,00
E3,4,00,00,11,11
E4,2,44,44
E5,16,0A,E9,D8,A0,0C,EB,D8,A0,0E,ED,D8,A0,10,EF,D8,A0
E6,4,00,00,11,11
E7,2,44,44
E8,16,09,E8,D8,A0,0B,EA,D8,A0,0D,EC,D8,A0,0F,EE,D8,A0
EB,7,02,00,E4,E4,88,00,40
EC,2,3C,00
ED,16,AB,89,76,54,02,FF,FF,FF,FF,FF,FF,20,45,67,98,BA
FF,5,77,01,00,00,13
E5,1,E4
FF,5,77,01,00,00,00
3A,1,60
11
29
:O,29
:o,28

To me it seems that we need to also describe the display as SPI device with a header that would look like this:

:H,ST7701,480,480,SPI,1,39,48,47,-1,-1,-1,-1,-1,6

Questions

• How to initialise the controller via SPI and then drive it using RGB?
• Does a double header make any sense?
• Does the initilisation sequence work?
• What about wait times at the end?
• What about single commands?

Would love to get somebody experienced in on this to work it out together.

[gemu2015]

this kind of display was already discussed and solved in another thread. i forgot to update the display docs.
the :I designator must be: (give pin numbers here)
:IS,clk,mosi,cs,reset
however currently this is done via software spi only which means there may be problems with an SD card on the same bus.

[gemu2015]

unfortunately not. i added this option on request from a user in this forum, but currently can't find the discussion

[s-hadinger]

For SD card on the same bus you need to disable DMA.

With the forthcoming Core3 based on esp-idf 5.1, do you think we can improve cohabitation of DMA for display and SD card?

[gemu2015]

did not yet dig into this, actually i do not think so. probably we need an option to wait for DMA complete to circumvent this problem.
but DMA is only relevant for SPI driven not RGB displays. LVGL DMA option does not make any sense with RGB displays.
in this special RGB display SPI bus is only used for initializing the chip

[ameeuw]

Hmm, I tried to find the discussion by filtering for ":H in:body,title,comments commenter:gemu2015" but could not see anything relevant. Can you find the relevant discussion?

https://github.com/arendst/Tasmota/discussions?discussions_q=%3AH%2C+in%3Abody%2Ctitle%2Ccomments+commenter%3Agemu2015+sort%3Adate_created+

[gemu2015]

very strange, i committed this change on Sep 27, 2023 , so the discussion had to be about a week before
may it has been deleted ?

[ameeuw]

So I have given it my best to compile the information into the following script, sadly the display only blinks three times at restart and then does nothing.

One mistake I have done before is to count the number of arguments in decimal where I found it in other descriptors to be done in hex (10 for 16 args) - is that assumption correct?

Any help is appreciated.

Is there anything obvious I am doing wrong?
I have found the C3 register in the data sheet to control the vsync and hsync polarity but that didn't to anything either (C3,1,8c)

:H,ST7701,480,480,16,RGB,18,17,16,21,38,4,5,6,7,15,8,20,3,46,9,10,11,12,13,14,0,14
:IS,48,47,39,-1
FF,5,77,01,00,00,10
C0,2,3B,00
C1,2,0D,02
C2,2,31,05
CD,1,00
B0,10,00,11,18,0E,11,06,07,08,07,22,04,12,0F,AA,31,18
B1,10,00,11,19,0E,12,07,08,08,08,22,04,11,11,A9,32,18
FF,5,77,01,00,00,11
B0,1,60
B1,1,32
B2,1,07
B3,1,80
B5,1,49
B7,1,85
B8,1,21
C1,1,78
C2,1,78
E0,3,00,1B,02
E1,B,08,A0,00,00,07,A0,00,00,00,44,44
E2,C,11,11,44,44,ED,A0,00,00,EC,A0,00,00
E3,4,00,00,11,11
E4,2,44,44
E5,10,0A,E9,D8,A0,0C,EB,D8,A0,0E,ED,D8,A0,10,EF,D8,A0
E6,4,00,00,11,11
E7,2,44,44
E8,10,09,E8,D8,A0,0B,EA,D8,A0,0D,EC,D8,A0,0F,EE,D8,A0
EB,7,02,00,E4,E4,88,00,40
EC,2,3C,00
ED,10,AB,89,76,54,02,FF,FF,FF,FF,FF,FF,20,45,67,98,BA
FF,5,77,01,00,00,13
E5,1,E4
FF,5,77,01,00,00,00
3A,1,50
11,80
29,80
:S,2,1,1,0,40,20
:V,0,10,8,50,0,10,8,20,0
:o,28
:O,29
:i,20,21
:R,36
:0,0
:2,10
:TI1,5d,45,19,-1,-1
#

[ysoyipek]

I have the same product. It's a nice cheap product costing 20 USD. There are only plastic and mold design errors.

[sfromis]

I'm also seeing that "twitching" with the similar Sunton ESP32-8048S070, and suspect that it is not a hardware issue. Like when I do an unrelated activity (like saving a big file), I'm also seeing the display tearing.

[ysoyipek]

@sfromis yes, it definitely happens when processor density increases. I have an ESP32-4848S040 (same as the one @ameeuw uses). I am using openHASP and when I upload a file for firmwareupdate, the screen scrolls until the upload is finished.

I ordered Sunton ESP32-8048S070 yesterday. The only common point in both products seems to be ESP32-S3.

[sfromis]

The similarites are much more than just the MCU, with both boards using the RGB interface with a display on the large end (for a MCU). Which display controller chip is used is actually a relatively small difference, and the pixel dimensions (beyond small) even less. It is really rather similar devices.

[ysoyipek]

Hi @ameeuw, I have the same product. I needed to use tasmota+zigbee+lvgl in a new project. Can you send me the firmware you use for testing? Or a diff/patch file would be better for compilation.

[sfromis]

When everything works, time to add the device here:
https://templates.blakadder.com/
https://github.com/tasmota/autoconf/tree/main/raw/esp32s3
https://github.com/arendst/Tasmota/tree/development/tasmota/displaydesc

Some devices present in autoconf are not also represented in displaydesc.

[ameeuw]

Here it is - you need to remove the .zip ending, upload it via File Manager and restart.

ESP32S3-4848S040.autoconf.zip

[ameeuw]

Btw @gemu2015 since the SPI pins are not used anymore after the :IS init procedure, couldn't we free them afterwards in order to make them available to SPI 1||2 to then use the SD-Card?

[sfromis]

@ameeuw When it comes to this specific autoconf setup, I notice that the autoexec.be contains code to setup a user interface. While I can, sort of, see a point in doing that, I'd also say that the goal of autoconf should be to configure Tasmota for the hardware, after which the next step would be to do something with it.

Mixing some user interface into the hardware setup is beside the point of "simply" doing the autoconfiguration to have the device ready for coding/installing some application. The included LVGL setup in autoexec.be may be nice as a sample application, but not as a part of doing device configuration for general purposes.

Such considerations are a reason why the autoconf files for very similar devices only have display.ini along with init.bat to set a template. The auto-configuration process is happening once only, not every boot, as the results of running it is to have the relevant persistent Tasmota settings done. Including a sample application here does not make much sense. Of course, not much harm either, as it is only first boot.

[ameeuw]

@ameeuw When it comes to this specific autoconf setup, I notice that the autoexec.be contains code to setup a user interface. While I can, sort of, see a point in doing that, I'd also say that the goal of autoconf should be to configure Tasmota for the hardware, after which the next step would be to do something with it.

Mixing some user interface into the hardware setup is beside the point of "simply" doing the autoconfiguration to have the device ready for coding/installing some application. The included LVGL setup in autoexec.be may be nice as a sample application, but not as a part of doing device configuration for general purposes.

Such considerations are a reason why the autoconf files for very similar devices only have display.ini along with init.bat to set a template. The auto-configuration process is happening once only, not every boot, as the results of running it is to have the relevant persistent Tasmota settings done. Including a sample application here does not make much sense. Of course, not much harm either, as it is only first boot.

Thank you for the clarification - I had actually asked myself that.

The autoconf at hand stems from my personal stash of autoconfs which are supposed to be preparing my devices at hand to be usable.

[sfromis]

What happens with auto-configuration is that once only it will run init.bat (meant for templates and other persistent settings) along with copying display.ini to the file system. This is in a flow managed to include the relevant reboot, and steps are dependent on the files being included. I was mistaken about the role of autoexec.be and autoexec.bat in the auto-configuration file, these are actually executed every boot, as expected for those file names.

This could be a good case for things like having a device driver coded in Berry, without which the hardware would not be operational, as in supported features being available in Tasmota. Such a device driver would need to be loaded every boot.

OTOH, coding some "smart management" of a lamp would not be at the device driver level, but more an application where having it in a .tapp file would make more sense, these are also automatically loaded and executed every boot, but can be removed or replaced without interfering with the more basic device setup done in autoconf.

[helmutnumber1]

I'm glad with files, thankyou all

[helmutnumber1]

After I reloaded the Tasmota S3 again without erasing and entered the template, I have a working display.
I have the flickering too.
First of all, thank you very much and my offer of coffee is still there.
I hope there are a lot of innovations too ;-)

[sfromis]

The intention with autoconf is not that you unpack it, but simply place it in the file system. In this case, you should first rename it from ESP32S3-4848S040.autoconf.zip to ESP32S3-4848S040.autoconf, as an autoconfig setup is simply a zip archive which was not compressed but stored directly. When uploading manually, instead of the standard web UI dialog, you may need to indicate that the new autoconf should be used by deleting the "hidden" file .autoconf (full file name).

[helmutnumber1]

Oh, I unpacked them and then uploaded them individually.
I notice with that.
Thankyou
Edit: I'm not a programmer at all, I can only paste and copy and then read up.
In my experience, the flickering could come from, as sfromis writes, the setup for the display being called up again.

But you know better.

[danielkucera]

Hi guys, a bit off-topic but what kind of box are you using? I cannot find one that would fit...

[helmutnumber1]

Try Kaiser 7651 Unterputz Q-range® Tiefe 65mm für Rohre M16-M20 ohne Schrauben Mittenabstand 60/71mm
Or aliexpress

[danielkucera]

Did you try it? I have doubts...

[helmutnumber1]

I'm waiting for https://de.aliexpress.com/item/32958909969.html?

[danielkucera]

Thanks, I have found one for solid wall:
https://a.aliexpress.com/_EIdmMn7
But I don't know, I am worried about fire safety. I am probably not brave enough to use it in my house.

[helmutnumber1]

First, the device costs 30 euros free, what can you expect?
And if you look at the inner workings, you can do that in detail on this page after registering. There you can also see my ESP32 version with 4 pages, including switch texts and UDP options.
https://cicciocb.com/forum/viewtopic.php?t=1069&start=10
I've seen worse boards from Shelly, Tuya and Co in the early days.
You can also install a VDR and capacitor on the board. Or provide other security.
on Side 5 is my Zip-file, you can set any thing over UDP and receive anything per UDP
In UDP Client_Socket is this a cmd:
//USCK_SendText(39372, "UDP11=1");
//USCK_SendText(39372, "TXT01= 23,3 Grad");
UDP11=1 set UDP_page1_relais1 = 1 and so on
Relais1 in Page 4 = UDP41=1 or 0
TXT11= "23,6 Grad" set page 1 text 1 to 23,6 Grad
Text in Page 4 Text 1 is TXT41= "xyz"
PWM Display per UDP TXT00= "200" or so.

[flexiti]

SW1 is connected to pin 5 IP5306, It disconnects the power (actually acts as a reset) if you hold it for 10 seconds

[danielkucera]

Can someone please help me with the firmware? I cannot find one that would have all three: berry, lvgl, wifi connectivity:

• tasmota32s3-qio_opi-all doesn't have wifi
• tasmota32s3 - doesn't have lvgl
• https://github.com/tasmota/install/raw/firmware/firmware/unofficial/tasmota32s3-qio_opi.bin - no wifi
  What else to try?

[sfromis]

You last one, tasmota32s3cdc-opi_opi does very much have both Wifi, Berry and LVGL. But to boot with Wifi, you need to make sure to have a good power source, which typically is not from a PC USB port.

[danielkucera]

tasmota32s3cdc-opi_opi didn't work at all. And I was powering it from an external power supply

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x18 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40378984
SPIWP:0xee
mode:DOUT, clock div:1
load:0x3fce3808,len:0x88
load:0x403c9700,len:0x964
load:0x403cc700,len:0x2788
SHA-256 comparison failed:
Calculated: c6bcfe350957c491eb1c90ae814017054d7c4e9c7813c58c7771fa39277bcad2
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98a0

abort() was called at PC 0x40378561 on core 0


Backtrace: 0x40378d66:0x3fceb260 0x4037e869:0x3fceb280 0x403844f5:0x3fceb2a0 0x40378561:0x3fceb320 0x403cd68b:0x3fceb350 0x403cd8f6:0x3fceb380 0x403c98f5:0x3fceb4b0 0x40045c01:0x3fceb570 0x40043ab6:0x3fceb6f0 0x40034c45:0x3fceb710

[sfromis]

What you post there is not at all about "no Wifi", but a boot failure. I specifically meant the last one you posted, opi_opi was a typo. Those QIO and/or OPI refers to expanded busses for flash/PSRAM access, and you need a variant to match your ESP32-S3 variant, and OPI/OPI is "less common", while QIO/OPI is more widespread. Some chips are without either, where Tasmota also has builds like tasmota32s3-lvgl.

In general, if it boots into Tasmota, and the first couple of messages after boot refers to PSRAM (if your ESP32 variant includes PSRAM), that part of the setup should be workable.

[danielkucera]

Thanks for hint. I have found out it is not in the firmware. When I erase flash, wifi works. Once I upload display.ini I start to get panics:

11:08:14.772 UFS: File '/' download
11:08:16.407 UPP: Multicast (re)joined
11:08:18.454 UFS: File '/' download
11:08:24.986 UPL: File display.ini (858 bytes)
11:08:25.105 UPP: Multicast (re)joined
11:08:25.112 UPL: Successful 858 bytes
11:08:32.154 UFS: File '/' download
11:08:41.369 APP: Restarting
x��ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x18 (SPI_FAST_FLASH_BOOT)
Saved PC:0x421474da
    0x421474da: esp_pm_impl_waiti at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_pm/pm_impl.c:850
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x128
load:0x403c9700,len:0xb90
load:0x403cc700,len:0x28c4
SHA-256 comparison failed:
Calculated: 2b075f82e0786adb0c1d62bbb8fd8473bc4c3a43b0e0018c7b88c06336b2c8a6
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98b8

00:00:00.001 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.035 UFS: FlashFS mounted with 12588 kB free
00:00:00.049 CFG: Loaded from File, Count 16
00:00:00.055 QPC: Count 1
00:00:00.104 BRY: Berry initialized, RAM used 6016 bytes
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x4037eebb  PS      : 0x00060233  A0      : 0x8037fdc5  A1      : 0x3fcaf8f0
    0x4037eebb: uxListRemove at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/list.c:192
A2      : 0x0000001d  A3      : 0x3fca38d8  A4      : 0x00000004  A5      : 0x0000abab
A6      : 0x00060223  A7      : 0x00060223  A8      : 0xb33fffff  A9      : 0xffffffff
A10     : 0x3fca38cc  A11     : 0x3fca38cc  A12     : 0x3fca38d0  A13     : 0x0000abab
    0x3fca38cc: ?? at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port/xtensa/port.c:91
    0x3fca38cc: ?? at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port/xtensa/port.c:91
A14     : 0x00ffffff  A15     : 0x00060220  SAR     : 0x00000014  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000021  LBEG    : 0x40056f5c  LEND    : 0x40056f72  LCOUNT  : 0xffffffff


Backtrace: 0x4037eeb8:0x3fcaf8f0 0x4037fdc2:0x3fcaf910 0x421497c6:0x3fcaf930 0x420c95cd:0x3fcaf970 0x420c9671:0x3fcaf9c0 0x42078285:0x3fcafaa0 0x420782bf:0x3fcafad0 0x4208d1df:0x3fcafaf0 0x4208656c:0x3fcafb10 0x420873e3:0x3fcafbe0 0x42078dad:0x3fcafc20 0x42079fe5:0x3fcafc40 0x420a0a6c:0x3fcafc60 0x42079ffd:0x3fcafd20 0x420b8c2e:0x3fcafd40 0x420c7718:0x3fcafd60 0x420238ce:0x3fcafea0
    0x4037eeb8: uxListRemove at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/list.c:187
    0x4037fdc2: xTaskRemoveFromEventList at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:3769
    0x421497c6: xQueueGenericSend at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/queue.c:883
    0x420c95cd: i2c_master_cmd_begin at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/i2c.c:1529
    0x420c9671: i2c_master_read_from_device at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/i2c.c:981
    0x42078285: _ZN7TwoWire11requestFromEtjb$part$5 at ??:?
    0x420782bf: TwoWire::requestFrom(unsigned char, unsigned char) at ??:?
    0x4208d1df: GT911_Touch_Init(TwoWire*, signed char, signed char, unsigned short, unsigned short) at ??:?
    0x4208656c: Init_uDisplay(char const*) at ??:?
    0x420873e3: Xdsp17(unsigned int) at ??:?
    0x42078dad: _Z8XdspCallj$part$412 at ??:?
    0x42079fe5: XdspCall(unsigned int) at ??:?
    0x420a0a6c: Xdrv13(unsigned int) at ??:?
    0x42079ffd: XdrvCall(unsigned int) at ??:?
    0x420b8c2e: XdrvXsnsCall(unsigned int) at ??:?
    0x420c7718: setup() at ??:?
    0x420238ce: loopTask(void*) at :?




ELF file SHA256: 0000000000000000

Rebooting...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x18 (SPI_FAST_FLASH_BOOT)
Saved PC:0x421474da
    0x421474da: esp_pm_impl_waiti at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_pm/pm_impl.c:850
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x128
load:0x403c9700,len:0xb90
load:0x403cc700,len:0x28c4
SHA-256 comparison failed:
Calculated: 2b075f82e0786adb0c1d62bbb8fd8473bc4c3a43b0e0018c7b88c06336b2c8a6
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98b8

00:00:00.001 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.035 UFS: FlashFS mounted with 12588 kB free
00:00:00.049 CFG: Loaded from File, Count 16
00:00:00.051 FRC: Some settings have been reset (2)
00:00:00.099 BRY: Berry initialized, RAM used 6016 bytes
00:00:00.564 UTI: GT911 initialized
00:00:00.908 DSP: Configured display 'ST7701'
00:00:00.916 Project tasmota - Tasmota Version 13.4.0(lvgl-haspmota)-2_0_14(2024-03-16T09:42:00)
00:00:00.919 RSL: RESULT = {"POWER4":"ON"}
00:00:00.919 RSL: POWER4 = ON

After the crash, the device restarts without wifi.
Do you have any idea what can be wrong with the config?

[danielkucera]

Okay, I am starting to understand how does it work. Now I removed the touch configuration line :TI.

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x18 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x128
load:0x403c9700,len:0xb90
load:0x403cc700,len:0x28c4
SHA-256 comparison failed:
Calculated: 2b075f82e0786adb0c1d62bbb8fd8473bc4c3a43b0e0018c7b88c06336b2c8a6
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98b8

00:00:00.001 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.026 UFS: FlashFS mounted with 12592 kB free
00:00:00.027 TFS: File '.settings' not found
00:00:00.044 CFG: Use defaults
00:00:00.119 QPC: Reset
00:00:00.268 BRY: Berry initialized, RAM used 6645 bytes
00:00:00.277 Project tasmota - Tasmota Version 13.4.0(lvgl-haspmota)-2_0_14(2024-03-16T11:32:04)
00:00:00.561 WIF: WifiManager active for 3 minutes
00:00:01.085 HTP: Web server active on tasmota-186D68-3432 with IP address 192.168.4.1
00:02:21.447 WIF: Connecting to AP asylum as tasmota-186D68-3432 ...
00:02:22.402 WIF: SSId asylum: Connected - IP Address 192.168.1.241
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x18 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x128
load:0x403c9700,len:0xb90
load:0x403cc700,len:0x28c4
SHA-256 comparison failed:
Calculated: 2b075f82e0786adb0c1d62bbb8fd8473bc4c3a43b0e0018c7b88c06336b2c8a6
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98b8

00:00:00.000 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.002 UFS: FlashFS mounted with 12588 kB free
00:00:00.006 CFG: Loaded from File, Count 5
00:00:00.012 QPC: Count 1
00:00:00.031 BRY: Berry initialized, RAM used 5975 bytes
00:00:00.037 Project tasmota - Tasmota Version 13.4.0(lvgl-haspmota)-2_0_14(2024-03-16T11:32:04)
00:00:01.000 WIF: Connecting to AP1 asylum in mode 11n as tasmota-186D68-3432...
00:00:02.648 WIF: Connected
00:00:02.851 HTP: Web server active on tasmota-186D68-3432 with IP address 192.168.1.241
12:14:51.401 RSL: INFO1 = {"Info1":{"Module":"ESP32S3","Version":"13.4.0(lvgl-haspmota)","FallbackTopic":"cmnd/DVES_186D68_fb/","GroupTopic":"cmnd/tasmotas/"}}
12:14:51.412 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-186D68-3432","IPAddress":"192.168.1.241","IP6Global":"fd09:b1d1:43e2::deda:cff:fe18:6d68","IP6Local":"fe80::deda:cff:fe18:6d68%st1"}}
12:14:51.424 RSL: INFO3 = {"Info3":{"RestartReason":"Vbat power on reset","BootCount":2}}
12:14:52.973 QPC: Reset
12:14:55.934 RSL: STATE = {"Time":"2024-03-16T12:14:55","Uptime":"0T00:00:10","UptimeSec":10,"Heap":223,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":5,"Objects":56},"Wifi":{"AP":1,"SSId":"asylum","BSSId":"0C:80:63:BA:AF:C8","Channel":1,"Mode":"11n","RSSI":76,"Signal":-62,"LinkCount":1,"Downtime":"0T00:00:03"}}
12:15:30.205 UFS: File '/' download
12:15:37.197 UPL: File display.ini (839 bytes)
12:15:37.326 UPP: Multicast (re)joined
12:15:37.333 UPL: Successful 839 bytes
12:15:39.863 UFS: File '/' download
12:16:02.631 RSL: RESULT = {"Module":{"1":"ESP32S3"}}
12:16:02.638 RSL: RESULT = {"GPIO0":{"6210":"Option A3"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"0":"None"},"GPIO5":{"0":"None"},"GPIO6":{"0":"None"},"GPIO7":{"0":"None"},"GPIO8":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO11":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"},"GPIO18":{"0":"None"},"GPIO19":{"0":"None"},"GPIO20":{"0":"None"},"GPIO21":{"0":"None"},"GPIO38":{"0":"None"},"GPIO39":{"0":"None"},"GPIO40":{"0":"None"},"GPIO41":{"0":"None"},"GPIO42":{"0":"None"},"GPIO43":{"0":"None"},"GPIO44":{"0":"None"},"GPIO45":{"0":"None"},"GPIO46":{"0":"None"},"GPIO47":{"0":"None"},"GPIO48":{"0":"None"}}

above I have uploaded the display.ini, set Option A 3 on GPIO0 and the module restarted:

12:16:04.044 APP: Restarting
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x18 (SPI_FAST_FLASH_BOOT)
Saved PC:0x421474da
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x128
load:0x403c9700,len:0xb90
load:0x403cc700,len:0x28c4
SHA-256 comparison failed:
Calculated: 2b075f82e0786adb0c1d62bbb8fd8473bc4c3a43b0e0018c7b88c06336b2c8a6
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98b8

00:00:00.001 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.036 UFS: FlashFS mounted with 12588 kB free
00:00:00.050 CFG: Loaded from File, Count 10
00:00:00.056 QPC: Count 1
00:00:00.107 BRY: Berry initialized, RAM used 5975 bytes
00:00:00.776 DSP: Configured display 'ST7701'
00:00:00.783 Project tasmota - Tasmota Version 13.4.0(lvgl-haspmota)-2_0_14(2024-03-16T11:32:04)
00:00:00.785 RSL: RESULT = {"POWER":"ON"}
00:00:00.786 RSL: POWER = ON

after restart there is no error but the wifi doesn't start.
How do I enable both display and wifi? 🤕

[OscarMayReal]

hello, slightly off-topic question, but does anyone still have the original manufacture zip file mentioned in the first post? I cannot find it anywhere, and the link on all the aliexpress pages lead to a 404 not found page.

[sfromis]

Maybe it was one of the files here. At least the names looks "plausible".
http://pan.jczn1688.com/1/ESP32%20module
To be clear, I know noting about that site, and cannot vouch for content or security.

[OscarMayReal]

do you see files there? Im just getting a 404 not found page.

[sfromis]

Obviously, I saw something, otherwise I'd not talk about names looking "plausible". And still works for me. Maybe you have a browser breaking the URL to be https instead of http?

[OscarMayReal]

thank you! Arc browser was automaticly changing the URL to https.

[GuidoSat]

Has somebody a running tasmota binaery and configuration for these module.

I flashed the officiell version "tasmota32-lvgl.bin" and used the config from ameeuw https://github.com/arendst/Tasmota/files/14019279/ESP32S3-4848S040.autoconf.zip, but it does not work, sometimes the tool menu is not further available.

Thanks for help

[Jason2866]

@GuidoSat I think this is the correct one https://github.com/Jason2866/Tasmota-specials/blob/firmware/firmware/tasmota32/other/tasmota32s3-qio_opi.bin

The print on the S3 module case shows N16R8 which is in espressif notation 16MB QIO Flash and 8MB OPI PSRAM. The S3 builds with Flash PSRAM variants in the name have all LVGL support.

[barbudor]

I'm missing the time when there was only ESP8266
🤯

[sfromis]

When you get LVG: Could not start Universal Display, you have some more basic config issue around the display driver setup, meaning issues with display.ini and/or gpio pins. While using a binary not working for PSRAM with that board (like tasmota32-lvgl.bin) could also be an issue, this would only be later. In this case, it does not provide info simply stating that you did as "above". Typical issues are not doing quite what was meant to be done.

[GuidoSat]

now I have the same problem like danielkucera. The display s on (shows ST7701 string), but Wifi is deactivated, I can't activate via web installer (gests over USB/com).

[helmutnumber1]

I lined this touch wall switch/panel with Annex ESP32 Basic.
The states can be changed by touch and then send the change in state to IP-Symcon via UDP.
You can of course change the displayed data via UDP (I do it with IP-Symcon) or write text messages into the display using commands.
The first side, as I did it like this, can switch the built-in 3 relays.
The small black rectangle is a slider that controls the brightness.
have a look
https://cicciocb.com/forum/viewtopic.php?t=1119 or https://www.youtube.com/watch?v=Sd55bO7z7cI

[jontwycross]

Has anyone managed to figure out the pins being used for the relay? I went down the OpenHASP route which seems to work fine and have it integrated with Home Assistant, but I just need to map the pin for the relay now. Would be a big help if anyone knows.

[barbudor]

There doesn't seem to have a lot of free remaining IOs
So you may just try them

[Jason2866]

From the manual, whatever it means:

The 4-inch screen relay and I2S audio are shared IO ports, IO1, IO2, and IO40. If audio is needed, the 0 ohm resistors R25, R26, and R27 should 
be moved to R21, R22, and R23.

[jontwycross]

I'll give them a go though it looks like this thread has moved on since last week when I attempted install from advice here! Looks promising

[jontwycross]

40 ended up being correct. I assume in the 3 way relay, 1 and 2 are used. Going to see if I can repurpose those pins as an input for a temperature and humidity sensor if it's even possible.

[kasbert]

How do you use the SD-card (without display) ?
I suppose the involved pins are
IO42 TF(D3)
IO41 TF(D1)
IO48 SPICLK_N TF(SCK)
IO47 SPICLK_P TF(SDA)
How do you map those to config code:

    spi_bus_config_t bus_cfg = {
        .mosi_io_num = 41, //PIN_NUM_MOSI,
        .miso_io_num = 47, //PIN_NUM_MISO,
        .sclk_io_num = 48, //PIN_NUM_CLK,
        .quadwp_io_num = -1,
        .quadhd_io_num = -1,
        .max_transfer_sz = 4000,
    };
...
    sdspi_device_config_t slot_config = SDSPI_DEVICE_CONFIG_DEFAULT();
    slot_config.gpio_cs = GPIO_NUM_NC; //PIN_NUM_CS;
    slot_config.gpio_cd = 42; //PIN_NUM_CD;
    slot_config.host_id = host.slot;

I (321) example: Initializing SD card
I (321) example: Using SPI peripheral
I (331) example: Mounting filesystem
E (351) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
HINT: Please verify if there is an SD card inserted into the SD slot. Then, try rebooting the board.

[ysoyipek]

now I have the same problem like danielkucera. The display s on (shows ST7701 string), but Wifi is deactivated, I can't activate via web installer (gests over USB/com).

The situation is the same with me.

The device has ESP32-S3 16MB-Flash 8MB-PSRAM. When I downloaded and tried the relevant tasmota (you tried the lvgl and PSRAM contributions), everything works normally.

as module template
{"NAME":"ESP32S3-4848S040","GPIO":[6210,226,225,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,224,8896,8960,0,0,0,0,8800,8832],"FLAG":0,"BASE":1}
Relays are working.

But when display.ini and autoecex.be are installed and restarted, the screen always starts and ST7701 is written on the screen. But I think ESP32 crashes. Serial port, wifi-ui etc. Nothing responds.

It's the same when I compile it myself from the source code.

[danielkucera]

I tried with following change but it didn't help:

diff --git a/tasmota/include/tasmota_configurations_ESP32.h b/tasmota/include/tasmota_configurations_ESP32.h
index 15fc570c1..5e62c330b 100644
--- a/tasmota/include/tasmota_configurations_ESP32.h
+++ b/tasmota/include/tasmota_configurations_ESP32.h
@@ -322,7 +322,7 @@
 #define SHOW_SPLASH
 #define USE_XPT2046
 #define USE_FT5206
-#define USE_GT911
+//#define USE_GT911
 #define USE_CST816S
 #define USE_MPU_ACCEL
 #define USE_RTC_CHIPS                            // Enable RTC chip support and NTP server - Select only one

[Jason2866]

Can you try to disable all touch driver?

 #undef USE_XPT2046
 #undef USE_FT5206
 #undef USE_GT911
 #undef USE_CST816S

[danielkucera]

No change either:

diff --git a/tasmota/include/tasmota_configurations_ESP32.h b/tasmota/include/tasmota_configurations_ESP32.h
index 15fc570c1..f1bb12ad5 100644
--- a/tasmota/include/tasmota_configurations_ESP32.h
+++ b/tasmota/include/tasmota_configurations_ESP32.h
@@ -320,10 +320,10 @@
 #define USE_LVGL_PNG_DECODER
 #define USE_DISPLAY
 #define SHOW_SPLASH
-#define USE_XPT2046
-#define USE_FT5206
-#define USE_GT911
-#define USE_CST816S
+#undef USE_XPT2046
+#undef USE_FT5206
+#undef USE_GT911
+#undef USE_CST816S
 #define USE_MPU_ACCEL
 #define USE_RTC_CHIPS                            // Enable RTC chip support and NTP server - Select only one
   #define USE_BM8563

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x18 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x128
load:0x403c9700,len:0xb90
load:0x403cc700,len:0x28c4
SHA-256 comparison failed:
Calculated: 2b075f82e0786adb0c1d62bbb8fd8473bc4c3a43b0e0018c7b88c06336b2c8a6
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98b8

00:00:00.000 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.045 UFS: FlashFS mounted with 12588 kB free
00:00:00.061 CFG: Loaded from File, Count 10
00:00:00.067 QPC: Count 6
00:00:00.125 BRY: Berry initialized, RAM used 5975 bytes
00:00:00.811 DSP: Configured display 'ST7701'
00:00:00.819 Project tasmota - Tasmota Version 13.4.0(lvgl-haspmota)-2_0_14(2024-03-23T12:48:32)
00:00:00.821 RSL: RESULT = {"POWER4":"ON"}
00:00:00.822 RSL: POWER4 = ON

[Jason2866]

Thx, so it is something different. When gemu2015 and i have received the device we will look into.

[danielkucera]

I've added some debug logging. This is without display configured:

00:00:00.001 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.042 UFS: FlashFS mounted with 12588 kB free
00:00:00.056 CFG: Loaded from File, Count 7
00:00:00.063 QPC: Count 1
00:00:00.115 BRY: Berry initialized, RAM used 5975 bytes
00:00:00.124 Project tasmota - Tasmota Version 13.4.0(lvgl-haspmota)-2_0_14(2024-03-23T13:08:28)
00:00:00.125 danman-setup end
00:00:00.125 danman-loop begin
00:00:00.175 danman-loop begin
00:00:00.225 danman-loop begin
00:00:01.000 WIF: Connecting to AP1 asylum in mode 11n as tasmota-186D68-3432...
00:00:01.553 danman-loop begin
00:00:01.603 danman-loop begin
00:00:01.653 danman-loop begin

This is after I configure the display:

00:00:00.000 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.019 UFS: FlashFS mounted with 12588 kB free
00:00:00.026 CFG: Loaded from File, Count 11
00:00:00.033 QPC: Count 1
00:00:00.066 BRY: Berry initialized, RAM used 5975 bytes
00:00:00.730 DSP: Configured display 'ST7701'
00:00:00.736 Project tasmota - Tasmota Version 13.4.0(lvgl-haspmota)-2_0_14(2024-03-23T13:08:28)
00:00:00.739 RSL: RESULT = {"POWER4":"ON"}
00:00:00.739 RSL: POWER4 = ON

The device apparently doesn't finish the setup() function so loop() is not called either.

[AK1Chel]

In openhasp firmware this device works fine. Maybe we should look there?
https://nightly.openhasp.com/

[Jason2866]

Thx for heads up. Does not help. Tasmota does work different and we have to verify first the assumption of the gt911 driver. If the solution is to replace with the already implemented Universal Touch driver.
As already mentioned ALL dedicated touch drivers we do have on our road list to remove completely.

[sfromis]

When it comes to GT911, I've not experienced touch issues running Tasmota+HASPmota on Sunton ESP32-8048S070C using this touch controller chip.

[gemu2015]

@Jason2866
the only U-touch driver i haven't yet tested is CST816S because i do not have a device.
it should be easy however. in another thread we currently test CST820 which should be very similar
btw. i also ordered the above display and will implement every options including SD card.

[gemu2015]

@Jason2866
since we are about to switch to universal touch. what is your opinion.
shall we replace all affected display.ini files with their utouch variants ?
i have prepared those for my own displays and may pr them instantly.
or shall we hold ut versions in parallel. (e.g. core2_ut_display.ini)

[Jason2866]

100% Universal Driver Route. Maybe we can do some automated migration for display.ini?
No more specific drivers. Great work you have done with Universal driver concept!

[Jason2866]

@danielkucera

And here is a video of a minor hiccup, the display twitches sometimes: e8bc06c9-1fb7-4406-8b77-633bdd745cb6.webm

Could the twitching have to do with the hsync & vsync polarity?

This is a known performance problem in underlying IDF https://espressif-docs.readthedocs-hosted.com/projects/esp-faq/en/latest/software-framework/peripherals/lcd.html

Maybe overclocking the S3 Flash and/or PSRAM to 120Mhz could solve this issue. I am in very early stage of testing this experimental feature of 120Mhz FLASH / PSRAM builds. To early to say if this speed gain will help.
The 120Mhz is an IDF 5.x feature, so only LVGL builds based on Tasmota Arduino 3.0.0 are possible to get this feature

@gemu2015 Do you see an possible advantage by enabling bounce buffer https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-reference/peripherals/lcd.html#bounce-buffer-with-single-psram-frame-buffer?

[mvdw]

OK, I use this: https://github.com/Jason2866/Tasmota-specials/blob/firmware/firmware/tasmota32/other/tasmota32s3-qio_opi.bin

[gemu2015]

ok we should evaluate the difference
do not include #define USE_GT911 in the build
and please post your display.ini

[gemu2015]

ok, i guess i know what the reason is. the old gt911 driver is activated too if you compile with the old driver.
in my display.ini i commented the ti line : ";:TI1,5d,45,19,-1,-1" but a comment is not recognized here and the driver is enabled. so delete this line from display.ini and it should work.
i am also interested if you did try to change display clock to 6 Mhz and if that affected your use case.
(:H,ST7701,480,480,16,RGB,18,17,16,21,38,4,5,6,7,15,8,20,3,46,9,10,11,12,13,14,0,6)
i have no issues at all and flickering is completely gone.

[danielkucera]

That works perfectly as you describe. 👌

[mvdw]

Yes, indeed, removing the comment from the display.ini fixes the buggy touch problem!
Thank you so much!

[Jason2866]

ok, SD card working. needs display driver update

Thx for the PR to fix. Just merged. New build with the changes will be soon available from https://tasmota.github.io/install under unofficial select Tasmota32-S3 (QIO Flash / OPI PSRAM)

[gemu2015]

according to flicker. on RGB displays we have heavy DMA from PSRAM to display due to the lack of display RAM inside display. this DMA may not be disturbed in any way, the linked lists are started in IRQ. so disabling IRQ leads to flicker. especially writing to flash in Tasmota causes this. setting SAVEDATA to 0 completely prevents this flickering. SD card traffic however does not cause flickering at all.

[gemu2015]

@s-hadinger
SPI DMA does not apply on RGB displays, so SD card usage is no problem.
enabling SPI DMA in RGB displays is simply ignored.
However in core 3 we may be able to enable SPI DMA with SPI displays together with SD card.
according to the docs core3 will fully support task and DMA save SPI

[gemu2015]

as i actually do not need a relays, i rejumpered for i2s and can confirm it works well.
i mounted a subminiature speaker inside which is not optimal, but sufficient.

if one could find an extremely small i2c gpio expander one would be able to support the relays too

[gemu2015]

interesting finding. reducing the RGB DMA bandwidth by reducing the display clock to 6 Mhz makes the flickering disappear.
this will only have a side effect when displaying animated pictures or so.

[gemu2015]

This reduces the framerate to about 12 Hz
However the lcd is slow enough not to flicker with 12 hz
This does not Affekt LVGL framerate, in the contrary this will increase because the cpu has also more bandwidth.
Since we are not playing games 12 hz is fast enough

[Jason2866]

There will be performance increase in the upcoming Tasmota Arduino Core 3.0.0.
With optimized sdkconfig settings for the S3 and using 120Mhz Flash frequency, i was able to set display clock to 16Mhz WITHOUT screen flicker. Mandantory is to set savedata 0

[gemu2015]

@Jason2866
that is good news for RGB displays. however we should check what the lowest pixel clock is that works.
on this display 6 Mhz is perfekt. savedata 1 does not flicker at all. also flash file system access does not flicker.
i checked my sunton display but this has a lowest clock of 12 Mhz, hopefully this can be decreased with the new core
the lower the pixel clock the lower the memory bandwidth the better the cpu performance for other tasks
and LVGL too.

[gemu2015]

@Jason2866
i have to correct the display transfer frame rate is not 12 Hz as stated above but 26 Hz with 6 Mhz pixel clock. (verified with oscilloscope, so simply divide pixel clock through display pixels => 6000000 / (480*480) with 16 Mhz you would get about 70 Hz which is definitely too much.

[Jason2866]

@gemu2015 Great, so we have a lot of MCU resources left.

[danielkucera]

Is there any way how to regulate the display backlight?
I configured GPIO38 as PWM and changed display config to set backlight pin to -1 like so:

:H,ST7701,480,480,16,RGB,18,17,16,21,-1,4,5,6,7,15,8,20,3,46,9,10,11,12,13,14,0,14

and that works.
I just wonder if there is some "display way" ?

[sfromis]

The usual way is to have the backlight pin configured as Backlight and then use the DisplayDimmer command. Did you try that?

[danielkucera]

Oh, I completely missed that, thank you. It works.

[danielkucera]

I am also thinking about microSD attached temperature sensor - see the concept on photo. But this would need SPI driver for BME280. Do you think it's worth the effort? Would someone be interested if I produced several of them? I would make it on a dedicated PCB of course.

[s-hadinger]

@Jason2866 Can you please confirm?

[Jason2866]

@s-hadinger Will check tomorrow

[Jason2866]

The config mentioned from @Solar320 does not work with my Guition ESP32-4848S040 and a SD-Card
The provided config via Autoconfig does work with the SD-Card

[Solar320]

The config mentioned from @Solar320 does not work with my Guition ESP32-4848S040 and a SD-Card The provided config via Autoconfig does work with the SD-Card

It does! look at this.

I have added the SDCard_CS pin and now it work fine.

[Jason2866]

No it does not work, look at the shown size of the SD Card. Please stop littering this thread with wrong settings.

[bughattiveyron]

Help with setup please

Does anyone have the proper pinout for this, these are my settings.

When I installed, I used this bin (Tasmota32-S3 (QIO Flash / OPI PSRAM)

I also downloaded this zip from above ESP32S3-4848S040.autoconf.zip and put all 3 files in it.

Here are my log files from console

00:00:00.001 CMD: Using USB CDC
00:00:00.001 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.027 UFS: FlashFS mounted with 12580 kB free
00:00:00.036 CFG: Loaded from File, Count 21
00:00:00.043 QPC: Count 1
00:00:00.046 SPI: Hardware using GPIO48(CLK), GPIO47(MOSI) and GPIO41(MISO)
00:00:00.047 I2C: Bus1 using GPIO45(SCL) and GPIO19(SDA)
00:00:00.679 BRY: Berry initialized, RAM used 5321 bytes
00:00:00.688 Project tasmota - tscreen001 Version 13.4.0.3(781491e-lvgl-haspmota)-2_0_14(2024-04-01T10:33:13)
00:00:00.790 LVG: Could not start Universal Display
00:00:00.791 BRY: failed to run compiled code (value_error - native constructor cannot return NULL)
00:00:02.001 WIF: Connecting to AP1 Liquid2g Channel 11 BSSId 04:18:D6:C1:B7:8F in mode HT20 as tasmota-177238-4664...
00:00:03.502 WIF: Connected
00:00:03.706 HTP: Web server active on tasmota-177238-4664 with IP address 10.66.66.166
02:51:47.555 MQT: Attempting connection...
02:51:47.570 MQT: Connected
02:51:47.572 MQT: tele/tasmota_177238/LWT = Online (retained)
02:51:47.573 MQT: cmnd/tasmota_177238/POWER = 
02:51:47.576 MQT: tele/tasmota_177238/INFO1 = {"Info1":{"Module":"ESP32S3","Version":"13.4.0.3(781491e-lvgl-haspmota)","FallbackTopic":"cmnd/tscreen001_fb/","GroupTopic":"cmnd/tasmotas/"}}
02:51:47.578 MQT: tele/tasmota_177238/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-177238-4664","IPAddress":"10.66.66.166","IP6Global":"","IP6Local":"fe80::deda:cff:fe17:7238%st1"}}
02:51:47.580 MQT: tele/tasmota_177238/INFO3 = {"Info3":{"RestartReason":"Vbat power on reset","BootCount":7}}
02:51:47.581 MQT: stat/tasmota_177238/RESULT = {"POWER":"OFF"}
02:51:47.582 MQT: stat/tasmota_177238/POWER = OFF
02:51:48.893 MQT: stat/tasmota_177238/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":" ","RestartReason":"Vbat power on reset","Uptime":"0T00:00:06","StartupUTC":"2024-04-02T01:51:42","Sleep":50,"CfgHolder":4617,"BootCount":6,"BCResetTime":"2024-04-01T15:46:53","SaveCount":21}}
02:51:48.946 MQT: stat/tasmota_177238/STATUS11 = {"StatusSTS":{"Time":"2024-04-02T02:51:48","Uptime":"0T00:00:06","UptimeSec":6,"Heap":208,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":10,"Objects":141},"POWER":"OFF","Wifi":{"AP":1,"SSId":"Liquid2g","BSSId":"04:18:D6:C1:B7:8F","Channel":11,"Mode":"HT20","RSSI":100,"Signal":-46,"LinkCount":1,"Downtime":"0T00:00:04"}}}
02:51:48.995 MQT: stat/tasmota_177238/RESULT = {"Time":"2024-04-02T02:51:48","Uptime":"0T00:00:06","UptimeSec":6,"Heap":208,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":20,"MqttCount":1,"Berry":{"HeapUsed":10,"Objects":141},"POWER":"OFF","Wifi":{"AP":1,"SSId":"Liquid2g","BSSId":"04:18:D6:C1:B7:8F","Channel":11,"Mode":"HT20","RSSI":100,"Signal":-46,"LinkCount":1,"Downtime":"0T00:00:04"}}
02:51:49.897 QPC: Reset
02:51:51.895 MQT: tele/tasmota_177238/STATE = {"Time":"2024-04-02T02:51:51","Uptime":"0T00:00:09","UptimeSec":9,"Heap":208,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":10,"Objects":141},"POWER":"OFF","Wifi":{"AP":1,"SSId":"Liquid2g","BSSId":"04:18:D6:C1:B7:8F","Channel":11,"Mode":"HT20","RSSI":100,"Signal":-43,"LinkCount":1,"Downtime":"0T00:00:04"}}
02:51:58.130 MQT: stat/tasmota_177238/RESULT = {"POWER":"ON"}
02:51:58.132 MQT: stat/tasmota_177238/POWER = ON
02:56:51.916 MQT: tele/tasmota_177238/STATE = {"Time":"2024-04-02T02:56:51","Uptime":"0T00:05:09","UptimeSec":309,"Heap":206,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":10,"Objects":141},"POWER":"ON","Wifi":{"AP":1,"SSId":"Liquid2g","BSSId":"04:18:D6:C1:B7:8F","Channel":11,"Mode":"HT20","RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:04"}}

[mvdw]

• The correct firmware: https://github.com/Jason2866/Tasmota-specials/blob/firmware/firmware/tasmota32/other/tasmota32s3-qio_opi.bin

• The configuration:
  {"NAME":"ESP32S3-4848S040","GPIO":[1,226,225,0,6210,0,0,0,0,0,0,0,0,0,0,0,0,0,0,640,0,0,0,0,0,0,0,992,0,224,672,6720,0,0,608,0,704,736],"FLAG":0,"BASE":1}

GPIO	Device
Name	ESP32S3-4848S040
Based on	ESP32S3 (1)
--	--
GPIO0	User
GPIO1	None or Relay 3
GPIO2	None or Relay 2
GPIO3	None
GPIO4	Option A 3
GPIO5	None
GPIO6	None
GPIO7	None
GPIO8	None
GPIO9	None
GPIO10	None
GPIO11	None
GPIO12	None
GPIO13	None
GPIO14	None
GPIO15	None
GPIO16	None
GPIO17	None
GPIO18	None
GPIO19	I2C SDA 1
GPIO20	None
GPIO21	None
GPIO33	None
GPIO34	None
GPIO35	None
GPIO36	None
GPIO37	None
GPIO38	Backlight
GPIO39	None
GPIO40	Relay 1
GPIO41	SPI MISO 1
GPIO42	SDCard CS
GPIO43	None
GPIO44	None
GPIO45	I2C SCL 1
GPIO46	None
GPIO47	SPI MOSI 1
GPIO48	SPI CLK 1

• The correct "autoexec.be" file contains:

import haspmota  
haspmota.start()

• The correct "display.ini" contains:

:H,ST7701,480,480,16,RGB,18,17,16,21,38,4,5,6,7,15,8,20,3,46,9,10,11,12,13,14,0,6
:V,1,10,8,50,1,10,8,20,0
:S,2,1,1,0,40,20
:IS,48,47,39,-1
FF,5,77,01,00,00,10
C0,2,3B,00
C1,2,0D,02
C2,2,31,05
CD,1,00
B0,10,00,11,18,0E,11,06,07,08,07,22,04,12,0F,AA,31,18
B1,10,00,11,19,0E,12,07,08,08,08,22,04,11,11,A9,32,18
FF,5,77,01,00,00,11
B0,1,60
B1,1,32
B2,1,07
B3,1,80
B5,1,49
B7,1,85
B8,1,21
C1,1,78
C2,1,78
E0,3,00,1B,02
E1,B,08,A0,00,00,07,A0,00,00,00,44,44
E2,C,11,11,44,44,ED,A0,00,00,EC,A0,00,00
E3,4,00,00,11,11
E4,2,44,44
E5,10,0A,E9,D8,A0,0C,EB,D8,A0,0E,ED,D8,A0,10,EF,D8,A0
E6,4,00,00,11,11
E7,2,44,44
E8,10,09,E8,D8,A0,0B,EA,D8,A0,0D,EC,D8,A0,0F,EE,D8,A0
EB,7,02,00,E4,E4,88,00,40
EC,2,3C,00
ED,10,AB,89,76,54,02,FF,FF,FF,FF,FF,FF,20,45,67,98,BA
FF,5,77,01,00,00,13
E5,1,E4
FF,5,77,01,00,00,00
21,0
3A,1,60
11,80
29,80
20,0
:B,40,02
:UTI,GT911,I1,5d,-1,-1
RDWM 8140 4
MV 0 1
CPR 39
RTF
MV 1 1
CPR 31
RTF
MV 2 1
CPR 31
RTF
RT
:UTT
RDW 814E
MV 0 1
AND 80
CPR 80
RTF
RDWM 8150 8
WRW 814E 00
RT
:UTX
MV 0 3
RT
:UTY
MV 2 3
RT
#

• There should be a "pages.jsonl" file too.

[mvdw]

I am writing up my experiences with this module - all this is not final yet, but anyhow: https://michiel.vanderwulp.be/domotica/Modules/SmartDisplay-ESP32-S3-4.0inch/ and about the software: https://michiel.vanderwulp.be/domotica/Modules/SmartDisplay-ESP32-S3-4.0inch/software.html .
I also tried to add a temperature sensor - see https://michiel.vanderwulp.be/domotica/Modules/SmartDisplay-ESP32-S3-4.0inch/Adding-a-SHT40/index.html .

All input is welcome...

[Noschvie]

I am writing up my experiences with this module

@mvdw well done blog post. Have you tried the Tasmota Online Installer?

[mvdw]

Thanks.
The online installer does not work on Firefox, thus, no.

[sfromis]

Using that tool, with a fully functional browser, is the recommended strategy for easy flashing of Tasmota.

[mvdw]

Recommending Chrome and implying that Firefox is not fully functional, hurts my feelings. No thanks.

[sfromis]

Grow up. I did not recommend Chrome, and Firefox clearly is lacking in function.

[s-hadinger]

Awesome, I added S3-4848S040 autoconf file

[Solar320]

My Autoconfig File: from somewhere I don't know anymore....
ESP32S3-4848S040.autoconf.zip
This file, I only Upload to the Flash File System over the Website of my Tasmota.
I use an self compiled Image with Tasmota 14.0.0.4
I do not remove the .zip ending like some other do it. I only copy this file and restart my Display.
In the Sourcecode I add #define USE_GT911 #define USE_I2C to make the touch screen usable. "#define USE_LVGL" i do not use, only the following:

/ -- LVGL Graphics Library ---------------------------------
// #define USE_LVGL // LVGL Engine, requires Berry (+382KB)
#define USE_LVGL_PSRAM // Allocate LVGL memory in PSRAM if PSRAM is connected - this might be slightly slower but leaves main memory intact
#define USE_LVGL_HASPMOTA etc etc. May be I forget something in the meantime, it is a while ago I changed the setings.

I think this should also be enabled, if not allready....
// -- Universal Display Driver ---------------------------------
#define USE_UNIVERSAL_DISPLAY // New universal display driver for both I2C and SPI
#define MAX_TOUCH_BUTTONS 16 // Virtual touch buttons
My Display is an ST7701 RGB which will reconized with this autoconfig.zip The SD-Card will not run out of the Box with my config, I additionally change the settings in the device config.

and all Pins:

I hope this will help. I am not an Pro in this area.

[Jason2866]

@Solar320 The touch screen does work perfect with the correct display config file. There is no need for using the deprecated GT911 dedicated driver. To be clear the device works 100% with the provided Autoconfig. If your device does not, it is an different device or variant. I am a Pro in this area ;-)

[Solar320]

@Solar320 The touch screen does work perfect with the correct display config file. There is no need for using the deprecated GT911 dedicated driver. To be clear the device works 100% with the provided Autoconfig. If your device does not, it is an different device or variant. I am a Pro in this area ;-)

Not in my case. When I do not use GT911 i see only the screen without touchscreen working.
I think that my autoconfig file is to old, may be there have been some changes in the between....into the display.ini inside this config file.

My device is the following.

[Jason2866]

Simply use the Autoconfig function from Tasmota. Select your device in the menu and hit enter. No need to provide any file manually. For correctly working the I2C driver GT911 needs to be removed from the firmware build!

[sfromis]

And if you even need to build yourself, make sure to have both of:

#define USE_UNIVERSAL_DISPLAY
#define USE_UNIVERSAL_TOUCH

[Solar320]

Simply use the Autoconfig function from Tasmota. Select your device in the menu and hit enter. No need to provide any file manually. For correctly working the I2C driver GT911 needs to be removed from the firmware build!

I disabled the driver now into the sourcecode and the touchscreen do not work anymore. Also in the meantime I tryed another autoconfig file from https://michiel.vanderwulp.be/domotica/Modules/SmartDisplay-ESP32-S3-4.0inch/hardware.html
It seems to be the same as I have, it do not work. Also the SD-Card do not work without the extra configuration.

Now were I disabled the driver i will try to use the mentioned Autoconfig.

Voila it is working Touchscreen is also working and without Display flickering GREAT!

BUT! The SD Card do not work with this setup and the Setup do not let my configure the SD card.

So in the display.ini is something wrong, I think it configure anywere this Pins I need for the SD card.......so they are not available over the GUI?? I need 41 42 47 and GPIO48

Now I can choose between an not flickering screen withoutSD-Card and Flickering screen with SD-Card.....hmmmmm.

It looks like I have to go futher inside the details of the Display .ini....

[Solar320]

Yesterday I get an solution for me, I combined the new Display.ini which comes with the autoconfig file from Tasmota, with my old INIT.bat and with my old autoexec.be sample.

To be sure I will check this again, which files are now from Tasmota and which are old.

The current used Display.ini is from the "Tasmota Autoconfig" because it has the line ":UTI,GT911,I1,5d,-1,-1" inside.
My old Display.ini do not contain this line.

The old init.bat contains the line: Template {"NAME":"ESP32S3-4848S040","GPIO":[0,226,225,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,640,0,0,6210,0,0,0,0,0,1,224,672,6720,1,1,608,0,704,736],"FLAG":0,"BASE":1}
Module 0

So it is confirmed that this is the old variant that I have inside the device.

The new, version of init.bat from https://github.com/arendst/Tasmota/files/14019279/ESP32S3-4848S040.autoconf.zip
contains the line:
Template {"NAME":"ESP32S3-4848S040","GPIO":[6210,226,225,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,224,8896,8960,0,0,0,0,8800,8832],"FLAG":0,"BASE":1}
Module 0

Before I had to change the settings in Tasmota device settings to get the SD-Card working. But now something strange is happening.
Today I only compile and flash tasmota 14.0.0.4 on an new, clean ESP32S3-4848S040 device. Then I only play my modified SD-ESP32S3-4848S040.autoconf.zip on this device without changing the Device settings (IO settings) and now the SD card is working out of the box. I can't explain why at the moment.

So, this happens when you write in enlish and german at different threads ;)

OK ich hab es, in der init.bat die in der Autoconfig von Tasmota drinnen ist muss irgend ein Murks drin sein.

Ich habe jetzt meine alte init.bat und autoconfig.be genommen aber dazu die neue display.ini wegen dem Bildflackern!
Das ganze habe ich in eine zip datei gepackt. Einfach ins dateisystem hochladen und neu starten. Nichts umbenennen es sei denn es ist von der Tasmota version abhängig. Ich hab 14.0.0.4

SD-ESP32S3-4848S040.autoconf.zip

---

EDIT: Das ist scheinbar nicht mehr nötig!! Die Einstellungen stehen auf ESP32S3 4848S040 (0) trotzdem funktioniert die
SD-Card jetzt auf dem neuen Bildschirm.
Danach manuell die IO einstellungen machen. Bei Einstellungen/Geräteeinstellungen statt ESP32S3-4848S040 den ESP32S3 (1) auswählen.

Vieleicht kann mal jemand aus den IO einstellungen eine neue init.bat machen. Eigentlich hätte ich die alte init.bat nicht verwenden müssen aber irgendwas hat die neue angerichtet was sich sonst nicht anders rückgängig hat machen lassen.

Ich hab meine Datei selbst getestet, nachdem ich alle alten dateien zuvor gelöscht habe. Bei mir geht jetzt alles, flackerfreier Bildschirm und eine funktionierende SD card die sich im menue hin und herschalten lässt.

00:00:00.000 CMD: Using USB CDC
00:00:00.000 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.014 UFS: FlashFS mounted with 11556 kB free
00:00:00.023 CFG: Loaded from File, Anzahl 279
00:00:00.024 SER: Set to 8N1 115200 bit/s
00:00:00.024 SER: HWCDC supports 115200 bit/s only
00:00:00.024 FRC: Some settings have been reset (2)
00:00:00.026 I2C: Bus1 using GPIO45(SCL) and GPIO19(SDA)
00:00:00.075 UFS: SDCard mounted (SDIO 1-bit) with 0 kB free
00:00:00.094 BRY: Berry initialized, RAM used 5382 bytes
00:00:00.464 UFS: SDCard mounted (SDIO 1-bit) with 0 kB free
00:00:00.787 UT : GT911
00:00:00.788 DSP: Configured display 'ST7701'
00:00:00.791 Projekt tasmota - Tasmota Version 14.0.0.4(lvgl-haspmota)-3_0_0(2024.05.31 20:32:20)
00:00:00.795 LVG: LVGL initialized

Schlußendlich kann ich nicht erklären wo die genaue Ursache liegt das die "Tasmota Autoconfig" version für das DIsplay nicht mit der SD Card funktioniert. Ich kann nur bestätigen das die derzeitige SD-ESP32S3-4848S040.autoconf.zip von mir auf einem brandneuen Display aufgespielt funktioniert, ohne das zusätzliche Einstellungen gemacht werden müssen.
Allerdings verwende ich keine fertigen Firmware images und bei der masse an Änderungen die ich bereits gemacht habe
könnte es sein das fertige Images aufgrund fehlender Einstellungen im Sourcecode nicht funktionieren.

For now I can't explain why the "Tasmota Autoconfig do not work in combination with the SD-Card.
I can confirm that my actual SD-ESP32S3-4848S040.autoconf.zip is working for me without to change any settings on a brandnew device.
But I do not use "ready to use" firmwarefiles and so it is possible that I changed anything in the settings of the Tasmota sourcecode which cause that it is working for me, but it is possible that "ready to use" Firmwares do not work.

When I have time I will try to use all files from Tasmota, original precompiled Firmware.bin and the autoconfig.zip.

[Solar320]

OK, 1th forget all I wrote. To make it simple:

1.Use the webinstaller https://tasmota.github.io/install/ (do not use the standard ESP32-S3 .bin's, they do not use PSRAM)
2.Choose ESP32-S3 QIO Flash / OPI PSRAM and choose erase flash! (erase to be sure to get rid of old data into the flash)
3. setup your wifi
4.Choose the Autoconfig and S3-4848S040
5. save restart
6. upload some autoexec.be to see something

after that you have installed "Tasmota 14.0.0.4 (8c4388b-lvgl-haspmota) by Theo Arends"

The Display is working without flicker
The SD_Card is working

00:00:00.251 CMD: Fall back to serial port, no SOF packet detected on USB port
00:00:00.251 HDW: ESP32-S3 v0.2 (PSRAM)
00:00:00.270 UFS: FlashFS mounted with 12576 kB free
00:00:00.277 CFG: Loaded from File, Count 16
00:00:00.282 QPC: Count 1
00:00:00.283 SPI: Bus1 using GPIO48(CLK), GPIO47(MOSI) and GPIO41(MISO)
00:00:00.284 I2C: Bus1 using GPIO45(SCL) and GPIO19(SDA)
00:00:00.314 UFS: SDCard mounted (SPI mode) with 31154624 kB free
00:00:00.337 BRY: Berry initialized, RAM used 5370 bytes
00:00:00.668 UFS: SDCard mounted (SPI mode) with 31154624 kB free
00:00:00.993 UT : GT911
00:00:00.994 DSP: Configured display 'ST7701'
00:00:00.999 Project tasmota - Tasmota Version 14.0.0.4(8c4388b-lvgl-haspmota)-3_0_0(2024-05-31T14:01:34)
00:00:00.002 LVG: LVGL initialized
00:00:00.224 BRY: Successfully loaded 'autoexec.be'

Not all of the PSRAM seems to be mounted:

ESP Chip Id | 13143632 (ESP32-S3 v0.2)

0x182085 (QIO)
16384 KB
16384 KB
2673 KB
206 KB
92.8 KB (frag. 14%)
5568 KB PSRAM
4979 KB PSRAM FREE
 
832 KB (used 90%)
2880 KB (used 92%)
12608 KB

Conclusion, it seems to be that the new autoconfig file had an problem with my selfcompiled Tasmota.
I will try it again with autoconfig and my self compiled. May be some switches are enabled that should be disabled...like USE_GT911 and so on...
I can confirm that the autoconfig + Webinstaller .bin is working fine with this device.

[Jason2866]

All PSRAM is used. Since OPI PSRAM is available some of the PSRAM is used for storing Flash content to avoid screen flickering by accessing Flash. Access of OPI PSRAM is faster and flicker can be avoided. So the usable PSRAM is smaller. But still plenty of there...
The OPI PSRAM LCD screen optimization is only in Tasmota Arduino framework.

[Solar320]

There is enough PSRAM left. Now I have to learn how to use the berry script :) One of this Devices I want to use with an PCM5102A.
It is easy to disconnect the relay PCB and use the L1 to L3 pins als I2S instead. In the Picture above from my device PCB, there are some pins labeled. Also the not soldered connector at the upper side. There is an connection to reset, 3,3V, gnd and RX TX for some reason.
At the moment I lost my connection to the Display....it is not accessable over the website after some time but still connected to my router and the touchscreen is responsive. later.....

[Staars]

The PCM5102 should work.
I applied the solder bridges as seen on the photos:

[Solar320]

The bridges seems to be at set to the same position. For the conector I can crimp me an adapter, I have the material there.

[Staars]

Looks correct, do not forget the other side of the PCB. SCK must be pulled to GND to activate the clock of the audio board.

[Zaur949]

Hi, friend. help me please.
I didn't understand this point "6. upload some autoexec.be to see something"

[sfromis]

It means that you can have some Berry code to enable display operation, and use the display for something. Without having that "something" you want to use it for, nothing will appear.

The haspmota_demo.tapp example mentioned in the docs include an autoexec.be inside, automatically getting that example started.

If you want to have your "something" all in the pages.jsonl file for HASPmota, see:
https://tasmota.github.io/docs/HASPmota/#running-haspmota
And you can still add further handling using the Berry language.

If you instead want to use LVGL, you still need some code to get things rolling, like the example from the docs:
https://tasmota.github.io/docs/LVGL/#using-lvgl

You could also use the older display functions with DisplayText commands etc, but that is not great for using larger displays like this one in a good way.