ECU software debugging via XCP protocol saves time and effort
The debugging interface is often difficult to access, especially for ECUs already installed in the vehicle. With their cooperation, Vector and Lauterbach are reacting to the demands of the automotive industry for parallel use of the interface and providing standardized access to the ECU for measurement, calibration and debugging purposes. This is based on the new ASAM standard “Software Debugging over XCP” adopted in November 2017, to which both partners contributed.
Vector’s VX1000 measurement and calibration hardware is used to access internal data from development or production ECUs. In the entire automotive temperature range, data rates of more than 100 MByte/s can be achieved in test vehicles and on test benches. The XCP slaves of the VX1000 hardware enable connection to the CANape measurement and calibration tool or to other tools with standard-compliant XCP masters. One such XCP master is Lauterbach’s TRACE32 debugger, which can access the ECU and the connected debugging interface via the XCP slave. This debugging configuration requires no expansion of the ECU software at all. The TRACE32 XCP master provides the same debugging features as a hardware-based TRACE32 debugger.
ECU developers benefit from this solution primarily through the interoperability of the Lauterbach debugger with Vector’s VX1000 and CANape measurement/calibration solutions. The two systems can now not only be used cooperatively, but also extend the debugging application spectrum to ECUs with integrated VX1000 installed in the vehicle. This simplifies handling and saves time in the development and testing of ECU software.
More information: https://vector.com/vi_vx1000_en.html and www.lauterbach.com/backend_xcp.html
If you enjoyed this article, you will like the following ones: don't miss them by subscribing to :
