Debugging via XCP

The embedded tools company
Configuration of the Software-only Debugger


Debugging via XCP
Communicate with the target CPU via the ETAS-specific XCP debug extension
Connect to target via the ETAS calibration tools XETK or ES89x+FETK
Almost the same debug feature as TRACE32 hardware-based debugger

C/C++ debugging
FLASH programming
Access to all peripheral devices
Multicore debugging
Autosar-OS aware debugging
Benchmark counters
Cache debugging
Debugging of all auxiliary controllers: GTM, HSM and SCR
Multicore tracing via on-chip trace
Support for TriCore, MPC5xxx, GTM

Link Order
Technical Support
TRACE32 Floating Licenses
Hardware-based TriCore Debugger
Hardware-based Qorivva Debugger


Configuration of the Software-only Debugger

Instead of sending the debug commands entered via the TRACE32 FrontEnd directly to the target CPU via JTAG, all debugging commands are encoded into XCP commands by the TRACE32 XCP Debug BackEnd. The XCP commands are then send over the host computers TCP stack and a network cable to the 3rd party system. The 3rd party system translates the XCP commands back into the low-level debug commands.

Copyright © 2017 Lauterbach GmbH, Altlaufstr.40, D-85635 Höhenkirchen-Siegertsbrunn, Germany  Impressum
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 12-Apr-2017