New Functions for Existing Controllers
The dSPACE prototyping systems are ideal for developing new functions for existing ECUs or for previous or prototype versions of ECUs. The new functions are implemented on the dSPACE prototyping system, while the ECU executes the existing code and takes care of input/output. Complex ECUs and short development cycles often do not allow all the software functions for new ECU generations to be developed from scratch. In these cases, existing code can simply be adapted and extended by this method, which is known as “bypassing”. The communication between the ECU and the prototyping system runs via dedicated ECU interfaces, for example, via DPMEM POD, on-chip-debugging interfaces (such as JTAG/Nexus, JTAG/OCDS, JTAG/SDI, JTAG/H-UDI, NBD, AUD/AUD2), XCP on CAN, XCP on Ethernet (UDP/IP), XCP on FlexRay, and CCP. Task execution on the two systems is synchronized. Sensors and actuators are interfaced via the existing harness of the ECU, and only the I/O which is additionally required needs to be connected to the prototyping system.
dSPACE supports a broad range of automotive microcontrollers for function bypassing.
For a list of microcontrollers and their corresponding on-chip debug ports supported by dSPACE’s generic serial interface (DCI-GSI1), please refer to Microcontrollers Supported By the DCI-GSI1
The dSPACE prototyping systems are ideal for developing new functions for existing ECUs or for previous or prototype versions of ECUs. The new functions are implemented on the dSPACE prototyping system, while the ECU executes the existing code and takes care of input/output. Complex ECUs and short development cycles often do not allow all the software functions for new ECU generations to be developed from scratch. In these cases, existing code can simply be adapted and extended by this method, which is known as “bypassing”. The communication between the ECU and the prototyping system runs via dedicated ECU interfaces, for example, via DPMEM POD, on-chip-debugging interfaces (such as JTAG/Nexus, JTAG/OCDS, JTAG/SDI, JTAG/H-UDI, NBD, AUD/AUD2), XCP on CAN, XCP on Ethernet (UDP/IP), XCP on FlexRay, and CCP. Task execution on the two systems is synchronized. Sensors and actuators are interfaced via the existing harness of the ECU, and only the I/O which is additionally required needs to be connected to the prototyping system.
dSPACE supports a broad range of automotive microcontrollers for function bypassing.
For a list of microcontrollers and their corresponding on-chip debug ports supported by dSPACE’s generic serial interface (DCI-GSI1), please refer to Microcontrollers Supported By the DCI-GSI1
|
| External bypassing: new functions run on the prototyping system, while unchanged algorithms stay on the ECU. |
