ATQT600 Atmel, ATQT600 Datasheet - Page 105

• 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

The GCC example projects for QMatrix does not
compile
(QT_DELAY_CYCLES) above a value of 5
because of the preprocessor expansions.
Compiling QT600 project files throws
unused variable warning.
When using IAR workbench for ATSAM to
integrate the touch libraries, the linker
would generate a warning indicating:
Warning[Lp005]: placement includes a mix
of sections with content (example "ro data
section .data_init in xfiles.o(dl7M_tl_if.a)")
and sections without content (example "rw
data section .data in xfiles.o(dl7M_tl_if.a)")
Warning[Lp006]: placement includes a mix
of writable sections (example "rw data
section .data in xfiles.o(dl7M_tl_if.a)") and
non-writable sections
section .data_init in xfiles.o(dl7M_tl_if.a)")
5.11 Checklist
This section lists troubleshooting tips and common configuration tips.
Symptom
Sensors do not go into detect or
have unknown results
Signal values report arbitrary
values
Waveforms of charging /
discharging of channels do not
show up properly in oscilloscopes
When using the example
applications, the debug values for
some of the channels does not
display appropriate values
the
(example "ro data
delay
Cause
Multiplexing pins
used by QTouch
libraries in your
design
Stray capacitance
JTAG ICE connected
to the board
JTAG Pins are
enabled in the target.
cycles
This is because
we link the
library in RW
data section.
Action
Check the Pins used for QTouch or
QMatrix acquisition methods do not
overlap with the applications usage
of the ports
Check the sensor design and
minimize stray capacitance
interference in your design
Try disconnecting the JTAG ICE
completely from the kit
JTAG Pins are explicitly needs to
be disabled in the main.c file
/* disable JTAG pins
Recommended to remove UL from
the preprocessor constants and in
the chain of macros used for
QT_DELAY_CYCLES. Valid for
QT_DELAY_CYCLES = 5,10,25,50.
These variables are available in
the debug protocol for future use.
MCUCR |= (1u << JTD);
MCUCR |= (1u << JTD)
*/
105