ESP32-2424S012 as LVGL light controller / CST816 Support

[H3adsho0ot]

I got this cheap ESP32 screen: Aliexpress and would love to use it as a litte light controller on my desk.

It is labeld as ESP32-2424S012 and found this schematics:

So we can see that we have these pins in use:
Display (GC9A01):

• clk = 6
• mosi = 7
• dc = 2
• cs = 10
• backlight = 3

Touch (CST816D):

• sda = 4
• scl = 5
• int = 0
• rst = 1

We have a ESP32c3 Board so I used the tasmota32c3-lvgl.factory.bin

I used the GC9A01_display.ini with this header: :H,GC9A01,240,240,16,SPI,3,10,6,7,2,3,-1,-1,80
I had some problems with wrong colors as described in #19339;

So I changed :R to

 :R,36
 :0,C8,00,00,00
 :1,A8,00,00,01
 :2,08,00,00,02
 :3,68,00,00,03

and removed :i,20,21.

I set GPIO18 to OptionA 3 for now as it's not used.

For testing I use this simple lvgl-berry script as autoexec.be file:

lv.start()

scr = lv.scr_act()            # default screan object

scr.set_style_bg_color(lv.color(lv.COLOR_GRAY), lv.PART_MAIN | lv.STATE_DEFAULT)

colp = lv.colorwheel(scr, false)
colp.set_size(200, 200)
colp.set_pos(20,20)

logo = lv.img(scr)
logo.set_tasmota_logo()
logo.center()

and this is how it looks for now:

Now I am trying to get the touch working. I added this line to my display.ini:
:TI1,15,5,4,-1,-1

The problem is that I think that it's not working - becaus I can't use the color wheel.

I also tried the calibration preset but it is not showing properly on the round display and it also seem to not respond to touch inputs at all.
I have absolutely no ide how to debug touch in tasmota so I hope that someone can help me a little.

[H3adsho0ot]

Is it possible that CST816 is not supported in tasmota? The device is not listed here: supported-i2c-devices

[sfromis]

Tasmota being able to detect a device as FT5206 implies some degree of "similarity", but it is not a given that this means actually compatible. I2C device detection is not very robust.

[H3adsho0ot]

Of course the case and the pcb are glued to the screen but I got my hotair gun out and got sure that I have the right touch controller and yes it is a CST816:

(Sorry for the bad image but the chip is really tiny)

[jpmorrison]

Silly question but how do I flash tasmota32c3-lvgl.factory.bin? It won't upload over the web/ota and I keep getting boot loops with esptool

[sfromis]

As posted in the other thread, #20695 the .factory binaries are only for initial wired flashing. For OTA upgrade (both via http and upload), remove the .factory part.

[jpmorrison]

I tried with/without the .factory - it was failing with the url and file upload.
But I finally got it loaded: it's now on 13.4.0.2 (6a35795-lvgl-haspmota) for esp32c3
I had the wrong url and forgot github redirects it somewhere else to the real .bin.

[Jason2866]

At the moment this touch controllers are supported: XPT2046, FT5206 and GT911
Maybe yours is compatible to? Didn't look in the datasheet

[Jason2866]

Maybe this lib is compatible to your controller https://github.com/fbiego/CST816S ?

[H3adsho0ot]

I can't get Serial working in arduino ide on this board for now - not sure why . So can't tell right now

[H3adsho0ot]

Got it to work with this lib.
The following seems to work perfect:

#include <CST816S.h>

CST816S touch(4, 5, 1, 0);

void setup() 
{
  Serial.begin(9600);
  touch.begin();
  while (!Serial) {
    ; // wait for serial port to connect. Needed for native USB port only
  }
}

void loop()
{
  if (touch.available()) 
  {
    Serial.print(touch.gesture());
    Serial.print("\t");
    Serial.print(touch.data.points);
    Serial.print("\t");
    Serial.print(touch.data.event);
    Serial.print("\t");
    Serial.print(touch.data.x);
    Serial.print("\t");
    Serial.println(touch.data.y);
  }
}

[s-hadinger]

Maybe we need a "universal touch driver" as well. Currently it is using dedicated libs for each touch screen. An global abstraction may be possible.

[ZigDuDim]

Hi guys ! I have the same module and I have EXACTLY the same problem. Display is working fine, but I cannot get the touchpad to work.
I already posted my problem here:
https://forum.lvgl.io/t/implement-squareline-lvgl-project-to-esp32-2424s012-module-ga9a01-cst816d-drivers/13150

I am using the CST816D.h driver instead of CST816S.h and I have the exact same result.

[ZigDuDim]

We found a solution on the LVGL forum. The solution was to introduce those function in the main loop.
lv_task_handler(); lv_tick_inc(5);
I don't know how implement those function in tasmota environment, I can't help you. But the touchpad is working fine since I add them in the Arduino code. So to me the problem is more due to the LVGL library and not the touchpad driver.

