ARTI-Compliant Profiling of AUTOSAR Classic Platform

The embedded tools company
ARTI: OS and RTE Runtime Profiling
Standardized Trace Export to Timing Verification Tool
TRACE32 Tools



ARTI: OS and RTE Runtime Profiling


TRACE32 ARTI profiling for AUTOSAR Classic Platform is based on an instrumented trace. The trace data generated for ARTI profiling requires a medium trace bandwidth and can be streamed to the host computer at program runtime. This allows very long recording times.

Standardized Trace Export to Timing Verification Tool

TRACE32 can export the trace information to timing verification tools such as INCHRON´s chronSUITE, Vector´s TA Tool Suite, and others. It uses the MDF format standardized by ASAM ARTI for this purpose.

TRACE32 Tools

The ARTI ECU description and the activated trace hooks that generate the OS and RTE information form the basis for the ARTI profiling for AUTOSAR Classic Platform. The implementation of the trace hooks is done by the Arti Module provided by Lauterbach. This module is AUTOSAR vendor independent and has to be linked to the final application.

Its task is to write the information received from the trace hooks to the ARTI variables and to open a trace channel to transfer these writes to a trace buffer that can be evaluated with TRACE32. This implementation allows the following TRACE32 tools to be utilized.

Cortex®-R, Qorivva MPC5xxx/SPC5, RH850

Since the Lauterbach trace hook implementation writes the OS and RTE information to ARTI variables, data trace messages are generated by the trace generation logic for Cortex-R, Qorriva, and RH850. ARTI profiling can therefore be performed with the well-established TRACE32 PowerTrace range of tools.


Since the Lauterbach trace hook implementation writes the OS and RTE information to ARTI variables, DWT/ITM trace messages are generated for Cortex-M. If the real-time processor consists exclusively of Cortex-M cores, the µTrace® for Cortex-M® tool can be used for ARTI profiling. In heterogeneous multicore processors, the DWT/ITM trace is merged with the core trace streams of the other cores.

AURIX™ TriCore™

To obtain profiling data for all cores, the Lauterbach trace hook implementation writes to a dedicated address range that allows tracing write accesses of all cores. Since the bandwidth of 30 MByte/s is sufficient, DAP streaming can be used for ARTI profiling (see CombiProbe 2 for TriCore DAP tool). The AGBT/SGBT off-chip trace and the onchip trace are also suitable for ARTI profiling. Please note that the onchip trace cannot be streamed directly to the host computer.

Copyright © 2023 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany   Impressum     Privacy Policy
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 02-Jan-2023