Compilation for ESP32S3 Display T-Display-S3

[SimonFili]

Hi all,

I'm trying to compile on gitpod.io for the ESP32S3 from Lilygo.

For my project, I need to enable the following:

scripts :
#ifndef USE_SCRIPT
#define USE_SCRIPT // adds about 17k flash size, variable ram size
#endif

ST7789
#ifndef USE_DISPLAY_ST7789
#define USE_DISPLAY_ST7789
#endif

CO2 sensor
#ifndef USE_MHZ19
#define USE_MHZ19
#endif

LVGL, HASPmota, and ST7789 display driver
#ifndef USE_LVGL
#define USE_LVGL
#endif

So I modified the user_config_override.h accordingly.

When I compile: platformio run -e tasmota32s3

I get lots of errors. I tried so many things, I lost track.

I get many undefined reference to lvbe_malloc, _Z10start_lvglPKc, _Z15lv_set_paint_cbPv, _Z15lv_get_paint_cbv, _Z12lvgl_startedv,
_Z24lvgl_set_screenshot_filePN2fs4FileE, _Z26lvgl_reset_screenshot_filev and maybe others. See the attached file for details.

Could someone you point me in the right direction please?

Thanks!

Simon

compile_output.txt

[sfromis]

That's what happens when you just pick a few #define instead of what would work. LVGL does not make sense without universal display.

And USE_DISPLAY_ST7789 is not really relevant with universal display.

Here's the setup used with standard precompiled LVGL builds:
https://github.com/arendst/Tasmota/blob/development/tasmota/include/tasmota_configurations_ESP32.h#L282-L484

[SimonFili]

Nice! I will keep this in mind! You guessed right, I was like a drunk driver, blind folded, trying to get around cones in a driving exam. Totally failed! ;-)

In my previous attempt, I tried this firmware:
https://github.com/Jason2866/Tasmota-specials/blob/firmware/firmware/tasmota32/other/tasmota32s3-lvgl.factory.bin

I could do commands like
DisplayText [z][x20y20s3]Test CO2

I compile the new firmware, by copying the section you provided, added MHZ19 and scripts.
It compiled OK.

But the DisplayText is not recognized and the console messages, does not show the ST7789. The firmware, from Jason, was showing this.

Any other tips ?

Thanks again,

Simon the blind! ;-)

[SimonFili]

Here's the boot log with the new firmware (compile with instruction from here)

00:00:00.001 CMD: Using USB CDC
00:00:00.002 HDW: ESP32-S3 v0.2 
00:00:00.039 UFS: FlashFS mounted with 12588 kB free
00:00:00.053 CFG: Loaded from File, Count 92
00:00:00.054 SER: Set to 8N1 115200 bit/s
00:00:00.054 SER: HWCDC supports 115200 bit/s only
00:00:00.062 QPC: Count 1
00:00:00.071 I2C: Bus1 using GPIO17(SCL) and GPIO18(SDA)
00:00:00.072 SCR: ufilesystem found
00:00:00.105 SCR: nv=1, tv=0, vns=1, vmem=30, smem=8192, gmem=344, pmem=0, tmem=8567
00:00:00.163 BRY: Berry initialized, RAM used 3831 bytes
00:00:00.206 Project tasmota - Tasmota Version 14.5.0.3(tasmota32)-3_1_3(2025-04-14T21:54:42)

With tasmota32s3-lvgl.factory.bin
Tasmota 14.5.0.3 (a4096ab-lvgl-haspmota)
With the Template for the T-Display-S3

00:00:00.002 CMD: Using USB CDC
00:00:00.002 HDW: ESP32-S3 v0.2 
00:00:00.025 UFS: FlashFS mounted with 12588 kB free
00:00:00.034 CFG: Loaded from File, Count 16
00:00:00.036 SER: Set to 8N1 115200 bit/s
00:00:00.036 SER: HWCDC supports 115200 bit/s only
00:00:00.042 QPC: Count 1
00:00:00.051 I2C: Bus1 using GPIO17(SCL) and GPIO18(SDA)
00:00:00.106 BRY: Berry initialized, RAM used 5268 bytes
00:00:01.076 DSP: ST7789 initialized
00:00:01.093 Project tasmota - Tasmota Version 14.5.0.3(a4096ab-lvgl-haspmota)-3_1_3(2025-04-14T09:07:11)
00:00:01.104 LVG: LVGL initialized

