User manual
STice features UM0036
272/385 Doc ID 7705 Rev 11
1. In the main window, from the Debug Instrument menu, select Profiling Session
Start.
2. Start execution of your application or continue execution if it is stopped at a breakpoint.
3. Continue application execution until it reaches the next breakpoint, or until the end of
the program. You can have as many breakpoints as you like, and they should be placed
anywhere that you wish to examine further in the program.
4. In the main window, from the Debug Instrument menu, select Profiling Session
Stop.
The results are displayed in the Coverage and Profiling Analysis window.
Note: In the lapse of time between starting the profiling session and starting your application, the
coverage and profiling counters remain at zero. Each time application execution stops at a
breakpoint, or at the end of the program, the counters are frozen.
The results displayed are dependent on the coverage and profiling settings. Configuration
settings are described in Section 9.2.1. For information on interpreting the results, refer to
Section 9.2.3: Reading coverage and profiling results.
9.2.3 Reading coverage and profiling results
When you run a coverage and profiling session during the execution of your application, the
test results depend on the profiling mode you select:
● Code coverage and profiling on page 272
● Data coverage and occurrence profiling on page 274
The STVD graphical user interface presents the coverage and profiling analysis results as
shown in Figure 205, and Figure 207.
Code coverage and profiling
To obtain the coverage and profiling results such as those shown in the Coverage and
Profiling Analysis window in Figure 205, you must run a profiling session with the option
Code coverage and profiling selected in the Mode field (see Section 9.2.1, step 2.) For
information on running a profiling session, see Section 9.2.2.
When you stop the profiling session, the Coverage and Profiling Analysis window is
displayed. It contains two tabs:
● A Functions/Instructions View
● A Source View, which is displayed optionally
Functions/Instructions View
On the Functions/Instructions view, the test results are displayed by function or
instruction, with the following fields for each function or instruction:
● Function
Indicates the name of the function in the application source files; function names
expand to show source lines and instructions.
● Location
Indicates the start address in memory in hexadecimal format.
● Time (ns)
Indicates the total time spent executing code in the selected component (function, or C
line or Assembler instruction) in nanoseconds.