Questa SIM User's Manual - История изменений

ANA: Содержимое страницы заменено на «* Analyzing Assertions and Cover Directives * /GUI Elements of the Assertions Wind…»

2015-01-11T12:16:57Z

Содержимое страницы заменено на «* Analyzing Assertions and Cover Directives * /GUI Elements of the Assertions Wind…»

Внесённые изменения

ANA: /* Comparing Assertions */

2015-01-10T10:17:54Z

‎Comparing Assertions

ANA: /* Viewing Assertions and Cover Directives in the Wave Window */

2015-01-10T10:12:58Z

‎Viewing Assertions and Cover Directives in the Wave Window

ANA: /* Viewing Memory Profile Data */

2015-01-10T10:07:38Z

‎Viewing Memory Profile Data

ANA: /* Viewing Cover Directives in the Cover Directives Window */

2015-01-10T10:06:41Z

‎Viewing Cover Directives in the Cover Directives Window

ANA: /* Viewing Assertions in the Assertions Window */

2015-01-10T08:56:22Z

‎Viewing Assertions in the Assertions Window

ANA: Новая страница: «== Analyzing Assertions and Cover Directives == The following tasks can be used for analyzing assertions and cover directives: * Viewing Assertions in the As…»

2015-01-10T07:45:36Z

Новая страница: «== Analyzing Assertions and Cover Directives == The following tasks can be used for analyzing assertions and cover directives: * Viewing Assertions in the As…»

Новая страница

== Analyzing Assertions and Cover Directives ==

The following tasks can be used for analyzing assertions and cover directives:

* Viewing Assertions in the Assertions Window
* Viewing Cover Directives in the Cover Directives Window
* Viewing Memory Profile Data
* Viewing Assertions and Cover Directives in the Wave Window
* Comparing Assertions

=== Viewing Assertions in the Assertions Window ===

The Assertions windows displays simulation data about assertions. To open the Assertions window, select View > Coverage > Assertions from the menus.

Figure 21-17 shows SystemVerilog assertions in the Assertions window. SV assertions are indicated by a light blue triangle. PSL assertions (not shown) are indicated by a purple triangle.

{| align=center
! [[Файл:Vsim Assertions window.gif]]
|-
!Figure 21-17. SystemVerilog Assertions in the Assertions Window
|}

The Assertions window lists all embedded and external assert directives that were successfully compiled and simulated during the current session. The plus sign (’+’) to the left of the Name field lets you expand the assertion hierarchy to show its elements (properties, sequences, clocks, and HDL signals).

The Assertions window includes several columns for displaying information about assertions. See GUI Elements of the Assertions Window for a description of each field.

When assertions fire with failure messages, the Assertions window displays the name and failure count in red, both during simulation and in post-simulation mode (Figure 21-18).

{| align=center
! [[Файл:Vsim Assertion fail red.gif]]
|-
! Figure 21-18. Assertion Failures Appear in Red
|}

You can use the assertion count command to return the sum of the assertion failure counts for a specified set of assertion directive instances. This command returns a "No matches" warning if the given path does not contain any assertions.
==== Assertions Window Display Options ====

The Assertions window can display assertion directives in hierarchical (tree) mode (Figure 21-19) or in the flattened form (Figure 21-17).

{| align=center
! [[Файл:Vsim Assertions hierarchy.gif]]
|-
! Figure 21-19. Hierarchy Display Mode
|}

The hierarchical display mode can be enabled or disabled by doing any one of the following:

* When the Assertions window is docked, select Assertions > Display Options > Hierarchy Mode from the Main menus.

* Right-click in the Assertions window and select Display Options > Hierarchy Mode from the popup menu.

The Display Options menu also includes the following options:

* The Recursive Mode option displays all assertions at and below the selected hierarchy instance, the selection being taken from a Structure window. (i.e., the sim tab). Otherwise only items actually in that particular scope are shown.

