View TM4300_4868507.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

? features ? complete touchscreen module : C projected c apacitive multi touch controller C 4.3in lcd C 4 capacitive navigation keys C 200 byte s non - volatile serial eeprom ? touch: C atmel maxtouch mxt224e touch controller C support s up to 10 touches ? display: C shelly sca04310 - bfn - lnn (a407) 4.3in lcd C 480x272 resolution C 20 ms response time C white led backlight ? navigation keys: C atmel at42qt1070 ? cover panel: C 1. 2 mm soda lime glass C optional 0.7mm gorilla glass ? pda TM4300: 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5
? 2 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 contents 1 module overview 4 1.1 pcb connections 4 1.2 host conne ctor 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 C arm ek configuration 9 2.1 introduction 9 2.2 understanding unfamiliar concepts 10 2.3 lcd panel 10 2.4 maxtouch 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 star ted - 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 in stalling the os image 14 3.2.3 using the touch module 14 3.2.4 using the touch module 14 4 sp ecifications 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 i2c - compatible bus specifications 17 4.6 power consumption 17 4.7 part n umber 17 5 i2c basics (i2c - compatible operation) 18 5.1 interface bus 18
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 5.2 transferring data bits 18 5.3 st art and stop conditions 18 5.4 address byte format 19 5.5 data byte format 19 5.6 combinin g address and data bytes into a transmission 20 6 revision history 21 7 notes 22
? 4 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 1 module overview 1.1 pcb connect ion s 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 i input only od open drain output o output only, push - pull p ground or power a t m e l m x t 2 2 4 e d s 2 4 b 3 3 j1 j2 j6 j3 j4 touch sensor flex p i n 1 h o s t pin 1 debug p i n 1 display flex p i n 1 p i n 1 h o s t
pda TM4300 : 4.3in pcap touch modul e C 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. p in type description mxt lcd qt ee p in type description mxt lcd qt ee 1 - n/c 16 i g4 ? 2 p gnd ? 17 p gnd 3 - n/c 18 i b0 ? 4 p gnd 19 i b1 ? 5 o ~ mxt_ chg ? 20 i b2 ? 6 o ~ qt_ chg ? 21 i b3 ? 7 i i 2 c scl ? ? 22 i b4 ? 8 i/o i 2 c sda ? ? 23 i b5 ? 9 p gnd 24 i b6 ? 10 i g7 ? 25 i b7 ? 11 p gnd 26 i g0 ? 12 i g5 ? 27 i g1 ? 13 p gnd 28 i g2 ? 14 i g6 ? 29 i g3 ? 15 p gnd 30 p gnd 1.3 debug connector j2 c onnector j2 carries signals used to debug the maxtouch touch controller and qtouch button controller. p in type description mxt qt p in type description mxt qt 1 p +5vdc 6 i/o i 2 c s cl ? ? 2 o ~qt_ chg ? 7 - n/c 3 o ~ mxt _ chg ? 8 p gnd 4 - n/c 9 o dbg data ? 5 i i 2 c s da ? ? 10 o dbg clk ?
? 6 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 1.4 touch sensor flex connector j3 c onnector j3 connects to the touch sensor flex and carries signals used by the maxtouch controller to detect input on the touch sensor . p in type description p in type description 1 p gnd 26 i/o x9 (duplicate) 2 p gnd 27 i/o x10 3 i/o y10 28 i/o x11 4 i/o y9 29 i/o x12 5 i/o y8 30 i/o x13 6 i/o y7 31 i/o x14 7 i/o y6 32 i/o x15 8 i/o y5 33 i/o x16 9 i/o y4 34 i/o x17 10 i/o y3 35 i/o x18 11 i/o y2 36 p gnd 12 i/o y1 37 p gnd 13 i/o y0 38 i/o y0 14 p gnd 39 i/o y1 15 p gnd 40 i/o y2 16 i/o x0 41 i/o y3 17 i/o x1 42 i/o y4 18 i/o x2 43 i/o y5 19 i/o x3 44 i/o y6 20 i/o x4 45 i/o y7 21 i/o x5 46 i/o y8 22 i/o x6 47 i/o y9 23 i/o x7 48 i/o y10 24 i/o x8 49 p gnd 25 i/o x9 50 p gnd
pda TM4300 : 4.3in pcap touch modul e C 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. p in type description mxt lcd qt ee p in type description mxt lcd qt ee 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 i r0 ? 25 - n/c 6 i r1 ? 26 - n/c 7 i r2 ? 27 - n/c 8 i r3 ? 28 i/o one - wire interface ? 9 i r4 ? 29 p gnd 10 i r5 ? 30 p gnd 11 i r6 ? 31 - n/c 12 i r7 ? 32 - n/c 13 p gnd 33 - n/c 14 p gnd 34 - n/c 15 i disp (display enable) ? 35 - n/c 16 i backlight pwm ? 36 o module presence detect 17 i vsync ? 37 - n/c 18 i hsync ? 38 - n/c 19 i de ? 39 p gnd 20 i pclk ? 40 p gnd
? 8 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 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. p in type description p in type description 1 p led - 21 o b0 2 p led+ 22 o b1 3 p gnd 23 o b2 4 p +3.3vdc 24 o b3 5 o r0 25 o b4 6 o r1 26 o b5 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 g0 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
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 2 overview of the 4.3in pcap touch modul e C arm ek configuration 2.1 introduction the 4.3in pcap touch modul e C arm ek configuration is a touchscreen module offering best - in - class pr ojected capacitance multi - touch functionality combined with a 4.3in lcd panel . the module is configured for development and evaluation with several atmel arm - based ek solutions as well as development and integration with a custom host system . for convenience, this module features host i nterface 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. figure 2 - functional block diagram host t o u c h s e n s o r l c d p a n e l pda 4.3in pcap touch module - arm ek configuration qt1070 nav keys mxt224e ds2433 capacitive button controller capacitive touchscreen controller serial eeprom pcb j1 j4 j3 j6
? 10 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 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 understa nding of each sub - system. ? for a basic overview of i 2 c communication, refer to section 5 of this document ? shelly sca04310 - bfn - lnn (a407) ( www.shellyinc.com ) ? atmel maxtouch mxt224e datasheet ( www.atmel.com ) ? atmel qtouch qt1070 datasheet ( www.atmel.com ) ? maxim ds24b33 datasheet ( www.maximintegrated.com ) in addition, when developing or evaluating with the atmel arm - based eks, it is recommended that the user visit www.at91.com which contains a broad range of resources for the eks 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 touchs creen 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) w hen new touch data is available. data communication with the maxtouch controller is performed over a shared i 2 c interface ( connector j1 - 7 scl and j1 - 8 sda). the i 2 c address of the to uch 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 C thus the i 2 c address is set to 0x4a by default . n ote: pull - up resistors for the i 2 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 2 c address selection a t m e l m x t 2 2 4 e j1 j3
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 2 c address selection r5 r8 i 2 c address 0 dnp 0x4a dnp 0 0x4b note: 0x4a i s the default i 2 c address 2.4.1 maxtouch controller interface 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 s ensor 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 ch anges 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 2.4.1.1 atmel software framework the atmel sof tware 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 pro tocol is common and can be applied to this module. 2.4.1.2 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.github.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 interr upt signal ( connector j1 - 6 ~chg) when a touch event has occurred. data communication with the qt1070 controller is performed over a shared i 2 c interface ( connector j1 - 7 scl and j1 - 8 sda). the i 2 c address of the bu tton controller is 0x1b and can not be changed. note: pull - up resistors for the i 2 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 q touch controller interface details of the q touch communication protocol are beyond the scope of this document. t he user is encouraged to review the qt1070 datasheet ( www.atmel.com ). 2.6 serial eep rom 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
? 12 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 subsystem on the touch module and can be freely used by the host system for any purpose. for example, atmel arm - based eks 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 communicate s via a one - wire interface ( connector j1 - 28 ). refer to the ds24b33 datasheet ( www.maximintegrated.com ) for details.
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 3 getting started - atmel arm - based ek this module was desig ned to install on a variety of atmel arm - based eks. 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 mo dule o n 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 C connecting the module 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 a tmel 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 .
? 14 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 1. 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. a fter 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 i mage from http://www.pdaatl.com/modules/4.3in/sam9x35_android.zip and unzip to a working folder. follow t he 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 en able 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 - === successfu l !!! 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 C initially the atmel logo, followed by the android start screen, finally displaying the androi d home screen. when running this android os image, the navigation keys function as follows: table 3 - 1 - navigation key function (android) key navigation function k1 back k2 menu k3 home k4 power / sleep 3.2.4 using the touch module for effective evaluation of the module C the touch sensor and the l cd panel in particular C 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
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 4 spec ifications for complete specifications, refer to the datash eet s 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 . figure 5 - sensor only dimensions sensor (p/n: 21 - 00002 - a0) may be purchased individually. minimum order quantities apply. contact pda for details. 99.2 mm (fpc max width) 25.5 mm (fpc min width) 3 0 . 9 5 m m glass profile 124.46mm x 83.82mm r6mm in corners 108.9 mm (sensor pet outline) 6 8 . 9 2 m m ( s e n s o r p e t o u t l i n e ) 6.53 mm (viewable to sensor pet edge) 3 . 7 4 2 m m ( v i e w a b l e t o s e n s o r p e t e d g e ) 5 4 . 6 6 m m ( v i e w a b l e ) 95.84 mm (viewable) 1.2 mm (cover panel) 0.635 mm or 0.510 (sensor) two variants available 0.076 mm (fpc) viewed from user side u s e r s i d e pcb contacts face down l c d s i d e p i n 1 p i n 5 0
? 16 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 figure 6 C module dimensions 4.2 absolute maximum specif ications parameter value operating temp 0 o c to + 70 o c storage temp - 40 o c to + 85 o 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 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. a t m e l m x t 2 2 4 e d s 2 4 b 3 3 4 3 . 2 m m glass profile 124.46mm x 83.82mm r6mm in corners 119.5 mm (frame length) 17.08 mm (cover panel rear surface to mounting boss) 8 0 . 2 6 m m ( f r a m e w i d t h ) 5.08 mm (pcb component clearance) 6 3 . 5 m m ( p c b w i d t h ) 7.62 mm 1 0 . 1 6 m m 134.62 mm (pcb length)
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 4.3 recommended operating conditions parameter value vin 5.0v 5 percent supply ripple + noise 2 0 mv 4.4 dc specifications v in = 5.0v, vdd=3.3vdc ta = recommended range, unless otherwise noted parameter description min typ max units notes v il low input logic level - 0.5 C 0. 3 vdd v 1.8 v ? 18 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 5 i2c basics (i2c - compatible operation) 5.1 interface bus the device communicates with the host over an i 2 c - compatible bus, in accordance with version 2.1 of the i 2 c specification. the following sections give an overview of the bus; more detailed information is available from www.i2c - bus.org. devices are conn ected to the i 2 c - compatible bus as shown in figure 7 b oth bus lines are connected to vdd via pull - up resistors. the bus drivers of all i 2 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 2 c - compatible in terface bus 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 5.3 start and stop conditions 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 sig naled by changing the level of the sda line when the scl line is high. sda scl device 1 device 2 device 3 device n vdd r1 r2 sda scl data stable data stable data change
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 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 recogniz es 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 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 sda scl start stop sda scl start 1 2 7 8 9 r/w addr lsb ack addr msb sla+r/w 1 2 7 8 9 r/w addr lsb ack addr msb aggregate sda sda from transmitter sda from receiver scl from master stop or next data byte data byte
? 20 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 5.6 combining address and data bytes into a transmission a transmissi on 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 da ta bytes can be transmitted between the sla+r or sla+w and the stop. figure 12 . byte transmission ack 1 2 7 8 9 data byte sda scl start data lsb data msb r/w 1 2 7 8 9 sla+r/w addr lsb addr msb ack stop
pda TM4300 : 4.3in pcap touch modul e C arm ek configuration ? 6 revision history revision no. history rev 1209 - 0 - 1 C sept 20 12 initial draft (unreleased) rev 1209 - 1 - 2 C sept 2012 preliminary draft ( limited release ) rev 12 10 - 2 - 3 C oct 2012 remove references to gesture support C not available on this module. rev 12 10 - 3 - 4 C oct 19, 2012 correct swapped i 2 c clock and data signals in debug connector j2 pinout table. rev 1211 - 4 - 5 C nov 21, 2012 add notes to figure 5 regarding sensor orientation and pin 1 location . add notes to figure 1 identifying connectors and pin 1 location s.
? 22 pda TM4300 : 4.3in pcap touch modul e C arm ek configuration 12 1 1 - 4 - 5 7 notes email: sales@pdaatl.com precision design associates, inc. 736 johnson ferry rd, suite c - 270 marietta, ga 30068 usa tel: (770) - 971 - 4490 url: http://www.pdaatl.com ? 201 2 precision design associates . all rights reserved. atmel ? , atmel logo and combinations thereof, maxtouch ? , q touch ? , and others are registered trademarks of atmel corporation or its subsidiaries. other terms and product names may be registered trademarks or trademarks of others.

▲Up To Search▲

Price & Availability of TM4300

	To Download TM4300 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .