ATQT600 Atmel, ATQT600 Datasheet - Page 51

• Manufacturer Part Number: ATQT600
• Description: KIT EVAL TOUCH FOR QT600
• Manufacturer: Atmel
• Series: QTouch™r

Specifications of ATQT600

• Sensor Type: Touch Screen
• Interface: USB
• Embedded: Yes, Other
• Utilized Ic / Part: ATtiny88, ATmega324PA, ATxmega128A1
• Processor To Be Evaluated: ATtiny88, ATmega324, ATxmega128
• Data Bus Width: 8 bit, 16 bit
• Interface Type: USB
• Maximum Operating Temperature: + 85 C
• Minimum Operating Temperature: - 40 C
• Operating Supply Voltage: 1.6 V to 3.6 V
• Silicon Manufacturer: Atmel
• Kit Application Type: Sensor
• Application Sub Type: Touch Sensor
• Kit Contents: USB Bridge, MCU Cards, Touchpad Cards
• Svhc: No SVHC (15-Dec-2010)
• Mcu Supported Families: ATtiny88,
• Rohs Compliant: Yes
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Voltage - Supply: -
• Sensitivity: -
• Sensing Range: -
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

Given the above requirements for the applications, the first step is to select the right library
variant required.
Step 1: Selecting the right library variant
Referring to the library selection guide, we see that there are a few variants of libraries supported
for ATmega1280. Since the application requires 12 channels and rotor slider support, one has to
select a library variant which supports at least 12 channels or more along with 3 Rotors/Sliders.
Hence we select the 12 channel library variant for GCC complier which supports the required
number of sensors/channels. This works out to be libavr51g1_12qt_k_3rs.a
Step 2: Defining the constants / symbols in the project space
In the host application file (say main.c), define the following constants and symbols
Step 3: Usage of library API’s
Now, you can use the touch API’s to create, initialize and perform touch sensing. Please refer to
the sample applications in section 5.6.11.2 for reference. These sample applications illustrate the
usage of the API’s and the sequence of operation.
Step 4: Adding necessary source files for compilation
The source files needed for compiling your application along with the touch library are
touch_api.h, touch_qt_config.h and qt_asm_tiny_mega.S.
5.6.10.2.2 Example for ATSAM
The example below will explain in detail the steps to follow for library selection.
Criteria
Microcontroller
IDE and compiler tool chain used
Number
application
Rotors and sliders required
Number of Rotors and Sliders required
Number of Channels required for the
application ( should be the sum of all
channels required for all the keys ,rotors
and sliders used in the design )
Charge cycle time required for the design
#define QTOUCH_
#define QT_NUM_CHANNELS
#define SNSK1
#define SNS1
#define SNSK2
#define SNS2
#define QT_DELAY_CYCLES
#define _POWER_OPTIMIZATION_
#define _SNS1_SNSK1_SAME_PORT_
NOTE: The above definitions are available in touch_qt_config.h file. Alternatively, you
can define these in your IDE’s project options or have them defined in a separate header
file. For IAR IDE, all these symbols have to defined for both compiler and assembler
preprocessor defines separately.
of
Keys
required
for
the
Selection
AT91SAM3S
IAR Workbench and GNU compiler
3
Yes
3
12
5 cycles
12
A
A
B
C
1
1
Notes
The
variant of the libraries for
the device selected needs
to be used.
Each
QTouch
channel
Each rotor / slider will
require 3 channels.
3 Keys + ( 3 rotors x 3
channels per rotor/slider )
Assuming the device is
configured with a clock
12 channels
key
GCC
requires
acquisition
compiled
51
1