AUTOSAR Aware Debugging
Realize any kind of AUTOSAR aware debugging
AUTOSAR (AUTomotive Open System ARchitecture) is a global development partnership for developing and establishing an open and standardized software architecture for electronic control units (ECUs) in vehicles. Numerous commercial operating systems are available based on the AUTOSAR standard. Our TRACE32® tools support debugging and tracing of operating systems based on both AUTOSAR Classic Platform as well as AUTOSAR Adaptive Platform. They also support various configurations for the concurrent debugging of AUTOSAR Classic and AUTOSAR Adaptive Platform.
Debugging the AUTOSAR Classic Platform
The AUTOSAR Classic platform uses a static operating system that is based on the OSEK OS and has been extended by AUTOSAR to include a number of functionalities. TRACE32® OS-aware debugging for AUTOSAR Classic based operating systems is activated by loading the ORTI file or the AUTOSAR ARTI description file. Our PowerView software is extended by an menu extension, which provides you access to AUTOSAR OS resources like tasks, alarms, stack coverage, and much more. If you are running multiple AUTOSAR Classic operating systems on multicore SoCs, our TRACE32® tools support the concurrent debugging of them, too. This includes also hypervisor debugging of virtualized systems.
Debugging the AUTOSAR Adaptive Platform
In contrast to the Classic Platform, AUTOSAR uses a POSIX operating system (POSIX Profile PSE51) in the Adaptive Platform. This means that Linux, for example, which has long been used in the automotive sector for infotainment systems and other applications, is also available as an operating system for the Adaptive Platform. In addition to Linux, our TRACE32® tools support all relevant POSIX-compatible operating systems such as QNX, PikeOS or eMCOS.
If you are running multiple AUTOSAR Adaptive Platform-compliant operating systems on multicore SoCs, our TRACE32® tools support the concurrent debugging of them, too. This includes also hypervisor debugging of virtualized systems.
Concurrent Debugging for AUTOSAR Classic and AUTOSAR Adaptive Platform
Due to the almost unlimited support for any multicore configuration our TRACE32® debug and trace tools also support various configurations for the concurrent debugging of AUTOSAR Classic based and AUTOSAR Adaptive compliant operating systems. A typical configuration can be seen in the picture on the right.
What do ORTI and ARTI stand for?
Two standards have been developed in the past to enable debugging with AUTOSAR awareness. Our automotive experts as members of the responsible AUTOSAR standardization committee played a pivotal role in the development of both.
ORTI – OSEK Runtime Interface
ORTI – OSEK Runtime Interface - is a standard interface and file format which provides information about OSEK1 compliant real-time operating systems and AUTOSAR Classic Platform. The specification enables our TRACE32® tools to become OS-aware. Most AUTOSAR/OSEK system builders are able to extract all necessary information of the OS component into a text file, called “ORTI file”. Our TRACE32® debugger can load such an ORTI file and adds some special extensions to itself. This information gives you an inside view of the operating system states.
1: OSEK/VDX: „Offene Systeme und deren Schnittstellen für die Elektronik in Kraftfahrzeugen / Vehicle Distributed Executive”
ARTI - AUTOSAR Run-Time Interface
ARTI - AUTOSAR Run-Time Interface - is a set of standards for debugging and tracing the run-time behavior of embedded systems. Whereas ORTI was specified focusing just on debugging embedded operating systems. The objective of ARTI is to extend the OS awareness by being capable of bringing debugging and tracing to all layers of the software stack and making the debug, trace, and other run-time tools aware of additional AUTOSAR modules such as the RTE. ARTI therefore describes interfaces needed to support static debugging and dynamic tracing.
Perform Timing Analyses of AUTOSAR-based Systems
For analyzing the runtime behavior of an automotive application, you require appropriate tools to measure execution times and check timing requirements. To do that, you have to record hardware events at the instruction level and process trace data into system events at an abstract level. Based on this, a timing tool can compare the results with the system requirements as part of the requirement analysis.
To meet all these requirements, we have jointly developed solutions with several partners, who provide special tools for performing Timing Analysis and provide appropriate software packages for support.
After performing an ARTI Real Time Trace with our TRACE32® tools, you can export the recorded trace data as ASAM MDF (Measurement Data Format) file, which can subsequently processed by the timing tools of our part-ners.
One example of this workflow is described in an Application Brief you can download at the right. It describes a solution for Vector’s AUTOSAR embedded software MICROSAR, using our TRACE32® tools as well as Vector’s TA. Inspection for performing the Timing Analysis.
Simplify Certification of AUTOSAR-based Software with TQSK
Functional safety is a key requirement for safety-critical automotive systems. Qualification also includes the development tools used and their integration into the project environment. Our certified Tool Qualification Support Kit (TQSK) for ISO 26262 provides everything you need to qualify our TRACE32 solutions for AUTOSAR-based automotive software. TQSK proves the suitability of code coverage, debugging, and instruction set simulator for use in automotive projects and reduces your time-to-market, effort, and costs.
Support of Any Popular AUTOSAR Compliant OS
TRACE32® supports all popular AUTOSAR-compliant OSes.
Our TRACE32® software package supports AUTOSAR-compliant OSes for Arm® / Cortex®, MPC55xx, RH850 and TriCore. Both standards ORTI and ARTI are supported. The support includes a OS specific menu extension and the display of OS resources based on system resources exported by ORTI/ARTI files.
Leverage all the TRACE32 OS-Awareness Features
Apart from AUTOSAR support, our TRACE32® OS-aware debugging provides you with several key insights into your applications and the operating systems they are running on, no matter if you use rich operating systems like Linux, real-time Operating Systems (RTOS) or a mixture of all.
On virtualized systems, where multiple OSes are controlled by a hypervisor, our TRACE32® Hypervisor-aware debugging allows you to perform concurrent OS-aware debugging for each guest OS/virtual machine (VM) and display an overview of the overall system.
