The standard 14-pin JTAG connector is outlined in red. The Tag-Connect is outlined in yellow.
20140509 - Chip
I want to replace my standard 7x2 JTAG connector with a Tag-Connect. This will reduce the footprint on the board and save me the time and expense of mounting a through-hole connector by hand.
The standard 14-pin JTAG connector is outlined in red. The Tag-Connect
is outlined in yellow.
This is the TagConnect TC2050 cable the connects between the MSP430
programmer and the target board.
This is the TagConnect cable connected to the TI MSP430 programmer and
my BlinkMtr01 board. Note that the TagConnector is firmly attached to
the board.
This is the schematic showing how the TagConnect pads are connected to the 14-pin JTAG header.
| Signal | 14pin | TagConnect |
|---|---|---|
| TDO/TDI | 1 | 6 |
| Vcc/Tool | 2 | -- |
| TDI | 3 | 8 |
| Vcc | 4 | 5 |
| TMS | 5 | 2 |
| TCK | 7 | 4 |
| TEST | 8 | -- (?) |
| GND | 9 | 3 |
| /RST | 11 | 10 |
Pins 1, 7, and 9 on the TagConnect are not connected.
This schematic uses external power to drive the board. If I want to drive the board using power from the JTAG programmer probe, I would connect to JTAG14:pin2 and TagConnect:pin1. (Correct?)
I am able to access, program, and debug the target MSP430 processor using the 14-pin connection. When I try to use the TagConnect, the CodeComposer programmer complains about "Unknown Device". This is the error that is displayed when the programmer is unable to read the DeviceID from the target processor.
What is the problem?
=== Solved ===
I had the TagConnect pins wrong in my component pattern:
WRONG: 6 7 8 9 10
1 2 3 4 5
CORRECT: 10 9 8 7 6
1 2 3 4 5
Also, my pin mapping was completely wrong. The map should be:
| Signal | 14pin | TC2050 |
|---|---|---|
| TDO/TDI | 1 | 1 |
| Vcc/Tool | 2 | 2 |
| TDI | 3 | 3 |
| Vcc | 4 | 4 |
| TMS | 5 | 5 |
| -- | 6 | 6 |
| TCK | 7 | 7 |
| TEST | 8 | 8 |
| GND | 9 | 9 |
| -- | 10 | -- |
| /RST | 11 | 10 |
| -- | 12 | -- |
| -- | 13 | -- |
| -- | 14 | -- |