1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
|
.. _simulation_and_runtime:
**********************
Simulation and runtime
**********************
.. _simulation_options:
Simulation options
==================
In most system environments, it is possible to pass options while
invoking a program. Contrary to most programming languages, there is no
standard method in VHDL to obtain the arguments or to set the exit
status.
In GHDL, it is impossible to pass parameters to your design. A later version
could do it through the generics interfaces of the top entity.
However, the GHDL runtime behaviour can be modified with some options; for
example, it is possible to stop simulation after a certain time.
The exit status of the simulation is :samp:`EXIT_SUCCESS` (0) if the
simulation completes, or :samp:`EXIT_FAILURE` (1) in case of error
(assertion failure, overflow or any constraint error).
Here is the list of the most useful options. Some debugging options are
also available, but not described here. The :option:`--help` options lists
all options available, including the debugging one.
.. option:: --assert-level=<LEVEL>
Select the assertion level at which an assertion violation stops the
simulation. `LEVEL` is the name from the `severity_level`
enumerated type defined in the `standard` package or the
:samp:`none` name.
By default, only assertion violation of severity level :samp:`failure`
stops the simulation.
For example, if `LEVEL` was :samp:`warning`, any assertion violation
with severity level :samp:`warning`, :samp:`error` or :samp:`failure` would
stop simulation, but the assertion violation at the :samp:`note` severity
level would only display a message.
Option :option:`--assert-level=none` prevents any assertion violation to stop
simulation.
.. option:: --ieee-asserts=<POLICY>
Select how the assertions from :samp:`ieee` units are
handled. `POLICY` can be :samp:`enable` (the default),
:samp:`disable` which disables all assertion from :samp:`ieee` packages
and :samp:`disable-at-0` which disables only at start of simulation.
This option can be useful to avoid assertion message from
:samp:`ieee.numeric_std` (and other :samp:`ieee` packages).
.. option:: --stop-time=<TIME>
Stop the simulation after :samp:`TIME`. :samp:`TIME` is expressed as a time
value, *without* any space. The time is the simulation time, not
the real clock time.
For example::
$ ./my_design --stop-time=10ns
$ ./my_design --stop-time=ps
.. option:: --stop-delta=<N>
Stop the simulation after `N` delta cycles in the same current time.
.. index:: display time
.. option:: --disp-time
Display the time and delta cycle number as simulation advances.
.. option:: --disp-tree[=<KIND>]
.. index:: display design hierarchy
Display the design hierarchy as a tree of instantiated design entities.
This may be useful to understand the structure of a complex
design. `KIND` is optional, but if set must be one of:
* none
Do not display hierarchy. Same as if the option was not present.
* inst
Display entities, architectures, instances, blocks and generates statements.
* proc
Like :samp:`inst` but also display processes.
* port
Like :samp:`proc` but display ports and signals too.
If `KIND` is not specified, the hierarchy is displayed with the
:samp:`port` mode.
.. option:: --no-run
Do not simulate, only elaborate. This may be used with
:option:`--disp-tree` to display the tree without simulating the whole
design.
.. option:: --vcd=<FILENAME>
.. option:: --vcdgz=<FILENAME>
.. index:: vcd
.. index:: value change dump
.. index:: dump of signals
Option :option:`--vcd` dumps into the VCD file `FILENAME` the signal
values before each non-delta cycle. If `FILENAME` is :samp:`-`,
then the standard output is used, otherwise a file is created or
overwritten.
The :option:`--vcdgz` option is the same as the *--vcd* option,
but the output is compressed using the `zlib` (`gzip`
compression). However, you can't use the :samp:`-` filename.
Furthermore, only one VCD file can be written.
:dfn:`VCD` (value change dump) is a file format defined
by the `verilog` standard and used by virtually any wave viewer.
Since it comes from `verilog`, only a few VHDL types can be dumped. GHDL
dumps only signals whose base type is of the following:
* types defined in the :samp:`std.standard` package:
* :samp:`bit`
* :samp:`bit_vector`
* types defined in the :samp:`ieee.std_logic_1164` package:
* :samp:`std_ulogic`
* :samp:`std_logic` (because it is a subtype of :samp:`std_ulogic`)
* :samp:`std_ulogic_vector`
* :samp:`std_logic_vector`
* any integer type
I have successfully used `gtkwave` to view VCD files.
Currently, there is no way to select signals to be dumped: all signals are
dumped, which can generate big files.
It is very unfortunate there is no standard or well-known wave file
format supporting VHDL types. If you are aware of such a free format,
please mail me (:ref:`Reporting_bugs`).
.. option:: --fst=<FILENAME>
Write the waveforms into a `fst`, that can be displayed by
`gtkwave`. The `fst` files are much smaller than VCD or
`GHW` files, but it handles only the same signals as the VCD format.
.. option:: --wave=<FILENAME>
Write the waveforms into a `ghw` (GHdl Waveform) file. Currently, all
the signals are dumped into the waveform file, you cannot select a hierarchy
of signals to be dumped.
The format of this file was defined by myself and is not yet completely fixed.
It may change slightly. The :samp:`gtkwave` tool can read the GHW files.
Contrary to VCD files, any VHDL type can be dumped into a GHW file.
.. option:: --psl-report=<FILENAME>
Write a report for PSL assertions and coverage at the end of
simulation. The file is written using the JSON format, but still
being human readable.
.. option:: --sdf=<PATH>=<FILENAME>
Do VITAL annotation on `PATH` with SDF file :file:`FILENAME`.
`PATH` is a path of instances, separated with :samp:`.` or :samp:`/`.
Any separator can be used. Instances are component instantiation labels,
generate labels or block labels. Currently, you cannot use an indexed name.
Specifying a delay::
--sdf=min=<PATH>=<FILENAME>
--sdf=typ=<PATH>=<FILENAME>
--sdf=max=<PATH>=<FILENAME>
If the option contains a type of delay, that is :samp:`min=`,
:samp:`typ=` or :samp:`max=`, the annotator use respectively minimum,
typical or maximum values. If the option does not contain a type of delay,
the annotator use the typical delay.
See :ref:`Backannotation`, for more details.
.. option:: --help
Display a short description of the options accepted by the runtime library.
Debugging VHDL programs
=======================
.. index:: debugging
.. index:: `__ghdl_fatal`
Debugging VHDL programs using `GDB` is possible only on GNU/Linux systems.
`GDB` is a general purpose debugger for programs compiled by `GCC`.
Currently, there is no VHDL support for `GDB`. It may be difficult
to inspect variables or signals in `GDB`, however, `GDB` is
still able to display the stack frame in case of error or to set a breakpoint
at a specified line.
`GDB` can be useful to precisely catch a runtime error, such as indexing
an array beyond its bounds. All error check subprograms call the
`__ghdl_fatal` procedure. Therefore, to catch runtime error, set
a breakpoint like this:
(gdb) break __ghdl_fatal
When the breakpoint is hit, use the `where` or `bt` command to
display the stack frames.
|