* The Show All Contexts option displays all instances in the design. It does not following the current context selection in a structure pane. The Show All Context display mode implies the recursive display mode as well, so the Recursive Mode selection is automatically grayed out.

* The Show Concurrent Asserts option displays only concurrent assertions.

* The Show Immediate Asserts option displays only immediate assertions.

=== Viewing Cover Directives in the Cover Directives Window ===

The Cover Directives window displays information about cover directives. To open the Cover Directives window, select View > Coverage > Cover Directives.

Figure 21-20 shows PSL cover directives in the Cover Directives window. PSL cover directives are indicated by a purple chevron. SystemVerilog cover directives (not shown) are indicated by a light blue chevron.

{| align=center
! [[Файл:Vsim Cover directives tab.gif]]
|-
! Figure 21-20. PSL Cover Directives in the Cover Directives Window
|}

The Cover Directives window displays accumulated cover directive statistics at the current simulation time, including percentages and a graph for each directive and instance. The plus sign (’+’) to the left of the Name field lets you expand the directive hierarchy to show its elements (properties, sequences, clocks, and HDL signals). Refer to GUI Elements of the Cover Directives Window for a description of each column.
Display Options for Cover Directives

Display options allow you to display cover directives in a Recursive Mode or in a Show All Contexts mode. For details, see Changing the Cover Directives Window Display Options.
Filtering Data in the Assertions and Cover Directives Window

You can filter the Assertions and Cover Directives data displayed by selecting Assertions > Filter > Setup or Cover Directives > Filter > Setup, depending on which window is active. For details, see “Filtering Functional Coverage Data”.

===Viewing Memory Profile Data===

The assertion profile command generates a fine grained profile of memory usage for assertions and cover directives. The results are displayed in the Memory, Peak Memory, Peak Memory Time, and Cumulative Threads columns of the Assertions and Cover Directives windows.

* The Memory column tracks the current memory used by the assertion or cover directive.

* The Peak Memory column tracks the peak memory used by the assertion or cover directive.

* The Peak Memory Time column indicates the simulation run time at which the peak memory usage occurred.

* The Cumulative Threads column counts the cumulative thread count for the assertion.

While the Cumulative Threads count is not specifically about memory, it is designed to highlight those assertions and cover directives that are starting too many attempts, such as the following assertion:

assert property ((@posedge clk) a |=> b);

If ‘a’ is true throughout the simulation, then the above assertion will start a brand new attempt at every clock. An attempt, once started, will only be alive until the next clock. So this assertion will not appear abnormally high in the Memory and Peak Memory columns, but it will have a high count in the Cumulative Threads column.

=== Viewing Assertions and Cover Directives in the Wave Window ===

You can view assertions and cover directives in the Wave window just like any other signal in your design. Use one of the following methods to add directives to the Wave window:

* To add all assertions in your design to the Wave window,
** Select a single object in the Assertions window, then select Add > To Wave > Objects in Design from the main menus.
** Select all objects in the Assertions window, then select Add > To Wave > Selected Objects from the main menus
** Right-click the selected assertions, then select Add Wave > Objects in Design from the popup menu.
** Select all objects in the window, then click the Add Selected To Window button in the Standard Toolbar.
* To add all cover directives in your design to the Wave window:
** Select a single directive in the Cover Directives window, then select Add > To Wave > Functional Coverage in Design from the main menus.
** Select all directives in the Cover Directives window, then select Add > To Wave > Selected Functional Coverage from the main menus.
** Right-click the selected cover directives, then select Add Wave > Functional Coverage in Design in Design from the popup menu.
** Select all directives in the window, then click the Add Selected To Window button in the Standard Toolbar.
* To place a single assertion or cover directive in the Wave window:
** Drag the object from the its window and drop it into the Wave window, or simply drop it onto the Wave tab if it is showing.
** Select the object, then click the Add Selected To Window button in the Standard Toolbar.
** Select the object then select Add > To Wave > Selected Objects from the menu bar.
* Right-click any selected assertion and select Add Wave > Selected Objects from the popup menu; or right-click any selected cover directive and select Add Wave > Selected Functional Coverage from the popup menu.

