OVERVIEW
Efficient Debugging of Automotive ECUs – From Prototype to Field
PowerView supports software debugging via XCP, enabling seamless, concurrent debugging and calibration without needing physical access changes. This is ideal for automotive ECU development across all stages.
Key benefits include:
Multicore and OS-aware debugging
On-chip trace
HLL support and flash programming
Full peripheral access
Performance benchmarks
Perfect for both prototype and in-field use.
BENEFITS
Use One Consistent Solution for Every Configuration
As an active member of the XCP Debug Working Group, we partner with leading MC tool vendors like ETAS, Vector, and dSpace to unify ECU debugging and engine data management over a single physical interface.
Our broad support for automotive microcontrollers, architectures, and OSes ensures end-to-end assistance—from silicon design to prototyping and field validation.
Accelerate Development with Tool-Agnostic Debugging
Our XCP-based debugger shares the same software stack as PowerDebug, delivering the full feature set and familiar user experience—no learning curve. New features remain fully compatible across both solutions.
Simultaneous Debug, Measurement, and Calibration
With XCP, you can debug, measure, and calibrate your ECU in parallel—no tool switching required. Our debugger accesses the ECU through the same XCP connection used for data collection and parameter tuning, delivering full debug functionality without extra hardware.
Debug Your ECU Directly in the Vehicle
With XCP infrastructure, you can debug the ECU even when it's installed deep within the engine compartment. This lets you detect and resolve issues that only appear under real-world conditions.
BENEFITS
SUPPORTED ARCHITECTURES
With PowerView software, you can debug a wide range of CPU architectures along with their commonly paired auxiliary cores.
- Arm Cortex-M
- Arm Cortex-R
- TriCore
- RH850
- MPC5XXX
- GTM
HOW IT WORKS
A Deeper Look Into Debugging over XCP
Debugging over XCP uses the Universal Measurement and Calibration Protocol (XCP), standardized by ASAM e.V. and widely adopted for MC applications.
With PowerView, debug commands from the front end are encoded into XCP commands by the XCP debug back end instead of using direct low-level protocols like JTAG, SWD, or DAP. These XCP commands (e.g., memory reads/writes, I/O access) are transmitted via the host’s TCP stack and network to a third-party XCP slave, which converts them back into low-level debug commands for the target.
SUPPORTED XCP TOOLS
Partnering with Leading Vendors
Debugging over XCP builds on an extended XCP standard, ensuring seamless interoperability between our debugger and various MC tools. As an active member of the ASAM Working Group, Lauterbach helps shape and advance the standard, collaborating closely with major MC tool vendors to validate our debug solutions.
VX1000
The VX1000 hardware enables direct access to ECU internal resources like RAM and Flash. Multiple tools can connect simultaneously via ASAM XCP, allowing—for example—software debugging on a near-series ECU in a vehicle while concurrently measuring data or calibrating parameters with CANape.
FETK/XETK
ETAS provides a comprehensive suite for measurement, calibration, and vehicle testing, including INCA software, ES8xx interface modules, and FETK/XETK ECU interfaces. Their products support software debugging using the extended XCP standard. Ask ChatGPT
CONFIGURATION EXAMPLES
Typical TRACE32 Configurations
Debug Solution for RH850
Debug your RH850 based ECU that is connected to an XCP tool.
Debug & On-Chip Trace Solution for Arm Cortex-M
Debug and trace your Arm Cortex-M based ECU that is connected to an XCP tool.
Debug & On-Chip Trace Solution for TriCore with HSM
Debug and trace your TriCore based ECU that is connected to an XCP tool. This allows concurrent debugging of all TriCore CPUs and HSM.
