JTAG Connectors

From Texas Instruments Embedded Processors Wiki

Jump to: navigation, search

Translate this page to

JTAG Connectors

There are several types of JTAG connectors that are utilized.
The XDS510 and XDS560 product lines support most of the JTAG_Connectors types. XDS100 also implements JTAG connectors.
For XDS560 Trace and Trace enabled devices that export through the pins, please see 60 Pin Trace Header. Note that a 60 pin header is not needed for Embedded Trace Buffer useage. This just utilizes JTAG, but is only available for selected devices.
For MSP430 see JTAG (MSP430) for details.

You may also want to review XDS Target Connection Guide

Documentation

Emulation and Trace Headers Technical Reference Manual SPRU655
The document SPRU641 "Designing for JTAG Emulation Reference Guide" describes the 14-pin JTAG connector and target board electrical requirements for XDS510 JTAG support (despite it's title it is not specific to the TMS320C6000 DSP). Also see your Emulator manufacturer's documentation for emulator specific information.
The XDS560 header document SPRU589 is available here
The XDS560 Trace 60 pin header guide is here. For Trace, you may also want to consider reading "Common Trace Transmission Problems and Solutions" here.
A useful document is SPRA439 here.

Pinout

For the TI 60 pin connector and the MIPI 60 pin connector, please check here.
For MSP430 see JTAG (MSP430) for details.

Pin	TI 14-Pin 0.10" 2 row Molex Target card connector:SAM-TSM-17-DV	Compact TI 20-Pin (CTI) Samtec 0.05" 2 row Molex Target card connector:FTR-110-51-S-D-06 Emulator connector: RSM-110-02-S-D	ARM 20-Pin 0.10" 2 row Molex Target card connector:SAM-TSM-110-DV Emulator connector: SSW-110-22-G-D-VS	ARM 14-Pin 0.10" 2 row Molex (Not recommended)
1	TMS	TMS	VTRef	VTRef
2	TRSTn	TRSTn	VSupply	GND
3	TDI	TDI	TRST	TRST
4	TDIS	TDIS	GND	GND
5	VTRef	VTRef	TDI	TDI
6	KEY	KEY	GND	GND
7	TDO	TDO	TMS	TMS
8	GND	GND	GND	GND
9	RTCK	RTCK	TCK	TCK
10	GND	GND	GND	GND
11	TCK	TCK	RTCK	TDO
12	GND	GND	GND	SRST
13	EMU0	EMU0	TDO	VTRef
14	EMU1	EMU1	GND	GND
15		SYSRST#	SRST
16		GND	GND
17		EMU2	DBGRQ
18		EMU3	GND
19		EMU4	DBGACK
20		GND	GND

Connector Information

TI 14-pin Header Information

Manufacturer: Samtec USA
Model Number: TSM-17-DV
Manufacturer’s Overview: http://samtec.com/technical_specifications/overview.aspx?series=TSM
Example: TSM-107-01-L-DV-006
Keyed header for target card: 3M has part number 2514-6002UB. Digikey has the part and the orderable number is MHB14K-ND.(Note this is shrouded, most connections are unshrouded)

TI 20-pin Header Information

Manufacturer: Samtec USA
Model Number: FTR-110-51-S-D-06
Manufacturer’s Overview:

http://www.samtec.com/technical_specifications/overview.aspx?series=FTR

Recommended Connector: RSM-110-02-S-D

Manufacturer:	OUPIIN (http://www.oupiin.com/)
Model Number:	2212-2X10G00D/2.8-1P6B (surface mount / mate length is 2.80 mm / 1 pin # 6 pulled Bulk package) 2212-2X10G00D/2.8-1P6U (surface mount / mate length is 2.80 mm / 1 pin # 6 pulled tube package)
Manufacturer’s Overview:	http://www.oupiin.com/
Recommended XDS Connector:	2212-2X10G00D/2.8-1P6B or 2212-2X10G00D/2.8-1P6U

ARM 20-pin Header Information

Manufacturer: Samtec USA
Model Number: TSM-110-DV
Manufacturer’s Overview:

http://samtec.com/technical_specifications/overview.aspx?series=TSM

Recommended Connector: SSW-110-22-G-D-VS

Adapters

JTAG Adapter Overview

There are two types of connectors:

Emulator-This is the connector on the emulator/JTAG ICE/UIF/XDS unit
Target-This is the connector on the target card

Types of adapters:

Pin Converters-Passive conversion of one connector type to another
Adapter-Some active components for different purposes. Ex: Addition of adaptive clocking, buffering of TCK/RTCK signals, Isolation, etc.

JTAG connectors cross reference

TI Part Number, Link to product, or 3rd party product Number

Target connector	10-pin ARM	14-pin TI	20-pin TI	20-pin ARM	60-pin TI	60-pin MIPI	microSD
Emulator Connector	10-pin ARM	14-pin TI	20-pin TI	20-pin ARM	60-pin TI	60-pin MIPI	microSD
10-pin ARM	N/A	Roadmap	Roadmap	MDL-ADA2
14-pin TI		TMDSADP1414-ISO¹ or TMDSADP1414²³⁴	TMDSADP1420²³⁴ or TMDSADPEMU-20T³	TMDSADPEMU-20A³	TMDSADP1460	Roadmap
20-pin TI		Usually supplied by manufacturer with emulator. Check manufacturer.	N/A	Usually supplied by manufacturer with emulator. Check manufacturer.	Usually supplied by manufacturer with emulator. Check manufacturer.	Roadmap	Roadmap
20-pin ARM	MDL-ADA2	Lauterbach LA-7748⁵	TMDSADPEMU-20T³	TMDSADPEMU-20A³		Roadmap
60-pin TI		Usually supplied by manufacturer with emulator. Check manufacturer.			N/A	Roadmap
60-pin MIPI		Usually supplied by manufacturer with emulator. Check manufacturer.	Usually supplied by manufacturer with emulator. Check manufacturer.	Usually supplied by manufacturer with emulator. Check manufacturer.	Usually supplied by manufacturer with emulator. Check manufacturer.	N/A

¹ Isolation adapter
² Voltage Translation
³ RTCK Signal Boost
⁴ Adaptive Clocking
⁵ http://www.lauterbach.com/frames.html?order/ord__7748.html - Code JTAG-ARM-CON-20-TI14

Part numbers:

Roadmap

Various standards organizations have tried to standardize on connectors. TI has several standards already in use. One particular area where significant work has been done is the high speed tracing connectors. This is being driven by technology changes and the changing needs for debug.
MIPI has a recommendation for a high speed 60 pin trace connector which can provide the flexibility needed for future tracing needs. The recommended connector is the QSH-030-01 (PCB/Target) and QTH-030-01 (Cable/Emulator) connectors from Samtec.
MIPI Connector recommendation is here. Pin mapping for the 60 pin MIPI connector is in this ocument.
IEEE 1149.7 does not require a specific connector. Instead, it will simply have the TMS pin become TMSC. When it becomes TMSC, the pin will be bi-directional instead of uni-directional.

FAQ

Q: What are the EMU0/1 pins used for?

A: The EMU0/1 pins can be used for High Speed RTDX (HSRTDX) or cross-core triggering (ex: one device halts and signals the others to halt, see Advanced Event Triggering). For selected devices, these pins are used for wait-in-reset (ex: TMS320F2808, etc. --> Please see the device datasheet/TRM for details). For selected devices, these pins may also be used to transfer instrumentation and trace information.

Q: What are the EMU2-x pins used for?

A: These are reserved for high speed instrumentation information and trace information.

Q: What is the difference between the TI 20 pin connector and the ARM 20 pin connector?

A: The TI 20 pin connector is physically smaller than the ARM 20 pin connector. Becuase it uses a simple "stake" connector, it should also be inexpensive. The TI 20 pin connector has additional EMU2, EMU3, and EMU4 pins, which allow it to carry instrumentation data that are available on selected devices. The TI 20 pin connector also features a System Reset (Emulation) pin.

Q: Do I have to use the ARM 20 pin connector to be able to use Adaptive Clocking?

A: No. Adaptive clocking has to do with the generation of of the clock signal based on the return clock. Your emulator needs to support this feature, or an adapter is needed. See Adaptive Clocking#Solutions for solutions. The header just needs to have a RTCK and TCK signal.

Q: Which connector should I use?

A: Use the 60 Pin Trace Header only if your device supports processor trace to the pins. Learn more about XDS560 Trace or from your processor datasheet. If your device is a 24x/28x, you should utilze the TI 14-pin connector. If you do not utilize CCS and XDS560/XDS510 as your toolset (ex: Green Hills, Lauterbach, etc.) and you have existing tools that support the ARM 20 pin connector, you should use the ARM 20 pin connector. For all other situations, the standard, recommended connector is the 20 pin compact TI connector. You should also check what connector your emulator product supports. Emulator vendors such as Spectrum Digital and Blackhawk typically include adapters for the 14 pin TI, 20 pin Compact TI, and the 20 pin ARM configurations.

Q: What do I need to do if I have a device with an ARM 9 or ARM 11?

A: These ARM devices require adaptive clocking. Please check the section on Adaptive Clocking

Q: What is a Scan Path Linker?

A: The Scan Path Linker (SPL) is a TI device that is used to configure JTAG scan paths, most often those that connect a motherboard to multiple daughter cards. (This is not the same as the ACT8990 Test-Bus Controller (TBC) device). The scan path linker is used to handle plug-in cards dynamically without breaking the scan path, by reconfiguring the scan path as needed. In general, it is useful whenever your board is in a situation where the scan path can be dynamic, such as during development, when, perhaps not all of the devices on the scan path are populated yet.

The Scan Path Linkers 'ACT8997’, are members of the Texas Instruments SCOPE^TM testability integrated-circuit family. This family of components facilitates testing of complex circuit-board assemblies. These devices also provide buffering of test signals to reduce the need for external logic. For additional information on the SPL device refer to the following TI site:

(sn74act8997) (sn54act8997)

Q: Does the TMDSADPEMU-20T, which translates from ARM 20 pin and TI 14 pin emulators to compact 20 pin TI target cards map the reset line from the ARM connector to the compact 20 pin TI target connector? Also, what pins are buffered.

A: (SRST/SYSRST#) Pin 15 on the compact 20 pin TI target connector is connected to pin 15 of the (SRST/ARM_RSTn) 20 pin ARM target connector. TCK and TCKRET are buffered.

Q: What is the SRST pin for?

A: SRST is the System Reset (Emulation) signal. If tied to the card or device reset line, it allows the debugger to control the reset of the device. For some devices, when debugging boot code the Wait in Reset may use this signal. See System Reset (Emulation) for details on how to use this feature in Code Composer Studio v4.

Q: What is TDIS used for?

A: XDS emulators can use this pin to detect when the target is disconnected from the emulator. It is usually a pull-up in the emulator and GND on the target. The emulator senses the removal of GND.