Software instrumentation based tracing for the verification of timing of embedded systems is becoming more and more important. This applies to single-core projects but even more to the increasingly common multi-core projects. Just as the need for visualization increases, hardware tracing solutions run into bandwidth limitations.
The way in which software instrumentation is implemented depends on the operating system in use. So far, there is no standard. The OSEK/AUTOSAR task hook routines are, for various reasons, unable to support effective tracing.
With OStimHooks we have created a standard, which defines a unified interface between the operating system and timing measurement and tracing tools. At the core is a highly efficient measurement or tracing technology and also simple implementation.
OStimHooks has been presented to the AUTOSAR timing group and is being continued within the specification of the AUTOSAR Run-Time Interface (ARTI).
Click here to download the OStimHooks standard as a PDF file.
Until now there was no standard for exchange of timing information between tools. OT1 is GLIWA's offering, which is gradually being adopted by timing tool suppliers, research groups and research projects.
OT1 has been presented to the AUTOSAR timing group. The goal is to implement the standard with partners, to develop it further and, if appropriate, to make part of the AUTOSAR standard.
Read more at the dedicated OT1 website. There you will find the standard available as a free download.
When integrating T1 into an embedded software project, GLIWA provides template C source modules. These provide the required interfaces and tell the user in comments what needs to be done. These templates are formatted using clang-format for which the configuration file can be found here for download. Using this clang-format configuration file for the GLIWA templates instead of any other clang-format configuration files avoids massive changes to the templates when editing them. This simplifies browsing the differences.