User manual

UM0036 STice features
Doc ID 7705 Rev 11 267/385
There are three counter sizes:
● Small 15-bit occurrence counters with a maximum value of 32767
● Large 30-bit occurrence counters with a maximum value of 1,073,741,823
● 36-bit time counters enabling to record 22.9 minutes of execution with a 50 MHz time
base
Data occurrence counters are enabled when you select Data coverage and occurrence
profiling.
Code occurrence and time counters are enabled when you select Code coverage and
profiling (see Section 9.2.1: Configuring the coverage and profiling settings, step 2.)
The counters record information during a coverage and profiling session as long as your
application is running. If you start execution of your application after having started your
profiling session, the counters remain at zero until the application starts running. When the
application execution stops at a breakpoint, or at the end of the program, the counters are
frozen. (They are unfrozen when the application resumes. When you stop the application,
they are frozen definitively for the current session.)
When an occurrence counter reaches its maximum value, it remains at that value for the rest
of the profiling session. In the results window, it is displayed with a greater than symbol (for
example, > 32767). This is the default behavior. However, because the results of occurrence
profiling are less meaningful if many occurrence counters reach the maximum value, you
have the option to stop the application when any one of the counters reaches the maximum
value (see Section 9.2.1: Configuring the coverage and profiling settings, step 4.)
9.2.1 Configuring the coverage and profiling settings
Before you configure the coverage and profiling settings, you must ensure that:
● Your STice advanced emulation system is properly connected to your PC and to your
application board.
● You have an open debugging session in STVD (see Section 5.3 on page 167).
● Your application is stopped, either because you have not started execution, or because
execution is stopped at a breakpoint.
To configure coverage and profiling settings:
1. In the main window, from the Debug Instrument menu, select Profiling Settings.
The Coverage and Profiling Settings window is displayed, as shown in Figure 202
and Figure 203.
2. In the General section, select the mode:
– Data coverage and occurrence profiling
Indicates whether data has been accessed, and the number of times data is
accessed. See Section 9.2.4 on page 276 for information on reading the results
obtained when you run a profiling session in this mode.
– Code coverage and profiling (default)
Provides time profiling information, and the number of times an instruction is
executed. Indicates how much processor time is spent on each instruction. See
Section on page 272 for information on reading the results obtained in this mode.
Note: Coverage and profiling is incompatible with the trace analysis feature described in
Section 9.1: Trace recording.