If you have any feedback or questions, support for the MSP430™ devices and the MSP-EXP430G2 is
provided by the Texas Instruments Product Information Center (PIC) and the TI E2E Forum
(http://e2e.ti.com/). Contact information for the PIC can be found on the TI web site at http://support.ti.com.
Additional device-specific information can be found on the MSP430 web site at http://www.ti.com/msp430.
Related Documentation from Texas Instruments
The primary sources of MSP430 information are the device-specific data sheets and user's guides
available at the Texas Instruments MSP430 web site: http://www.ti.com/msp430.
MSP430 device user's guides, application reports, software examples and other MSP430 user's guides
can be found at the Tech Docs section. The CCS user's guide includes detailed information on setting up
a project and using Code Composer Studio™ for the MSP430 microcontroller (SLAU157).
Information specific to the MSP-EXP430G2 LaunchPad Evaluation Kit, all the available IDEs, Software
Libraries, and examples can be found at the Tools & Software section: http://www.ti.com/tool/msp-
exp430g2.
User's Guide
1MSP-EXP430G2 LaunchPad Overview
1.1Overview
The MSP-EXP430G2 LaunchPad is an inexpensive and simple evaluation kit for the MSP430G2xx Value
Line series of microcontrollers. It is an easy way to start developing on the MSP430 with on-board
emulation for programming and debugging as well as buttons and LEDs for a simple user interface.
Rapid prototyping is simplified by the 20-pin BoosterPack headers which support a wide range of available
BoosterPack plug-in modules. You can quickly add features like wireless connectivity, graphical displays,
environmental sensing, and much more. You can either design your own BoosterPack or choose among
many already available from TI and third party developers.
The LaunchPad features an integrated DIP target socket that supports up to 20 pins, allowing MSP430™
Value Line devices to be plugged into the LaunchPad board. The MSP-EXP430G2 LaunchPad comes
with an MSP430G2553 device by default. The MSP430G2553 has the most memory available of the
compatible Value Line devices.
The MSP430G2553 16-bit MCU has 16KB flash, 512 bytes RAM, up to 16-MHz CPU speed, 10-bit ADC,
capacitive touch enabled I/Os, universal serial communication interface, and more – plenty to get you
started in your development.
Free software development tools are also available: TI's Eclipse-based Code Composer Studio™ IDE
(CCS), IAR Embedded Workbench™ IDE (IAR), and the community-driven Energia open source code
editor. More information about the LaunchPad, including documentation and design files, can be found on
the tool page at http://www.ti.com/tool/msp-exp430g2.
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
MSP-EXP430G2 LaunchPad Evaluation KitSLAU318F–July 2010–Revised January 2015
•USB debugging and programming interface featuring a driverless installation and application UART
serial communication with up to 9600 Baud
•Supports MSP430G2xx2, MSP430G2xx3, and MSP430F20xx devices in PDIP14 or PDIP20 packages
(see Section 4.7 for a complete list of supported devices)
•Two general-purpose digital I/O pins connected to green and red LEDs for visual feedback
•Two push button for user feedback and device reset
•Easily accessible device pins for debugging purposes or as socket for adding customized extension
boards
•High-quality 20-pin DIP socket for an easy plug-in or removal of the target device
MSP-EXP430G2 LaunchPad Overview
Figure 1. MSP-EXP430G2 LaunchPad Overview
1.3Kit Contents
The MSP-EXP430G2 evaluation kit includes the following hardware:
•LaunchPad emulator socket board (MSP-EXP430G2)
•Mini USB-B cable, 0.5 m
•Two MSP430 flash devices
– MSP430G2553: Low-power 16-bit MSP430 microcontroller with an 8-channel 10-bit ADC, on-chip
comparator, touch-sense enabled I/Os, universal serial communication interface, 16kB flash
memory, and 512 bytes of RAM (preloaded with a sample program)
– MSP430G2452: Low-power 16-bit MSP430 microcontroller with an 8-channel 10-bit ADC, on-chip
comparator, touch-sense enabled I/Os, universal serial interface, 8kB flash memory, and 256 bytes
of SRAM
•Two 10-pin PCB connectors female
•32.768-kHz clock crystal from Micro Crystal (http://www.microcrystal.com)
•Quick start guide
•Two LaunchPad stickers
SLAU318F–July 2010–Revised January 2015MSP-EXP430G2 LaunchPad Evaluation Kit
The first production revision of the LaunchPad in 2010 was 1.3. In 2012 the LaunchPad board revision
changed from 1.4 to 1.5 to align with the new release of Value Line devices. 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 two UART configurations: vertical (SW UART), horizontal (HW
UART)
– 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 MSP-EXP430G2 LaunchPad installation consists of three easy steps:
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 pre-programmed demo application.
2.1Download the Required Software
Different development software tools are available for the MSP-EXP430G2 LaunchPad development
board. IAR Embedded Workbench™ KickStart IDE and Code Composer Studio™ (CCS) IDE are both
available in a free limited version. IAR Embedded Workbench allows 4KB of C-code compilation. CCS is
limited to a code size of 16KB. The software is available at http://www.ti.com/mspds. There are many
other compilers and integrated development environments (IDEs) available to use with the MSP-EXP430
LaunchPad including Rowley Crossworks and MSPGCC. However, example projects have been created
using IAR Embedded Workbench KickStart IDE and Code Composer Studio IDE (CCS). For more
information on the supported software and the latest code examples, visit the LaunchPad tool page
(http://www.ti.com/tool/msp-exp430g2).
www.ti.com
2.2Install the Software
Download one of the integrated development environments (IDEs) (see Section 2.1). IAR KickStart and
CCS offer the required driver support to work with the MSP-EXP430 LaunchPad onboard emulation. Once
installed, the IDE should find the MSP-EXP430G2 LaunchPad as USB:HID debugging interface. Now all is
set for developing MSP430G2xx based application on the LaunchPad.
2.3Install the Hardware
Connect the MSP-EXP430G2 LaunchPad socket board with the enclosed USB cable to a PC. The driver
installation starts automatically. If prompted for software, allow Windows to install the software
automatically. This is possible only if either IAR KickStart or CCS is already installed.
6
MSP-EXP430G2 LaunchPad Evaluation KitSLAU318F–July 2010–Revised January 2015
The first time the MSP-EXP430G2 LaunchPad Evaluation Kit is used, a demo application automatically
starts as soon as the board is powered from the USB host. To start the demo, connect the MSPEXP430G2 LaunchPad with the included mini USB cable to a free USB port. The demo application starts
with an LED toggle to show the device is active. More information about the demo application can be
found in Section 3.2.
3.2Demo Application, Internal Temperature Measurement
The LaunchPad includes a pre-programmed MSP430G2553 device already installed in the target socket.
When LaunchPad is connected via USB, the demo starts with an LED toggle sequence. The onboard
emulation generates the supply voltage and all the signals necessary to start.
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 on-board red or green LED, respectively. The reference temperature can
also be recalibrated with another button press on P1.3. The collected temperature data is also
communicated via back-channel UART through the USB emulation circuitry back to the PC. The internal
temperature sensor data from the MSP430G2553 device is sent to the PC to be displayed on the GUI.
The pre-loaded demo application and the GUI are found in the Software Examples zip folder. The GUI is
opened with LaunchPad_Temp_GUI.exe. This GUI is made with Processing (http://processing.org) with
the source available for customization. The serial communication port on the PC must be configured with
2400 bps, one stop bit, and no flow control to display the values correctly.
The demo application uses the on-chip peripherals of the MSP430G2553 device such as the 10-bit ADC,
which samples the internal temperature sensor, and 16-bit timers, which drive the PWM to vary brightness
of the LEDs and enable software UART for communication with the PC. The MSP430G2553 offers a USCI
interface that is capable of communicating through UART at up to 2 MBaud, but to be aligned with all the
other MSP430G2xx devices, the demo uses the Timer UART implementation, which can be used on all
the other devices. This way the demo can be used with any other MSP430G2xx device with an integrated
ADC, without any change in the program.
The provided applications can be a great starting point for various custom applications and give a good
overview of the various applications of the MSP430G2xx Value Line devices.
SLAU318F–July 2010–Revised January 2015MSP-EXP430G2 LaunchPad Evaluation Kit
Develop an Application With the MSP-EXP430G2 LaunchPad
4Develop an Application With the MSP-EXP430G2 LaunchPad
4.1Developing an Application
The integrated development environments (IDEs) shown in Section 2 offer support for the whole
MSP430G2xx Value Line. The MSP-EXP430G2 LaunchPad needs only a connection to the USB of the
Host PC—there is no external hardware required. The power supply and the Spy-Bi-Wire JTAG signals
TEST and RST must be connected with jumper J3 to allow the onboard emulation connection to the
device. Now the preferred device can be plugged into the DIP target socket of the LaunchPad (see
Figure 2). Both PDIP14 and PDIP20 devices of the MSP430G2xx Value Line and the MSP430F20xx
family can be inserted into the DIP socket aligned to pin 1. A complete list of supported devices can be
found in Section 4.7.
Figure 2. Insert Device Into Target Socket
The following example for Code Composer Studio shows how to download and debug the demo
application described in Section 3.2.
www.ti.com
4.2Program and Debug the Temperature Measurement Demo Application
The source code of the demo application can be found in the Software Examples zip folder. 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.
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 MSP-EXP430G2Launchpad project appears inside the CCS workspace. The project must be marked as the active project
to start programming and debugging the device.
Connect the LaunchPad with an inserted MSP430G2553 device to the host PC and click the Debug button
on the CCS Toolbar. The MSP-EXP430G2 LaunchPad is initialized and the download of the compiled
demo application starts. The CCS view switches to a debugging interface once the download is completed
and the application is ready to start. Figure 3 shows Code Composer Studio v4 with the MSP-EXP430G2
LaunchPad demo application in debug view.
8
MSP-EXP430G2 LaunchPad Evaluation KitSLAU318F–July 2010–Revised January 2015
Develop an Application With the MSP-EXP430G2 LaunchPad
Figure 3. Code Composer Studio™ v4 in Debugging Mode
4.3Disconnect Emulator From Target With Jumper J3
The connection between the MSP-EXP430G2 emulator and the attached target device can be opened
with the jumper array J3. This can be useful to access an attached eZ430 target board by disconnecting
the Spi-Bi-Wire JTAG lines RST and TEST or if the JTAG lines are used for other application purposes.
The jumper array can also be used to measure the power consumption of the LaunchPad application. For
this intention, all connections except VCC must be opened, and a multi meter can used on the VCC
Jumper to measure the current of the MSP-EXP430G2 target device and its peripherals. The jumper J5
VCC also must be opened if the LaunchPad board is powered with an external power supply over J6
Table 1 or the eZ430 interface J4.
NOTE: The assignment of jumper J3 has been changed in MSP-EXP430G2 revision 1.5, see the
comments in Table 1 to find the assignment for a specific board revision.
Table 1. Jumper Connection J3 Between Emulator and Target
JumperSignalDescription
1VCCTarget socket power supply voltage (power consumption test jumper) (located on 5 before Rev. 1.5)
2TEST
3RSTReset or Spy-Bi-Wire test data input/output during programming and test (located on 2 before Rev. 1.5)
4RXDUART receive data input (direction can be selected by jumper orientation) (located on 3 before Rev. 1.5)
5TXDUART transmit data output (direction can be selected by jumper orientation) (located on 4 before Rev. 1.5)
Test mode for JTAG pins or Spy-Bi-Wire test clock input during programming and test (located on 1 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.
These jumpers can be used to select between a software (SW) UART or a hardware (HW) UART by their
orientation. In vertical orientation (SW UART), the jumpers connect the emulation TXD signal to target
P1.2 and the emulation RXD signal to target P1.1, as they are used for the software UART communication
on the demo application (see Section 2.2). In horizontal orientation (HW UART), the jumpers connect the
SLAU318F–July 2010–Revised January 2015MSP-EXP430G2 LaunchPad Evaluation Kit
Develop an Application With the MSP-EXP430G2 LaunchPad
emulator TXD signal to target P1.1 and the emulator RXD to target P1.2, as required for the USCI module.
Keep in mind that UART communication is full duplex, so connections are made for both transmit and
receive on each side, and the labeling is specific to what action each side of the UART bus is performing.
For example, the emulator TXD (transmit) signal connects to the target RXD (receive) signal, and the
emulator RXD signal connects to the target TXD signal.
4.4Program Connected eZ430 Target Boards
The MSP-EXP430G2 LaunchPad can program the eZ430-RF2500T target boards, the eZ430-Chronos
watch module, or the eZ430-F2012T/F2013T. To connect one of the ez430 targets, connector J4 must be
populated with a 0.050-in (1.27-mm) pitch male header, as shown in Figure 4.
www.ti.com
Figure 4. MSP-EXP430G2 LaunchPad With Attached eZ430-RF2500 Target Board
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
MSP-EXP430G2 emulator, so the programming and debugging of a connected LaunchPad target device
is possible only if the eZ430 target is not connected on the same time. The application UART, on the other
hand, is connected directly to the LaunchPad target device, and jumper J3 can be closed to monitor the
transmission from the LaunchPad target to the attached eZ430. This way both possible connections, from
the device to the PC and from the device to the eZ430, can be established without changing the direction
of the UART pins.
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
PinSignalDescription
1TXDUART transmit data output (UART communication from PC or MSP430G2xx to eZ430 target board)
2VCCPower supply voltage (J3 VCC needs to be closed to supply via onboard emulator)
3TEST / SBWTCKTest mode for JTAG pins and Spy-Bi-Wire test clock input during programming and test
4RST / SBWTDIOReset, Spy-Bi-Wire test data input/output during programming and test
5GNDPower supply ground
6RXDUART receive data input (UART communication from eZ430 target board to PC or MSP430G2xx)
10
MSP-EXP430G2 LaunchPad Evaluation KitSLAU318F–July 2010–Revised January 2015
The MSP-EXP430G2 LaunchPad offers a footprint for a variety of crystal oscillators. The XIN and XOUT
signals of the LFXT1 oscillator can support low-frequency oscillators like a watch crystals of 32768 Hz or a
standard crystal with a range defined in the associated data sheet. The signal lines XIN and XOUT can
also be used as multipurpose I/Os or as a digital frequency input. More information on the possibilities of
the low-frequency oscillator and the possible crystal selection can be found in the MSP430x2xx FamilyUser's Guide (SLAU144) or the device-specific data sheet.
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 BoosterPack
The LaunchPad can connect to many BoosterPacks within the ecosystem. The BoosterPack headers J1
and J2 along with power supply J6 fall on a 100-mil (0.1-in) grid to allow for easy and inexpensive
development with a breadboard. The LaunchPad adheres to the 20-pin LaunchPad pinout standard. A
standard was created to aid compatibility between LaunchPads and BoosterPacks, across the TI
ecosystem.
The 20-pin standard is backward compatible with the 40-pin standard used by LaunchPads like the MSP-
EXP430F5529LP. This allows a subset of some 40-pin BoosterPacks to be used with 20-pin LaunchPads.
While most BoosterPacks are compliant with the standard, some are not. The LaunchPad is compatible
with all 20-pin (and 40-pin) BoosterPacks that are compliant with the standard. If the reseller or owner of
the BoosterPack does not explicitly indicate compatibility with the MSP430G2 LaunchPad, you might want
to compare the schematic of the candidate BoosterPack with the LaunchPad, to ensure compatibility.
Keep in mind that sometimes conflicts can be resolved by changing the G2 device pin function
configuration in software. More information about compatibility can also be found at
http://www.ti.com/launchpad.
Develop an Application With the MSP-EXP430G2 LaunchPad
4.7Supported Devices
Texas Instruments offers several MSP430 devices in a PDIP package that is compatible with LaunchPad.
The MSP-EXP430G2 on-board emulator enables programming and debugging of supported MSP430
devices (see Section 4.7). It offers several features that are enabled by a 2-wire JTAG interface called
Spy-Bi-Wire. For a more feature-complete emulator, the MSP-FET430UIF flash emulation tool may be
more appropriate. See Table 4 for more details on the MSP-EXP430G2 LaunchPad on-board emulator.
Table 4. Features Supported by On-Board Emulator
Develop an Application With the MSP-EXP430G2 LaunchPad
Supports MSP430F20xx, F21x2, F22xx, G2x01, G2x11, G2x21, G2x31, G2x53✓
Allows fuse blow
Adjustable target supply voltage
Fixed 2.8-V target supply voltage
Fixed 3.6-V target supply voltage✓
4-wire JTAG
2-wire JTAG✓
Application UART✓
Supported by CCS✓
Supported by IAR✓
5MSP-EXP430G2 Hardware
5.1Device Pinout
Feature
Support by LaunchPad
(MSP-EXP430G2)
SLAU318F–July 2010–Revised January 2015MSP-EXP430G2 LaunchPad Evaluation Kit
The primary sources of MSP430™ information are the device-specific data sheets and the family user's
guides. The most up-to-date versions of those documents can be found at the Texas Instruments MSP430
landing page.
For more information on CCS and IAR, download the latest version from http://www.ti.com/mspds and
read the included user's guides and documentation in the installation folder. Documents describing the
IAR tools (Workbench/C-SPY, the assembler, the C compiler, the linker, and the library) are located in
common\doc and 430\doc. All necessary CCS documents can be found in the msp430\doc folder in the
CCS installation path. The FET user's guide also includes detailed information on how to set up a project
for the MSP430 using IAR or CCS, and it is included in most of the IDE releases and on the TI MSP430
side.
7Frequently Asked Questions (FAQ)
1. Can other programming tools like the MSP-FET430UIF interface the MSP-EXP430G2 LaunchPad
socket device?
The LaunchPad evaluation kit works with any programming tool that supports the 2-wire Spy-Bi-Wire
interface. Both the MSP430 USB FET (MSP-FET430UIF) and the Gang Programmer (MSP-GANG430)
support these devices, but the connection must be made directly to the dedicated Spy-Bi-Wire ports.
See MSP-FET430 Flash Emulation Tool User's Guide (SLAU138) for details on using MSP430 USB
FET and the Gang Programmer for a 2-wire Spy-Bi-Wire interface. Do not try to connect the standard
JTAG connector to the MSP-EXP430G2 pinheads, as this could result in damage to the attached
hardware.
2. Does the MSP-EXP430G2 support fuse blow?
The MSP-EXP430G2 LaunchPad evaluation kit onboard debugging interface lacks the JTAG security
fuse-blow capability. To ensure firmware security on devices going to production, the USB Flash
Emulation Tool or the Gang Production Programmer, which support the fuse-blow feature, are
recommended.
3. What versions of IAR Embedded Workbench and Code Composer Studio are supported?
The MSP-EXP430G2 LaunchPad hardware is supported by IAR Embedded Workbench KickStart
Version 6.00 or higher and Code Composer Studio v4 or higher. To download the IDE visit
http://www.ti.com/mspds.
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, Digi-Key: S9016E-06-ND)
Socket: FEMALE CONN HEADER .050" 6POS PCB R/A (for example, Digi-Key: S9010E-06-ND)
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 MSP-EXP430G2 LaunchPad with the included Mini USB cable.
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.
If the application UART is installed but not receiving UART data, ensure that the jumpers on J3 are
configured for the proper UART communication. The two UART jumpers are configured vertically for a
software (SW) UART, and horizontally for a hardware (HW) UART. The application implementation and
J3 jumpers should match for UART data to be properly transmitted.
www.ti.com
24
MSP-EXP430G2 LaunchPad Evaluation KitSLAU318F–July 2010–Revised January 2015
6. The device is not answering to any communication, JTAG or UART.
7. I soldered the 32-kHz crystal to the board and the oscillation is not starting.
8. The power consumption of the board is much higher than specified in the device data sheet, or I am
Frequently Asked Questions (FAQ)
If you are experiencing difficulties in communicating to the attached MSP430 target device, even
though all the communication drivers for the MSP-EXP430G2 are loaded correctly, the emulator is
probably set to a wrong communication state. This can be fixed by reconnecting the LaunchPad
evaluation kit 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.
The MSP430 driving capabilities for the low-frequency crystal is limited, because it is designed for lowpower applications. To ensure proper operation, the load on these pins must be as small as possible,
the matching capacitors (12.5 pF for 32.768 kHz) for the crystal must be soldered to the board, and the
resistors R28 and R29 must be removed. Measuring the frequency of the oscillation with an
oscilloscope typically disturbs the oscillation.
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 47-kΩ resistor is used as a pullup for
the button S2. If the port P1.3 is driven to ground, as suggested to keep the power consumption down,
the pullup resistor generates an additional current of approximately 77 µA. To reduce the power
consumption, the port should stay in input mode or the resistor should be removed if button S2 is not
used. The internal pullup of the MSP430G2xx can be used instead.
SLAU318F–July 2010–Revised January 2015MSP-EXP430G2 LaunchPad Evaluation Kit
Changes from E Revision (March 2014) to F Revision ................................................................................................... Page
•Corrected the description of jumper settings in the paragraph that starts "Jumpers 4 and 5 connect the UART
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and other
changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latest
issue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and
complete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s terms and conditions of sale
supplied at the time of order acknowledgment.
TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TI’s terms
and conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessary
to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarily
performed.
TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their products and
applications using TI components. To minimize the risks associated with Buyers’ products and applications, Buyers should provide
adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, or
other intellectual property right relating to any combination, machine, or process in which TI components or services are used. Information
published by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty or
endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the
third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of significant portions 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. TI is not responsible or liable for such altered
documentation. Information of third parties may be subject to additional restrictions.
Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service
voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice.
TI is not responsible or liable for any such statements.
Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements
concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or support
that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which
anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might cause
harm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the use
of any TI components in safety-critical applications.
In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TI’s goal is to
help enable customers to design and create their own end-product solutions that meet applicable functional safety standards and
requirements. Nonetheless, such components are subject to these terms.
No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the parties
have executed a special agreement specifically governing such use.
Only those TI components which TI has specifically designated as military grade or “enhanced plastic” are designed and intended for use in
military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI components
which have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal and
regulatory requirements in connection with such use.
TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case of use of
non-designated products, TI will not be responsible for any failure to meet ISO/TS16949.
ProductsApplications
Audiowww.ti.com/audioAutomotive and Transportationwww.ti.com/automotive
Amplifiersamplifier.ti.comCommunications and Telecomwww.ti.com/communications
Data Convertersdataconverter.ti.comComputers and Peripheralswww.ti.com/computers
DLP® Productswww.dlp.comConsumer Electronicswww.ti.com/consumer-apps
DSPdsp.ti.comEnergy and Lightingwww.ti.com/energy
Clocks and Timerswww.ti.com/clocksIndustrialwww.ti.com/industrial
Interfaceinterface.ti.comMedicalwww.ti.com/medical
Logiclogic.ti.comSecuritywww.ti.com/security
Power Mgmtpower.ti.comSpace, Avionics and Defensewww.ti.com/space-avionics-defense
Microcontrollersmicrocontroller.ti.comVideo and Imagingwww.ti.com/video
RFIDwww.ti-rfid.com
OMAP Applications Processorswww.ti.com/omapTI E2E Communitye2e.ti.com
Wireless Connectivitywww.ti.com/wirelessconnectivity