|
|
|
|
|
virtual log
The virtual log command causes the sim-mode dependent signals of the specified virtual signals to be logged by the kernel. If wildcard patterns are used, it will also log any normal signals found, unless the -only option is used. You unlog the signals using the virtual nolog command.
Syntax
virtual log
[-kind <kind>]|[-region <path>] [-recursive] [-only] [-in] [-out] [-inout] [-internal] [-ports] [<signalName>|<pattern>]Arguments
-kind <kind> Specifies a subset of virtuals to look at. Optional. <kind> can be any of the following: signals, functions, designs, implicits, and explicits. Unique abbreviations are accepted.
-region <path> Used in place of -kind to specify a region of design space in which to look for signals to log. Optional.
-recursiveSpecifies that the scope of the search is to descend recursively into subregions. Optional. If omitted, the search is limited to the selected region.
-only Can be used with a wildcard to specify that only virtual signals (as opposed to all signals) found by the wildcard should be logged. Optional.
-inSpecifies that the kernal log data for ports of mode IN whose names match the specification. Optional.
-outSpecifies that the kernal log data for ports of mode OUT whose names match the specification. Optional.
-inoutSpecifies that the kernal log data for ports of mode INOUT whose names match the specification. Optional.
-internalSpecifies that the kernal log data for internal items whose names match the specification. Optional.
-portsSpecifies that the kernal log data for all ports. Optional.
<signalName>|<pattern> Indicates which signal names or wildcard patterns should be used in finding the signals to log. Required. Any number of names or wildcard patterns may be used.
See also
virtual nolog, Virtual Objects (User-defined buses, and more)
|
Model Technology Incorporated Voice: (503) 641-1340 Fax: (503)526-5410 www.model.com sales@model.com |
|
|
|
|
|