Today, the GT911 register map is almost fully public, mostly thanks to leaked datasheets appearing on GitHub and sites like Linux Hardware Database.
The typical map used by developers looks like this:
Below is the definitive register map for the GT911. All addresses are 16-bit. Note: The GT911 uses Big-Endian (MSB first) for multi-byte values.
| Start Addr | End Addr | Size (bytes) | Name / Section | Type | Description |
| :--- | :--- | :--- | :--- | :--- | :--- |
| 0x8000 | 0x8000 | 1 | Product ID (MSB) | RO | First char of ID (e.g., '9') |
| 0x8001 | 0x8001 | 1 | Product ID | RO | Second char (e.g., '1') |
| 0x8002 | 0x8002 | 1 | Product ID | RO | Third char (e.g., '1') |
| 0x8003 | 0x8003 | 1 | Product ID (LSB) | RO | Fourth char (e.g., 0x00 for string end) |
| 0x8004 | 0x8004 | 1 | Firmware Version | RO | Major/minor version |
| 0x8005 | 0x8005 | 1 | X Output Maximum (MSB) | RO | Reserved / default |
| 0x8006 | 0x8006 | 1 | X Output Maximum (LSB) | RO | Reserved / default |
| 0x8007 | 0x8007 | 1 | Y Output Maximum (MSB) | RO | Reserved / default |
| 0x8008 | 0x8008 | 1 | Y Output Maximum (LSB) | RO | Reserved / default |
| 0x8009 | 0x800F | 7 | Reserved / Status | RO | Touch count & flags |
| 0x8010 | 0x8024 | 21 | Point 1 Data (TrackID, X, Y, Size) | RO | First touch report |
| 0x8025 | 0x8039 | 21 | Point 2 Data | RO | Second touch report |
| 0x803A | 0x804E | 21 | Point 3 Data | RO | Third touch report |
| 0x804F | 0x8063 | 21 | Point 4 Data | RO | Fourth touch report |
| 0x8064 | 0x8078 | 21 | Point 5 Data | RO | Fifth touch report |
| 0x8079 | 0x807E | 6 | Reserved / Checksum | RO | Touch protocol integrity |
| 0x8040 | 0x8040 | 1 | Gesture ID | RO | Up/Down/Left/Right/Double-Click |
| 0x8041 | 0x80FF | 191 | Reserved | - | Not documented |
| 0x8100 | 0x8100 | 1 | Config Version | RW | Configuration version number |
| 0x8101 | 0x8101 | 1 | X Resolution (MSB) | RW | Screen width (max touch X) |
| 0x8102 | 0x8102 | 1 | X Resolution (LSB) | RW | Screen width |
| 0x8103 | 0x8103 | 1 | Y Resolution (MSB) | RW | Screen height (max touch Y) |
| 0x8104 | 0x8104 | 1 | Y Resolution (LSB) | RW | Screen height |
| 0x8105 | 0x8105 | 1 | Touch Threshold | RW | Finger detection sensitivity (default 80) |
| 0x8106 | 0x8106 | 1 | Active (Screen-On) Gain | RW | Amplification factor for touch |
| 0x8107 | 0x8107 | 1 | Standby (Screen-Off) Gain | RW | Low-power detection gain |
| 0x8108 | 0x8108 | 1 | Debounce | RW | Number of consecutive samples (1-10) |
| 0x8109 | 0x8109 | 1 | Noise Reduction | RW | Filter level (0-7) |
| 0x810A | 0x810A | 1 | Screen Touch Level | RW | Reserved |
| 0x810B | 0x810B | 1 | Proximity Enable | RW | Enable/Disable proximity sensing |
| 0x810C | 0x810C | 1 | Handheld/Pen Enable | RW | Mode selection for stylus |
| 0x810D | 0x811D | 17 | Key Area Array | RW | Physical button mapping |
| 0x811E | 0x812F | 18 | Proximity & Noise Settings | RW | Advanced tuning |
| 0x8130 | 0x813F | 16 | Gesture Parameters | RW | Swipe angles, double-tap timing |
| Address | R/W | Name | Description |
|---------|-----|------|--------------|
| 0x8040 | R | Product ID (first byte) | Usually '9' |
| 0x8041 | R | Product ID (second byte) | Usually '1' |
| 0x8042 | R | Product ID (third byte) | Usually '1' |
| 0x8043 | R | Firmware version | Major/minor |
| 0x8044 | R | Resolver version | -- |
| 0x8045 | R | Patch version | -- |
| 0x8046 - 0x8047 | R | Vendor ID | -- |
| 0x8048 - 0x804A | R | LCD X resolution | Bytes: LSB, MSB, reserved |
| 0x804B - 0x804D | R | LCD Y resolution | Bytes: LSB, MSB, reserved |
| 0x804E | R/W | Config checksum (high) | Used for verification |
| 0x804F | R/W | Config checksum (low) | Used for verification |
| 0x8050 | R | Number of touch points | 0x00=no touch, 0x01-0x05 |
| 0x8051 | R | Gesture ID | 0x00=none, 0x01=slide up/down, etc. |
If you want, I can produce a device-specific register map for your GT911 module—tell me the Product ID string or share the module's PCB markings.
(Invoking related search terms.)
While there isn't a single famous "folktale" about the Go to product viewer dialog for this item.
, the story of its register map is a classic rite of passage for many embedded systems engineers. For those working with capacitive touchscreens, diving into the Goodix GT911 registers often feels more like solving a puzzle than following a manual. The "Hidden" Nature of the GT911
For years, the GT911 was a bit of a "black box" in the maker community. Many developers found themselves with cheap, high-quality touchscreens from platforms like AliExpress but lacked clear documentation. The "story" of its register map is one of community reverse-engineering and shared discovery: gt911 register map
The Checksum Mystery: One of the most famous hurdles is that the configuration registers (starting at 0x8047) aren't just values you write; they require a specific checksum calculation at the end of the block. If your math is off by even one bit, the chip simply ignores the entire configuration.
The Volatile Reset: Beginners often share the frustrating story of writing a perfect configuration only to have it disappear. The GT911 register map has a quirk where some configuration writes are temporary unless you trigger a specific reset sequence using the RESET and INT pins to "bake" the settings in.
Interrupt vs. Polling: A common community "ghost story" involves the INT pin. Developers frequently report that while they can read touch data through polling, getting the interrupt register (0x814E) to fire correctly is notoriously finicky, often depending on the voltage levels of the VDDIO. Key Landmarks in the Map
If you are currently looking into the map, these are the "characters" you'll encounter most often:
0x8040 (Command Register): The brain. This is where you tell the chip to sleep, wake up, or enter "HotKnot" mode.
0x8140 (Touch Status): The gatekeeper. You must read this first to see if a touch is even happening before you waste time reading coordinates.
0x814E to 0x8150: The prize. These hold the X and Y coordinates for the first touch point. There are enough registers here to track up to five fingers simultaneously.
For a deep dive into the technical specifics, you can find the official programming guide on Orient Display or explore the community-maintained drivers on GitHub's Goodix driver repository.
Are you trying to calibrate the screen resolution or just trying to get the first touch coordinates to show up? GT911 Programming Guide - Orient Display Today, the GT911 register map is almost fully
Understanding the GT911 Register Map: A Comprehensive Guide
The GT911 is a popular capacitive touch screen controller chip used in various electronic devices, including smartphones, tablets, and laptops. To effectively communicate with the GT911 chip, it's essential to understand its register map. In this blog post, we'll dive into the details of the GT911 register map, exploring its structure, functions, and applications.
Introduction to GT911
The GT911 is a highly integrated touch screen controller chip developed by GTCOM (Guangdong GTCOM Technology Co., Ltd.). It's designed to detect touch events on capacitive touch screens, providing a robust and reliable user interface. The GT911 supports various interfaces, including I2C, SPI, and USB, making it a versatile solution for a wide range of applications.
GT911 Register Map Overview
The GT911 register map is a set of memory-mapped registers that store configuration data, control the chip's behavior, and report touch events. The register map is divided into several sections, each serving a specific purpose:
GT911 Register Map Structure
The GT911 register map consists of 256 registers, each 8 bits wide. The registers are organized into several sections, with each section having a specific function. Here's a breakdown of the GT911 register map:
| Register Address | Section | Description | | --- | --- | --- | | 0x00-0x0F | Configuration | Touch sensitivity, debounce time, and gesture recognition settings | | 0x10-0x1F | Control | Power management, interrupt handling, and communication interface settings | | 0x20-0x3F | Status | Touch event detection, gesture recognition, and error flags | | 0x40-0x5F | Data | Touch coordinates, pressure, and gesture information | | 0x60-0xFF | Reserved | Reserved for future use or proprietary functions | GT911 Register Map Structure The GT911 register map
Key Registers and Functions
Here are some key registers and their functions:
Applications and Use Cases
Understanding the GT911 register map is essential for developing applications that utilize the chip's features. Here are some use cases:
Conclusion
In conclusion, the GT911 register map is a critical component of the GT911 touch screen controller chip. Understanding its structure, functions, and applications is essential for developing efficient and reliable touch screen interfaces. This blog post provides a comprehensive guide to the GT911 register map, covering its overview, structure, key registers, and use cases. Whether you're a developer, engineer, or simply interested in touch screen technology, this guide should provide valuable insights into the GT911 register map.
If you read register 0x8000 and always get 0x00, your I²C is working, but the GT911 is not initialized. Ensure you performed the hardware reset sequence correctly. Many libraries forget to pull INT low before reset.
Your X and Y are swapped or mirrored. The GT911 reports physical panel coordinates, not LCD coordinates. If you rotated your LCD via software, you must either: