Difference between revisions of "How many connections are required for JTAG"
From MKRD.info Wiki
(Created page with "The JTAG interface standard requires the following connections: TDI (Test Data In) TDO (Test Data Out) TCK (Test Clock) TMS (Test Mode Select) However, when designing your...") |
|||
| Line 2: | Line 2: | ||
TDI (Test Data In) | * TDI (Test Data In) | ||
TDO (Test Data Out) | * TDO (Test Data Out) | ||
TCK (Test Clock) | * TCK (Test Clock) | ||
TMS (Test Mode Select) | * TMS (Test Mode Select) | ||
| Line 11: | Line 11: | ||
TDI | * TDI | ||
TDO | * TDO | ||
TCK | * TCK | ||
TMS | * TMS | ||
TRST (Test Reset) | * TRST (Test Reset) | ||
V<sub>DD</sub> | * V<sub>DD</sub> | ||
GND | * GND | ||
DONE | * DONE | ||
Plus any chip-specific or platform-specific configuration pins. For example, most devices and programmers use the DONE signal to specify that the programming succeeded. | Plus any chip-specific or platform-specific configuration pins. For example, most devices and programmers use the DONE signal to specify that the programming succeeded. | ||
Latest revision as of 14:48, 6 January 2013
The JTAG interface standard requires the following connections:
- TDI (Test Data In)
- TDO (Test Data Out)
- TCK (Test Clock)
- TMS (Test Mode Select)
However, when designing your hobby project with a JTAG interface, allocate at least 8 pins on a header (dedicated header is best), for the following signals:
- TDI
- TDO
- TCK
- TMS
- TRST (Test Reset)
- VDD
- GND
- DONE
Plus any chip-specific or platform-specific configuration pins. For example, most devices and programmers use the DONE signal to specify that the programming succeeded.
