Simulator Configuration Guide for Synopsys Models

More documents

Recommendations

Info

Chapter 7: Using QuickSim II with Synopsys ModelsSimulator Configuration GuideTest Vector LoggingThe SIGnal INSTance logvectors -p filename command turns on modeling system testvector logging for the selected instance. With test vector logging enabled, the inputs tothe device and sensed outputs from the device are stored to filename. By convention, thefilename used for the test vector output is device_name.VEC. The SIGnal INSTancenologvectors command turns off test vector logging for the selected instance, which isthe default behavior.For example, consider the following commands:sig inst logvectors -p '$ASIC2/vectors/vector11.VEC'dofile '$ASIC2/dofiles/run11.do'sig inst nologvectorsIn this example, the modeling system creates a test vector file called vector11.VEC.This file contains the vectors played to and sensed from the selected instance during thesimulation run by the dofile. The SIGnal INSTance nologvectors command turns off themodeling system test vector logging capability.After logging vectors, you can replay them directly to the device and note anydiscrepancies using the lm Play Vectors utility. This utility is particularly useful forASIC verification. For more information about ASIC verification and test vector (.VEC)file format, refer to the LM-family Modeler Manual or the ModelSource User’s Manual.Timing MeasurementThe SIGnal INSTance tm [-p filename] command turns on the modeling system timingmeasurement for the selected instance. The system then returns to the simulator theactual measured delay values for that instance. If you provide an optional filename, thesystem also saves the measured delays to a timing measurement (.TIM) file. Byconvention, device_name.TIM is the filename used for the timing measurement output.The SIGnal INSTance notm command turns off timing measurement for the selectedinstance, which is the default behavior. If timing measurement is disabled, theTechnology File delays (or the Shell Software delays if SIGnal INSTance lst isspecified) are returned to the simulator.For example, consider the following commands:sig inst tm -p '$ASIC2/timing/timing11.TIM'dofile '$ASIC2/dofiles/run11.do'sig inst notmIn this example, the modeling system creates a timing measurement file calledtiming11.TIM. This file contains the delays of the selected instance measured during thesimulation run created by the dofile. The SIGnal INSTance notm command turns off themodeling system timing measurement capability.182 Synopsys, Inc. October 6, 2003
Simulator Configuration GuideChapter 7: Using QuickSim II with Synopsys ModelsThis Signal Instance command performs a similar function to that of the lm MeasureTiming utility. Timing measurement is particularly useful for ASIC verification. Formore information about ASIC verification and timing measurement (.TIM) file format,refer to the LM-family Modeler Manual or the ModelSource User’s Manual.NoteThe timing measurement (.TIM) file can be converted to a Shell Softwaredelays (.DLY) file by using the lm Create Timing File utility. (For moreinformation, refer to the LM-family Modeler Manual or the ModelSourceUser’s Manual.) The delays file can then be converted into a technology file,if desired, by using the lm_model utility with the -Step Timing option.Loop ModeThe SIGnal INSTance loop command turns on the modeling system pattern loopingcapability (loop mode) for the currently selected instance. In loop mode, the modelingsystem continually replays the complete pattern history of the selected instance to thedevice. The SIGnal INSTance noloop command turns off pattern looping.Pattern looping is a model development feature useful for analyzing the device behaviorand pattern history with an oscilloscope or logic analyzer connected to the device.However, while loop mode is enabled, no other user can access the modeling system;patterns are replayed to the selected device exclusively until loop mode is disabled. Forthis reason, QuickSim II returns an error if this command is specified when more thanone user is accessing the modeling system.Printing Model InformationA number of Signal Instance commands are available for printing information about theselected model instances. The SIGnal INSTance dump command prints all informationavailable about the currently selected instances, including:●●●Instance IDName of the modeling system in which the hardware model is locatedSetting for test vector logging (On or Off)● Setting for indeterminate strength mapping (S or Z)●●●Setting for Shell Software timing (On or Off)Model name, as specified in the Shell Software device_nameSetting for timing measurement (On or Off)October 6, 2003 Synopsys, Inc. 183
Page 1:
Simulator ConfigurationGuide for Sy
Page 4 and 5:
ContentsSimulator Configuration Gui
Page 6 and 7:
ContentsSimulator Configuration Gui
Page 8 and 9:
FiguresSimulator Configuration Guid
Page 10 and 11:
TablesSimulator Configuration Guide
Page 12 and 13:
PrefaceSimulator Configuration Guid
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Chapter 1: Using Synopsys Models wi
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Chapter 2: Using VCS with Synopsys
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Chapter 3: Using ModelSim Verilog w
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Chapter 4: Using ModelSim VHDL with
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Chapter 5: Using NC-Verilog with Sy
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Chapter 6: Using NC-VHDL with Synop
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Chapter 7: Using QuickSim II with S
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133: Chapter 7: Using QuickSim II with S
Page 174 and 175: .Chapter 7: Using QuickSim II with
Page 192 and 193: Chapter 8: Using Scirocco with Syno
Page 208 and 209: Chapter 9: Using VERA with Synopsys
Page 232 and 233:
Chapter 9: Using VERA with Synopsys
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Chapter 10: Using SystemC with Syno
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Appendix A: Using LMTV with Synopsy
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Appendix B: Using Custom Memory Mod
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
IndexSimulator Configuration Guide$
Page 304 and 305:
IndexSimulator Configuration Guidef
Page 306 and 307:
IndexSimulator Configuration GuideL
Page 308 and 309:
IndexSimulator Configuration GuideQ
Page 310 and 311:
IndexSimulator Configuration GuideS
show all

Simulator Configuration Guide for Synopsys Models

Create successful ePaper yourself

Delete template?

Save as template?