ORTI-Compliant Profiling of AUTOSAR Classic Platform

For trace protocols that include a data trace, TRACE32 ORTI profiling is based on the information that the operating system writes to its own internal variables. Alternatively, the operating system can write the profiling information into core-related task ID registers like the Nexus PID. The trace data generated for ORTI profiling requires a medium trace bandwidth and can be streamed to the host computer at program runtime. This allows for very long recording times.

TRACE32 can export the timing data to timing verification tools such as INCHRON´s chronSUITE, Vector´s TA Tool Suite, and others.

The ORTI file generated by the AUTOSAR vendor forms the basis for the ORTI profiling for AUTOSAR Classic Platform. The following TRACE32 tools can be used.

ORTI profiling can be performed with the well-established TRACE32 PowerTrace range of tools.

Cortex-M uses a DWT/ITM trace to visualize the write access to the OS internal variables. For real-time processors consisting exclusively of Cortex-M cores, the µTrace® for Cortex-M® tool can be used for ORTI profiling. In heterogeneous multicore processors, the DWT/ITM trace is merged with the core trace streams of the other cores and the TRACE32 PowerTrace tools should be used for this.

Due to limitations of the AURIX TriCore, data trace is generated, in most cases, only for n cores out of r (n ≤ r). Consequently, ORTI profiling cannot be performed for all cores at the same time. DAP streaming can be used for ORTI profiling (see CombiProbe 2 for TriCore DAP tool) as the 30 Mbytes/s bandwidth is sufficient for this purpose. The AGBT/SGBT off-chip trace and the onchip trace are also suitable for ORTI profiling. Please note that the onchip trace cannot be streamed directly to the host computer.