AUTOSAR/OSEK OS Awareness
Developing embedded software based on a Real-Time Operating System (RTOS) can be supported by the debugger by making it aware of the underlying RTOS. In other words, the debugger understands the structure of the RTOS and its elements such as tasks, interrupts, alarms, etc..
For applications, based on an AUTOSAR/OSEK compliant OS such as ERIKA Enterprise, the OSEK Run-Time Interface (OTRI) file is a method for describing the structure of the RTOS to the debugger. By reading in the ORTI file generated by the RTDRUID when building an ERIKA-based application, the winIDEA debugger becomes ERIKA Enterprise OS-aware.ERIKA Enterprise OS awareness provides the following features:
- Display of OS Resources and Status
- Run-Time Analysis (Profiler Timeline) of Tasks and Interrupts (ISR Category 1 and 2)
- Analysis of CPU Utilization (Profiler Statistics) of Tasks and Interrupts (ISR Category 1 and 2)
Display of OS Resources and Status
A dedicated windows of the winIDEA IDE reports the resources and the current status of the ERIKA Enterprise OS.
- Currently running Task
- Currently running ISR
- Status of each Task
- Stack Utilization for each Task
Run-Time Analysis of Tasks and Interrupts (ISR Category 1 and 2)
The Trace Analyzer of winIDEA automatically configures the on-chip trace logic of the micro controller, based on the information provided by the ORTI file. The state changes of all ERIKA Enterprise OS objects selected by the user are recorded and displayed by the winIDEA Profiler.
The Trace Analyzer of winIDEA also provides statistical information about OS ojects, such as Tasks and Interrupts.