2.15
Measure Coverage [Simulator] [E20 [RX71M, RX66x, RX65x, RX64M, RX66T, RX671, RX72T, RX72M, and RX72N Groups]]
This section describes coverage measurements that are conducted using the coverage facility.
There are several kinds of coverage measurement methods. Of these, CS+ performs, in areas designated below, a code coverage measurement of fetch-related operations on source lines and functions (C0 coverage) and a data coverage measurement of access-related operations on variables.
The areas in which CS+ performs coverage measurements are as follows:
Table 2.17 | Subject Areas of Coverage Measurements |
|
|
Simulator
|
Internal ROM/RAM, emulation ROM/RAM
|
E20 [RX71M, RX66x, RX65x, RX64M, RX66T, RX671, RX72T, RX72M, and RX72N Groups]
|
Any desired area (up to four areas in 4-Mbyte units)
|
Remark | C0 coverage refers to an instruction coverage rate (statement coverage).
For example, if all instructions (statements) in code are executed at least once, then C0 = 100%. |
Caution 1. | In the E20 [RX71M, RX66x, RX65x, RX64M, RX66T, RX671, RX72T, RX72M, and RX72N Groups], this function cannot be used together with the trace function or real-time RAM monitor function. |
Caution 2. | In the E20 [RX71M, RX66x, RX65x, RX64M, RX66T, RX671, RX72T, RX72M, and RX72N Groups], data coverage cannot be measured. |
Caution 3. | In the E20 (JTAG) [RX71M, RX66x, RX65x, RX64M, RX66T, RX671, RX72T, RX72M, and RX72N Group], if you connect the emulator by using hot plug-in, the coverage measurement function is not available.
If you use hot plug-in to connect the emulator, please select [No] for the [Use code coverage function] property in the [Coverage] [E20 [RX71M, RX66x, RX65x, RX64M, RX66T, RX671, RX72T, RX72M, and RX72N Groups]] category on the [Debug Tool Settings] tab on the Property panel. |
Caution 4. | In the E20 (JTAG) [RX71M, RX66x, RX65x, RX64M, RX66T, RX671, RX72T, RX72M, and RX72N Group], when the error message "The system was reset." is displayed during program execution, coverage from the start of the program to the system reset will not have been measured. |