FPGA/myhdl
1
0
Fork 0
mirror of https://github.com/myhdl/myhdl.git synced 2025-01-24 21:52:56 +08:00
Code Issues Projects Releases Wiki Activity

changes

Browse Source
This commit is contained in:
jand 2003-08-03 16:03:39 +00:00
parent 1ca6689bac
commit 99ee6b7c9a
1 changed files with 13 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
doc/whatsnew03/whatsnew03.tex
View File

@ -29,9 +29,8 @@ loaded and viewed in a waveform viewer tool such as \program{gtkwave}.
The user interface of this feature consists of a single function,
\function{traceSignals()}. To explain how it works, recall that in
\myhdl{}, an instance is created by calling a function that returns a
sequence of generators, and by assigning the result to an instance
name. For example:
\myhdl{}, an instance is created by a function call and by assigning
the result to an instance name. For example:
\begin{verbatim}
tb_fsm = testbench()
@ -44,20 +43,15 @@ instead:
tb_fsm = traceSignals(testbench)
\end{verbatim}
All signals in the instance hierarchy will be traced in
an output VCD file called \file{tb_fsm.vcd}. Note that the argument of
\function{traceSignals()} consists of the uncalled function. By calling
the function under its control, \function{traceSignals()} gathers
information about the hierarchy and the signals to be traced. In
addition to a function argument, \function{traceSignals()} accepts an
arbitrary number of non-keyword and keyword arguments that will be
All signals in the instance hierarchy will be traced in an output VCD
file called \file{tb_fsm.vcd}. Note that first the argument of
\function{traceSignals()} consists of the uncalled function. By
calling the function under its control, \function{traceSignals()}
gathers information about the hierarchy and the signals to be traced.
In addition to a function argument, \function{traceSignals()} accepts
an arbitrary number of non-keyword and keyword arguments that will be
passed to the function call.
The restrictions on VCD tracing are as follows. First, only
\class{Signal} objects can be traced. Second, only a hierarchy of
instances returned by a pre-simulation top level function call can be
traced.
Signals are dumped in a suitable format. This format is inferred at
the \class{Signal} construction time, from the type of the initial
value. In particular, \class{bool} signals are dumped as single
@ -218,13 +212,10 @@ def top(...):
\end{verbatim}
This permits fine grained control: for example, it
is possible to return a different set of instances
under parameter control.
However, having to return instances explicitly can be inconvenient,
especially if there are a large number of them. Therefore, \myhdl\ 0.3
provides a function \function{instances()} which assembles a list of
all instances automatically. It is used as follows:
It may be convenient to assemble the list of instances automatically,
especially if there are a large number of instances. For this purpose,
\myhdl\ 0.3 provides the function \function{instances()}.
It is used as follows:
\begin{verbatim}
from myhdl import instances