Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vcd2vzt(1) [debian man page]

VCD2VZT(1)							Filetype Conversion							VCD2VZT(1)

NAME

       vcd2vzt - Converts VCD files to VZT files

SYNTAX

       vcd2vzt [option]... [VCDFILE] [VZTFILE]

DESCRIPTION

       Converts VCD files to VZT files.

OPTIONS

       -v,--vcdname <filename>
	      Specify VCD input filename.

       -l,--vztname <filename>
	      Specify VZT output filename.

       -d,--depth <value>
	      Specify 0..9 gzip compression depth, default is 4.

       -m,--maxgranule <value>
	      Specify number of granules per section, default is 8.  One granule is equal to 32 timesteps.

       -b,--break <value>
	      Specify break size (default = 0 = off).  When the break size is exceeded, the VZT dumper will dump all state information at the next
	      convenient granule plus dictionary boundary.

       -z,--ziptype <value>
	      Specify zip type (default = 0 gzip, 1 = bzip2, 2 = lzma).  This allows you to override the default compression algorithm	to  use  a
	      more  effective  one  at	the expense of greater runtime.  Note that bzip2 does not decompress as fast as gzip so the viewer will be
	      about two times slower when decompressing blocks.

       -t,--twostate
	      Forces MVL2 twostate mode (default is MVL4).  When enabled, the trace will only store 0/1 values for  binary  facilities.   This	is
	      useful for functional simulation and will speed up dumping as well as make traces somewhat smaller.

       -r, --rle
	      Uses  an	bitwise  RLE compression on the value table.  Default is off.  When enabled, this causes the trace data table to be stored
	      using an alternate representation which can improve compression in many cases.

       -h,--help
	      Show help screen.

       EXAMPLES

       Note that you should specify dumpfile.vcd directly or use "-" for stdin.

       vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --break 1073741824
	      This sets the compression level to 9 and sets the break size to 1GB.

       vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --maxgranule 512
	      Allows more granules per section which allows for greater compression at the expense of memory usage.

LIMITATIONS

       vcd2vzt does not store glitches as these are coalesced together into one value change during the writing of the VZT file.

AUTHORS

       Anthony Bybell <bybell@rocketmail.com>

SEE ALSO

       vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)

Anthony Bybell							      3.1.21								VCD2VZT(1)

Check Out this Related Man Page

VZTMINER(1)						       Dumpfile Data Mining						       VZTMINER(1)

NAME

       vztminer - Data mining of VZT files

SYNTAX

       vztminer [option]... [VZTFILE]

DESCRIPTION

       Mines VZT files for specific data values and generates gtkwave save files to stdout for future reload.

OPTIONS

       -d,--dumpfile <filename>
	      Specify VZT input dumpfile.

       -m,--match <value>
	      Specifies "bitwise" match data (binary, real, string)

       -x,--hex <value>
	      Specifies hexadecimal match data that will automatically be converted to binary for searches

       -n,--namesonly
	      Indicates  that  only  facnames  should  be printed in a gtkwave savefile compatible format.  By doing this, the file can be used to
	      specify which traces are to be imported into gtkwave.

       -c,--comprehensive
	      Indicates that results are not to stop after the first match.  This can be used to extract all the matching values in the trace.

       -h,--help
	      Show help screen.

EXAMPLES

       vztminer dumpfile.vzt --hex 20470000 -n

       This attempts to match the hex value 20470000 across all facilities and when the value is encountered, the facname only is printed to  std-
       out in order to generate a gtkwave compatible save file.

LIMITATIONS

       vztminer  only  prints  the  first time a value is encountered for a specific net.  This is done in order to cut down on the size of output
       files and to aid in following data such as addresses through a simulation model.  Note also that the reader algorithm  attempts	to  recon-
       struct  bitblasted  nets  back into their original vectors but this is not always successful, specifically in the case where the individual
       bitstrands are dumped in non-sequential order.

AUTHORS

       Anthony Bybell <bybell@rocketmail.com>

SEE ALSO

       lxt2miner(1) vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)

Anthony Bybell							       3.2.1							       VZTMINER(1)
Man Page