This website uses cookies so that we can provide you with the best user experience. To read more about the cookies we use and to change your settings see our Cookies Policy.
When using Automatic Trace configuration (i.e., when Manual Trigger C onfiguration is not selected) and starting the recording, the Analyzer may show a warning: Cannot configure: There are no hardware resources to configure all of the requested areas. The Analyzer attempts to use one POB (...
Trace Configuration Helper (iTCHi) is a set of scripts that can help you configure OS and RTE-aware hardware traces for the winIDEA Analyzer.iTCHi is located in the folder scripts/itchi within your winIDEA installation folder. iTCHi is supported from winIDEA version 9.17.156 on. iTCHi Wiza...
BTF (Best Trace Format) is a CSV-based trace format supported by different timing tool vendors. winIDEA's Analyzer can export OS-aware traces into BTF. Refer to the Export Profiler data to BTF format how-to guide in winIDEA Help.
ASAM MDF4 is a storage efficient binary trace format that is widely used in the embedded industry. In the context of the AUTOSAR ARTI project, MDF has been extended with support for AUTOSAR OS and RTE objects, as well as customizable signals. Possible solution 1.Use iTCHi to create a threa...
When encountering issues with profiling, always verify that the underlying hardware trace configuration works as intended. After recording a trace, you can use the Trace Window or Profiler Timeline Window to verify that events of interest have been recorded. If no events are visible, or if...
There may be occasions when the winIDEA Analyzer displays hexadecimal values instead of the expected object names or states. This outcome is expected when using a Data area as opposed to OS objects. However, when utilizing OS objects, the Analyzer should display the names. If this isn’t th...
The winIDEA Analyzer supports tracing of ISRs via the AUTOSAR ARTI and ORTI, or via the OS trace hooks provided by the OS vendor. However, in some cases, users might want to trace so-called category 1 ISRs, i.e., ISRs that are not managed by the OS, and therefore usually don't have hooks r...