AUTOSAR Classic profiling means profiling the runtime behavior of an AUTOSAR Classic based application, specifically the application itself, the Run-Time Environment (RTE), the Operating System (OS), and other parts of the Basic Software (BSW). Results cover use-cases such as CPU load analysis, event-chain analysis, timing requirements validation, timing constraint validation, OS metric calculation etc.
This Application Note gives an overview of the AUTOSAR Classic Profiling use-case.
The boot-up process of complex SoCs can be quite elaborate and may involve a mixture of SoC-specific bootloaders for the real-time core, often used as the master boot core, and various bootloaders for the application cores.
This Application Note describes how to utilize the ARM System Trace Macrocell (STM) for timing measurement of the boot-up process of complex SoCs, such as the Renesas R-Car family.
This Application Note provides an overview of the on-chip trace architecture and capabilities of the Infineon TriCore AURIX microcontroller family, and introduces two use cases (Multi-Core OS Profiling via DAP interface and Multi-Core OS and Program Trace via AGBT interface) of the AURIX trace infrastructure in combination with the iSYSTEM On-Chip Analyzers BlueBox iC5000, iC5700 or iC6000.
This Application Note describes three approaches for OS scheduling analysis on EB tresos Safety OS. EB tresos Safety OS is a micro-kernel based OS and thus does not follow the approaches known from classic AUTOSAR OS (i.e. OSEK) implementations.
This Application Note describes how to use the winIDEA Analyzer for the timing analysis of the Elektrobit EB tresos AutoCore operating system. Timing analysis records and examines the runtime behavior of operating system objects such as tasks and ISRs.
This Application Note describes how to use the iSYSTEM winIDEA IDE Analyzer for the timing analysis of AUTOSAR Runnables of the two Elektrobit AUTOSAR solutions “EB tresos AutoCore” and “EB tresos Safety”.
Online Help
Documentation