Technical guidance

Which cable fits which debugger, how to lay out a Tag-Connect footprint properly, and why all of this exists in the first place — the answers are on these pages.

Your board photo

Already using Tag-Connect? A photo of your board helps others decide — how it works, and the terms for publication.

In practice

Tag-Connect on real boards: footprint, cable and application, shown on photos from users.

Pin assignments

Which signal sits on which contact — SWD, JTAG, UART and ST-LINK (STDC14) for the 6-, 10- and 14-pin footprints, with the matching cables.

Microcontrollers

Which cable you need depends on the programming tool, not on the controller. A mapping for SWD debuggers, J-Link, and older architectures such as MSP430, Microchip and Renesas.

FPGA and JTAG

Xilinx, Altera/Intel and Lattice each use their own programming tools with their own connectors. Which cable belongs to which — and where we do not yet stock one.

Where it is used

Where Tag-Connect turns up beyond the development bench: production programming in appliances and vending machines, and the service engineer with a cable in the toolbox.

Build or buy

Why almost every development department ends up building its own programming connector, what that costs — and how we came to distribute the alternative.