I hope this will help. Good Luck

[s-hadinger]

lv_task_handler and lv_tick_inc are called by Tasmota. Otherwise LVGL wouldn't work correctly.

[Jason2866]

@ZigDuDim The CST816 touch driver is not implemented in Tasmota.

[ZigDuDim]

I have the same module and the same problem as @H3adsho0ot without using Tasmota. So I thought that maybe, even if CST816 is not yet implemented in Tasmota, the problem could be some where else.

[ameeuw]

Thank you all for this discussion - I have been eager to get this board to work with Tasmota.
Yesterday I sat down and added support for the CST816S driver and opened a PR (#20213) - if you could try it out yourself I have compiled it with the [env:tasmota32c3] environment and added -DFIRMWARE_LVGL and -DUSE_CST816S.

The PR has an .autoconf attached which should apply the necessary settings after being flashed.

[AloneHUANG]

I got the same display and want to run tasmota on it and make it a smart switch control board. After define the GPIOs according to the schematic drawing, the screen is still no response. Would you please help to post the template (GPIO) of it? Thanks.

[sfromis]

It needs mcp23x.dat defined - I think it's customized to the board?

No, don't worry about that message. It is totally unrelated to using displays, and is not even an error message.

[jpmorrison]

display.ini listed above is missing the I2C interrupt and reset gpios as well as the touch mappings.

The PR for the CST touch driver has them in a zip file for this module.

:TI1,15,5,4,0,1
:M,240,0,240,0

Now I just need to get the berry script working to see if the touchscreen really works.

[sfromis]

With log level 4, you should get console messages when some touch is detected, irrespective of it being used for anything.

[jpmorrison]

Thanks that helps. I see touch events. Maybe the mapping is wrong - the x, y and gesture never changes

16:07:47.031 TS : TSGlobal.touched x=240 y=0 gest=0x00 (raw x=0 y=1536)
16:07:47.046 LVG: TS: 240, 0
16:07:47.086 LVG: TS: 240, 0
16:07:47.126 LVG: TS: 240, 0

[sfromis]

Your words sounds like you "just" copied the config lines from somewhere. Did you make sure to verify/adjust the I2C address and 4 pin numbers to your actual hardware?

[jpmorrison]

Your words sounds like you "just" copied the config lines from somewhere. Did you make sure to verify/adjust the I2C address and 4 pin numbers to your actual hardware?

I copied the info from the ESP32C3-2424S012 autoconf, which is from the same PR that added the touchscreen driver. I can read the PCB schematic too.

I have the exact same model, and the touch screen worked perfectly in the demo.
The Arduino demo files have all the SPI/I2C, chip info (don't know why the OP had to open it up).
Still, I guess I should build the demo sketch just to confirm.

I'm comparing the Arduino CST816D.h from the demo with the Tasmota CST816S code and all of the taps/presses in Tasmota are set to none, Tasmota only has the swipe gestures.

Aliexpress has a download link for the demo software. All the taps/presses return a value, maybe Tasmota doesn't support that, and they are all set to 0 (None).

~/1.28inch_ESP32-2424S012/1-Demo/Demo_Arduino/1_1_Factory_samples/Factory_samples/CST816D.h
#define I2C_ADDR_CST816D 0x15

//手势
enum GESTURE
{
    None = 0x00,       //无手势
    SlideDown = 0x01,  //向下滑动
    SlideUp = 0x02,    //向上滑动
    SlideLeft = 0x03,  //向左滑动
    SlideRight = 0x04, //向右滑动
    SingleTap = 0x05,  //单击
    DoubleTap = 0x0B,  //双击
    LongPress = 0x0C   //长按
};

[jpmorrison]

Well it's working now after I added the init.bat from @ameeuw's autoconf.zip and made some other changes.
I had to remove the I2C line for touch :TI1,15,5,4,0,1 from display.ini and configure the same GPIOs for I2C
Maybe it works on his build/version but it doesn't work for me using the dev build I downloaded tasmota32c3-lvgl.bin (13.4.0.2 (6a35795-lvgl-haspmota)).

His autoexec.be also has to be changed as well to remove lv.colorwheel() - online docs must be out of date as there are numerous examples using colorwheel.

I currently have a mixed config of @H3adsho0ot's template and @ameeuw's init.bat and my settings.
I'll just list some output here. Later I'll reset and see if I can make a working init.bat/autoexec.be.
This module should take all of 2 minutes to setup.

TL:DR; ESP32-2424S012C-I working touch display with tasmota32c3-lvgl.bin/(13.4.0.2 (6a35795-lvgl-haspmota) CST916 driver.
I downloaded from https://github.com/tasmota/install/blob/firmware/firmware/unofficial/tasmota32c3-lvgl.bin but these are constantly changing so YMMV.

For future template(s): ESP32-2424S012C-I has touch input. ESP32-2424S012N-I does not have touch - display only. (The other ESP32-2424S012C SKUs are just the touchscreen model in a case.)

The touchscreen is working for press (gest=0)/release, gestures for swipe down/up/left/right (0x10-0x13). There's no longpress or doubletap gesture. Original demo code/drivers says it should report those but I really can't remember.

These log messages are with the touchscreen working properly. I've seen other versions or nothing at all depending on settings.

00:00:00.053 I2C: Bus1 using GPIO05(SCL) and GPIO04(SDA)
...
00:00:00.170 I2C: CST816S found at 0x15
00:00:00.281 UTI: CST816S, version: 0, versionInfo: 182.2.2
00:00:00.650 DSP: Configured display 'GC9A01'
00:00:00.655 SRC: Restart

With web logging set to 4 (More debug) I can see tap/gestures and x,y coordinates:

09:07:52.849 TS : TSGlobal.touched x=5 y=134 gest=0x10 (raw x=5 y=134)
09:07:52.856 LVG: TS: 5, 134
09:07:52.931 LVG: TS: 5, 134
09:07:52.950 TS : TSGlobal.touched x=197 y=41 gest=0x00 (raw x=197 y=41)
09:07:52.967 LVG: TS: 197, 41
09:07:53.007 LVG: TS: 197, 41
09:07:53.047 LVG: TS: 197, 41
09:07:53.052 TS : TSGlobal.touched x=149 y=20 gest=0x12 (raw x=149 y=20)
09:07:53.087 LVG: TS: 149, 20
09:07:53.127 LVG: TS: 149, 20

Other stuff:
Setting GPIO09 to Button_n turns the display on/off. This is the boot button at the back

08:33:00.601 BTN: Button1 multi-press 1
08:33:01.102 SRC: Button
08:33:01.108 RSL: RESULT = {"POWER":"OFF"}
08:33:01.110 RSL: POWER = OFF
08:33:04.740 BTN: Button1 multi-press 1
08:33:05.236 SRC: Button
08:33:05.242 RSL: RESULT = {"POWER":"ON"}
08:33:05.244 RSL: POWER = ON

There's a small switch on the side of the PCB. SW1 connects to the battery/charger circuit (KEY) - from other discussions it's an on/off switch for battery power.

S1 on the schematic is connected to GPIO8 through a zero ohm resistor, and a 10k pullup. I haven't opened the case to check, maybe it can be used for something.

There are logs from the bootloader on USB serial but nothing is logged on serial after tasmota boots.
USB D+ D- use GPIO18/19 - but the module has Option A3 on both. Maybe the Option A3 can be moved or set some other way.
The module has a separate connector using TX/RX so maybe it's going there instead. I can't check until I get the proper parts to test it.

Working display + touch input

Config - it works for me, with this particular Tasmota build/version and module from Aliexpress.

Backlog Template; Module; GPIO 255:

09:15:33.135 CMD: Backlog Template; Module; GPIO 255:
09:15:33.137 SRC: WebConsole from 192.168.0.178
09:15:33.139 CMD: Grp 0, Cmd 'BACKLOG', Idx 1, Len 27, Pld -99, Data 'Template; Module; GPIO 255:'
09:15:33.165 SRC: Backlog
09:15:33.169 CMD: Grp 0, Cmd 'TEMPLATE', Idx 1, Len 0, Pld -99, Data ''
09:15:33.171 RSL: RESULT = {"NAME":"GC9A01","GPIO":[1,1,800,992,1,1,736,704,1,1,768,0,0,0,0,0,0,0,1,6210,1,1],"FLAG":0,"BASE":1}
09:15:33.379 SRC: Backlog
09:15:33.380 CMD: Grp 0, Cmd 'MODULE', Idx 1, Len 0, Pld -99, Data ''
09:15:33.382 RSL: RESULT = {"Module":{"0":"GC9A01"}}
09:15:33.590 SRC: Backlog
09:15:33.591 CMD: Grp 0, Cmd 'GPIO', Idx 1, Len 4, Pld 255, Data '255:'
09:15:33.596 RSL: RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"0":"None"},"GPIO2":{"800":"SPI DC1"},"GPIO3":{"992":"Backlight"},"GPIO4":{"640":"I2C SDA1"},"GPIO5":{"608":"I2C SCL1"},"GPIO6":{"736":"SPI CLK1"},"GPIO7":{"704":"SPI MOSI1"},"GPIO8":{"0":"None"},"GPIO9":{"64":"Button_n1"},"GPIO10":{"768":"SPI CS1"},"GPIO11":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO18":{"6210":"Option A3"},"GPIO19":{"6210":"Option A3"},"GPIO20":{"0":"None"},"GPIO21":{"0":"None"}}

This just shows the tasmota logo, you can see touch screen input in the console with more logging set.

autoexec.be

lv.start()

# call from berry console: load("autoexec.be")

hres = lv.get_hor_res()       # should be 240
vres = lv.get_ver_res()       # should be 240

scr = lv.scr_act()            # default screen object
#f10 = lv.montserrat_font(10)

scr.set_style_bg_color(lv.color(lv.COLOR_GRAY), lv.PART_MAIN | lv.STATE_DEFAULT)

# not working in 13.4.0.2 6a35795-lvgl-tasmota
#colp = lv.colorwheel(scr, false)
#colp.set_size(200, 200)
#colp.set_pos(20,20)

logo = lv.img(scr)
logo.set_tasmota_logo()
logo.center()

display.ini

don't use # for comments/docs - it seems everything after the first # is ignored

:H,GC9A01,240,240,16,SPI,3,10,6,7,2,3,-1,-1,80
:S,2,1,0,1,80,80
:I
EF,0
EB,1,14
FE,0
EF,0
EB,1,14
84,1,40
85,1,FF
86,1,FF
87,1,FF
88,1,0A
89,1,21
8A,1,00
8B,1,80
8C,1,01
8D,1,01
8E,1,FF
8F,1,FF
B6,2,00,20
3A,1,05
90,4,08,08,08,08
BD,1,06
BC,1,00
FF,3,60,01,04
C3,1,13
C4,1,13
C9,1,22
BE,1,11
E1,2,10,0E
DF,3,21,0c,02
F0,6,45,09,08,08,26,2A
F1,6,43,70,72,36,37,6F
F2,6,45,09,08,08,26,2A
F3,6,43,70,72,36,37,6F
ED,2,1B,0B
AE,1,77
CD,1,63
70,9,07,07,04,0E,0F,09,07,08,03
E8,1,34
62,0C,18,0D,71,ED,70,70,18,0F,71,EF,70,70
63,0C,18,11,71,F1,70,70,18,13,71,F3,70,70
64,7,28,29,F1,01,F1,00,07
66,0A,3C,00,CD,67,45,45,10,00,00,00
67,0A,00,3C,00,00,00,01,54,10,32,98
74,7,10,85,80,00,00,4E,00
98,2,3e,07
35,0
21,0
11,80
29,14
:o,28
:O,29
:A,2A,2B,2C,01
:R,36
:0,C8,00,00,00
:1,A8,00,00,01
:2,08,00,00,02
:3,68,00,00,03
:D,51
:M,240,0,240,0
:r,2
#:TI1,15,5,4,0,1
#:TI1,addr,SCL,SDA,IRQ,RST
#:TI1,15,*,*,0,1
#:i,20,21
#

[Jason2866]

There are logs from the bootloader on USB serial but nothing is logged on serial after tasmota boots.

With next commit done in Tasmota repo there should be an Tasmota32-C3 CDC LVGL build available in unofficial WebInstaller.

[jpmorrison]

CDC works well - 13.4.0.2 (268fad6-lvgl-haspmota) tasmota32c3cdc-lvgl.bin

From USB serial I can see the touch screen is very responsive! You can't tell from the web console.

Anyone know if esp32c3cdc-lvgl-bluetooth is possible/request for an unofficial?

The vendor docs show programming with 80 MHz SPI/QIO. Tasmota shows DIO - should I try to switch this?

[Jason2866]

The Tasmota default flash compile mode is DIO. There are modules which do not work with QIO.
For fine tuning / customizing self compile is the way to go.
There will be no BT LVGL build. Either BT or LVGL will not work well or the build is unreliable at all.

[sfromis]

Don't expect much of a Tasmota core performance increase going from DIO to QIO for flash access, this is more if you have heavy file system access.

[jpmorrison]

Updated autoconf tested with 13.4 tasmota32c3cdc-lvgl.bin and tasmota32c3-lvgl.bin

• updated autoexec.be to show the touchscreen works (nothing fancy), removed colorwheel() which no longer works
• updated display.ini to remove I2C settings which break CST816. I2C is already set in template
• init.bat - renamed the module, only the 2424S012C versions have a touch sensors. You can buy a 2424S012N which is display only
• I left gpio8, 9 and gpio20,21 RX/TX unset in the template.

ESP32C3-2424S012C.autoconf.zip

[aykevl]

For those that can't get this device to work: I found that it requires a USB 2.0 USB-C cable. So what I did to make it work, was to use a USB-C to the older USB receptable adapter, and then a cheap 2.0-only USB cable (A to C).
Without this particular cable, it won't even power up and show up on the computer.