PRIME PLC Device Firmware Upgrade

Application Report
SPRABT5 – July 2013
PRIME PLC Device Firmware Upgrade
Jeanne Yi, Harvey Wang, Jones Chen
MCU Central FAE Team
ABSTRACT
The PLC PRIME standard defines a procedure to upgrade the PRIME firmware image of a
service node (SN) to a newer version. This document describes in detail how to run
Device Firmware Upgrade (DFU) on the F28069 running the TI-delivered PRIME PLC
modem code based on host processor–PLC modem communication streams.
1
SPRABT5
Contents
Overview ............................................................................................................................................... 3
1
Prepare PLC Firmware For Upgrade ........................................................................................... 3
1.1 Format of the .sbin File ........................................................................................................... 3
1.2 Convert .sbin File to Binary Format on Host Side ................................................................... 4
1.2.1 Placement of First Segment ........................................................................................ 4
1.2.2 Data-Sending Requirements ....................................................................................... 5
1.3 Flash Memory Layout ............................................................................................................. 5
2
Firmware Upgrade Flow ............................................................................................................... 5
3
Set Up DC Network Connection .................................................................................................. 6
3.1 Set Up DC Connection ........................................................................................................... 6
3.1.1 Hardware Connction ................................................................................................... 6
3.1.2 Operation on the Linux PC .......................................................................................... 6
3.2 Set Up PLC Modem and Host Connection .............................................................................. 7
3.2.1 Hardware Connection ................................................................................................. 7
3.2.2 Software Configuration of the PLC Modem With Host Processor ................................ 7
4
Firmware Upgrade ........................................................................................................................ 8
4.1 Host Converting .sbin Image File to Binary Format, Flashing them to TMS320F28069......... 10
References ......................................................................................................................................... 12
Figures
Figure 1. Firmware Upgrade Stream Flow .......................................................................................... 6
Table 1.
Table 2.
2
Tables
.sbin File Format Details ................................................................................................. 3
Flash Memory Layout on F28069.................................................................................... 5
PRIME PLC Device Firmware Upgrade
SPRABT5
Overview
Texas Instruments provides the PRIME PLC modem using TMS320F28069+AFE031.
Customers can treat this modem as a black box. All communication is done using the TI
proprietary PLC suite Host Messaging Protocol Specification. The firmware upgrade described in
this document is specifically for PRIME firmware upgrade protocol. The firmware upgrade
procedure is a joint process between the host application and the PLC modem where firmware
images are assumed to be stored on the DC. The following steps must be completed to perform
a successful upgrade:
1. The PLC modem gets registration and connection with the DC.
2. The user initiates a firmware upgrade (FU) though DC and provides the sbin image.
3. DC sends PLC firmware sbin image to the emeter PLC modem on a packet basis. Each
packet is referred to as a page in the PRIME standard.
4. The PLC modem receives the packets and forwards them to the host processor.
5. The host processor stores the packets in its external or internal memory.
6. Once all packets are received, the host processor converts the sbin image to a binary file
and sends it back to the PLC modem for flashing on a packet basis.
7. After the PLC modem receives all flashing packets, it resets automatically and works with a
new image.
Implementation of the PRIME firmware upgrade is mandatory to get PRIME certification for the
SN. Unicast (UC) and multicast (MC) FU must be supported. For simplicity, only UC FU is
discussed in this document.
1
Prepare PLC Firmware For Upgrade
TI delivers PLC modem firmware code for DFU in sbin format: prime_7.1.8.1.sbin
1.1
Format of the .sbin File
Table 1 shows the format of the .sbin file.
Table 1.
Length of
Bytes
.sbin File Format Details
Bits
7
6
5
4
3
2
2
Number of sections
2
Section Index # 0
4
Start address of section # 0
4
Length of section # 0
1
0
PRIME PLC Device Firmware Upgrade
3
SPRABT5
Note 1:
Note 2:
1.2
4
CRC32 of section # 0
var
Data of section # 0
2
Section Index # 1
4
Start address of section # 1
4
Length of section # 1
4
CRC32 of section # 1
var
Data of section # 1
…
Section #2 ~ Section #(N-2)
2
Section Index # (N-1)
4
Start address of section # (N-1)
4
Length of section # (N-1)
4
CRC32 of section # (N-1)
var
Data of section # (N-1)
“Length of section #” is calculated with byte unit and just contains the length of Data. var equals the length of section.
One .sbin file could include 3 or 4 sections.
Convert .sbin File to Binary Format on Host Side
After the host received the total .sbin image file successfully, it should convert the .sbin file to
binary format and flash the binary format file to TMS320F28069.
1.2.1 Placement of First Segment
The first segment is always at the beginning of the data (that is, packet ID 0). The following
stream is the first data packet sent by the DC through the PLC modem to the host:
13 00 CA 00 E4 79 00 00 00 00 00 00 00 00 03 00 00 00 00 C0 3D 00 C2 53 02 00 25 A3 24 5A 56
1F 76 22 B9 C0 28 29 00 68 76 1A 00 7F 2D 69 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F
25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00
3F 25 2F 00 3F 25 2F 00 3F 23 98 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F
00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25
2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F
1C 86 00 3F 1C 86 00 3F 25 2F 00 3F 1C 86 00 3F 25 2F 00 3F
The meaning of colored data field in the above stream is described as follows:
Red 03 00: Number of sections in image is 3. (0x0003)
Pink 00 00: Current section ID is 0. (0x0000)
Green 00 C0 3D 00: The start address of current section (0 section) is 0x003D C000.
Blue C2 53 02 00: Data length of current section (0 section).
Brown 25 A3 24 5A: CRC of current section (0 section).
4
PRIME PLC Device Firmware Upgrade
SPRABT5
1.2.2
Data-Sending Requirements
When the host is required to send the data to the PLC modem, it must be sent in the following
manner:
94 80 F8 00 5C AD A1 11 - 01 00 01 00 00 C0 3D 00 75 00 1F 56 22 76 C0 B9 29 28 68 00 1A 76 7F
00 A7 2A 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89
22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 F2 20 3F 00 89
22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89
22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89
22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 E0 19 3F 00 E0 19 3F 00 89 22 3F 00 E0 19 3F 00
89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00
89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22
The meaning of green field data 00 C0 3D 00 is not very same as that in the description in Section
1.1.1, it is the start address of the data to be flashed in current packet, each packet sent by host
to PLC will include such a start address.
The red field data 75 00 means 0x0075 words data will be flashed.
The orange field data length is (2 × 0x0075) bytes.
1.3
Flash Memory Layout
Table 2 shows flash memory layout.
Table 2.
Flash Memory Layout on F28069
ADDRESS RANGE
0x3D 8000 – 0x3D BFFF
0x3D C000 – 0x3D FFFF
0x3E 0000 – 0x3E 3FFF
0x3E 4000 – 0x3E 7FFF
0x3E 8000 – 0x3E BFFF
0x3E C000 – 0x3E FFFF
0x3F 0000 – 0x3F 3FFF
0x3F 4000 – 0x3F 7FF5
0x3F 7FF6 – 0x3F 7FF7
0x3F 7FF8 – 0x3F 7FFF
Note:
2
PROGRAM AND DATA SPACE
Sector H (16K x 16)
Sector G (16K x 16)
Sector F (16K x 16)
Sector E (16K x 16)
Sector D (16K x 16)
Sector C (16K x 16)
Sector B (16K x 16)
Sector A (16K x 16)
Boot-to-Flash Entry
Point
(program branch instruction
here)
The address increases by 1 per word unit; that means 2 bytes are stored in one addressing room.
Firmware Upgrade Flow
Figure 1 shows the stream flow during firmware upgrade process.
PRIME PLC Device Firmware Upgrade
5
SPRABT5
Figure 1. Firmware Upgrade Stream Flow
3
Set Up DC Network Connection
3.1
Set Up DC Connection
The embedded PRIME DC, which is based on Concerto platform, was used for this application.
®
A PC with Linux OS is required to run the client.
3.1.1 Hardware Connction
1. Apply 15-V power to the EDC board.
2. Connect the UART1 interface to the Linux PC COM port (a USB COM port was used).
3. Connect the power line interface to the PLC modem power line interface.
3.1.2 Operation on the Linux PC
3.1.2.1
Preparation
1. Copy the image file to the Linux file system /tmp. (prime_7.7.1.1.sbin is used as an
example.)
2. Copy the uart_intf, mgmt_cli executables to the /home path.
3. Open a new terminal, and run the following command:
sudo ./uart_intf –c /dev/ttyUSB0
6
PRIME PLC Device Firmware Upgrade
SPRABT5
After running the command, input your Linux root password.
4. Open a new terminal, and run the following command:
./pdc_mgmt_cli –p 56666
If the command executes successfully, the following prompt appears:
>>
5. Use the ? command to get a list of all implemented commands.
3.1.2.2
Commands for DFU
1. Show the node information:
>>get-node-info
2. Download the image file from PC to DC:
>>send-new-image –f /tmp/ prime_7.7.1.1.sbin –p
3. Get the image information in the DC:
>>show-curr-image
4. After the image file is downloaded and the node is connected, start FU with the following
command:
>>start-uc-fu –f /tmp/ prime_7.7.1.1.sbin –e 00:00:00:00:00:12 –p 192
5. Get the FU status:
>>show-uc-fu
6. Cancel the FU process:
>>cancel-fu
3.2
Set Up PLC Modem and Host Connection
3.2.1 Hardware Connection
1. Connect host UART port to the SCIA interface of TMS320F28069.
2. Apply power to the PLC modem + host processor board.
3. Connect the power line interface of the PLC modem to the power line interface of DC.
3.2.2 Software Configuration of the PLC Modem With Host Processor
After power on the host and PLC modem, the host should perform the following process:
1. When power on, the host keeps receiving ReadBlob request from the PLC: 96 00 04 00 01
00 04 00 until the host replies with 96 c0 08 00 01 00 04 00 00 00 00 00.
PRIME PLC Device Firmware Upgrade
7
SPRABT5
2. The PLC sends request: 96 00 04 00 00 00 04 00
The host replies: 96 c0 08 00 00 00 04 00 00 00 00 00
3. Get system information.
Host send: 01 80 04 00 2A 81 00 00
PLC reply: 01 00 34 00 E5 BF 00 00 00 01 02 07 06 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 01 04 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 61 7B B4 26 F0
87
4. Load system information.
Host send: 0C 80 27 00 19 EB 23 45 01 00 01 00 05 03 00 1A 00 06 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 34 00 00 00
PLC reply: 0C 00 06 00 94 E5 00 00 05 00
5. Soft reset the PLC.
Host send: 05 80 06 00 B9 2D 00 00 00 00
PLC reply: 05 00 06 00 E3 16 00 00 00 00
6. The host waits for 2 seconds.
7. The host gets ReadBlob from the PLC modem again and replies with the proper data same
as Steps 1 and 2.
8. Get system information:
Host send: 01 80 04 00 2A 81 00 00
PLC reply: 01 00 34 00 E5 BF 00 00 00 01 02 07 06 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 01 00 00 00 00 00 00 00 12 34 05 00 00 00 00 00 00 00 00 00 C5 08 CA D7 32
B1
9. Attach Request:
Host send: 10 80 0C 00 90 65 CB 80 06 00 00 00 00 00 00 00
PLC reply: 10 00 12 00 B6 7E 00 00 07 30 06 00 00 00 00 00 00 00 00 00 00 00
After completing Steps 1 through 9, DC gets the IEC432 connection with the PLC node.
4
Firmware Upgrade
This chapter describes the communication between the PLC modem and the host processor in
detail using real communication streams.
NOTE: The embedded dash (-) in the stream separates the message header from the data and
is inserted for better readability only.
NOTE: The host receives the image file and saves it to internal or external memory
8
PRIME PLC Device Firmware Upgrade
SPRABT5
1. After the DC triggers a FIRMWARE_UPGRADE request with the start-uc-fu command, the
host receives a WriteBlob (message type is 0x97) request message from the PLC:
Host receives: 97 00 08 00 01 00 04 00 00 01 00 00
Host should reply: 97 C0 02 00 00 00
Host receives: 97 00 08 00 00 00 04 00 AF 4B 59 71
2. After replying to the WriteBlob message, the host receives the
FIRMWARE_UPGRADE.preperation_request message:
Host receives: 13 00 10 00 08 83 00 00 - 01 00 C0 00 36 DE 02 00 71 59 4B AF
Message type: Firmware_upgrade(0x13)
Message subtype: Preparation_request (0x0001)
Page size: (0x00C0)
Image size: (0x0002DE36)
Image CRC: (0xAF4B5971)
Host should reply: 13 80 08 00 88 32 B4 76 - 01 00 00 00
Message type: Firmware_upgrade (0x13)
Message subtype: Preparation_reply (0x0001)
Status: Success (0x00)
3. The host receives the data packets (PRIME image) with the proposed packet size (192
bytes). The message subtype is FIRMWARE_UPGRADE.data_indicate.
Host receives:
13 00 CA 00 E4 79 00 00 - 00 00 00 00 00 00 03 00 00 00 00 C0 3D 00 C2 53 02 00 25 A3
24 5A 56 1F 76 22 B9 C0 28 29 00 68 76 1A 00 7F 2D 69 25 2F 00 3F 25 2F 00 3F 25 2F
00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F
00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 23 98 00 3F 25 2F 00 3F 25 2F 00
3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00
3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00
3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 25 2F 00 3F 1C 86 00 3F 1C 86 00 3F 25 2F 00
3F 1C 86 00 3F 25 2F 00 3F
Message type: Firmware_upgrade (0x13)
Message subtype: data_indicate (0x0000)
Page index: (0x00000000)
Data:
Host should reply: 13 80 12 00 30 DE 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Message type: Firmware_upgrade (0x13)
Message subtype: data_reply (0x0000)
Status: Success (0x0000)
Page index: (0x00000000)
CRC valid flag: (0x0000)
Image CRC: (0x00000000)
PRIME PLC Device Firmware Upgrade
9
SPRABT5
This procedure is repeated until the entire image is sent by the DC and received by the PLC
modem (and the host). PLC packets may be lost during transmission. This results in the host
receiving nonconsecutive page indices. However, the PRIME protocol fixes takes care of that.
When the DC sends out all the pages, the PLC modem tracks the received pages and
requests any missing pages. This mechanism is transparent to the user. The host should
store the packets with an offset based on the particular page index.
The response of the last packet should include the CRC of the entire image, which is
calculated with the CRC32_BlockChecksum() function. (The CRC32_BlockChecksum
function code is in the attached code package). If the CRC is the same value as received by
FIRMWARE_UPGRADE.preparation_request, the host receives the FIRMWARE_UPGRADE.
flash_request message. Otherwise, if the CRC is a different value or the host has not replied
to some packets, the PLC forwards the data packets again until cancel upgrade with the
cancel-fu command on the Linux PC.
4. After all image packets are received successfully by the host (the entire image is received and
the CRC is correct), the host receives a FIRMWARE_UPGRADE.flash_request message from
the PLC modem.
Host receives: 13 00 06 00 DD 2A 00 00 - 03 00
Message type: Firmware_upgrade (0x13)
Message subtype: Flash_request (0x0003)
Host should reply: 13 80 08 00 88 32 DC 9B - 03 00 00 00
Message type: Firmware_upgrade (0x13)
Message subtype: Flash_reply (0x0003)
Status: Success (0x0000)
4.1
Host Converting .sbin Image File to Binary Format, Flashing them to
TMS320F28069
The step-by-step procedure for sending packets to PLC modem follows:
1. The host sends the following to the PLC modem:
94 80 0C 00 59 72 39 A6 - 00 00 00 00 94 D8 02 00
Message type: Firmware_flash (0x94)
Page index: (0x00)
Format: SREC (0x00)
Image size: Could be any value (This is not a necessary parameter and could be any value.)
2. The host receives from PLC modem:
94 00 08 00 C7 85 00 00 - 00 00 00 00
Message type: Firmware_flash (0x13)
Page index: BOF (0x0000)
Status: Success (0x0000)
10
PRIME PLC Device Firmware Upgrade
SPRABT5
3. The host sends packet 1 to the PLC modem. The overall packet size can be
changed, but must be smaller than 256 bytes.
94 80 F8 00 5C AD A1 11 - 01 00 01 00 00 C0 3D 00 75 00 1F 56 22 76 C0 B9 29 28 68 00
1A 76 7F 00 A7 2A 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F
00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00
89 22 3F 00 F2 20 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89
22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22
3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F
00 E0 19 3F 00 E0 19 3F 00 89 22 3F 00 E0 19 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00
89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89
22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22 3F 00 89 22
Message type: Firmware_flash (0x94)
Page index: (0x0001)
Format: Binary (0x0001)
Flash start address: (0x003DC000)
Data length with word unit: (0x0075 – 117 words)
Data (to be flashed to PLC): 117*2 bytes
Upon reception of packet 1 (first with valid data) the PLC modem starts the erase
cycle of internal flash.
4. The host receives the following from the PLC modem:
94 00 08 00 C7 85 70 BA - 01 00 04 00 (Erase pending; the host does nothing for this
message.)
94 00 08 00 C7 85 41 89 - 01 00 05 00 (Erase complete; the host does nothing for this
message.)
94 00 08 00 C7 85 B4 76 - 01 00 00 00 (Erase success; the host can send the next packet.)
The time between erase pending and erase complete takes approximately 800 ms.
During this time, the PLC modem erases flash segments to be written with the new
firmware image.
The host must wait until the success message arrives before taking further actions.
5. The host sends packet 2 to the PLC modem.
The host waits for a reply from the PLC modem (see Step 4) until it receives a
success message.
6. The process repeats until the entire image is transferred.
The host notifies the PLC modem that the entire image has been transferred by
sending the packet with EOF page index.
The host sends the following to the PLC modem:
94 80 0C 00 59 72 74 95 - FE FF 01 00 94 D8 02 00
PRIME PLC Device Firmware Upgrade
11
SPRABT5
Message type: Firmware_flash (0x94)
Page index: EOF (0xFFFE)
Format : Binary (0x0001)
Virtual Parameter: Data in this field is of no use and can be any value. (0x0002D894)
The host receives the following reply from the PLC modem:
94 00 08 00 C7 85 74 F2 FE FF 00 00
7. After receives the EOF page, the PLC modem will reset automatically and the host
should process as described in section 3.2.2.
NOTE:
If the power line connection is broken during the DFU image file transferring from DC
to PLC, the transfer automatically continues after the connection becomes available
again.
References
1. Draft Specification for PowerLine Intelligent Metering Evolution
2. PRIME Host Message Protocol Specification
12
PRIME PLC Device Firmware Upgrade
IMPORTANT NOTICE
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.
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
www.ti.com/consumer-apps
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
www.ti.com/space-avionics-defense
Microcontrollers
microcontroller.ti.com
Video and Imaging
www.ti.com/video
RFID
www.ti-rfid.com
OMAP Applications Processors
www.ti.com/omap
TI E2E Community
e2e.ti.com
Wireless Connectivity
www.ti.com/wirelessconnectivity
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2013, Texas Instruments Incorporated
Download PDF