Categories

{{ selectedCategory.name }}

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!

OSEK / AUTOSAR: Tasks Profiling

04-Jun-2021

Solution:

1. Open View menu / Analyzer / Analyzer Configuration button.
2. Navigate to App/MCU / Profiler page.
3. Enable OS.
4. You can further control which objects to profile by (un)checking the boxes.


winIDEA supports OSEK tasks profiling. ORTI file is used as a source of information for Profiler configuration (if automatic configuration is used), as well as profiler analysis. 

Tasks and software level interrupts (ISRs2) are the minimum required signals for quality OS profiling. Ideally OS Signaling is traced as well, as it provides additional context deactivation information, which allows better accuracy in case of context nesting (e.g. when is a task preempted by an IRQ, or an IRQ by another IRQ).


More resources: 

Was this answer helpful?

Sorry this article didn't answer your question, we'd love to hear how we can improve it.
Note: This form won't submit a case. We'll just use it to make this article better.

Similar topics

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No similar topics found!

Other topics in the same category

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!