Questa SIM represents assertions and cover directives as signals or waveforms in the Wave window. The Wave window in Figure 21-21 shows several SystemVerilog assertions and a single cover directive. SystemVerilog assertions are represented by light blue triangles in the pathnames column. SystemVerilog cover directives are represented by light blue chevrons.

{| align=center
! [[Файл:Vsim Sv assert wave.gif]]
|-
! Figure 21-21. SystemVerilog Assert and Cover Directives in the Wave Window
|}

The Wave window in Figure 21-22 shows several PSL assertions and cover directives. PSL assertions are represented by magenta triangles. PSL cover directives are represented by magenta chevrons.

{| align=center
! [[Файл:Vsim Assertions wave.gif]]
|-
! Figure 21-22. PSL Assert and Cover Directives in the Wave Window
|}

The name of each assertion and cover directive comes from the assertion code. The plus sign (’+’) to the left of the name indicates that an assertion or cover directive is a composite trace and can be expanded to show its elements (properties, sequences, clocks, and HDL signals). Note that signals are flattened out; hierarchy is not preserved.

The value in the value pane is determined by the active cursor in the waveform pane. The value will be one of ACTIVE, INACTIVE, PASS, FAIL, or ANTCDENT.

The waveform for an assertion or cover directive represents both continuous and instantaneous information.

* Continuous information is either active or inactive. The directive is active anytime it matches the first element in the directive. When active, the trace is green; when inactive it is blue.

* Instantaneous information is represented as a start, pass, or fail event. A start event is shown as a blue square. A green triangle represents a pass. And a red triangle indicates a fail.

A yellow triangle represents an antecedent match (Figure 21-23). The yellow triangle is displayed only if the directive is browseable and assertion debug is on (vsim -assertdebug). The yellow triangle is shown for each thread of the assertion under ActiveCount in the assertion (see Using the Assertion Active Thread Monitor). The signal values of the assertion also reflect the antecedent match (ANTCDENT).

{| align=center
! [[Файл:Vsim Wave antecedent.gif]]
|-
! Figure 21-23. Antecedent Matches Indicated by Yellow Triangle
|}

Table 21-1 summarizes the graphic elements for assertions and cover directives used in the Wave and ATV windows (see Viewing Assertion Threads in the ATV Window):

{| class=standard align=center
|+ Table 21-1. Graphic Elements for Assertions and Cover Directives
! Graphic element
! Meaning
|-
| blue line
|assertion or cover directive is inactive
|-
|green line
|assertion or cover directive is active
|-
|blue square
|assertion or cover directive starts
|-
|green triangle
|assertion or cover directive passed
|-
|red triangle
|assertion or cover directive failed
|-
|yellow triangle
|antecedent match occurred in assertion
|}

==== Displaying Cover Directives in Count Mode ====

You can change the coverage directive waveform in the Wave window so it displays in count mode format, which shows the instantaneous waveform value as a decimal integer. To change to count-mode format, right-click a coverage waveform name and select Cover Directive View > Count Mode.

{| align=center
! [[Файл:Vsim Sv count mode.gif]]
|-
! Figure 21-24. Viewing Cover Directive Waveforms in Count Mode
|}

Count mode can be useful for gauging the effectiveness of stimulus over time. If all cover directive counts are static for a long period of time, it may be that the stimulus is acting in a wasteful manner and can be improved.

=== Comparing Assertions ===

Questa SIM’s compare feature allows you to compare assertions (which includes any assertion-like object such as accAssertion, accCover, accEndpoint, or accImmediateAssert.) There is no cross-compare with assertion types outside the set listed, and assertion compare is further limited to like types only. That is, both the reference and test items must be of the same type.

Comparing assertion signals differs from comparing normal HDL signals/ports because assertion signals have two attributes:

The current assertion state (ACTIVE | INACTIVE)

The current assertion event (START | PASS | FAIL | EVAL)

