Simulator Configuration Guide for Synopsys Models

More documents

Recommendations

Info

Chapter 7: Using QuickSim II with Synopsys ModelsSimulator Configuration Guide●●Setting for loop mode (On or Off)Runtime vector count● Evaluation status (Enabled or Disabled)The SIGnal INSTance lmc and SIGnal INSTance vector commands print subsets of theinformation provided by SIGnal INSTance dump:●●The SIGnal INSTance lmc -p shell command prints the Shell Software timingsetting (On if you have specified SIGnal INSTance lst; Off if you have not) for theselected instances. SIGnal INSTance lmc -p allshell prints the Shell Software timingsetting for all hardware model instances, if you have at least one instance selected. Ifyou do not specify one of the -p arguments, this command will print a list of theavailable subcommands.The SIGnal INSTance vector command prints the runtime vector count of theselected instances.Performance MonitoringYou can monitor the performance of the hardware modeler and append the results to thesimulator log file after simulation. To enable performance monitoring, in the windowwhere you are running the simulator, enter the following:% setenv LM_OPTION “monitor_performance”For more information, refer to “Performance Monitoring” in the ModelSource User’sManual.Ending the Simulation SessionTermination of a normal simulation session notifies the hardware modeling system thatthe simulation session has ended. All modeling system resources being used by thatsimulation are then made available for other users.If the simulation exits abnormally, “orphaned” processes may exist on the modelingsystem, even though the simulation has terminated. If lmdaemon is running on yourworkstation, it automatically deletes orphaned processes. You can also use the lm AbortUser utility to remove the unwanted processes manually. Both of these methods releasemodeling system resources. (For more information about lmdaemon and the lm utilities,refer to the LM-family Modeler Manual or the ModelSource User’s Manual.)LM-family and ModelSource modeling systems support simulation save and restorecapabilities. When a save simulation state is performed, the state of all hardware modelsbeing used by the simulation session is automatically saved into a QuickSim II savedirectory. Similarly, restoring the simulation state automatically restores the state of themodel as used by the saved simulation, including all stored pattern history.184 Synopsys, Inc. October 6, 2003
Simulator Configuration GuideChapter 7: Using QuickSim II with Synopsys ModelsAttentionIf you are using Shell Software that contains enhanced features—such asmodel state tracking or “when” conditions—the translation to the resultingtechnology file may be incomplete and contain “compromise” statements. Ifyou elect to use the technology file instead of the Shell Software duringsimulation, the device may exhibit incorrect timing and/or behavior. Toeliminate this possibility, translate the technology file from pre-R2.0 ShellSoftware, which does not contain these statements, or use the Shell Softwaredirectly during simulation by issuing the SIGnal INSTance lst command onthe hardware model instance. For more information about this procedure,refer to “Timing Shell Selection” on page 179.lm_model Command ReferenceThe lm_model shell command registers a hardware model by invoking hardware modelregistration and conversion programs.Syntaxlm_model input_dir [output_path] [-Dir name] [-Ifc interface] [-LAbel label][-Mdl mdl_filename] [-Step Register|Symbol|Timing|Update] [-Replace][-VERBose] [-Help] [-Usage] [-VERSion] [-Old] [-LM]Required Argumentinput_dirSpecifies the pathname to the directory containing the files tobe registered. This argument is required and must appear first.All pathname specifications use the following locationconvention:If the pathname is relative, the input_dir is assumed to be inthe working directory, as specified by $MGC_WD. If$MGC_WD is not set, the input_dir is assumed to be in thecurrent working directory.If the pathname starts with a dollar sign ($), the input_dir isassumed to be in the location of the location map variablespecified after the dollar sign.If the pathname is an absolute pathname, the input_dir isassumed to be in the location of the absolute pathname.October 6, 2003 Synopsys, Inc. 185
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:
Page 134 and 135: 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 234 and 235:
Chapter 9: Using VERA with Synopsys
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?