You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: cv32e40p/docs/VerifPlans/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Below are two different chapters describing verification plans status and direct
8
8
# CV32E40P (V2) Verification Plans
9
9
10
10
## Short verification methodology introduction
11
-
For CV32E40P**v2** verification, the formal verification methodology has been choosen over the stimuli-based simulation that was done for version one of the core. However, full verification closure is not feasible using only formal verification due to complexity of specific scenarios. All these specific uncoverable scenarios from formal verification are then exercised by stimuli-based simulation using a reference model of the core. These scenarios along with formal assertions are described inside verifications plans, for which details are given in a table below. Regarding already available v1 plans, their re-use or not is specified in this table.
11
+
For CV32E40Pv2 verification, the formal verification methodology has been chosen over the stimuli-based simulation that was done for v1 version of the core. However, full verification closure is not feasible using only formal verification due to complexity of specific scenarios. All these specific uncoverable scenarios from formal verification are then exercised by stimuli-based simulation using a reference model of the core. These scenarios along with formal assertions are described inside verifications plans, for which details are given in a table below. Regarding already available v1 plans, their re-use or not is specified in this table.
12
12
13
13
## Verification Plan Status
14
14
@@ -34,7 +34,7 @@ Under the heading `Link`, the name shown corresponds to the filename of the vpla
34
34
|**Debug & Trace**| Debug | v1-reused | Reviewed | Missing XPULP-specific debug are in a separate vplan |[CV32E40Pv2_debug.xlsx](https://github.com/openhwgroup/core-v-verif/blob/cv32e40p/dev/cv32e40p/docs/VerifPlans/Simulation/debug-trace/CV32E40Pv2_debug.xlsx"Debug Vplan")|
0 commit comments