GOODIX CONFIDENTIAL
Reproduction and/or distribution of this document in whole or in part is strictly prohibited without written consent of GOODIX.
22
the sum.
[0xAD91] Data_Fresh
The host writes data to other addresses before writing 0xAA to 0xAD91; that is to say, the host sets the
Transmit Buffer flushed flag; after GT911 finds the flag, it will check whether the data in the Transmit Buffer
passes the verification. If the data passes the verification, GT911 will switch to Send Mode and start
transmission immediately; if the data does not pass the verification, GT911 will notify the host to handle via
INT.
3.7 Hotknot Receive Buffer
Addr
Access
bit7
bit6
bit5
bit4
bit3
bit2
bit1
bit0
0xAE10
R/W
buffer status
0x AE11
R/W
DataLength valid data length , <129 bytes
0xAE12
R
Data0: the first data byte
0xAE13
R
Data1: the second data byte
…
R
…
0xAE91
R
Data127 : the 128
th
data byte
0xAE92~
0xAE93
R
Crc16Check data CRC16 verification. Please note that it should stay behind
the data, not fixed in this address. big-edian mode
Supplementary description on some registers:
The data in this area is valid only when GT911 operates in Receive Mode, GT911_Status is 0xAA, and
RevStatus is 0x03.
[0xAE10]buffer status
bit7: buffer status as 1 indicates data in Receive Buffer is ready to be read.
[0x AE11]DataLength
Valid data length, < 128 bytes.
[0xAE92~0xAE93]
Crc16Check
Data CRC-CICTT verification, big-edian mode
。
Instruction on check mechanism:
As for data frame whose length is n, the result of CRC check is
：
the check of the n data bytes+length. For
example
：
the data frame length is 112 bytes; the host needs to read 114 bytes ( 112 data bytes+2 bytes CRC16
check) from the address 0xAE12. The host figures out the CRC of “112 data bytes+length”, and compares it with
the CRC at (112). If the two CRCs are the same, the data passes verification; otherwise, verification
fails. Please note that, the calculation of CRC and length is performed in the end of the process, not at the
