Calibration and Debugging Simultaneously: Techniques for Utilizing the XCP Protocol
Calibration and debugging with just one port. A smart choice for XCP.
◆ What is XCP? In product development involving "control," such as in automobiles and general industrial equipment, there is a process called "calibration." This involves measuring and adjusting internal parameters of the ECU, actuators, and sensors in the state of the final product. XCP (Universal Measurement and Calibration Protocol) is a protocol that realizes this via communication methods such as CAN and Ethernet. ◆ Switching between calibration and debugging is cumbersome! There is a need to perform debugging even in the late stages of development, such as during calibration. However, both processes generally use the same debugging interface for ECU access, which cannot be used simultaneously, necessitating a switch. ◆ No need for switching with XCP debugging! By sending debugging commands over XCP communication in a way that overlays the XCP protocol, calibration and debugging can coexist. This eliminates the hassle of physical exchanges and improves development efficiency. Even with debugging via XCP, many world-class debugging features such as multi-core debugging, OS recognition, and on-chip tracing can be utilized.
basic information
◆Simultaneously perform debugging, measurement, and calibration of ECUs You can execute all ECU development tasks without switching tools or connecting multiple tools at the same time. The debugger accesses the ECU's debug port via the XCP tool and can perform the same tasks as a hardware debugger. At the same time, the XCP tool collects ECU data and adjusts parameter data through the target's debug port. ◆Tool-agnostic concept The XCP debugger is based on the software stack used in our PowerDebug system. Therefore, you can utilize the full feature set familiar from our hardware debugger, the same user interface, and almost the same functionality. ◆Debugging ECUs installed in vehicles By leveraging the infrastructure of XCP tools, you can debug ECUs located deep within the final housing in the engine compartment. This allows for effective discovery and analysis of software issues that only occur in the field.
Price information
Please contact us.
Delivery Time
Model number/Brand name
TRACE32
Applications/Examples of results
Mainly software development tools for embedded microcontrollers and microprocessors.
Line up（11）
| Model number | overview |
|---|---|
| LA-9015L 1 User Floating License XCP RH850 Debug Backend | Debugging solution for RH850 |
| LA-8889L 1 User Floating License V850/RH850 Front End | Debugging solution for RH850 |
| LA-8890L 1 User Floating License Arm Frontend | Debugging and On-Chip Trace Solutions for Arm |
| LA-9014L 1 User Floating License XCP Cortex-M Debug Backend | Debugging and On-Chip Trace Solutions for Arm Cortex-M |
| LA-9009L 1 User Floating License XCP Cortex-A/R Debug Backend | Debugging and On-Chip Trace Solutions for Arm Cortex-A/R |
| LA-9001L 1 User Floating License Arm Trace License | Arm Debugging & On-Chip Trace Solutions |
| LA-8893L 1 User Floating License TriCore Front End | Debugging and on-chip trace solution for TriCore equipped with HSM. |
| LA-9010L 1 User Floating License XCP TriCore Debug Backend | Debugging and on-chip trace solution for TriCore with HSM support. |
| LA-9011L 1 User Floating License TriCore ED Trace License | Debugging and on-chip trace solution for TriCore equipped with HSM. |
| LA-8890L 1 User Floating License Arm Front End | Debugging and on-chip trace solution for TriCore equipped with HSM. |
| LA-9014L 1 User Floating License XCP Cortex-M Debug Backend | Debugging and on-chip trace solution for TriCore equipped with HSM. |