Assertions expand to show child signals but these child signals don't participate in the compare evaluation. Child signals are, however, visible in the compare waveforms when the you expand compare assertions.
Setting Up the Assertions Compare

You can set up and run an assertion compare using the compare commands or the menu-based Waveform Comparison Wizard. For example, a comparison using compare commands may look like the following:

add wave /top/assert_sig
run 1000 ns
dataset open vwim_test.wlf
compare start sim vsim_test
compare add sim:/top/assert_sig vsim_test:/top/assert_sig
compare run

All existing compare commands are supported for comparing assertion signals. Refer to the Command Reference for syntax and command descriptions.

The Waveform Comparison Wizard will guide you through the selection of a reference dataset and a test dataset. Assertions within those datasets are compared along with other signals. You can start the Wizard is by selecting Tools > Waveform Compare > Comparison Wizard.

The Compare Signal

When two assertion signals are compared — for example, vsim_pass:/top/my_assertion_sig and vsim_fail:/top/my_assertion_sig — a third virtual signal is created:

compare:/top/\my_assertion_sig<>my_assertion_sig\

The compare signal created is composed of the reference signal and the test signal. Differences between the reference and text assertion signals are highlighted in red in the compare signal when it is displayed in the Wave Window. Assertion differences cannot be viewed in the ATV window.
Two Types of Assertion Differences

There are two types of assertion differences:

Instantaneous difference — When the assertion event (START | PASS | FAIL | EVAL) is different but the state of the assertion (ACTIVE | INACTIVE) is the same.

For example, considering two datasets vsim_top and vsim_ntop with an assertion signal my_assertion_sig.

vsim_top:/top/my_assertion_sig is PASS_INACTIVE at 20 ns

vsim_ntop:/top/my_assertion_sig is FAIL_INACTIVE at 20ns

This is an instantaneous difference the difference will marked at time 20 ns and the width of the difference marker will be equal to the width of the PASS/FAIL symbol.

Range difference — When there is a state change (ACTIVE->INACTIVE) or vice-versa, between the reference and test assertion, irrespective of the event on the assertions.

Child Signals

An assertion object is composed of child signals. It is the evaluation of these child signals that determine the assertion event (START/PASS/FAIL). If you choose to expand the assertion, the difference marker is propagated to the child signals as well, but this may not necessarily mean a change in value on the child signal at that specific time — the difference could have occurred earlier.

If the reference signal has child signals but the test signal does not, or vice-versa, waveform compare will still work because compare cares only about the absolute event on the assertion. If there is a difference, it will be marked.

[[Категория:PSL]]

@@ Строка 235: / Строка 235: @@
 Comparing assertion signals differs from comparing normal HDL signals/ports because assertion signals have two attributes:
-    The current assertion state (ACTIVE | INACTIVE)
+*    The current assertion state (ACTIVE | INACTIVE)
-    The current assertion event (START | PASS | FAIL | EVAL)
+*    The current assertion event (START | PASS | FAIL | EVAL)
 Assertions expand to show child signals but these child signals don't participate in the compare evaluation. Child signals are, however, visible in the compare waveforms when the you expand compare assertions.
 Setting Up the Assertions Compare
 You can set up and run an assertion compare using the compare commands or the menu-based Waveform Comparison Wizard. For example, a comparison using compare commands may look like the following:
 add wave /top/assert_sig
 run 1000 ns
@@ Строка 250: / Строка 252: @@
 compare add sim:/top/assert_sig vsim_test:/top/assert_sig
 compare run
 All existing compare commands are supported for comparing assertion signals. Refer to the Command Reference for syntax and command descriptions.
-The Waveform Comparison Wizard will guide you through the selection of a reference dataset and a test dataset. Assertions within those datasets are compared along with other signals. You can start the Wizard is by selecting Tools > Waveform Compare > Comparison Wizard.
+The Waveform Comparison Wizard will guide you through the selection of a reference dataset and a test dataset. Assertions within those datasets are compared along with other signals. You can start the Wizard is by selecting '''Tools > Waveform Compare > Comparison Wizard'''.
 The Compare Signal