I can now do
DisplayText [z][x20y20s3]Test CO2

[sfromis]

Again, LVGL needs universal display, and it does not look like you activated this.

You need some Tasmota configuration.
https://tasmota.github.io/docs/Universal-Display-Driver/#migrating-to-udisplay

[SimonFili]

Alright, again, thanks for the quick feedback.

I tried to re-apply the auto config, since this is recommended in the migrating-to-udisplay section.
Funny thing is, when I do that, the device disconnect from the network and I need a hard reset.

From what I read, on the udisplay page, universal display support ST7789 TFT display in SPI.
I'm pretty sure that this board is using parallel more, according to the specs sheet: https://lilygo.cc/en-ca/products/t-display-s3

So, udisplay is not the way to go for this, it seems.

Maybe I require haspmota? In the previous code you provided, I see
#ifndef CODE_IMAGE_STR
#define CODE_IMAGE_STR "lvgl-haspmota"
#endif

Not sure if this is it?

@Jason2866, can you provide some insight how you compiled the version tasmota32s3-lvgl.factory.bin

Thanks!

[sfromis]

The buttons are not associated to display anything at all. The ON/OFF you see is not buttons but a power channel, and the display would be one, going on/off as you click. If you do not config anything to avoid the default actions of buttons, they will be coupled with available power channel(s). Decoupling buttons can be done via SetOption73 (or having classic rules).

[SimonFili]

Ok. I'm really working hard, hours of testing things, reading, trying. But I'm really not getting things working as expected. So sorry if I sound like an IQ of 70.

1. I'm fine with the webcam display, I don't mind.
2. This firmware does not see any I2C, i2cScan does not detect anything. So I will use the physical button.
3. Setoption73 is now ON. So button1 and button2 display action:single. Which is fine, I can trap those with Berry.
4. I have the toggle button on the main GUI page. This controls the display ON/OFF. Which is OK. I can use power on/off in the console to turn ON/OFF the display.
5. I have configured PWM 6 on GPIO2. Doc : PWM O6..11 are general purpose PWM.

• 6: because I want to have a "normal" PWM, that I can control with PWM6 0 to turn OFF the buzzer and PWM6 128 to turn it ON
• The issue: when I press the toggle, to turn on/off the display, GPIO2 is turning ON, even when PWM6 is 0. So when I will turn on the display, the alarm will sound.

So the question is, how do I detach power(toggle) On/off from the PWM6 output?
I want to have button1 through Berry control the display on/off and button2 through berry turn off the alarm.
But button1 is that case, would turn on the alarm when turning on the display.
How do I have independence of PWM from power?

Thanks!

[sfromis]

Experimenting a bit on a T-Display-S3, I'm also seeing that link from PWM to display, even when moving it to another pin, and not configuring that pin as PWM in Configure/Template (or Module). Using Berry gpio.set_pwm is still enough to influence the display, like changing PWM duty cycle can also influence display brightness, and the DisplayDimmer command can influence led brightness. I did not see similar linking with a SSD1306 display (instead of the ST7789).

This does not look like intended behavior, more like a bug. One speculation could be whether it might be related to RMT channels used for PWM, and maybe also somehow for the display. Not sure where such a link might even originate.

@s-hadinger - could this be related to the work about taking advantage of RMT channels where useful?

[SimonFili]

I found a workaround the bug.

I configured
GIPO2 to PWM6
GIPO3 to PWM7 (connected to Piezo)

Now, PWM7, remains independent of the display power toggle.
I can use PWM6 for the display brightness.
I will work around this for now.

Let me know if you find a fix.

Thanks!

[SimonFili]

Here's the latest, after the find of a solution for the PWM / Display issue!

With alarming in red zone (buzzer on), button 1, to turn on/off display, button2 to silence the alarm.