Default `GT911` configuration of kit `EP-0172`

[rubienr]

Please make the default configuration of the GT911 touch controller publicly available.

• Kit: EP-0172 (MTP2063a-GFF 2.5 EYA-Display).

Unfortunately i ran into the same issue as described by this post: DiveInEmbedded/GT911-Touch-driver#1
During the attempt to swap the XY axis and invert X and Y axis by the controller itself (not as in the example code in the PI Pico firmware) i have overwritten the shipped config and cannot restore the original state.

I would appreciate if somebody can post the bytes dumped from the registers 0x8047 up to 0x8100 of the GT911 GOODiX controller.

Kind regards!

[Fighter19]

These are the config bytes starting from 8040, not related to this kit. (So you'll have to remove a few bytes first)
I don't know if this will help you.
I'm currently investigating an issue on my own, where the GT911 seems to have absolutely no config set and also seems to refuse any new config.
gt911_offset_8040.txt

EDIT: In case anyone is stumbling across this, the GT911 uses a bi-directional INT pin.
Failing to briefly de-assert this pin from host to touch upon reset, will leave the chip in sleep mode.

[ColinPamplin]

Resolved: GT911 blank config + sleep mode fix for EP-0172 in MicroPython

After extensive debugging I can confirm that all EP-0172 boards appear to ship with a completely blank GT911 touchscreen controller config (all zeros from 0x8047).
This affects both MicroPython and any code that relies on the factory config being present.
The chip also stays in sleep mode unless the INT pin is correctly toggled during reset.
Two issues to fix:

Sleep mode — the INT pin must be held low, then briefly pulsed after reset goes high:

touch_rst.value(0); int_pin.value(0); time.sleep_ms(20)
touch_rst.value(1); time.sleep_ms(5)
int_pin.value(0); time.sleep_ms(50)
int_pin.init(Pin.IN); time.sleep_ms(200)

Blank config — the GT911 needs a full 184-byte config written before it will report any touches. I used the config bytes posted by Fighter19 in this thread (thanks for sharing those) with the resolution corrected to 320x480.

I've written a MicroPython config writer touch_config.py that fixes both boards I tested.

The touch data byte mapping for this panel is also non-standard:

X = data[0] (8-bit, wraps at 255, range ~19-275)
Y = data[2] | (data[3] << 8) (range ~0-476)

I tested this on two EP-0172 boards, both of which appeared completely dead for touch.
Both work correctly after running the config writer once.

Full touch_config.py and MicroPython touch_example attached

touch_config.py

touch_example.py

Hope this helps someone