ARTI - ASAM Run-Time Interface
Debugging and tracing enables efficient development, integration, optimization and of software. For analyzing several aspects - especially timing aspects - it becomes essential to link the debugging and tracing data to the scheduling of the system. verification
Goals for Standardization
We propose to create a new set of data exchange formats called "ASAM Run-Time Interface" (ARTI), which shall simplify debugging & tracing of software modules and analyzing their real time behavior. ARTI shall define the following data exchange formats:
- ARTI ECU Description Format
- ARTI Event Description Format
- ARTI Trace Format
- ARTI Profiling Format
ARTI shall function as a standardized interface between debugging & tracing tools on the one hand and trace-visualization tools as well as timing analysis tools on the other. The interface shall ease and speed up the debugging, tracing and of system behavior as well as round-trip engineering. verification
Good interoperability of individual tools of a tool chain provides complete round-trip engineering from the model down to hardware and back - covering several software levels and several phases of the V-model.
ARTI shall especially provide:
- Support of “OS Awareness”, for example examination of OS specific tasks, threads etc.
- Support of distributed systems and multi-core
- Support of functional units (e.g. AUTOSAR modules or proprietary software modules)
- Support of instrumentation-based tracing and measurement solutions
Positioning of ARTI in the Tool Chain
To implement the features, ARTI uses a similar approach that the former OSEK-ORTI had, but extends this regarding additional requirements as well as other tracing technologies such as instrumentation-based tracing. Build tools shall export internal information about a software module and emit the configuration as a separate file (“ARTI file”).
The information therein shall allow debugging and tracing the behavior of this module. Additional tools will collect all ARTI files and allow selecting specific items to trace and create tracing hook files for a specific trace channel (e.g. internal buffer, hardware trace buffers, etc.). The build environment creates the final application, which then can be used on the target hardware. Debugging and tracing tools can read the ARTI files and are “OS aware”, giving additional debugging and tracing features to the developer. These tools can export trace-files, which in turn can be used by trace analysis tools for extended timing analysis, profiling, optimization etc.
Relationship to Other Standards
ASAM ARTI aligns with ARTI, a AUTOSAR defining a unified interface between specification modules and debugging & tracing tools. AUTOSAR ARTI defines the interfaces necessary to generate an executable with excellent debugging/tracing/timing-analysis support and ASAM ARTI defines the data exchange formats relevant for debugging, tracing and analyzing the executable. AUTOSAR
A similar coupling of ASAM and standards has successfully been used for many years with ASAM AUTOSAR-2 MCD ( MC) and the corresponding M&C support data in the A2L Software Component Template. AUTOSAR
Please register by Dec 10, 2018