-When two assertion signals are compared — for example, vsim_pass:/top/my_assertion_sig and vsim_fail:/top/my_assertion_sig — a third virtual signal is created:
+When two assertion signals are compared — for example, <code>vsim_pass:/top/my_assertion_sig and vsim_fail:/top/my_assertion_sig</code> — a third virtual signal is created:
-compare:/top/\my_assertion_sig<>my_assertion_sig\
+ compare:/top/\my_assertion_sig<>my_assertion_sig\
 The compare signal created is composed of the reference signal and the test signal. Differences between the reference and text assertion signals are highlighted in red in the compare signal when it is displayed in the Wave Window. Assertion differences cannot be viewed in the ATV window.
-There are two types of assertion differences:
+====Two Types of Assertion Differences====
-    Instantaneous difference — When the assertion event (START | PASS | FAIL | EVAL) is different but the state of the assertion (ACTIVE | INACTIVE) is the same.
+There are two types of assertion differences:
-For example, considering two datasets vsim_top and vsim_ntop with an assertion signal my_assertion_sig.
+*    '''Instantaneous difference''' — When the assertion event (START | PASS | FAIL | EVAL) is different but the state of the assertion (ACTIVE | INACTIVE) is the same.
-vsim_top:/top/my_assertion_sig is PASS_INACTIVE at 20 ns
+:For example, considering two datasets ''vsim_top'' and ''vsim_ntop'' with an assertion signal ''my_assertion_sig''.
-vsim_ntop:/top/my_assertion_sig is FAIL_INACTIVE at 20ns
+::<code>vsim_top:/top/my_assertion_sig</code> is PASS_INACTIVE at 20 ns
-This is an instantaneous difference the difference will marked at time 20 ns and the width of the difference marker will be equal to the width of the PASS/FAIL symbol.
+:This is an instantaneous difference the difference will marked at time 20 ns and the width of the difference marker will be equal to the width of the PASS/FAIL symbol.
-    Range difference — When there is a state change (ACTIVE->INACTIVE) or vice-versa, between the reference and test assertion, irrespective of the event on the assertions.
+*    '''Range difference''' — When there is a state change (ACTIVE->INACTIVE) or vice-versa, between the reference and test assertion, irrespective of the event on the assertions.
-Child Signals
+====Child Signals====
 An assertion object is composed of child signals. It is the evaluation of these child signals that determine the assertion event (START/PASS/FAIL). If you choose to expand the assertion, the difference marker is propagated to the child signals as well, but this may not necessarily mean a change in value on the child signal at that specific time — the difference could have occurred earlier.

@@ Строка 131: / Строка 131: @@
 *    To add all assertions in your design to the Wave window,
-**    Select a single object in the Assertions window, then select Add > To Wave > Objects in Design from the main menus.
+**    Select a single object in the Assertions window, then select '''Add > To Wave > Objects in Design''' from the main menus.
-**    Select all objects in the Assertions window, then select Add > To Wave > Selected Objects from the main menus
+**    Select all objects in the Assertions window, then select '''Add > To Wave > Selected Objects''' from the main menus
-**    Right-click the selected assertions, then select Add Wave > Objects in Design from the popup menu.
+**    Right-click the selected assertions, then select '''Add Wave > Objects in Design''' from the popup menu.
-**    Select all objects in the window, then click the Add Selected To Window button in the Standard Toolbar.
+**    Select all objects in the window, then click the '''Add Selected To Window''' button in the [[Standard Toolbar]]. [[Файл:Vsim Button add selected to wave.gif]]
 *    To add all cover directives in your design to the Wave window:
