Profiled data can be exported to the MDF format. For other export options, refer to the chapter Profiler Export.
MDF files generated by winIDEA conform to the ASAM ARTI MDF standard. Regardless of whether you use an AUTOSAR operating system or not, information about several kinds of operating system objects can be exported, each corresponding to an ARTI trace class (when using a correctly configured Profiler XML file). These files can then be imported into timing analysis tools.
To create a Profiler XML, use the iSYSTEM Trace Configuration Helper iTCHi.
For Vector MICROSAR, you can follow the steps in iSYSTEM Webinar – Trace-Based Vector MICROSAR Timing Analysis 2022 Edition to create the configuration.
To choose which kinds of objects to export, click the Options button in the Export dialog, which opens the Export MDF Options dialog.
Each of these options corresponds to an ARTI trace class.
Generates an AR_CP_OS_TASK and/or AR_CP_OSARTI_TASK data group (depending on how operating system-specific task states are mapped to ARTI task states) containing information about the state of each task at any point in time. This requires a profiler XML file generated by iTCHi.
Generates an AR_CP_OS_CAT2ISR data group containing information about when each interrupt service routine was called. This requires a profiler XML file generated by iTCHi.
Generates an AR_CP_OS_SPINLOCK data group containing information about when each spinlock was acquired and released. This requires a profiler XML file generated by iTCHi.
Generates an AR_CP_RTE_RUNNABLE data group containing information about when each runnable object was started and when it returned. Assuming that the profiler is aware of runnable objects, this option requires no extra configuration.
Generates a USER_DATAPOINT data group containing information about writes to profiler objects of level None. Those objects must be specified in the profiler XML file.