Please enable JavaScript to view this site.

winIDEA Help

Version: 9.21.36

Trace window

Trace provides deepest possible insight in the real-time workings of the application. The quality of captured information depends on trace capabilities of the CPU and the used trace tool, and can include:

 

  • Program trace
  • Data trace
  • Instrumentation trace
  • Auxiliary I/O trace

 

Trace view reconstructs the low level captured events to:

  • Program counter movement
  • Instruction flow on assembly level
  • Source code flow
  • Data variable read/write accesses
  • Labels (association between the address and a symbol obtained from the download file)

 

Please refer to the Analyzer Configuration chapter to learn how to configure the Analyzer to record the events you are interested in.

 

 

 

Right click to copy the link address Elements of the Trace window

Once you have the trace recording, you can open the Trace Window by selecting the Trace button TraceView-TraceButton in the Analyzer toolbar.

 

TraceView-WindowSample

 

Right click to copy the link address Trace window toolbar

Icon

Name

Description

ProfilerTimelineSaveButton

Export

Export data.

AnalyzerTraceBut

Configure Signals

Opens a dialog for Signal configuration.

ProfilerTimelineFilterItemsButton

Configure States and Filters

Opens a dialog for State and Filter configuration.

TraceFirstSampleButton

Go to First Function Sample

Caret is moved to the first op-code executed in the current function body – i.e. when execution entered the range, either as it was called or a called function returned to it. If the caret is already located on the first sample in a function, then the caret is moved to the previous last sample in the current function – i.e. when the function exited or called another function.

TraceLastFuncSampleButton

Go to Last Function Sample

Caret is moved to the last op-code executed in the current function body – i.e. before the execution moves to a different function wither as a call or return. If the caret is already located on the last sample in a function, then the caret is moved to the next first sample in the current function – i.e. after the called function returns or the function is called again.

TraceWindownavigation

Location box

Indicates the function to which the indicated instruction belongs.

 

 

Number - Trace sample number, relative to the trigger position. On on-chip traces where multiple actions of the CPU are packed into a single message, the number is encoded as <sample.subsample>

Sample is the trace message count since the trigger.

Subsample is the index of the CPU activity within a single message. In this picture, where on-chip-trace data display is enabled, it is shown how a Nexus IBHM message is decoded into program flow.

 

Address - Associated address of a trace item:

    • Op-code address
    • Address of data access
    • Address or part of address encoded in the trace message

 

Data - Associated data of a trace item:

    • Op-code
    • Value of a data access
    • Data or part of data encoded in the trace message

If only a part of data is valid (e.g. 8-bit data access on a 32-bit CPU), the ignored bits are displayed grayed.

 

Content - Displays the decoded trace item in readable form. The text depends on the trace item class.

 

Time - Time of the trace item.

 

 

bulb

More resources

hmtoggle_arrow0 Trace display settings

 

 

 

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