Touch on Sunton ESP32-8048S043C

[oschettler]

I've installed sunton-8048s043c_full_16MB_v0.7.0-rc6_2f4092b.bin
The board has an 800x480 capacitive touch screen.

The display works nicely. However, I've noticed that the touch interface is of an incorrect scale:

When I touch the display a little below and right of the center, the pointer already is in the lower right corner.

The configuration for this board starts here:

openHASP/user_setups/esp32s3/sunton-esp32-s3-tft.ini

Line 123 in 6cf4262

[env:sunton-8048s043c_16MB]

I see TFT_WIDTH=800 and TFT_HEIGHT=480, but also TOUCH_WIDTH=480 and TOUCH_HEIGHT=272. Maybe this is the problem?

Best,
-- Olav

[fvanroie]

Are you sure it is the ESP32-8048S043C and not the ESP32-8048S050C ? Which link did you buy the display from?

If it is an actual ESP32-8048S043C (check the PCB code on the backside), maybe they changed the hardware revision of the touchscreen...

[oschettler]

The board has "ESP32-8048S043" on the back.

[oschettler]

I have compiled a version with TOUCH_WIDTH and THOUCH_HEIGHT fixed:

diff --git a/user_setups/esp32s3/sunton-esp32-s3-tft.ini b/user_setups/esp32s3/sunton-esp32-s3-tft.ini
index 7cbb14d8..73eec22e 100644
--- a/user_setups/esp32s3/sunton-esp32-s3-tft.ini
+++ b/user_setups/esp32s3/sunton-esp32-s3-tft.ini
@@ -144,8 +144,8 @@ build_flags =
     -D TFT_PREFER_SPEED=14000000  ; 1/2 of Typical DCLK Frequency
     -D TFT_AUTO_FLUSH=1
     ; Touch Settings
-    -D TOUCH_WIDTH=480
-    -D TOUCH_HEIGHT=272
+    -D TOUCH_WIDTH=800
+    -D TOUCH_HEIGHT=480
     -D TOUCH_DRIVER=0x911
     -D TOUCH_SCL=20
     -D TOUCH_SDA=19

To make it compile, in platform_override.ini, I also had to add:

extra_default_envs =
    sunton-8048s043c_16MB

I also needed to comment the upload_speed in platform.ini:

[env]
;upload_speed = 921600

With this, I get the full screen width for touch.

Thank you for this fine software.
-- Olav

[Gemelon]

I have the exact same display and I have the exact same problem, how do you resolve the problem?

[RyanEwen]

Do you guys get backlight flicker at 100% and a rolling effect at lower brightnesses? I also get some artifacts when changing pages. Not sure if it's just me

[RyanEwen]

Following-up, I switched to ESPHome with the new LVGL widget support and have working configs for a handful of devices here: https://github.com/RyanEwen/esphome-lvgl/tree/main/devices

The key thing with the larger CYDs was to use specific older versions of esp-idf. Maybe that can help someone here.

[Rolibaer]

Test Report – Display ESP32-8048S043C with RC12 & RC15

Hardware: ESP32-8048S043C
Touch Controller: GT911
Firmware Versions Tested: RC12, RC15
Build Environment: Gitpod (compiled .bin file with platform_override.ini from oschettler)
Web Interface: Working as expected
Display: Not working (white screen...)
Touch (GT911): Not responding

Issue Description:
After flashing RC12 and RC15 firmware to the ESP32-8048S043C, the web interface is fully functional. However, the display remains blank and shows no content. The touch controller (GT911) is also unresponsive.

Questions:

Have there been any recent changes to display/touch drivers between RC6 and RC15?
Is the ESP32-8048S043C supported in these release candidates?

[fvanroie]

Thanks @ELNL , that's very useful information indeed. I have reworked the GT911 driver to use the maximum coordinates from the firmware registers. Can you please test with this firmware below on both devices and see if it auto-detects the touch resolution?

https://github.com/HASwitchPlate/openHASP/actions/runs/29157291451

TOUCH_WIDTH and THOUCH_HEIGHT are now optional and not needed for the GT911 driver to know the maximum coordinates.

[ELNL]

I looked at the link. Important to know, Once more learning, I am not a software develloper. Also, only experienced with the ESP-IDF platform, not Arduino.
But, the idea to read the max coordinates out of registers sonds likea great option. The link points to code I cannot deploy or fully understand. Could you point out how the members xResolution and yResolution from 'TouchGt911* instance" get the value?

