tobozo

Can you confirm you have witnessed a working reference e.g. arduino_gfx, adafruit or other gfx library example sketch drawing lines without showing those symptoms? That will eliminate the hardware failure...

I converted TFT_eSPI init sequence, apparently it's using different values for pixel format and DFC, order of the commands is different too, some are repeated twice. You can try it...

this value is set to `0x22` in the original init sequence, but set to `0x02` in TFT_eSPI version  and there's `CMD_COLMOD, 1, 0x55,` where the color format should be...

hi, thanks for your feedback :+1: indeed the autodetect sequence will need a new entry, but first let's validate the display and touch configuration does it work if you edit...

[can't find much difference](https://github.com/search?q=repo%3Aespressif/esp-box%20CONFIG_BSP_BOARD_ESP32_S3_BOX_3&type=code) either maybe disable the id checker since miso is disabled, e.g. replace `0x04, 0xff, 0xE3` by `0,0,0`

last thing to try: manually set the reset pin as input_pullup `pinMode(GPIO_NUM_48, INPUT_PULLUP)` and set the RST pin to `(gpio_num_t)-1` in the autodetect config block after this I can't think...

:partying_face: > Now for the touchscreen? remove the while(1) from you setup and use this loop() test function: ```cpp void loop() { std::int32_t x, y, number = 0; while (display.getTouch(&x,...

Touch_TT21xxx class doesn't seem to make much of `cfg.pin_int` so unless you want to read the touch data from an ISR it's safe to disable it you can first try...

`Wire1.begin`

whoops `I2C device found at address 0x5D` actually smells like GT911 instead of TT21100 maybe update `cfg.i2c_addr = 0x5D` and change this: `auto t = new lgfx::Touch_TT21xxx()` into this `auto...