Bypass of an Entire ECU Functionality. ETAS INTECRIO

ETAS Bypass Concept

Fig. 8-9 OS configuration for a classical ECU function bypass

8.6.3.3

Bypass of an Entire ECU Functionality

One INTECRIO task may contain pre and post write actions from different service points and ECU tasks. This can be used to bypass the entire ECU functionality (consisting of several processes in different ECU tasks), which minimizes the number of interrupts and thus latency. Read signals are not updated while the task runs on the rapid prototyping target. Partial results are sent to the ECU as fast as possible to ensure the currency of the values of other functions.

In the example shown in Fig. 8-10, service points SP 1 and SP 2 belong to a

high-priority ECU task A. Service point SP 3 belongs to a medium-priority ECU task B. Service point SP n belongs to a low-priority ECU task C. The read action of SP 1 and the write actions of all service points are assigned to the same

INTECRIO software task.

Read_F1

F1'

Write_F1

F2'

Write_F2

F3'

Write_F3

…

Fn’

Write_Fn

SW task

F1

SP 1

F2

SP 2

ECU task A

F3

SP 3

ECU task B

Fn

ECU task C

Fig. 8-10 Example: Bypass of an entire ECU functionality

SP n

To achieve this kind of OS configuration, the following steps are required:

INTECRIO V4.7 - User’s Guide 154