The solution is based on Vector´s Autosar Classic basic software Microsar and runs on TriCore Aurix Processors from Infineon. A typical Aurix 2G processor has up to six TriCore CPUs. However, the on-chip trace and trigger logic does not support simultaneous tracing of all of them. Accurately comparing the Operating System and Autosar RTE runtime measurements against the system requirements was often rather demanding. This often led to increased efforts for developers.
Lauterbach and Vector have jointly developed a solution to simplify timing analysis, especially in Autosar multicore architectures. For this purpose, Microsar tracing hooks are used. They trigger dedicated hardware trace features for an efficient trace recording which is bandwidth and performance efficient. This involves programming the on-chip trigger logic of the Aurix device. Furthermore, a ready-to-use trigger program is provided by Lauterbach. Developers of embedded automotive systems now can measure their systems and fine-tune them using the tools at hand.
The solution is compatible with TriCore devices featuring MCDS, MCDSlight (TC3xx only) and miniMCDS (TC3xxonly) and is supported by the TRACE32 PowerTrace II, PowerTrace Serial and CombiProbe 2 trace tools. Since the bandwidth of the generated trace is resource-saving, it can be streamed to a file on the local hard disc in order to extend the time for data collection.
Once the trace data has been collected, it can either be analyzed in TRACE32 or directly exported to the option TA.Inspection from Vector´s TA Tool Suite where a detailed analysis of timing events, response times and utilization can be performed.
Lauterbach said it will have a demonstration available at Embedded World.
A detailed description of this process is available in the Vector KnowledgeBase at kb.vector.com.