Hi there,
I don’t know what is your issue, I spend a lot of my free time Testing and making and anyone here long enough knows it. I don’t have to prove anything. I post ALL of my findings and help a lot of people, kind and courteous. While my Solutions may not fit your issue exactly I make the effort to move the conversation along to a better solution. look at this…
https://forum.seeedstudio.com/t/welcome-using-seeed-forums-and-forum-etiquette/251064?u=pj_glasso
I’m in the “Teach a man to fish” camp and try to have pride in if NOT knowing the ANSWER then where to find it. it’s what I offer and it’s what I do. that won’t change. Acting like a 14 year old and spamming posts with derogatory personal attacks won’t get you the solution.
Even though I wasn’t going to a posted proof it does work is all. You can rest assured I won’t answer any of your thoughts so Good Luck and have a better day!
HTH
GL 
PJ 
BTW, it doesn’t work for you … The Touchscreen because, The Seeed Studio Round Display with CST816S touch controller connected to the Xiao ESP32S3 Plus does not use TOUCH_INT = -1. It does use GPIO7 (D7) as the interrupt pin.
- The CST816S can work with or without using the INT pin.
- But the Seeed driver (like in
CST816S.h) requires INT pin to be defined for.available()to function properly, as it checks that pin’s state. - If you define it incorrectly (e.g.
-1), thetouch.available()check won’t respond. - Always call
Wire.begin(SDA, SCL)with correct pins, even if the driver sometimes does it behind the scenes.