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
-v, --verbose Print test output immediately and not only when
64
66
failure
65
67
--no-color Do not color output
66
-
--gui {load,run} Open test case(s) in simulator gui. 'load' only loads
67
-
the test case and gives the user control. 'run' loads
68
-
and runs the test case while recursively logging all
69
-
variables and signals
70
68
--log-level {info,error,warning,debug}
71
69
-p NUM_THREADS, --num-threads NUM_THREADS
72
70
Number of tests to run in parallel. Test output is not
73
71
continuously written in verbose mode with p > 1
74
72
73
+
com:
74
+
Flags specific to the com message passing package
75
+
76
+
--use-debug-codecs Run with debug features enabled
77
+
78
+
modelsim:
79
+
ModelSim specific flags
80
+
81
+
-g [{load,run}], --gui [{load,run}]
82
+
Open test case(s) in simulator gui. 'load' only loads
83
+
the test case and gives the user control (default).
84
+
'run' loads and runs the test case while recursively
85
+
logging all variables and signals.
86
+
--new-vsim Do not re-use the same vsim process for running
87
+
different test cases (slower)
88
+
--coverage [COVERAGE]
89
+
Enable code coverage. Choose any combination of
90
+
"bcestf". When the flag is given with no argument
91
+
everthing is enabled. Remember to run --clean when
92
+
chaning this as re-compilation is not triggered.
93
+
Experimental feature not supported by VUnit main
94
+
developers.
95
+
75
96
activehdl:
76
97
Aldec Active HDL specific flags
77
98
78
-
--gui Open test case(s) in simulator gui with top level pre
99
+
-g, --gui Open test case(s) in simulator gui with top level pre
79
100
loaded
80
101
81
102
rivierapro:
82
103
Aldec Riviera Pro specific flags
83
104
84
-
--gui Open test case(s) in simulator gui with top level pre
105
+
-g, --gui Open test case(s) in simulator gui with top level pre
85
106
loaded
86
107
87
108
ghdl:
@@ -91,15 +112,6 @@ ghdl:
91
112
--gtkwave-args GTKWAVE_ARGS
92
113
Arguments to pass to gtkwave
93
114
94
-
modelsim:
95
-
ModelSim specific flags
96
-
97
-
--gui {load,run} Open test case(s) in simulator gui. 'load' only loads
98
-
the test case and gives the user control. 'run' loads
99
-
and runs the test case while recursively logging all
100
-
variables and signals
101
-
--new-vsim Do not re-use the same vsim process for running
102
-
different test cases (slower)
103
115
```
104
116
105
117
## VHDL Test Benches
@@ -242,7 +254,7 @@ When interfacing with pre-compiled libraries such as `unisim` from Xilinx the `a
242
254
## Running a test case in the ModelSim GUI
243
255
Sometimes the textual error messages and logs are not enough to pinpoint the error and a test case needs to be opened in the GUI for visual debugging using single stepping, breakpoints and wave form viewing. VUnit makes it easy to open a test case in the GUI by having a `--gui={load,run}` command line flag:
244
256
```console
245
-
> python run.py --gui=load my_test_case
257
+
> python run.py --gui my_test_case
246
258
```
247
259
This launches a GUI window for each test case with specific functions pre-loaded printing the following help:
248
260
```tcl
@@ -264,7 +276,7 @@ vunit_run
264
276
265
277
It is also possible to automatically run the test case in the gui while logging all signals and variables recursively using the `--gui=run` flag.
266
278
After simulation the user can manually add objects of interest to the waveform viewer without re-running since everything has been logged.
267
-
When running large designs this mode can be quite slow and it might be better to just do `--gui=load` and manually add a few signals of interest.
279
+
When running large designs this mode can be quite slow and it might be better to just do `--gui` and manually add a few signals of interest.
268
280
269
281
## GHDL - Viewing signals in GTKWave
270
282
Signals can be viewed in GTKWave when using the GHDL simulator and GTKWave executable is found in the `PATH` environment variable.
0 commit comments