-**    Select a single directive in the Cover Directives window, then select Add > To Wave > Functional Coverage in Design from the main menus.
+**    Select a single directive in the Cover Directives window, then select '''Add > To Wave > Functional Coverage in Design''' from the main menus.
-**    Select all directives in the Cover Directives window, then select Add > To Wave > Selected Functional Coverage from the main menus.
+**    Select all directives in the Cover Directives window, then select '''Add > To Wave > Selected Functional Coverage''' from the main menus.
-**    Right-click the selected cover directives, then select Add Wave > Functional Coverage in Design in Design from the popup menu.
+**    Right-click the selected cover directives, then select '''Add Wave > Functional Coverage in Design''' in Design from the popup menu.
-**    Select all directives in the window, then click the Add Selected To Window button in the Standard Toolbar.
+**    Select all directives in the window, then click the '''Add Selected To Window''' button in the [[Standard Toolbar]]. [[Файл:Vsim Button add selected to wave.gif]]
 *    To place a single assertion or cover directive in the Wave window:
 **    Drag the object from the its window and drop it into the Wave window, or simply drop it onto the Wave tab if it is showing.
-**    Select the object, then click the Add Selected To Window button in the Standard Toolbar.
+**    Select the object, then click the '''Add Selected To Window''' button in the [[Standard Toolbar]].
-**    Select the object then select Add > To Wave > Selected Objects from the menu bar.
+**    Select the object then select '''Add > To Wave > Selected Objects''' from the menu bar.
-*    Right-click any selected assertion and select Add Wave > Selected Objects from the popup menu; or right-click any selected cover directive and select Add Wave > Selected Functional Coverage from the popup menu.
+*    Right-click any selected assertion and select '''Add Wave > Selected Objects''' from the popup menu; or right-click any selected cover directive and select '''Add Wave > Selected Functional Coverage''' from the popup menu.
 Questa SIM represents assertions and cover directives as signals or waveforms in the Wave window. The Wave window in Figure 21-21 shows several SystemVerilog assertions and a single cover directive. SystemVerilog assertions are represented by light blue triangles in the pathnames column. SystemVerilog cover directives are represented by light blue chevrons.
@@ Строка 176: / Строка 178: @@
 *    Instantaneous information is represented as a start, pass, or fail event. A start event is shown as a blue square. A green triangle represents a pass. And a red triangle indicates a fail.
-A yellow triangle represents an antecedent match (Figure 21-23). The yellow triangle is displayed only if the directive is browseable and assertion debug is on (vsim -assertdebug). The yellow triangle is shown for each thread of the assertion under ActiveCount in the assertion (see Using the Assertion Active Thread Monitor). The signal values of the assertion also reflect the antecedent match (ANTCDENT).
+A yellow triangle represents an antecedent match (Figure 21-23). The yellow triangle is displayed only if the directive is browseable and assertion debug is on (vsim -assertdebug). The yellow triangle is shown for each thread of the assertion under ActiveCount in the assertion (see [[Using the Assertion Active Thread Monitor]]). The signal values of the assertion also reflect the antecedent match (ANTCDENT).
@@ Строка 216: / Строка 218: @@
 ==== Displaying Cover Directives in Count Mode ====
