Please enable JavaScript to view this site.

winIDEA Help

Version: 9.21.36

Navigation: » No topics above this level «

Scroll Prev Top Next More


iSYSTEM Analyzer is a powerful tool, which enables you to record the program execution trace, data trace or other trace messages and then analyze these recordings to produce coverage or timing measurements.



Elements of the Analyzer Window

Analyzer window can show several aspects of the recording in different views, which can be toggled from the main toolbar. It is open by clicking the View menu / Analyzer or Analyzer button AnalyzerButtonfrom the main toolbar.



Document pane


Analyzer window toolbar


Profiler Timeline


Coverage Statistics


Trace window




The main toolbar provides access to Analyzer configuration and to toggle display of specialized views.



Analyzer Configuration

Analyzer Configuration window combines trigger, profiler and coverage settings. Analyzer Configuration drop-down menu offers selection and manipulation of trigger configurations. Analysis and Configuration block on the Hardware page offers selection of Profiler and Coverage analysis. If Manual Trigger is selected, manual trigger settings are used; otherwise optimal settings are determined based on the analysis selection.


Begin New Session

A new live analyzer session is started. The acquired data is loaded from the emulation hardware on the host PC and analyzed. The live session will end when either of these situations occurs:

  • debugger trace buffer is full
  • CPU stops
  • The maximum amount of acquired data is reached
  • Session is aborted with the Stop button

Re-analyze Last session

Previously acquired analyzer data can be analyzed again. This off-line analysis is started automatically when the analyzer document is opened. Manually the analysis can be started to gain more information from an existing session, e.g. add or remove some functions from the profiler. The off-line analysis can be stopped with the Stop button.



Stops the active session – live or off-line.

In a live session, Stop will on first click stop data acquisition on the debugger. Upload of the trace buffer and analysis of the loaded data will continue. A second click will stop this too.



Toggles the Trace window display.


Profiler Timeline

Toggles the Profiler Timeline window display. Right-clicking on the document pane opens the context menu from which it is possible to Rename the Profiler Timeline.


Profiler Statistics

Toggles the Profiler Statistics window display.


Coverage Statistics

Toggles the Coverage Statistics window  display. Read more in the Coverage Analysis chapter.


Output Window

Open Output to display possible error, overflows during trace recordings.


Auto Synchronize

If this button is pressed, caret marker position between trace view and timeline view is synchronized. If moved in one view, the other view will scroll to the new position too.



Opens the Options dialog where it is possible to configure:

  • Fonts, colors, Trace, Profiler and Coverage display options
  • How you wish to save the Analyzer recording.

Set Information

Every document can have additional user information associated. Read more in Analyzer Recording information chapter.



Trace recording

Before we can do any analysis, we need to record the program execution, data writes or other information of interest.

  • Read the Analyzer Configuration chapter to learn how to configure the analyzer to record required data for trace, coverage and profiler analysis.
  • Read the Analyzer Recording chapter to learn how to operate the Analyzer once it's configured.



Trace window


Once you have created an analyzer recording, read the Trace window chapter to learn how to interpret the trace output and how to export it for further inspection.



Coverage Analysis - Coverage Statistics window


Code coverage is a metric that is commonly used to determine when the testing of a product is complete, as it can show which parts of the code were exercised during testing. It is often required to produce the coverage measurements when certifying a product under ISO26262, DO-178B or DO-178C standard. iSYSTEM tools produce coverage results based on program execution trace and therefore do not require any code instrumentation.

To read more about the coverage measurements, please refer to the Coverage Analysis chapter.



Profiler Analysis - Profiler Analysis window


Profiler provides timing and count information for the part of the program which has been traced. As such it is most commonly used during development, when developer suspects that timing constraints are being violated. Trace recording, together with the timing analysis can provide insight into what caused the violation.


For more information on profiling and Profiler Inspectors, please refer to the Profiler Analysis chapter.

Copyright© iSYSTEM AG Carl-Zeiss-Str.1 85247 Schwabhausen Germany