reTerminal DM 10.1" GT9271 touch mapping wrong after Raspbian image flash

Products & Technology Raspberry Pi
1

Hi Seeed / community,

I need help with the GT9271 touch configuration for the reTerminal DM 10.1".

History:
After buying the device I initially had a black screen. I then followed the official flashing guide:

I flashed the image with integrated drivers:
Raspbian-reTerminal-DM-arm64-v1.1.8.tar.xz

After that the display turned on immediately, but the touch input is wrong. The touch controller responds, but the coordinates are not mapped correctly. It is not just a simple X/Y swap or axis inversion. or any guide here reTerminal DM Flash OS | Seeed Studio Wiki
Some areas appear mirrored or shifted, and the touch position does not match the screen position.

Current status:

  • Touch controller: Goodix GT9271
  • I2C address: 0x5d
  • Linux driver binds as: Goodix-TS
  • Firmware/config file used: /lib/firmware/goodix_9271_cfg.bin

I have been trying to build/tune a goodix_9271_cfg.bin myself. Changing this file clearly changes the raw touch range, so it looks like the GT9271 config is important. But so far I only had limited success.

Could Seeed or someone with a working reTerminal DM 10.1" please confirm:

  • Is a correct goodix_9271_cfg.bin required for this device?
  • If yes, where can I get the official factory config?
  • Can someone share a working goodix_9271_cfg.bin or register dump?
  • Is the mainline Goodix-TS driver expected to work, or is a Seeed-specific driver required?
  • Or is my approach wrong and this could indicate a defective touch panel?

Any known-good config or guidance would help a lot.

Thanks.

2

I tested multiple older OS versions, both with and without the Seeed drivers pre-installed. The touch behavior remains unpredictable in all cases.

After a fresh installation with the default config, the mirrored half issue is gone, but the touchpad is still uncontrollable overall. Please see the screenshot attached.

I traced the lines with my finger and tracked the mouse pointer to verify the behavior. The pointer movement is still not stable or consistent across the full screen.

testet on Raspbian-reTerminal-DM-arm64.zip V1.0.9

As of now, I don’t see a practical way to calibrate it for this; it should work right out of the box.

touch_desktop_20260626_220205
touch_desktop_20260626_2202051280×800 31.8 KB

touch_desktop_20260626_220413
touch_desktop_20260626_2204131280×800 37.4 KB

touch_desktop_20260626_220352
touch_desktop_20260626_2203521280×800 79.6 KB

touch_desktop_20260626_220305
touch_desktop_20260626_2203051280×800 59.1 KB

3

Update with new screenshots

  • The cyan line shows the target path drawn by the test script.

  • The red line shows the measured touch input

  • The screenshots from the raw I2C script show the direct sensor input mapped locally in the script.

  • The screenshots from the desktop script in post above show the touch input after the full desktop/Wayland input chain.

This post is only to show the difference between the raw input layer and the final desktop touch result.

touch_20260626_225423
touch_20260626_2254231280×800 73 KB

touch_20260626_225347
touch_20260626_2253471280×800 70.8 KB

touch_20260626_225325
touch_20260626_2253251280×800 29.3 KB

touch_20260626_225309
touch_20260626_2253091280×800 34.1 KB

touch_20260626_225156
touch_20260626_2251561280×800 37.8 KB

4

Hi!

I have flashed a fresh Raspbian-reTerminal-DM-arm64-v1.1.8.tar.xz system for test.
After boot, it works well without any configuration.

Maybe it’s hardware issue?

5

Hi Hanzo,
thanks for reply.

I can not tell you if this is a hardware issue, because I have only one TerminalDM device for testing.

But if you have no issue after flashing with official Raspbian-reTerminal-DM-arm64-v1.1.8.tar.xz it seems to be a hardware issue.

There is one point that I would like to clarify before pushing for progress on complain at www.mouser.de for my device.

Does this file exist “/lib/firmware/goodix_9271_cfg.bin” ??? or is it not needed to make the touch-screen working normal in your case?

6

After checking, there is no such file like /lib/firmware/goodix_9271_cfg.bin.

seeed@reTerminal-DM:~ $ ls /lib/firmware/goodix_9271_cfg.bin
ls: cannot access '/lib/firmware/goodix_9271_cfg.bin': No such file or directory
7

If the file isn’t needed and it still works, then my hardware must have been defective when it was delivered.

Thank you very much for your help.

8

Yeah, you are welcome!

9

@Remudo I was facing same issue, checked which rules was created for screen - /etc/udev/rules.d/.

This folder contained screen rules, deleted and rebooted. Working fine for now.

10

**@AnshumanFauzdar
**
removing that file makes it worst in my case.