Contact
In the development of ECU software, besides checking for correct coding, the runtime behavior of the various routines must also be tested. This lets the developer verify that the specified time windows are maintained and that no instabilities occur. However, it is not easy to determine execution times or check for runtime conflicts.
The MICROSAR OS operating system simplifies this job by measuring the execution times of tasks and Interrupt Service Routines (ISR) itself. The developer reads out the measured data via a defined system call. This offers a number of advantages:
- There is no need to insert test code in the application routines.
- It is easy to activate/deactivate the measurement function via a graphic configuration tool.
- Both execution times and disable times are measured.
- Interruptions by ISRs and tasks of higher priority are considered in the measurement of execution time.
Analysis of time behavior is performed with the TimingAnalyzer, a PC-based analysis tool that is included in the scope of delivery of the operating system. As inputs to the TimingAnalyzer, the developer enters the measured execution times of the application’s tasks and ISRs together with task priorities, time limits and the typical cycle time. Based on these data, the TimingAnalyzer checks whether the specified time limits are always maintained by all routines. The computed time behavior is displayed graphically. 
The TimingAnalyzer lets software engineers quickly and easily test different solution scenarios such as regrouping of priorities or swapping out of functions to tasks with lower priority or cycling.
[Please contact us for more information]
