
PDA TM7000: 7in PCAP Touch Module
15
Table 2-4 - Touch Controller I2C Address Selection
Note: 0x4C is the default I2C address
2.4.1 maXTouch Controller Interface
Details of the maXTouch communication protocol are beyond the scope of this document. However information is
provided in Section 3.2 below to facilitate evaluation and initial development.
This module is pre-loaded with a configuration already optimized for this touch sensor and panel, so the
developer need only focus on interfacing with the device. When developing the maXTouch controller
interface during evaluation and host development, care should be taken to avoid changing the maXTouch
configuration or committing changes to NV storage on the maXTouch controller.
To get started with host interface development, the user is strongly encouraged to leverage existing code available
from the resources outlined in Sections 3.2.
2.5 QTouch Capacitive Button Controller
The module’s “nav key” interface is based on the Atmel QT1070 7-Channel Capacitive Sensor Driver.
The button controller scans the 4 capacitive nav keys (K1, K2, K3 and K4) and will signal the host with an active
low interrupt signal (~QT_CHG on Connector J4 or J6) when a touch event has occurred. Data communication
with the QT1070 controller is performed over a shared I2C interface (I2C SCL and I2C SDA on J4 or J6). The I2C
address of the button controller is 0x1B and cannot be changed.
NOTE: The TM7000 does not have pull-up resistors on the I2C SCL and SDA lines. A pull-up resistor for
the QTouch ~CHG interrupt signal is located at R16.
2.5.1 QTouch Controller Interface
Details of the QTouch communication protocol are beyond the scope of this document. The user is encouraged
to review the QT1070 Datasheet (www.atmel.com).
2.6 Serial EEPROM
The module includes a DS24B33 Serial EEPROM providing 512 bytes of non-volatile storage. Data
communication with the EEPROM is performed over a One-Wire Interface. The EEPROM is not used by another
subsystem on the touch module and can be freely used by the host system for any purpose. For example, Atmel
ARM-based EK’s running Linux or Android operating systems use the pre-programmed contents of the EEPROM
to identify this module type.
NOTE: The user should take care if choosing to overwrite the pre-programmed EEPROM contents. As
noted above, certain builds of Linux or Android targeted for the Atmel ARM-based EKs use the EEPROM
contents to identify the module and may no longer recognize the module. The user is advised to backup
the EEPROM contents before overwriting.
The serial EEPROM communicates via a one-wire interface (One-wire Interface on J5 or J6). Refer to the
DS24B33 Datasheet (www.maximintegrated.com) for details.