ams simulator manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:ams simulator manual.pdf
Size: 1857 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 1 May 2019, 18:27 PM
Rating: 4.6/5 from 726 votes.
Status: AVAILABLE
Last checked: 15 Minutes ago!
In order to read or download ams simulator manual ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
ams simulator manualTo browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser. You can download the paper by clicking the button above. The Virtuoso AMS environment and simulator work together to enable you to netlist, compile, elaborate, and simulate a circuit that contains analog, digital, and mixed-signal components. The AMS environment consists of the AMS netlister and AMS Design Prep. The AMS simulator provides both the Spectre and the UltraSim solvers and you can switch back and forth between them as your design evolves. The tools will be used in this tutorial include. If you are used to the 16.2 HDL-AMS flow, things are not going to be radically different in 16.5. IF you have an AMS Studio license, you will also have the Advanced Analysis options, see the pspaugca.pdf in the doc\pspaugca directory, for more information. If you are looking deeper into the model details, take a look at the PSpice Reference Manual, pspcref, in the doc\pspcref directory. You will probably only need to reference the pspug.pdf to get started. Your help and quick reply are appreciated. The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines. The language is object-oriented, which means that the action to be performed on the object is supplied as a modifier to the command. For example, in the following command, database is the object, and -open is a modifier. The command name is always the first or left-most word in the command. -modifiers may have -options.http://www.vinaconexmec.vn/uploads/news_file/kenwood-at-440-manual.xml
- Tags:
- ams simulator manual, ams simulator manual transmission, ams simulator manual download, ams simulator manual software, ams simulator manual pdf.
For example, you might have So you might have a Tcl command and response like the following: For example, consider the following code. Use a semicolon to separate the commands. If a command description includes a cross-reference to a detailed description later in this appendix, use that information to determine how to use the command.The attribute command is enabled only for purely digital designs. This command is enabled only for purely digital designs. This command is enabled only for purely digital designs. Also lets you pass OMI model manager run-time commands to model managers that support this capability. This command is disabled while the analog solver is active. This command is enabled only for purely digital designs.This command is enabled only for purely digital designs.This command is enabled only for purely digital designs. This command can be used only for digital objects. This command is disabled while the analog solver is active. In addition, you cannot use the call command for digital tasks or functions while the analog solver is active.If the name of the task or function contains any dollar signs, you must enclose the argument in curly braces or precede each dollar sign by a backslash.Enclose strings in curly braces or use the backslash character to escape quotes, spaces, and other characters that have special meaning to Tcl. For example: Relative path names are relative to the current debug scope (set by the scope command). Object names can include a bit select or part select. For example: For example, the following two commands result in an error: Therefore, user-defined system functions can be used to generate literals for other commands. For example: This option is available because the call command is also used to invoke functions from the VHDL C-interface, and there may be a user-defined C-interface function with the same name as a PLI system task or function. The -systf option causes the lookup in the C-interface task list to be skipped.http://sterenstein.ru/userfiles/kenwood-at200-manual.xml This option must appear before the task or function name on the command line. You cannot use this option with the -predefined option. The command call -systf with no task or function name argument displays a list of all registered user-defined system tasks and functions. You cannot use the -predefined option when calling a user-defined system task or function. This option must appear before the CFC function name on the command line. You cannot use this option with the -systf option. The command call -predefined with no function name argument displays a list of all predefined C function names. The task and function can also be invoked from the command line. Behaviors that are sensitive to value changes on the object run when the simulation resumes, just as if the value change was caused by the Verilog or VHDL code. In addition, you cannot use the deposit command to set the value of digital objects while the analog solver is active.However, it differs from a force in that future transactions on the signal are not blocked. In VHDL, a deposit with a delay is different from Verilog in that it creates a transaction on a driver, much the same as a VHDL signal assignment statement. Use the -inertial or -transport option to deposit the value after an inertial delay or after a transport delay, respectively. If a delay is specified, you cannot deposit to variables or to signals with multiple sources. Records and non-character array values are not supported, but objects of these types can be assigned to by issuing commands for each subelement individually. If you do not specify a time, the assignment happens immediately, before simulation resumes. If the specified time is the current simulation time, the assignment occurs after simulation resumes, but before time advances. This is the default. This operation might lead to violation of globally static bounds. The equal sign is optional. The assignment occurs at simulation time 10 ns. The resolved discipline is in parentheses.https://skazkina.com/ru/boss-gt-10-user-manual The value is the potential of the net. For example, To see the flow through the branch, use the value -flow command instead. The output of the command does not include the object's value, but the string (-RW). You must specify at least one object. However, even if you have specified access to an object, its drivers may have been collapsed, combined, or optimized away. In this case, the output of the command may indicate that the object has no drivers.By default, the drivers command displays contributions to the driving value. Only VHDL inout and linkage ports can have different driving and effective values. Displays all of the processes (signal assignment statements), resolution functions, and type conversion functions that contribute to the value of the specified signal. If you don't include the -verbose option, resolution and type conversion function information is omitted from the output. A verbose drivers report is displayed (indented) for all inputs to the resolution function. A verbose drivers report is displayed (indented) for the formal port that is the input to the function. A verbose drivers report is displayed (indented) for the actual that is the input to the function. For example: Use the -verbose option to display this additional information. The report also shows that there is a concurrent signal assignment statement contributing as one of the sources to the resolution function. If the analog solver is interactive when the finish command is issued, the analog solver's simulation time is printed; otherwise the digital solver's simulation time is printed. Releasing a force causes the value to immediately return to the value that would have been there if the force hadn't been blocking transactions. In addition, you cannot use the force command on digital objects while the analog solver is active.An error is printed if it does not.https://eastwestmacrobiotics.com/images/95-corolla-repair-manual.pdfThe force can be released by a Verilog release statement or replaced by a Verilog force statement during subsequent simulation. Even if the literal is generated using value substitution or Tcl's expr command, the value is considered to be a constant. The forced value does not change if objects used to generate the literal change value during subsequent simulation. Records and non-character array values are not supported, but objects of these types can be assigned to by issuing commands for each subelement individually. Object x is forced to the current value of w. If you explicitly specify any analog argument objects, the probe command ignores them and the simulator issues a warning. The probe command also ignores any analog objects selected by the -all, -inputs, -outputs, and -ports arguments but does not issue any warning.You can create a VCD database for VHDL objects by using the call command to call predefined CFC routines, which are part of the NC VHDL simulator C interface.If you specify an object as an argument to the probe command, and that object does not have read access, an error message is printed. If you specify a scope as an argument to the probe command, objects within that scope that do not have read access are excluded from the probe and a warning message is printed.The -create modifier is optional. The -create modifier can be followed by an argument that specifies: The digital object(s) to be traced The scope(s) to trace A combination of object(s) and scope(s) An object must have read access in order to be probed. If no argument is specified, the current debug scope is assumed, but you must include an option that specifies which objects to include in the trace ( -all, -inputs, -outputs, or -ports ). You must include an option to specify the database into which values are dumped. The database must already exist. -shm Send the probe to the default SHM database. If no default database is open, a default database called ncsim.shm is opened. -vcd Send the probe to the default VCD database. If no default database is open, a default database called ncsim.vcd is opened. This applies to: The current debug scope, if no scope(s) or object(s) is named in an argument The scope(s) named in the argument The subscopes specified with the -depth option Use -all -variables to include VHDL variables in the probe. This database must be open. The -database option does not create a database for you. If you do not include the -database option, you must include either the -shm or -vcd option to specify that you want to save the probe to the default SHM or VCD database, respectively. You must specify one of the following arguments: n Descend the specified number of scopes. For example, -depth 1 means include only the given scope, -depth 2 means include the given scope and its subscopes, and so on. The default is 1. all Include all scopes in the hierarchy below the specified scope(s).This applies to: The current debug scope (if no scope(s) or object(s) is named in an argument) The scope(s) named in the argument Subscopes specified with the -depth option The name you assign to a probe can then be used with the -disable, -enable, -delete, and -show modifiers. If you do not use -name to name your probes, every probe you create is given a sequential number. This applies to: The current debug scope (if no scope(s) or object(s) is named in an argument) The scope(s) named in the argument Subscopes specified with the -depth option This applies to: The current debug scope (if no scope(s) or object(s) is named in an argument) The scope(s) named in the argument Subscopes specified with the -depth option This option cannot be used with any other probe command-line option. Include the -redirect option to redirect the output to a file. For example: probe -screen -redirect myfile sum Use the -format option to specify the output format. Variables and objects are paired sequentially with specifiers. Valid formats are: b --Binary format. The argument must be an object name that is either a scalar object or a logic vector. d --Decimal format. The argument must be an object name whose type is integer, physical, or enumeration. f --Real number in floating-point notation. The argument must be an object whose base type is real. o --Unsigned octal object. The argument must be a scalar object or a logic vector. s --Substitute. The argument is substituted on an as-is basis. x --Unsigned hex object. The argument is an object name that is either a scalar object or a logic vector. v --Default value format. The argument must be a signal or a variable name. The value of the object is formatted appropriately, according to its type. The simulator opens a default database named ncsim.shm if one does not already exist. The associated file is ncsim.shm. The file is placed in the current working directory. You must use the -all option with -variables. A default database named ncsim.vcd is opened if one does not already exist. The associated file is ncsim.vcd. The file is placed in the current working directory. SHM probes can be deleted at any time. VCD probes can only be deleted at the time the VCD database is created. Once the simulation is advanced, the VCD header is written to the file and no modifications to the probes are possible. While the probe is disabled, values for the objects in that probe are not written to the database. To resume probing, use the -enable modifier. SHM probes can be disabled individually at any time. VCD probes cannot be disabled individually. Use database -disable to disable all VCD probes. As soon as the probe resumes, all objects in the probe have their values written to the database. If no filename argument is specified, the script is printed to the screen. If you don't include an argument, information on all probes is displayed. Use the -database option to print information on probes in a specified database. All objects have read access. Data is sent to the default SHM database. If no default SHM database exists, a default database called ncsim.shm in the file ncsim.shm is created. The -create modifier is not required.Data is sent to the default VCD database.Data is sent to the database waves. This database must already exist.When either of these signals changes value, output is displayed on the screen. Releasing a force causes the value to immediately return to the value that would have been there if the force hadn't been blocking transactions. In addition, you cannot use the release command on digital objects while the analog solver is active.The behavior is the same as that of a Verilog release statement. Cannot release digital object: top.sar.b6 The time-zero snapshot, created by the elaborator, must still be available. For example: In this case, an error message is issued, and a list of available snapshots is printed. That is, you cannot use the restart command to load a snapshot of a different elaborated design or one that comes from a different elaborated design. To load a different model, exit ncsim and then invoke it with the new snapshot. Any probes and breakpoints are deleted. If you want to restore the full Tcl debug environment when you restart, make sure that you save the environment with the save -environment command. This command creates a Tcl script that captures the current breakpoints, databases, probes, aliases, and predefined Tcl variable values. You can then use the Tcl source command after restarting or the -input option when you invoke the simulator to execute the script. For example, This snapshot can be loaded using either of the following two restart commands. A second save command is issued to save the Tcl debug environment. If you exit the simulator, you can restart with the saved snapshot and then restore the debug settings by sourcing the script created with the save -environment command. Because the view name is not specified, the snapshot name is ambiguous if there is more than one view, and an error message is issued. You can only restart snapshots of the same elaborated design. A simulation cycle consists of two phases: signal evaluation and process execution. In VHDL, a process is a process statement. In Verilog-AMS it is an always block, an initial block, or some other behavior that can be scheduled to run.The time specification can be absolute or relative. Relative is the default. In addition to time units such as fs, ps, ns, us, and so on, you can use deltas as the unit. For example,If you include a time specification, the simulator stops at the specified time with the digital solver active. If you include a time specification and a breakpoint or interrupt stops simulation before the specified time is reached, the time specification is thrown away. For example, in the following sequence of commands, the last run command does not stop the simulation at 500 ns.Note: The -step option does not step into function calls made by an analog statement. In this situation, the behavior of the -step option is identical to the behavior of the -next option. The -timepoint option is not required. With a time specification, -relative is the default. The subprogram can be a task, function, or procedure. They both run the simulation for 5 delta cycles. For example, if you are simulating worklib.top:rtl, The simulator cannot be in the middle of executing procedural statements. Use the run -clean command to run the simulation to the next point at which the save command will work. If a library database exceeds this limit, you cannot add objects to the database. If you save many snapshot checkpoints to unique views in a single library, this file size limit could be exceeded. If you reach this limit, you can:For example, For example, For example, To save the debug environment, you must issue a separate save -environment command. You can then restore the environment by executing this script with the Tcl source command, or you can use the -input option when you invoke the simulator. If you invoke the simulator, set some breakpoints and probes, and then source a script that contains commands to set breakpoints and probes, the simulator will probably generate errors telling you that some commands in the script could not be executed. These errors are due to name conflicts. You can, of course, give your breakpoints unique names to avoid this problem. You can also edit the scripts to make them work the way you would like them to work.If no file name is specified, the script is written to standard output. This option is the default. Note: This option can be used with only pure digital designs. Note: This option can be used with only pure digital designs. Nor can you describe such a scope, or list its drivers or source lines.If used with -recurse, the -all option recursively lists all AICM instances in the entire design. If no scope is specified, objects in the current debug scope are described. For objects without read access, the output of scope -describe does not include the object's value. For objects that have read access but no write access, the string (-W) is included in the output. For objects with neither read nor write access, the string (-RW) is included in the output.There are three possible arguments to the -sort option: name --sort alphabetically by name kind --sort by declaration type (reg, wire, instance, branch, etc.) declaration --sort by the order in which objects are declared in the source code If no scope is specified, the drivers of digital objects in the current debug scope are displayed. The output of scope -drivers includes only the digital objects that have read access. However, even if an object has read access, its drivers may have been collapsed, combined, or optimized away, and the output of the command might indicate that the object has no drivers.If used with -recurse, recursively lists all resolved net disciplines in the entire design. The default is to sort by discipline. You can follow the -list modifier with: No range of lines to print all lines for the scope. One line number to display that line of source text. Two line numbers to display the text between those two line numbers.If no scope or other option is given, the name of the current scope is printed. The -set modifier is optional. The -set modifier is not required. The -set modifier is not required. No description is included. Objects are listed in alphabetical order. Objects are sorted by type of declaration. Objects are listed in the order in which they were declared in the source code. In this example, only the drivers for wires and registers with read access are shown. When the analog solver is active, the delta cycle count is not displayed. This modifier must be followed by an option that specifies the breakpoint type: -condition -delta (VHDL only) -line -object -process (VHDL only) -time The simulator does not support stop points on individual bits of registers. If a bit-select of a register appears in the expression, the simulator stops and evaluates the expression when any bit of that register changes value. The same holds true for compressed wires. An error is printed if the object does not have read access.The simulator does not go into interactive mode. The delta cycle specification can be absolute or relative (the default). If absolute, the breakpoint is automatically deleted after the delta cycle is reached and the breakpoint triggers. If relative, the delta cycle specification is an interval, and the breakpoint stops the simulation every n delta cycles. Use -start to specify the absolute delta cycle at which a repetitive breakpoint is to begin firing. If this cycle is before the current cycle, the first stop occurs at the next cycle at which it would have occurred had the stop been set at the cycle specified with -start. Use -modulo to specify the absolute delta cycle of the first stop cycle for a repeating delta cycle stop. This differs from -start only when the given cycle is more than one repeat interval in the future. In this case, the first stop occurs at a delta cycle less than or equal to one interval in the future such that a stop eventually occurs at the given cycle. For example, if you set a delta breakpoint to stop the simulation every 10 delta cycles, and specify -modulo 15, the simulation stops at delta cycle 5, 15, 25, and so on. When you execute a save -environment command to save your debug environment, this option is written to the script to restore your delta breakpoint pattern.If the command that you want to execute requires an argument, enclose the command and its argument in curly braces. You also can specify that you want to execute a list of commands. Separate the commands with a semi-colon. Tcl, however, displays only the output of the last command. The breakpoint triggers only if the given Tcl boolean expression evaluates to true (non-zero, non-x, non-z). This option can be used with any breakpoint type. Objects included in an -if expression must have read access. An error is printed if the object does not have read access.You can set breakpoints on both analog and digital code statements. You must specify which design unit contains the line. There are two ways to do this: Use -unit. The stop occurs whenever the line number in the specified design unit is about to execute, no matter where in the design hierarchy that unit appears. Specify the name of a particular scope in the design hierarchy. This creates an instance-specific breakpoint. The breakpoint occurs only for that particular instance of the corresponding design unit, no matter where else it may appear in the design hierarchy. If the scope name is omitted, then the current debug scope is used. This is necessary if the design unit has multiple source files. You must compile with the -linedebug option to enable the setting of line breakpoints.This name can then be used to delete, disable, or enable the breakpoint. If you do not use -name, breakpoints are numbered sequentially. Note: You cannot create object breakpoints for analog objects. The object specified as the argument must have read access for the breakpoint to be created. An error is printed if the object does not have read access.You must compile with the -linedebug option to enable the setting of process breakpoints.You can use -skip to set a breakpoint on the n'th occurrence of an event; in particular, you can use it to get inside for loops. The time can be absolute or relative (the default). Absolute time breakpoints are automatically deleted after they trigger. Relative time breakpoints are periodic, stopping, for example, every 10 ns.If this time is before the current simulation time, the first stop occurs at the next future time at which it would have occurred had the stop been set at the time specified with -start. Use -modulo to specify the absolute simulation time of the first stop time for a repeating stop. This differs from -start only when the given time is more than one repeat interval in the future. In this case, the first stop occurs at a time less than or equal to one interval in the future such that a stop eventually occurs at the given time. For example, if you set a time breakpoint to stop the simulation every 100 ns, and specify -modulo 250, the simulation stops at time 50, 150, 250, and so on. When you execute a save -environment command to save your debug environment, this option is written to the script to restore your time breakpoint pattern.If no breakpoint is specified, all breakpoints are shown.The -create modifier is not required. Because the -name option is not included to specify a breakpoint name, ncsim assigns a sequential number as the name. This breakpoint is called 1. The breakpoint is ignored the first 3 times it triggers. The value data command is executed when the breakpoint triggers. Because the value command requires an argument, it must be enclosed in curly braces. The value data command is executed when the breakpoint triggers. The -continue option prevents the simulator from entering interactive mode every time the stop triggers. The -delbreak option specifies that the breakpoint is deleted after it triggers three times. The breakpoint occurs on all scopes which are instances of the same module. For example if there are two instances of module m16, as follows: Both commands create non-instance-specific breakpoints. This is necessary if the scope has multiple source files. The breakpoint is automatically deleted after it triggers. The -relative option is the default for time breakpoints. The -start option specifies the absolute time at which the breakpoint starts. For example, if the current simulation time is 300 ns, the breakpoint stops the simulation at time 600, 800, 1000, and so on. The absolute time specified with -start is before the current simulation time. The first stop occurs at the next future time at which it would have occurred had the stop been set at the time specified with -start. In this example, the first stop occurs at time 450 ns. Suppose that you simulate to time 300 ns and then set a repetitive breakpoint with the following command: If you then execute a save -environment command to save your debug environment, the following line is written to the script: In this example, if you reinvoke the simulation and start at time 0, the breakpoint triggers the first time at time 150. It then triggers at 350, 550, 750, and so on. The breakpoint is automatically deleted after it triggers. The -start option specifies the absolute delta cycle at which the breakpoint starts. For example, if the current delta cycle count is 0, the breakpoint stops the simulation when the delta cycle count is 30, 40, 50, and so on. The signal count is available from the top level of the hierarchy. For example, you can set the breakpoint on count as follows: Vectors must be enclosed in quotation marks, as shown in the next example. For VHDL, single-bit entities must be enclosed in single quotation marks. An explicit value command is used to get the value of count (bit 0) into the expression parser. This breakpoint stops the simulation at the next positive edge of the clock if en1 or en2 is 1. After that, clock changes depending on the condition in the if expression, and this happens repeatedly every 5 ns. The -continue option is used to prevent the simulation from stopping every time the breakpoint triggers. VHDL requires use of the single quotation marks. The first command creates a source line breakpoint called break1; the second creates an object breakpoint called break2. The third command shows the status of the two breakpoints. Both options require a Tcl expression argument. A condition breakpoint triggers when any digital object named in the Tcl expression has an event that would trigger an object breakpoint and the expression evaluates to non-zero, non-x, or non-z. Although condition breakpoints are not triggered by changes in analog objects, you can include analog objects in the conditional expression and their values are used when the condition is evaluated (due to a digital object changing value). The Tcl expression argument is evaluated, and the stop triggers if the expression evaluates to non-zero, non-x, or non-z. For example, the following command generates an error message. For example, The unit can be: For example, Note: The -delta option is ignored if the analog solver is active. At any given simulation time, values of nets are first updated and then behaviors that are sensitive to those nets are executed. This two step process may be repeated any number of times because of zero-delays.