12.07.2015 Views

Simulator Configuration Guide for Synopsys Models

Simulator Configuration Guide for Synopsys Models

Simulator Configuration Guide for Synopsys Models

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Simulator</strong> <strong>Configuration</strong> <strong>Guide</strong>vChapter 5: Using NC-Verilog with <strong>Synopsys</strong> <strong>Models</strong>NC-Verilog Utilities Reference Pages$lm_log_test_vectors Command ReferenceThe $lm_log_test_vectors command enables test vector logging <strong>for</strong> a specified instance,and specifies a file name <strong>for</strong> the test vector log.Syntax$lm_log_test_vectors (“instance_path”, on_off, “filename”)Argumentsinstance_pathon_offfilenameSpecifies the pathname of the model instance <strong>for</strong> which testvector logging is to be enabled or disabled.Indicates whether test vector logging is to be enabled ordisabled. Allowed values are 1 to enable logging, or 0 (thedefault) to disable logging.Specifies the file name to be used <strong>for</strong> the test vector log.DescriptionEnables test vector logging <strong>for</strong> a specified instance and specifies a filename <strong>for</strong> the testvector log. By default, test vector logging is not per<strong>for</strong>med. When test vector logging ison, the pin value in<strong>for</strong>mation created during the simulation <strong>for</strong> the specified deviceinstance is written in test vector file <strong>for</strong>mat to filename.For detailed in<strong>for</strong>mation about test vector logging, refer to the ModelSource User’sManual or the LM-family Modeler Manual.ExampleThe following example enables test vector logging <strong>for</strong> the instance “U1”, and saves thetest vector log in the file “U1.log”.$lm_log_test_vectors (“Tbench.U1”, 1, “U1.log”);October 6, 2003 <strong>Synopsys</strong>, Inc. 99

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!