Datasheet - Precision Design Associates
Contents
1. 1 P GND 2 P GND 3 VO Y10 4 V O Y9 5 O Y8 6 VO Y7 7 O Y6 8 VO Y5 9 VO Y4 10 O Y3 11 O Y2 12 O Y1 13 O YO 14 B GND 15 P GND 16 O XO 17 VO X1 18 VO X2 19 V O X3 20 V O X4 21 VO X5 22 VO X6 23 VO X7 24 O X8 25 O X9 26 1O X9 Duplicate 27 VO X10 28 VO X11 29 VO X12 30 VO X13 31 VO X14 32 VO X15 33 VO X16 34 VO X17 35 O X18 36 P GND 37 P GND 38 O YO 39 VO Y1 40 VO Y2 41 VO Y3 42 VO Y4 43 VO Y5 44 O Y6 45 VO Y7 46 O Y8 47 O Y9 48 O Y10 49 P GND 50 P GND 6 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 BSS TM4300 4 3in PCAP Touch Module ARM EK Configuration 1 5 Host Connector J4 Connector J4 connects to the host and carries signals between the host and 1 the LCD Panel and 2 serial EEPROM 1 P 5Vdc 21 P GND 2 P GND 22 P GND 3 P 5Vdc 23 N C 4 P GND 24 N C 5 RO 25 N C 6 R1 26 N C 7 R2 27 N C 8 l R3 28 I O One Wire Interface 9 R4 29 P GND 10 R5 30 P GND 11 R6 31 N C 12 R7 32 N C 13 P GND 33 s N C 14 P GND 34 N C 15 I DISP Display Enable 352. E a ee ae a aad N The TM4300 is replaced by the TM4301 P D 21 7 Notes S N Precision Design Associates Inc 736 Johnson Ferry Rd Suite C 270 ga D A Marietta GA 30068 Na INC email sales pdaatl com tel 770 971 4490 url http Avww pdaatl com 2014 Precision Design Associates All rights reserved Atmel Atmel logo and combinations thereof maXTouch QTouch and others are registered trademarks of Atmel Corporation or its subsidiaries Other terms and product names may be registered trademarks or trademarks of others 22 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6
3. K1 lt a Back K2 Menu K3 Home K4 Power Sleep 3 2 4 Using the Touch Module For effective evaluation of the module the touch sensor and the LCD panel in particular the user is encouraged to try the following Android apps available from Google Play TouchTest by Moonblink Dotty by Gerry Steele Multitouch Visible Test by Battery Powered Games Screen Test by Amberfog eee es ee ee en ee ee ee a 27 14 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 ee TM4300 4 3in PCAP Touch Module ARM EK Configuration 4 Specifications For complete specifications refer to the datasheets listed in section 2 2 for the various sub system components outlined in sections 2 3 through 2 6 4 1 Mechanical Specifications Drawings and CAD models available upon request Glass Profile 124 46mm x 83 82mm 108 9 mm gt R6mm in corners Sensor PET Outline Zz 6 53 mm Viewable to Sensor PET Edge N ij gt 1 2 mm Cover Panel a A x lt s L gt tl lt 0 635 mm or 0 510 Sensor S o two variants available zs g 53 3 a o3 2 Viewed from 3 A 9 user side 2 D 3 2 g3 sie amp v v D pA m 2 fa A m 3 J Q Y v PEPE EEE EPEC en Y 0 076 mm FPC ww G6 0 lni wn face down 25 5 mm IS Ziq FPC Min Width Z 99 2 mm I FPC Max Width Figure 5 Sensor Only Dimensions Sensor P N 21 000
4. The TM4300 has been replaced by the TM4301 STN Features p D e Complete Touchscreen Module Projected Capacitive Multi Touch Controller N C 4 3in TFT LCD 4 Capacitive Navigation Keys 200 bytes non volatile serial EEPROM iij PDA TM4300 e Touch Atmel maXTouch mXT224E Touch Controller Supports up to 10 touches 4 3in PCAP i Touch Module 480x272 resolution 20 ms response time ARM EK White LED backlight Navigation Keys Configuration Atmel AT42QT1070 Cover Panel 1 2mm Soda Lime Glass Optional 0 7mm Gorilla Glass Bere ar Friday March 23 Charged 1404 5 6 TN P D Nee INC Contents 1 Module Overview 4 1 1 PCB Connections 4 1 2 Host Connector J1 5 1 3 Debug Connector J2 5 1 4 Touch Sensor Flex Connector J3 6 1 5 Host Connector J4 7 1 6 Display Flex Connector J6 8 2 Overview of the 4 3in PCAP Touch Module ARM EK Configuration 9 2 1 Introduction 9 2 2 Understanding Unfamiliar Concepts 10 2 3 LCD Panel 10 2 4 maxXTouch Capacitive Touchscreen Controller 10 2 4 1 maXTouch Controller Interface 11 2 5 QTouch Capacitive Button Controller 11 2 5 1 QTouch Controller Interface 11 2 6 Serial EEPROM 11 3 Getting Started Atmel ARM based EK 13 3 1 Hardware Connection 13 3 2 Loading an OS Image 13 3 2 1 Installing SAM BA 13 3 2 2 Installing the OS Image 14 3 2 3 Using the Touch Module 14 3 2 4 Using the Touch Module 14 4 Specifi
5. A 5 6 Combining Address and Data Bytes into a Transmission A transmission consists of a START condition an SLA R or SLA W one or more data bytes and a STOP condition The wired ANDing of the SCL line is used to implement handshaking between the host and the device The device extends the SCL low period by pulling the SCL line low whenever it needs extra time for processing between the data transmissions Figure 12 shows a typical data transmission Note that several data bytes can be transmitted between the SLA R or SLA W and the STOP Figure 12 Byte Transmission Addr Addr Data Data MSB LSB RW ACK MSB LSB ACK 7 ve 1 2 7 2 7 8 9 START SLA R W Data Byte STOP ae eee eee eee na 20 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 SSS TM4300 4 3in PCAP Touch Module ARM EK Configuration 6 Revision History Revision No History Rev 1209 0 1 Sept 2012 Initial Draft unreleased Rev 1209 1 2 Sept 2012 Preliminary Draft limited release Rev 1210 2 3 Oct 2012 Remove references to gesture support not available on this module Rev 1210 3 4 Oct 19 2012 Correct swapped I C clock and data signals in Debug Connector J2 pinout table Add notes to Figure 5 regarding sensor orientation and pin 1 location ROU Sees NOV AI AOE Add notes to Figure 1 identifying connectors and pin 1 locations Rev 1404 5 6 Apr 4 2014 Add note concerning TM4300 replaced by TM4301
6. Conditions 5 4 Address Byte Format All address bytes are 9 bits long They consist of 7 address bits one READ WRITE control bit and an acknowledge bit If the READ WRITE bit is set a read operation is performed Otherwise a write operation is performed An address byte consisting of a slave address and a READ or a WRITE bit is called SLA R or SLA W respectively When the device recognizes that it is being addressed it acknowledges by pulling SDA low in the ninth SCL ACK cycle The most significant bit of the address byte is transmitted first Figure 10 Address Byte Format i Addr MSB Addr LSB R W ACK l START 5 5 Data Byte Format All data bytes are 9 bits long consisting of 8 data bits and an acknowledge bit During a data transfer the host generates the clock and the START and STOP conditions The slave device is responsible for acknowledging the reception An acknowledge ACK is signaled by the slave device pulling the SDA line low during the ninth SCL cycle If the slave device leaves the SDA line high a NACK is signaled Figure 11 Data Byte Format Addr MSB Addr LSB R W ACK Aggregate i SDA I I SDAfrom Transmitter _ Oe I SDAfrom Receiver__ i SCL from Master 1 2 7 8 9 I l l F l l l l r l l l l TE l l l l l L l l l STOP or SLA R W Data Byte Next Data Byte ES E N The TM4300 is replaced by the TM4301 P D 19 Wu INC TN P D Wu INC
7. only push pull P Ground or power Eee ee E 4 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 BRST TM4300 4 3in PCAP Touch Module ARM EK Configuration 1 2 Host Connector J1 Connector J1 connects to the host and carries signals between the host and 1 the MaXTouch Touch Controller 2 the QTouch Button Controller and 3 LCD Panel Description Description NC 2 P GND 3 NC 4 P GND 5 O MXT_CHG 6 O QT_CHG 7 C SCL 8 1O PCSDA 9 P GND 10 G7 11 P GND 12 G5 13 P GND 14 G6 15 P GND 1 3 Debug Connector J2 Connector J2 carries signals used to debug the MaXTouch Touch Controller and QTouch Button Controller 1 P 5Vdc 6 VO PCSCL o o 2 O QT_CHG 7 NC 3 O MXT_CHG 8 P GND 4 NC 9 O DBGDATA 5 C SDA o o 10 O DBG CLK a E E _ The TM4300 is replaced by the TM4301 P D 5 PD we IN 1 4 Touch Sensor Flex Connector J3 C Connector J3 connects to the touch sensor flex and carries signals used by the maXTouch controller to detect input on the touch sensor
8. org Devices are connected to the C compatible bus as shown in Figure 7 both bus lines are connected to Vdd via pull up resistors The bus drivers of all I C compatible devices must be open drain type This implements a wired AND function that allows any and all devices to drive the bus one at a time A low level on the bus is generated when a device outputs a zero Figure 7 I C compatible Interface Bus Vdd SDA SCL 5 2 Transferring Data Bits Each data bit transferred on the bus is accompanied by a pulse on the clock line The level of the data line must be stable when the clock line is high the only exception to this rule is for generating START and STOP conditions Figure 8 Data Transfer SDA f Ne l l l l l I I l I l I 1 I I i I l j l SCL I 1 I I I I Data Stable Data Stable Data Change 5 3 START and STOP Conditions 18 The host initiates and terminates a data transmission The transmission is initiated when the host issues a START condition on the bus and is terminated when the host issues a STOP condition Between the START and STOP conditions the bus is considered busy As shown in Figure 9 START and STOP conditions are signaled by changing the level of the SDA line when the SCL line is high PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 SSS TM4300 4 3in PCAP Touch Module ARM EK Configuration Figure 9 START and STOP
9. 02 A0 may be purchased individually Minimum order quantities apply Contact PDA for details Ee ee ee Saeed AAN The TM4300 is replaced by the TM4301 P D 15 Glass Profile 124 46mm x 83 82mm R6mm in corners z si i Tg E pag E ce El 2 gS Els ire Sion gis SS a i E A 4 L 17 08 mm le Cover Panel rear surface 134 62 mm 4 ij PCB Length to Mounting Boss 5 08 mm PCB Component Clearance Mir DT 119 5 mm Frame Length Figure 6 Module Dimensions 4 2 Absolute Maximum Specifications Parameter Value Operating temp 0 C to 70 C Storage temp 40 C to 85 C Vdd 0 5 to 6V Max continuous pin current any control or drive pin 40 mA Voltage forced onto any pin 0 5V to Vdd 0 5 Volts CAUTION Stresses beyond those listed under Absolute Maximum Specifications may cause permanent A damage to the device This is a stress rating only and functional operation of the device at these or other conditions beyond those indicated in the operational sections of this specification are not implied Exposure to absolute maximum specification conditions for extended periods may affect device reliability 16 PDA TM4300 4 3in
10. N C 16 l Backlight PWM 36 O Module Presence Detect 17 VSYNC 37 N C 18 HSYNC 38 N C 19 DE 39 P GND 20 PCLK 40 P GND Sa ee ee ee ee aS rd N The TM4300 is replaced by the TM4301 PpP D 7 P D JC 1 6 Display Flex Connector J6 Connector J6 connects to the LCD panel flex and carries signals between the host and the LCD Panel Note J6 is located on the back side of the PCB 1 P LED 21 O BO 2 P LED 22 O Bi 3 P GND 23 O B2 4 P 3 3Vdc 24 O B38 5 O RO 25 O B4 6 O Ri 26 O BS 7 O R2 27 O B6 8 O R3 28 O B7 9 O R4 29 P GND 10 O R5 30 O PCLK 11 O R6 31 O DISP 12 O R7 32 O HSYNC 13 O GO 33 O VSYNC 14 O G1 34 O DE 15 O G2 35 N C 16 O G3 36 P GND 17 O G4 37 N C 18 O G5 38 N C 19 O G6 39 N C 20 O G7 40 N C ae ee ee E 8 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 TM4300 4 3in PCAP Touch Module ARM EK Configuration 2 Overview of the 4 3in PCAP Touch Module ARM EK Configuration 2 1 Introduction The 4 3in PCAP Touch Module ARM EK Configuration is a touchscreen module offering best in class projected capacitance multi touch functionality combined with a 4 3in LCD panel The module is configured for development and evaluati
11. PCAP Touch Module ARM EK Configuration 1404 5 6 SRST TM4300 4 3in PCAP Touch Module ARM EK Configuration 4 3 Recommended Operating Conditions Parameter Value Vin 5 0V 5 percent Supply ripple noise 20 mV 4 4 DC Specifications Vin 5 0V Vdd 3 3Vdc Ta recommended range unless otherwise noted Parameter Description Min Typ Max Units Notes Vit Low input logic level 0 5 0 3 Vdd V 1 8V lt Vdd lt 3 3V Va High input logic level 0 7 Vdd Vdd 0 5 V 1 8V lt Vdd lt 3 3V VoL Low output voltage 0 2Vdd V VoH High output voltage 0 8Vdd V li Input leakage current 1 uA 4 5 12C compatible Bus Specifications Parameter Operation Address 0x4A or 0x4B Maximum bus speed SCL 400 kHz 12C Specification Version 2 1 4 6 Power Consumption Vdd V Mode Idd mA 3 3Vde mXT224E in Free Run LCD backlight on 200 maximum intensity 4 7 Part Number 90 00002 A0 4 3 Touchscreen Module For Atmel ARM EK S aed The TM4300 is replaced by the TM4301 Vee INC T 5 5 1 I2C Basics I2C compatible Operation Interface Bus The device communicates with the host over an C compatible bus in accordance with version 2 1 of the I C specification The following sections give an overview of the bus more detailed information is available from www i2C bus
12. 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 when overwriting the pre programmed EEPROM contents As noted above certain builds of Linux or Android targeted for the Atmel ARM based EKs 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 Connector J1 28 Refer to the DS24B33 Datasheet www maximintegrated com for details PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 TM4300 4 3in PCAP Touch Module ARM EK Configuration 3 Getting Started Atmel ARM based EK This module was designed to install on a variety of Atmel ARM based EK s This provides perhaps the fastest way to evaluate the performance of the touchscreen and display using a familiar full featured OS The following sections will outline the process of installing the module on an Atmel AT91SAM9X35 EK running Android 3 1 Hardware Connection The module interfaces with the EK board via the two large dual row headers J1 and J4 Connectors J1 and J4 on the module PCB connect with J21 and J22 respectively on the EK board AT91SAM9X5 EK in this example Disconnect power and USB from the EK board and remove any other display module before installing the touch module as shown below in Figure 4 Figure 4 Connecting the mo
13. cations 15 4 1 Mechanical Specifications 15 4 2 Absolute Maximum Specifications 16 4 3 Recommended Operating Conditions 17 4 4 DC Specifications 17 4 5 12C compatible Bus Specifications 17 4 6 Power Consumption 17 4 7 Part Number 17 5 12C Basics l2C compatible Operation 18 5 1 Interface Bus 18 eee E R 2 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 has TM4300 4 3in PCAP Touch Module ARM EK Configuration 5 2 Transferring Data Bits 5 3 START and STOP Conditions 5 4 Address Byte Format 5 5 Data Byte Format 5 6 Combining Address and Data Bytes into a Transmission 6 Revision History 7 Notes E a ee ae a aad The TM4300 is replaced by the TM4301 18 18 19 19 20 21 22 TN P D Wu INC A 1 Module Overview 1 1 PCB Connections Touch Sensor Flex ON aed hg c PDA Inc 2012 1029 Rev A3 www pdaatl com Figure 1 PCB Connectors NOTE Connector J6 is on the bottom side of the PCB The following notations are used for pin descriptions MXT maXTouch touchscreen QT QTouch Button Controller EE Serial EEPROM LCD LCD Panel Input only OD Open drain output O Output
14. d zip and unzip to a working folder Follow the procedure below to load the OS image onto the EK 1 Remove power from the EK J4 and remove any USB cables from the mini USB connector J19 2 On the Computer Module CM board disable the NAND flash chip select Refer to schematic for the particular CM used For example on the Embest 9X35 CM SW1 1 should be switched OFF to disable NAND flash 3 Connect power to the EK J4 and connect a USB cable from the mini USB connector J19 to the computer 4 On the CM board enable the NAND flash chip select Refer to schematic for the particular CM used For example on the Embest 9X35 CM SW1 1 should be switched ON to enable NAND flash 5 Run the at91SAM9x5 bat file in the folder where the ZIP file was extracted This will execute a script causing SAM BA to download the various OS images to the EK The process can take 1 or 2 minutes 6 When the download process completes check the logfile log file The last line of the log file should read I Successful Now reboot the board 3 2 3 Using the Touch Module Reboot the EK and wait for the OS to startup The display should show several different progress screens initially the Atmel logo followed by the Android start screen finally displaying the Android home screen When running this Android OS image the navigation keys function as follows Table 3 1 Navigation Key Function Android
15. dule to the EK 3 2 Loading an OS Image In order demonstrate the complete functionality of the module an OS image has been prepared that includes support for all of the subsystems 3 2 1 Installing SAM BA Before the OS image can be loaded you must first ensure that the Atmel SAM Boot Assistant SAM BA utility is installed The SAM BA software can be found at http www atmel com atmelsam bain systemprogrammer aspx for both Windows and Linux platforms E M AAN The TM4300 is replaced by the TM4301 P D 13 INC Nee INC SESE ea _ Remove power from the EK J4 and remove any USB cables from the mini USB connector J19 2 Run the installation for the SAM BA utility and following the installation steps until setup is complete 3 On the Computer Module CM board disable the NAND flash chip select Refer to schematic for the particular CM used For example on the Embest 9X35 CM SW1 1 should be switched OFF to disable NAND flash 4 Connect power to the EK J4 and connect a USB cable from the mini USB connector J19 to the computer 5 After the USB device is recognized a driver may be required Point to the drv subfolder where SAM BA was installed For example C Program Files Atmel Corporation SAM BA drv 3 2 2 Installing the OS Image Once the SAM BA utility has been installed the OS image can be loaded onto the EK Download the Android OS image from hittp Awww pdaatl com modules 4 3in sam9x35_androi
16. ins a broad range of resources for the EK s and the ARM devices they feature 2 3 LCD Panel The module provides the host with a direct connection from the host Connector J1 and J4 to the LCD panel interface Connector J6 Aside from generating supply voltages for the LED backlight and providing backlight control to the host no display panel control is performed by the module 2 4 maXTouch Capacitive Touchscreen Controller The module touch screen interface is based on the Atmel maXTouch mXT224E Touch Controller The touch controller scans the touch sensor and will signal the host with an active low interrupt signal Connector J1 5 CHG when new touch data is available Data communication with the maXTouch controller is performed over a shared I C interface Connector J1 7 SCL and J1 8 SDA The I C address of the touch controller can be configured by populating R5 or R8 shown below in Figure 3 according to Table 2 1 below The PCB ships with R5 populated thus the I C address is set to 0x4A by default NOTE Pull up resistors for the I C SCL and SDA lines are located at R3 and R2 respectively A pull up resistor for the maXTouch CHG interrupt signal is located at R4 Figure 3 Touch Controller I C Address Selection 10 PDA TM4300 4 3in PCAP Touch Module ARM EK Configuration 1404 5 6 LE TM4300 4 3in PCAP Touch Module ARM EK Configuration Table 2 1 Touch Con
17. on with several Atmel ARM based EK solutions as well as development and integration with a custom host system For convenience this module features host interface connectors J1 and J4 positioned for direct installation on Atmel ARM based EK boards As shown in Figure 2 below the module provides host access to several sub system components to maximize effective integration PDA 4 3in PCAP Touch Module ARM EK Configuration J3 YTS QT1070 Capacitive Button Controller mXT224E Capacitive Touchscreen ie Controller HOST 4 fo QO a n D DS n O Q j ued A07 Serial EEPROM Figure 2 Functional Block Diagram E T AAN The TM4300 is replaced by the TM4301 P D 9 P D _ Ne Xx 2 2 Understanding Unfamiliar Concepts Throughout this document the functionality of the module sub system will be outlined and summarized However the user is encouraged to refer to the resources and documents below in order to gain a more thorough understanding of each sub system For a basic overview of I C communication refer to Section 5 of this document e Atmel maXTouch mXT224E Datasheet www atmel com e Atmel QTouch QT1070 Datasheet www atmel com e Maxim DS24B33 Datasheet www maximintegrated com In addition when developing or evaluating with the Atmel ARM based Ek s it is recommended that the user visit www at91 com which conta
18. thub com atmel maxtouch linux which provide numerous out of cycle improvements to the mainline Linux Kernel driver 2 5 QTouch Capacitive Button Controller The module 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 Connector J1 6 CHG when a touch event has occurred Data communication with the QT1070 controller is performed over a shared I C interface Connector J1 7 SCL and J1 8 SDA The I C address of the button controller is 0x1B and cannot be changed NOTE Pull up resistors for the I C SCL and SDA lines are located at R3 and R2 respectively A pull up resistor for the QTouch CHG interrupt signal is located at R27 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 E N The TM4300 is replaced by the TM4301 P D 11 WS INC TN Nee INC Ea A 12 subsystem on the touch module and can be freely used by the host system for any purpose For example Atmel ARM
19. troller I C Address Selection 00 DNP Ox4A DNP 00 0x4B Note 0x4A is the default C address 2 4 1 maXTouch Controller Interface A 2 4 1 1 2 4 1 2 Details of the maXTouch communication protocol are beyond the scope of this document However information is provided below to facilitate evaluation and initial development The 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 the following sections Atmel Software Framework The Atmel Software Framework asf atmel com contains examples of code for interfacing with devices in the maXTouch family of touch controllers The capabilities of various maXTouch devices may differ but the basic communication protocol is common and can be applied to this module Linux Kernel Android The Linux Kernel www kernel org has included basic support for maXTouch touch devices since version 2 6 36 The mainline driver has undergone considerable evolution since then In addition Atmel maintains patches www gi
Download Pdf Manuals
Related Search