-You can change the coverage directive waveform in the Wave window so it displays in count mode format, which shows the instantaneous waveform value as a decimal integer. To change to count-mode format, right-click a coverage waveform name and select Cover Directive View > Count Mode.
+You can change the coverage directive waveform in the Wave window so it displays in count mode format, which shows the instantaneous waveform value as a decimal integer. To change to count-mode format, right-click a coverage waveform name and select '''Cover Directive View > Count Mode'''.
 {| align=center
@@ Строка 226: / Строка 228: @@
 Count mode can be useful for gauging the effectiveness of stimulus over time. If all cover directive counts are static for a long period of time, it may be that the stimulus is acting in a wasteful manner and can be improved.
 === Comparing Assertions ===

@@ Строка 112: / Строка 112: @@
 The assertion profile command generates a fine grained profile of memory usage for assertions and cover directives. The results are displayed in the Memory, Peak Memory, Peak Memory Time, and Cumulative Threads columns of the Assertions and Cover Directives windows.
-*    The Memory column tracks the current memory used by the assertion or cover directive.
+*    The '''Memory column''' tracks the current memory used by the assertion or cover directive.
-*    The Peak Memory column tracks the peak memory used by the assertion or cover directive.
+*    The '''Peak Memory''' column tracks the peak memory used by the assertion or cover directive.
-*    The Peak Memory Time column indicates the simulation run time at which the peak memory usage occurred.
+*    The '''Peak Memory Time''' column indicates the simulation run time at which the peak memory usage occurred.
-*    The Cumulative Threads column counts the cumulative thread count for the assertion.
+*    The '''Cumulative Threads''' column counts the cumulative thread count for the assertion.
 While the Cumulative Threads count is not specifically about memory, it is designed to highlight those assertions and cover directives that are starting too many attempts, such as the following assertion:
@@ Строка 124: / Строка 124: @@
   assert property ((@posedge clk) a |=> b);
-If ‘a’ is true throughout the simulation, then the above assertion will start a brand new attempt at every clock. An attempt, once started, will only be alive until the next clock. So this assertion will not appear abnormally high in the Memory and Peak Memory columns, but it will have a high count in the Cumulative Threads column.
+If ‘a’ is true throughout the simulation, then the above assertion will start a brand new attempt at every clock. An attempt, once started, will only be alive until the next clock. So this assertion will not appear abnormally high in the '''Memory''' and '''Peak Memory''' columns, but it will have a high count in the '''Cumulative Threads''' column.
-−
 === Viewing Assertions and Cover Directives in the Wave Window ===

@@ Строка 86: / Строка 86: @@
 === Viewing Cover Directives in the Cover Directives Window ===
-The Cover Directives window displays information about cover directives. To open the Cover Directives window, select View > Coverage > Cover Directives.
+The Cover Directives window displays information about cover directives. To open the Cover Directives window, select ''View > Coverage > Cover Directives''.
 Figure 21-20 shows PSL cover directives in the Cover Directives window. PSL cover directives are indicated by a purple chevron. SystemVerilog cover directives (not shown) are indicated by a light blue chevron.
@@ Строка 98: / Строка 98: @@
-The Cover Directives window displays accumulated cover directive statistics at the current simulation time, including percentages and a graph for each directive and instance. The plus sign (’+’) to the left of the Name field lets you expand the directive hierarchy to show its elements (properties, sequences, clocks, and HDL signals). Refer to GUI Elements of the Cover Directives Window for a description of each column.
+The Cover Directives window displays accumulated cover directive statistics at the current simulation time, including percentages and a graph for each directive and instance. The plus sign (’+’) to the left of the Name field lets you expand the directive hierarchy to show its elements (properties, sequences, clocks, and HDL signals). Refer to [[GUI Elements of the Cover Directives Window]] for a description of each column.
-Display Options for Cover Directives
-Display options allow you to display cover directives in a Recursive Mode or in a Show All Contexts mode. For details, see Changing the Cover Directives Window Display Options.
+==== Display Options for Cover Directives ====
-Filtering Data in the Assertions and Cover Directives Window
-You can filter the Assertions and Cover Directives data displayed by selecting Assertions > Filter > Setup or Cover Directives > Filter > Setup, depending on which window is active. For details, see “Filtering Functional Coverage Data”.
+Display options allow you to display cover directives in a '''Recursive Mode''' or in a '''Show All Contexts''' mode. For details, see [[Changing the Cover Directives Window Display Options]].
 ===Viewing Memory Profile Data===

@@ Строка 11: / Строка 11: @@
 === Viewing Assertions in the Assertions Window ===
-The Assertions windows displays simulation data about assertions. To open the Assertions window, select View > Coverage > Assertions from the menus.
+<!--
+The Assertions windows displays simulation data about assertions. To open the Assertions window, select View > Coverage > Assertions from the menus.-->
-Figure 21-17 shows SystemVerilog assertions in the Assertions window. SV assertions are indicated by a light blue triangle. PSL assertions (not shown) are indicated by a purple triangle.
+Окна Утверждения (Assertions windows) отображают данные моделирования об утверждениях. Чтобы открыть окно Утверждения, выберите ''View → Coverage → Assertions'' из меню.
 {| align=center
 ! [[Файл:Vsim Assertions window.gif]]
 |-
-!Figure 21-17. SystemVerilog Assertions in the Assertions Window
+! Figure 21-17. SystemVerilog Assertions in the Assertions Window
 |}
+<!--
 The Assertions window lists all embedded and external assert directives that were successfully compiled and simulated during the current session. The plus sign (’+’) to the left of the Name field lets you expand the assertion hierarchy to show its elements (properties, sequences, clocks, and HDL signals).
-The Assertions window includes several columns for displaying information about assertions. See GUI Elements of the Assertions Window for a description of each field.
+<!-- The Assertions window includes several columns for displaying information about assertions. See GUI Elements of the Assertions Window for a description of each field.-->
+Окно Утверждения включает в себя несколько столбцов для отображения информации о утверждениях. Смотри [[GUI Elements of the Assertions Window]] для описания каждого поля.
-When assertions fire with failure messages, the Assertions window displays the name and failure count in red, both during simulation and in post-simulation mode (Figure 21-18).
 {| align=center
@@ Строка 37: / Строка 43: @@
-You can use the assertion count command to return the sum of the assertion failure counts for a specified set of assertion directive instances. This command returns a "No matches" warning if the given path does not contain any assertions.
+<!-- You can use the assertion count command to return the sum of the assertion failure counts for a specified set of assertion directive instances. This command returns a "No matches" warning if the given path does not contain any assertions.
 ==== Assertions Window Display Options ====
-The Assertions window can display assertion directives in hierarchical (tree) mode (Figure 21-19) or in the flattened form (Figure 21-17).
+<!-- The Assertions window can display assertion directives in hierarchical (tree) mode (Figure 21-19) or in the flattened form (Figure 21-17).-->
@@ Строка 50: / Строка 61: @@
-The hierarchical display mode can be enabled or disabled by doing any one of the following:
+<!-- The hierarchical display mode can be enabled or disabled by doing any one of the following:-->
+Режим иерархического отображения может быть включен или отключен с помощью одного из следующий действий:
-*    When the Assertions window is docked, select Assertions > Display Options > Hierarchy Mode from the Main menus.
-*    Right-click in the Assertions window and select Display Options > Hierarchy Mode from the popup menu.
+<!-- *    When the Assertions window is docked, select Assertions > Display Options > Hierarchy Mode from the Main menus.-->
-The Display Options menu also includes the following options:
+<!-- *    Right-click in the Assertions window and select Display Options > Hierarchy Mode from the popup menu.-->
-*    The Recursive Mode option displays all assertions at and below the selected hierarchy instance, the selection being taken from a Structure window. (i.e., the sim tab). Otherwise only items actually in that particular scope are shown.
+<!-- The Display Options menu also includes the following options:-->
-*    The Show All Contexts option displays all instances in the design. It does not following the current context selection in a structure pane. The Show All Context display mode implies the recursive display mode as well, so the Recursive Mode selection is automatically grayed out.
+<!-- *    The Recursive Mode option displays all assertions at and below the selected hierarchy instance, the selection being taken from a Structure window. (i.e., the sim tab). Otherwise only items actually in that particular scope are shown.-->
-*    The Show Concurrent Asserts option displays only concurrent assertions.
+<!-- *    The Show All Contexts option displays all instances in the design. It does not following the current context selection in a structure pane. The Show All Context display mode implies the recursive display mode as well, so the Recursive Mode selection is automatically grayed out.-->
-*    The Show Immediate Asserts option displays only immediate assertions.
+<!-- *    The Show Concurrent Asserts option displays only concurrent assertions.-->
 === Viewing Cover Directives in the Cover Directives Window ===