Vector MICROSAR Profiling: No data is shown or other general issues

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 your trace recording doesn’t trigger (i.e., stays in WAITING or SAMPLING), refer to the architecture-specific documentation and do a manual hardware trace configuration.

Possible solution

1. Assuming you have been able to record some data, open the Trace Window and search for the recorded events.

• If you are using data trace, look for write events to your variable of interest.
• When using RH850 software tracing, search for DBPUSH or DBTAG instructions.
• When using program flow tracing, search for program flow instructions.

2.  Configure a data or code section in the winIDEA Analyzer configuration to visualize the events of interest in the timeline.

For example, if you want to verify that write accesses to isystem_trace have been recorded as expected:

1. Navigate to the Profiler configuration, and enable data trace.
2. When you record a new trace, you should see the variable changes in the Profiler Timeline. If it does not change, there is an issue with the underlying trace configuration and not the operating system profiling.

More resources in winIDEA Help

• Vector MICROSAR Profiling
• Trace Configuration
• RH850 Software trace