I'll try reading the values of registers 0x8048 .. 0x804B of both modules. Maybe they come up with the right values. It is late now, It will take 1 or 2 days for me to do the test . Grtzz.

[fvanroie]

The code is here, it already reads the info block which includes the resolution:

openHASP/src/drv/touch/touch_driver_gt911.cpp

Lines 88 to 99 in 118fc6e

	info = touch.readInfo();
	if(info && info->xResolution > 0 && info->yResolution > 0) {
	break;
	}
	}
	}
	if(info && info->xResolution > 0 && info->yResolution > 0) {
	xResolution = info->xResolution;
	yResolution = info->yResolution;
	_read_strategy = &TouchGt911::read_active;
	LOG_INFO(TAG_DRVR, "GT911 %s (%dx%d)", D_SERVICE_STARTED, info->xResolution, info->yResolution);

You do not need to change this yourself or compile it yourself, you can download Sunton.zip from the bottom of the Build Actions, under Artifacts:
https://github.com/HASwitchPlate/openHASP/actions/runs/29157291451

The ESP32-8048S043C firmware bin files are already compiled in the Sunton.zip file.
You should see in the serial log a line that says GT911 Service started (800x480) or GT911 Service started (480x272).
That line should already appear in your current firmware too. Just check the serial log at (re)boot.

[ELNL]

I am sorry I don't know how to download code into the target. I use the Visual Code IDE with the plugin from Espressif. The workflow is just execute some pyton call and the flash process runs. For me this proces is a 'black box'.

But, maybe I can be of some help. I made two functions that read following of the chip:

bool readTouchChip8bitRegister(const uint16_t reg, uint8_t * value)
{
    if (touchInstanceHandle == NULL)
    {
        return false;
    }
    if (touchInstanceHandle->io == NULL)
    {
        return false;
    }
    if (esp_lcd_panel_io_rx_param(touchInstanceHandle->io, reg, value, sizeof(uint8_t)) != ESP_OK)
    {
        return false;
    }
    return true;
}

bool readTouchChip16bitRegister(const uint16_t reg, uint16_t * value)
{
    uint8_t lowByte = 0;
    if (!readTouchChip8bitRegister(reg, &lowByte))
    {
        return false;
    }
    uint8_t hiByte = 0;
    if (!readTouchChip8bitRegister(reg + 1, &hiByte))
    {
        return false;
    }
    *value = (((uint16_t)hiByte) << 8) + (uint16_t)lowByte;
    return true;
}

After initialisation of the GT911 chip I added this code to read the maximum values the GT911 chip would give. With these numbers I can scale the position of the touch to send to LVGL.

#define ESP_GT911_REGISTER_CONFIG_VERSION   0x8047
#define ESP_GT911_REGISTER_OUT_MAX_X_LOW    0x8048
#define ESP_GT911_REGISTER_OUT_MAX_X_HI     0x8049
#define ESP_GT911_REGISTER_OUT_MAX_Y_LOW    0x804A
#define ESP_GT911_REGISTER_OUT_MAX_Y_HI     0x804B

    uint8_t versionByte;
    if (esp_lcd_panel_io_rx_param(touchInstanceHandle->io, ESP_GT911_REGISTER_CONFIG_VERSION, &versionByte, 1) != ESP_OK)
    {
        ESP_LOGE(TAG, "%s: fail reading version", __func__);
        return false;
    }
    if (!readTouchChip16bitRegister(ESP_GT911_REGISTER_OUT_MAX_X_LOW, &touchHres))
    {
        ESP_LOGE(TAG, "%s: fail Hres", __func__);
        return false;
    }
    if (!readTouchChip16bitRegister(ESP_GT911_REGISTER_OUT_MAX_Y_LOW, &touchVres))
    {
        ESP_LOGE(TAG, "%s: fail Vres", __func__);
        return false;
    }

    ESP_LOGI(TAG, "%s: current version=%u Hres:%u Vres:%u", __func__, versionByte, touchHres, touchVres);
    return true;

This works for both display versions 65 and 66 perfect. This eliminates constants in the code.

Version 65 outputs:
I (1194) Display: Display8048S043_Touch_init: current version=65 Hres:480 Vres:272
Version 66 outputs:
I (1194) Display: Display8048S043_Touch_init: current version=66 Hres:800 Vres:480

Hope you can use this confirmation.

[ELNL]

The performance of the two different displays is not noticable.

VID-20260712-WA0005.mp4