Board
User's Guide
Literature Number: SLAU318B
July
Contents
Preface ....................................................................................................................................... |
|
||
1 |
|||
|
1.1 |
Overview .................................................................................................................. |
|
|
1.2 |
Kit Contents .............................................................................................................. |
|
|
1.3 |
Revisions ................................................................................................................. |
|
2 |
Installation ......................................................................................................................... |
||
|
2.1 |
Download the Required Software ..................................................................................... |
|
|
2.2 |
Install the Software ...................................................................................................... |
|
|
2.3 |
Install the Hardware ..................................................................................................... |
|
3 |
Getting Started With |
||
|
3.1 |
Getting Started ........................................................................................................... |
|
|
3.2 |
Demo Application, Internal Temperature Measurement ............................................................ |
|
4 |
Develop an Application With the |
||
|
4.1 |
Developing an Application .............................................................................................. |
|
|
4.2 |
Program and Debug the Temperature Measurement Demo Application ........................................ |
|
|
4.3 |
Disconnect Emulator From Target With Jumper J3 ................................................................. |
|
|
4.4 |
Program Connected eZ430 Target Boards ......................................................................... |
|
|
4.5 |
Connecting a Crystal Oscillator ...................................................................................... |
|
|
4.6 |
Connecting a Satellite Board ......................................................................................... |
|
|
4.7 |
Supported Devices ..................................................................................................... |
|
5 |
|||
|
5.1 |
Device Pinout ........................................................................................................... |
|
|
5.2 |
Schematics Emulator .................................................................................................. |
|
|
5.3 |
PCB Layout ............................................................................................................. |
|
|
5.4 |
Bill of Materials (BOM) ................................................................................................ |
|
6 |
Suggested Reading ........................................................................................................... |
||
7 |
Frequently Asked Questions (FAQ) ...................................................................................... |
2 |
Table of Contents |
|
|
|
Copyright ©
|
|
|
|
List of Figures |
|
1 |
||
2 |
Insert Device Into Target Socket.......................................................................................... |
|
3 |
Code Composer Studio™ v4 in Debugging Mode...................................................................... |
|
4 |
||
5 |
Device Pinout .............................................................................................................. |
|
6 |
Schematics, Emulator (1 of 3) ........................................................................................... |
|
7 |
Schematics, Emulator (2 of 3) ........................................................................................... |
|
8 |
Schematics, Target Socket (3 of 3) ..................................................................................... |
|
9 |
Layout, LaunchPad Top Layer........................................................................................... |
|
10 |
Layout, LaunchPad Bottom Layer....................................................................................... |
|
11 |
Layout, LaunchPad Silkscreen .......................................................................................... |
|
|
List of Tables |
|
1 |
Jumper Connection J3 Between Emulator and Target................................................................. |
|
2 |
eZ430 Debugging Interface .............................................................................................. |
|
3 |
Supported Devices ........................................................................................................ |
|
4 |
Bill of Materials............................................................................................................. |
List of Figures |
3 |
|
|
|
Copyright ©
Preface
SLAU318B – July 2010 – Revised March 2012
Read This First
If You Need Assistance
If you have any feedback or questions, support for the MSP430™ devices and the
Related Documentation from Texas Instruments
The primary sources of MSP430 information are the
MSP430 device user'sguides, application reports, software examples and other MSP430 user'sguides can be found at the Tech Docs section. The CCS user'sguide includes detailed information on setting up a project and using Code Composer Studio for the MSP430 microcontroller (SLAU157).
Information specific to the Buy MSP-EXP430G2 LaunchPad Experimenter Board Now, all the available IDEs, Software Libraries, and examples can be found at the Tools & Software section:
FCC Warning
This equipment is intended for use in a laboratory test environment only. It generates, uses, and can radiate radio frequency energy and has not been tested for compliance with the limits of computing devices pursuant to subpart J of part 15 of FCC rules, which are designed to provide reasonable protection against radio frequency interference. Operation of this equipment in other environments may cause interference with radio communications, in which case, the user will be required to take whatever measures may be required to correct this interference his own expense.
MSP430, Code Composer Studio are trademarks of Texas Instruments.
IAR Embedded Workbench is a trademark of IAR Systems.
All other trademarks are the property of their respective owners.
4 |
Preface |
|
|
|
Copyright ©
User's Guide
SLAU318B – July 2010 – Revised March 2012
Buy MSP-EXP430G2 LaunchPad Experimenter Board Now
1
1.1Overview
The
The
•USB debugging and programming interface featuring a driverless installation and application UART serial communication with up to 9600 Baud
•Supports all MSP430G2xx and MSP430F20xx devices in PDIP14 or PDIP20 packages
•Two
•Two push button for user feedback and device reset
•Easily accessible device pins for debugging purposes or as socket for adding customized extension boards
•
5 |
||
|
|
Copyright ©
Figure 1.
For latest information on the
1.2Kit Contents
The
•LaunchPad emulator socket board
•Mini
•Two MSP430 flash devices
–MSP430G2553:
–MSP430G2452:
•Two
•
•Quick start guide
•Two LaunchPad stickers
1.3Revisions
The first production revision of the LaunchPad in 2010 was 1.3 and in 2012 the LaunchPad board revision changed again from 1.4 to 1.5 to align with the new release of value line device. The differences in the Schematic and the Kit Contents are:
•Layout and Schematic:
–Voltage feedback in the emulator changed to increase startup stability (Rev 1.3 to Rev 1.4)
–Rearranged jumper J3 to support a vertical jumpers position for the UART lines
6 |
||
|
|
Copyright ©
Installation |
–VCC on the connector J4 can now be disconnected from the emulator VCC by J3
–Pullup resistor R34 and capacitor C24 on P1.3 removed to reduce the current consumption
–Presoldered male headers J1 and J2
2Installation
The
1.Download the required software.
2.Install the selected IDE.
3.Connect the LaunchPad to the PC.
Then the LaunchPad is ready to develop applications or to use the
2.1Download the Required Software
Different development software tools are available for the
2.2Install the Software
Download one of the integrated development environments (IDEs). IAR KickStart and CCS offer the required driver support to work with the
2.3Install the Hardware
Connect the
3 Getting Started With
3.1Getting Started
The first time the Buy MSP-EXP430G2 LaunchPad Experimenter Board Now is used, a demo application automatically starts as soon as the board is powered from the USB host. To start the demo, connect the
3.2Demo Application, Internal Temperature Measurement
The LaunchPad includes a
7 |
||
|
|
Copyright ©
Develop an Application With the |
Press button P1.3 to switch the application to a temperature measurement mode. A reference temperature is taken at the beginning of this mode, and the LEDs of the LaunchPad signal a rise or fall in temperature by varying the brightness of the
The demo application uses the
The provided applications can be a great starting point for various custom applications and give a good overview of the manifold possibilities of the MSP430G2xx Value Line devices. Also available are the executable and source files for a GUI, which displays the data that is being communicated back to the PC from the LaunchPad.
4 Develop an Application With the
4.1Developing an Application
The integrated development environments (IDEs) shown in Section 2 offer support for the whole MSP430G2xx Value Line. The
Figure 2. Insert Device Into Target Socket
The following example for Code Composer Studio v4 shows how to download and debug the demo application described in Section 3.2.
4.2Program and Debug the Temperature Measurement Demo Application
The source code of the demo application can be downloaded from the MSP430 LaunchPad wiki page. Download the project folder and unpack it to a location of your choice. For this demo, Code Composer Studio v4 or newer must be installed.
8 |
||
|
|
Copyright ©
Develop an Application With the |
The demo application can be loaded to the CCS workspace by clicking File→Import. Select the location of the extracted project files and import Existing projects into Workspace. Now the
Connect the LaunchPad with an inserted MSP430G2553 device to the host PC and click the Debug button on the CCS Toolbar. The
Figure 3. Code Composer Studio™ v4 in Debugging Mode
4.3Disconnect Emulator From Target With Jumper J3
The connection between the
NOTE: The assignment of jumper J3 has been changed in
|
|
|
Table 1. Jumper Connection J3 Between Emulator and Target |
|
|
|
|
|
|
|
Jumper |
Signal |
|
Description |
|
|
|
|
|
|
1 |
VCC |
Target socket power supply voltage (power consumption test jumper) (located on 5 before Rev. 1.5) |
|
|
|
|
|
|
|
2 |
TEST |
Test mode for JTAG pins or |
|
|
Rev. 1.5) |
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Copyright ©
Develop an Application With the
Table 1. Jumper Connection J3 Between Emulator and Target (continued)
Jumper |
Signal |
Description |
|
|
|
3 |
RST |
Reset or |
|
|
|
4 |
RXD |
UART receive data input (direction can be selected by jumper orientation) (located on 3 before Rev. 1.5) |
|
|
|
5 |
TXD |
UART transmit data output (direction can be selected by jumper orientation) (located on 4 before Rev. 1.5) |
|
|
|
Jumpers 4 and 5 connect the UART interface of the emulator to the target device pins P1.1 and P1.2. The direction of the UART signal lines can be selected by the orientation of the attached jumpers. In horizontal orientation, the jumpers connect TXD to P1.1 and RXD to P1.2, as they are used for the software UART communication on the demo application (see Section 3.2). In vertical orientation, the jumpers connect the TXD signal to P1.2 and the RXD signal to P1.1, as required for the MSP430G2553 USCI.
4.4Program Connected eZ430 Target Boards
The
Figure 4.
To program the attached target without interfering with the LaunchPad socket board, jumper connections TEST and RST of J3 must be open. The interface to the eZ430 target board is always connected to the
The VCC connection to the eZ430 interface is directly connected to the LaunchPad target VCC and can be separated with jumper J3, if the LaunchPad itself should be powered via a connected battery on J4. To supply the eZ430 interface with the onboard emulator the jumper J3 VCC needs to be closed.
Table 2 shows the pinout of the eZ430 debugging interface J4, the first pin is the left pin located on the emulator part of the LaunchPad.
|
|
|
|
|
Table 2. eZ430 Debugging Interface |
|
|
|
|
|
|
|
|
|
Pin |
|
|
Signal |
|
Description |
|
|
|
|
|
|
|
|
1 |
|
|
TXD |
UART transmit data output (UART communication from PC or MSP430G2xx to eZ430 target board) |
|
|
|
|
|
|
|
|
|
2 |
|
|
VCC |
Power supply voltage (J3 VCC needs to be closed to supply via onboard emulator) |
|
|
|
|
|
|||
|
3 |
TEST / SBWTCK |
Test mode for JTAG pins and |
|||
|
|
|
|
|
|
|
|
4 |
|
|
/ SBWTDIO |
Reset, |
|
|
RST |
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
Copyright ©
www.ti.com Develop an Application With the
|
|
Table 2. eZ430 Debugging Interface (continued) |
|
|
|
Pin |
Signal |
Description |
|
|
|
5 |
GND |
Power supply ground |
|
|
|
6 |
RXD |
UART receive data input (UART communication from eZ430 target board to PC or MSP430G2xx) |
|
|
|
4.5Connecting a Crystal Oscillator
The
The oscillator signals are connected to J2 to use the signals on an attached application board. In case of signal distortion of the oscillator signals that leads to a fault indication at the basic clock module, resistors R29 and R28 can be used to disconnect the pin header J2 from the oscillating lines.
4.6Connecting a Satellite Board
The LaunchPad is the perfect experimenter board to start hardware development with the MSP430G2xx Value Line. Connectors J1 and J2 and the power supply at J6 are aligned in a
4.7Supported Devices
Texas Instruments offers several MSP430 devices in a PDIP package that is compatible with LaunchPad. Table 3 shows the supported devices.
|
|
|
|
Table 3. Supported Devices |
|
|
|
|
|
|
Part Number |
Family |
|
Description |
|
|
|
|
|
|
F2xx |
|||
|
|
|
|
|
|
F2xx |
|||
|
|
|
|
|
|
F2xx |
|||
|
|
|
|
|
|
F2xx |
|||
|
|
|
|
|
|
F2xx |
|||
|
|
|
|
|
|
F2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
|
|
|
|
|
G2xx |
|||
|
Enabled I/O Pins |
|
||
|
|
|
|
|
|
|
|
|
|
|
G2xx |
|||
|
Enabled I/O Pins |
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Copyright ©
Develop an Application With the
|
|
Table 3. Supported Devices (continued) |
|
|
|
|
|
Part Number |
Family |
Description |
|
|
|
|
|
G2xx |
|||
Enabled I/O Pins |
|||
|
|
||
|
|
|
|
G2xx |
|||
Enabled I/O Pins |
|||
|
|
||
|
|
|
|
G2xx |
|||
Sense Enabled I/O Pins |
|||
|
|
||
|
|
|
|
G2xx |
|||
Sense Enabled I/O Pins |
|||
|
|
||
|
|
|
|
G2xx |
|||
Sense Enabled I/O Pins |
|||
|
|
||
|
|
|
|
G2xx |
|||
Sense Enabled I/O Pins |
|||
|
|
||
|
|
|
|
G2xx |
|||
|
|
||
|
|
|
|
G2xx |
|||
|
|
||
|
|
|
|
G2xx |
|||
|
|
||
|
|
|
|
G2xx |
|||
|
|
||
|
|
|
|
G2xx |
|||
SPI/I2C, 16 |
|||
|
|
||
|
|
|
|
G2xx |
|||
SPI/I2C, 16 |
|||
|
|
||
|
|
|
|
G2xx |
|||
SPI/I2C, 16 |
|||
|
|
||
|
|
|
|
G2xx |
|||
SPI/I2C, 16 |
|||
|
|
||
|
|
|
|
G2xx |
|||
I2C/SPI/UART, 24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
I2C/SPI/UART, 24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
I2C/SPI/UART, 24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
I2C/SPI/UART, 24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
I2C/SPI/UART, 24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
I2C/SPI/UART, 24 |
|||
|
|
||
|
|
|
|
G2xx |
|||
I2C/SPI/UART, 24 |
|||
|
|
||
|
|
|
|
Copyright ©
5
5.1Device Pinout
Figure 5. Device Pinout
13 |
||
|
|
Copyright ©
5.2Schematics Emulator
Figure 6. Schematics, Emulator (1 of 3)
14 |
||
|
|
Copyright ©
Figure 7. Schematics, Emulator (2 of 3)
15 |
||
|
|
Copyright ©
Figure 8. Schematics, Target Socket (3 of 3)
16 |
||
|
|
Copyright ©
5.3PCB Layout
Figure 9. Layout, LaunchPad Top Layer
17 |
||
|
|
Copyright ©
Figure 10. Layout, LaunchPad Bottom Layer
18 |
||
|
|
Copyright ©
Figure 11. Layout, LaunchPad Silkscreen
19 |
||
|
|
Copyright ©
5.4Bill of Materials (BOM)
Table 4. Bill of Materials
|
|
Pos. |
Ref Name |
Number per |
Description |
|
|
|
|
|
Board |
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
C2, C3 |
|
2 |
16 pF 0402 (33 pF on Rev 1.3) |
|
|
|
|
|
|
|
|
|
|
|
2 |
C9, C10 |
|
2 |
22 pF 0402 |
|
|
|
|
|
|
|
|
|
|
|
3 |
C1 |
|
1 |
10 nF 0402 |
|
|
|
|
|
|
|
|
|
|
|
4 |
C5, C7, C11, C12, C13 |
|
5 |
100 nF 0402 |
|
|
|
|
|
|
|
|
|
|
|
5 |
C4, C6, C8 |
|
3 |
1 µF/6.3 V 0604 |
|
|
|
|
|
|
|
|
|
|
|
6 |
D1 |
|
1 |
1N4148 MicroMELF |
|
|
|
|
|
|
|
|
|
|
|
7 |
EZ_USB |
|
1 |
Mini USB connector |
|
|
|
|
|
|
|
|
|
|
|
8 |
Q1 |
|
1 |
SMD Oscillator 12 MHz |
|
|
|
|
|
|
|
|
|
|
|
9 |
R1, R2, R3, R16, R17 |
|
3 |
47k 0402 (R16, R17 is not populated) |
|
|
|
|
|
|
|
|
|
|
|
10 |
R8 |
|
1 |
61k5 0402 (6k8 in Rev 1.3 and prior) |
|
|
|
|
|
|
|
|
|
|
|
11 |
R19, R22 |
|
2 |
3k3 0402 |
|
|
|
|
|
|
|
|
|
|
|
12 |
R9 |
|
1 |
30k 0402 (3k3 in Rev 1.3 and prior) |
|
|
|
|
|
|
|
|
|
|
|
13 |
R12 R21 |
|
2 |
33k 0402 |
|
|
|
|
|
|
|
|
|
|
|
14 |
R4, R5, R6, R7, R23 |
|
5 |
100R 0402 |
|
|
|
|
|
|
|
|
|
|
|
15 |
R14, R15 |
|
2 |
33R 0402 |
|
|
|
|
|
|
|
|
|
|
|
16 |
R18, R20 |
|
2 |
100k 0402 |
|
|
|
|
|
|
|
|
|
|
|
17 |
R13, R24, R25 |
|
3 |
1k5 0402 |
|
|
|
|
|
|
|
|
|
|
|
18 |
R10 |
|
1 |
10k 0402 |
|
|
|
|
|
|
|
|
|
|
|
19 |
R11 |
|
1 |
15k 0402 |
|
|
|
|
|
|
|
|
|
|
|
20 |
U1 |
|
1 |
MSP430F1612IPMR |
|
|
|
|
|
|
|
|
|
|
|
21 |
U4 |
|
1 |
TPD2E001DRLR |
|
|
|
|
|
|
|
|
|
|
|
22 |
U3 |
|
1 |
TUSB3410VF |
|
|
|
|
|
|
|
|
|
|
|
23 |
U2 |
|
1 |
TPS77301DGKR |
|
|
|
|
|
|
|
|
|
|
|
24 |
U5 |
|
1 |
I2C EEPROM 128k |
|
|
|
|
|
|
|
|
|
|
|
25 |
TP1, TP2, TP3, TP4, |
|
|
|
|
|
|
TP5, TP6, TP7 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
26 |
C14 |
|
1 |
1 nF, SMD0603 |
|
|
|
|
|
|
|
|
|
|
|
27 |
C21, C22 |
|
|
12.5 pF, SMD0603 (not populated) |
|
|
|
|
|
|
|
|
|
|
|
28 |
C23 |
|
1 |
10 µF/10 V, SMD 0805 |
|
|
|
|
|
|
|
|
|
|
|
29 |
C20, C24 |
|
1 |
100 nF, SMD0603 (C24 is not populated) |
|
|
|
|
|
|
|
|
|
|
|
30 |
LED0, LED1 |
|
2 |
green DIODE0603 |
|
|
|
|
|
|
|
|
|
|
|
31 |
LED2 |
|
1 |
red DIODE0603 |
|
|
|
|
|
|
|
|
|
|
|
32 |
R34, R27 |
|
1 |
47k SMD0603 (R34 is not populated) |
|
|
|
|
|
|
|
|
|
|
|
33 |
R32, R26 |
|
2 |
270R SMD0603 |
|
|
|
|
|
|
|
|
|
|
|
34 |
R33 |
|
1 |
470R SMD0603 |
|
|
|
|
|
|
|
|
|
|
|
35 |
R28, R29 |
|
2 |
0R SMD0603 |
|
|
|
|
|
|
|
|
|
|
|
36 |
IC1 |
|
1 |
DIP20 Socket |
|
|
|
|
|
|
|
|
|
|
|
37 |
Q2 |
|
|
Clock Crystal 32 kHz (Micro Crystal |
|
|
|
|
|
32.768 kHz CL: 12.5 pF |
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
38 |
J1, J2, |
|
2 |
|
|
|
|
|
included) |
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
39 |
J3 |
|
1 |
2X05 Pin Header Male |
|
|
|
|
|
|
|
|
|
|
|
40 |
J4 |
|
|
6 Pin Header Male 1.28 mm |
|
|
|
|
|
|
|
|
|
|
|
41 |
J5 |
|
1 |
2X02 Pin Header Male |
|
|
|
|
|
|
|
|
|
|
|
42 |
J6 |
|
2 |
|
|
|
|
|
|
|
|
|
|
|
|
43 |
S1, S2 |
|
2 |
Push Button |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
20 |
|
||||||
|
|
|
|
|
|
Copyright ©
www.ti.com Suggested Reading
6 Suggested Reading
The primary sources of MSP430™ information are the
http://www.ti.com/msp430,
To get an inside view of the supporting IDEs like CCS and IAR, download the latest version from the web pages above and read the included user'sguides and documentation inside the installation folder. Documents describing the IAR tools
7Frequently Asked Questions (FAQ)
1.Can other programming tools like the
The LaunchPad experimenter board works with any programming tool that supports the
2.Does the
The Buy MSP-EXP430G2 LaunchPad Experimenter Board Now onboard debugging interface lacks the JTAG security
3.What versions of IAR Embedded Workbench and Code Composer Studio are supported?
The
6.00or higher and Code Composer Studio v4 or higher. To download the software and for more information on the supported software visit the LaunchPad Wiki page.
4.What are the part numbers for the connectors between the LaunchPad emulator board and the other eZ430 target boards?
Header: MALE CONN HEADER .050" 6POS PCB R/A (for example,
5.I am not able to select the MSP430 Application UART and cannot receive data.
Ensure that the Application UART driver is correctly installed. This is done by installing either IAR Embedded Workbench or Code Composer Studio v4.
To determine if the driver is correctly installed:
a.Plug in the
b.Right click My Computer and select Properties.
c.Select the Hardware tab and click on Device Manager.
d.Under Ports (COM & LPT) should be an entry for "MSP430 Application UART (COM xx)".
If the entry is there, but no characters are received, reconnect the LaunchPad to the PC and restart the application to reload the drivers. If the Application UART is not listed, install the driver by following the instructions in Section 2.2.
6.The device is not answering to any communication, JTAG or UART.
If you are experiencing difficulties in communicating to the attached MSP430 target device, even though all the communication drivers for the
21 |
||
|
|
Copyright ©
Frequently Asked Questions (FAQ) |
Experimenter Board and restarting the communicating application. Also make sure that all the jumpers on J3 are connected properly between the emulator and the target device. On revision 1.5 and newer, the orientation of the UART jumpers must align with the software implementation on the target device.
7.I soldered the
The MSP430 driving capabilities for the
8.The power consumption of the board is much higher than specified in the device data sheet, or I am not measuring a current at all.
The MSP430 device inside of the LaunchPad socket can be powered with an external power supply at header J6 or J4. To measure the power consumption in this mode, the VCC jumper, usually used to measure the power consumption, must be removed, and the current must be measured directly at the power supply. If the jumper J3 is not removed, the emulator circuitry of the LaunchPad is powered as well. Measuring the current consumption during a debug session is not possible, because the cross current through the JTAG connection influences the measurement. The most accurate results are achieved with all jumpers on J3 removed. If the measurement is still not matching the data sheet parameters, make sure that the code is aligned with all the power saving recommendations on the web site MSP430™ - The World's Lowest Power MCU.
LaunchPad revisions 1.3 and 1.4 come with R34 populated. The
22 |
||
|
|
Copyright ©
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. All products are sold subject to TI’s terms and conditions of sale supplied at the time of order acknowledgment.
TI warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TI’s standard warranty. Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty. Except where mandated by government requirements, testing of all parameters of each product is not necessarily performed.
TI assumes no liability for applications assistance or customer product design. Customers are responsible for their products and applications using TI components. To minimize the risks associated with customer products and applications, customers should provide adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right, copyright, mask work right, or other TI intellectual property right relating to any combination, machine, or process in which TI products or services are used. Information published by TI regarding
Reproduction of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Reproduction of this information with alteration is an unfair and deceptive business practice. TI is not responsible or liable for such altered documentation. Information of third parties may be subject to additional restrictions.
Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids all express and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements.
TI products are not authorized for use in
TI products are neither designed nor intended for use in military/aerospace applications or environments unless the TI products are specifically designated by TI as
TI products are neither designed nor intended for use in automotive applications or environments unless the specific TI products are designated by TI as compliant with ISO/TS 16949 requirements. Buyers acknowledge and agree that, if they use any
Following are URLs where you can obtain information on other Texas Instruments products and application solutions:
Products |
|
Applications |
|
Audio |
www.ti.com/audio |
Automotive and Transportation |
www.ti.com/automotive |
Amplifiers |
amplifier.ti.com |
Communications and Telecom |
www.ti.com/communications |
Data Converters |
dataconverter.ti.com |
Computers and Peripherals |
www.ti.com/computers |
DLP® Products |
www.dlp.com |
Consumer Electronics |
|
DSP |
dsp.ti.com |
Energy and Lighting |
www.ti.com/energy |
Clocks and Timers |
www.ti.com/clocks |
Industrial |
www.ti.com/industrial |
Interface |
interface.ti.com |
Medical |
www.ti.com/medical |
Logic |
logic.ti.com |
Security |
www.ti.com/security |
Power Mgmt |
power.ti.com |
Space, Avionics and Defense |
|
Microcontrollers |
microcontroller.ti.com |
Video and Imaging |
www.ti.com/video |
RFID |
|
|
|
OMAP Mobile Processors |
www.ti.com/omap |
|
|
Wireless Connectivity |
www.ti.com/wirelessconnectivity |
|
|
|
TI E2E Community Home Page |
e2e.ti.com |
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2012, Texas Instruments Incorporated