Specifications

Table Of Contents
ARM Debugger 1 4 5 T a r g e t A d a p t i o n
©1989-2014 Lauterbach GmbH
Target Adaption
Probe Cables
For debugging two kind of probe cable can be used to connect the debugger to the target:
“Debug Cable” and “CombiProbe”
The CombiProbe is mainly used on Cortex-M derivatives or in case a system trace port is available because
it includes besides the debug interface a 4 bit wide trace port which is sufficient for Cortex-M program trace
or for system trace.
For off-chip program and data trace an additional trace probe cable “Preprocessor” is needed.
Interface Standards JTAG, Serial Wire Debug, cJTAG
Debug Cable and CombiProbe support JTAG (IEEE 1149.1), Serial Wire Debug (CoreSight ARM), and
Compact JTAG (IEEE 1149.7, cJTAG) interface standards. The different modes are supported by the same
connector. Only some signals get a different function. The mode can be selected by debugger commands.
This assumes of course that your target supports this interface standard.
Serial Wire Debug is activated/deactivated by SYStem.CONFIG SWDP [ON | OFF] alternatively by
SYStem.CONFIG DEBUGPORTTYPE [SWD | JTAG]. In a multidrop configuration you need to specify the
address of your debug client by SYStem.CONFIG SWDPTARGETSEL.
cJTAG is activated/deactivated by SYStem.CONFIG DEBUGPORTTYPE [CJTAG | JTAG]. Your system
might need bug fixes which can be activated by SYStem.CONFIG CJTAGFLAGS.
Serial Wire Debug (SWD) and Compact JTAG (cJTAG) require a Debug Cable version V4 or newer
(delivered since 2008) or a CombiProbe (any version) and one of the newer base modules (Power Debug
Interface USB 2.0, Power Debug Ethernet, PowerTrace or Power Debug II).
Connector Type and Pinout
Debug Cable
Adaption for ARM Debug Cable: See http://www.lauterbach.com/adarmdbg.html.
For details on logical functionality, physical connector, alternative connectors, electrical characteristics,
timing behavior and printing circuit design hints refer to ”ARM JTAG Interface Specifications”
(arm_app_jtag.pdf).