WebDust21

@minilogic Curious if there's a reason you used the LVGL partial buffer -> blit to "outside" framebuffer, instead of utilizing the LVGL full-buffer/double-buffering methodology? It's not like we're lacking for...

> @WebDust21 You're probably right and it's worth trying double buffering. It's a pity that I have so little free time. This damn war took away not only my home...

> If anyone has any suggestions I am open to all suggestions and will be involved. Thank you again https://github.com/lvgl/lvgl_esp32_drivers/blob/master/lvgl_touch/gt911.c might be able to leverage some hints from here (although...

It is worth noting that @minilogic already implemented I2C touch functionality in the LVGL 9 example--for the NS2009 resistive touch controller. You just need to adapt this to the GT911...

actually digging further, I realized that the "ns2009_read" call is a specialized function inside the general "twi.c"... https://github.com/minilogic/f1c_nonos/blob/bbde37f38aaccbc5d3f34ebb7e0bae37ae4052bc/drv/twi.c#L233-L298 so not as simple as it might seem from the LVGL 9...

Looks like it should work. I'd highly recommend test debugging with printf statements to indicate values at particular locations (i.e. read chip device ID, print the result -> compare to...

Are you running the ESP32 and F1C200s test code on the exact same GT911 sensor?

> Do you think I2C of F1C200S is normal? Of course. This is one of the most basic chip functions, so likelihood of fault with it is extremely low--plus @minilogic...