User manual

UM0036 STice features
Doc ID 7705 Rev 11 271/385
have chosen two small counters to record read and write operations separately,
the maximum value may be reached very quickly.
– Place a checkmark in the Stop after application reset checkbox in the General
section, to stop the execution when a reset has occurred (due to watchdog, for
example). In fact this option should always be checked unless your application
should not be stopped, otherwise the time profiling results in the two subroutine
modes will become erroneous. Once the application is stopped, the user must
click on Profiling Session Stop to stop the session.
– Place a checkmark in the Stop when time counter reaches max checkbox in the
Time profiling section, to stop the execution when the global profiler time counter
reaches the maximum value. All time counters are recorded in 36-bit large
counters. In fact this option should always be checked unless your application
shouldn't be stopped as otherwise the time profiling results will become
erroneous. Once the application is stopped, the user must click on Profiling
Session Stop to stop the session.
Note: This option is disabled if you selected Data coverage and occurrence profiling.
5. In the Data Occurrence Profiling section, select the data access mode:
– Read and write (two small counters) - default
Records the number of read and write operations in two separate 15-bit counters.
The maximum value each counter can reach is 32767.
– Read (one large counter)
Records the number of read operations only in one 30-bit counter. The maximum
value the counter can reach is 1,073,741,823.
– Write (one large counter)
Records the number of write operations only in one 30-bit counter. The maximum
value the counter can reach is 1,073,741,823.
– Read + write (one large counter)
Records the number of read and write operations in the same 30-bit counter. The
maximum value the counter can reach is 1,073,741,823.
Note: This section is disabled if you selected Code coverage and profiling.
The occurrence counter for code execution is a large 30-bit counter.
6. Click OK. The settings that you configured will be used the next time you start a
coverage and profiling session.
9.2.2 Running a coverage and profiling session
To run coverage and profiling on your application, you must first 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: Running an
application on page 167 ).
● Your application is stopped, either because you have not started execution, or because
execution is stopped at a breakpoint.
If you have not configured the coverage and profiling settings, either the ones from the last
session or the default ones will be used.
To start and stop a coverage and profiling session: