Documente Academic
Documente Profesional
Documente Cultură
Guide
Product Version 6.1.5
April 2011
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Licensing in amsDmv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Related Documents for amsDmv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installation, Environment, and Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Virtuoso Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Third-Party Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Typographic and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SKILL Syntax Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Form Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1
Getting Started with amsDmv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The amsDmv Model Validation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simulators Supported By amsDmv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the Virtuoso Design Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting amsDmv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting amsDmv from the Virtuoso Environment . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting amsDmv from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up the Environment for Using amsDmv from an IC 5.1.41 Session . . . . . . .
The amsDmv User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering or Modifying Values in Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sorting Data in Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................
Viewing Tooltips for Help Information
Specifying amsDmv Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
16
17
18
19
19
21
23
24
25
29
31
32
32
33
33
35
April 2011
amsDmv Examples
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2
Setting Up and Running Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
3
Validating Measured Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
April 2011
4
Validating Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113
Validating Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying Global Options for Validating Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying Maximum Acceptable Tolerance Values for Analog Signals . . . . . . . . . .
Specifying Logic Time Tolerance Values for Digital Signals . . . . . . . . . . . . . . . . . . .
Filtering Glitches in Digital Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating Only Signals With Specific Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Validation of Signals With Specific Names . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Validation of Specific Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating Only Waveform Signals for Specific Analyses . . . . . . . . . . . . . . . . . . . . .
Validating Only Signals for Specific ADE XL Tests . . . . . . . . . . . . . . . . . . . . . . . . . .
Excluding Specific Time Ranges of Waveform Signals from Validation . . . . . . . . . .
Validating Only Specific Time Ranges of Waveform Signals . . . . . . . . . . . . . . . . . .
Working with Local Options for Validating Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying Local Options for Validating Analog Signals . . . . . . . . . . . . . . . . . . . . . .
114
121
121
123
124
126
127
128
128
129
129
130
130
130
April 2011
132
135
136
136
139
140
141
143
145
146
146
146
146
147
5
Running Pin Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
6
amsDmv Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
156
156
167
175
April 2011
Preface
AMS Design and Model Validation (amsDmv) is an integrated model validation solution that
enables you to validate differences in measured and simulated behavior and interfaces of
reference (for example, design) and compared (for example, model) blocks.
This manual describes how you can setup and run amsDmv. The information presented in
this manual is intended for integrated circuit designers and assumes that you are familiar with
analog, digital and mixed-signal design and simulation.
This preface consists of the following sections:
April 2011
Licensing in amsDmv
amsDmv requires one of the following licenses. The first available license will be checked out
in the order given below:
1. 95200 Virtuoso(R) Analog Design Environment L
2. 95210 Virtuoso(R) Analog Design Environment XL
3. 95220 Virtuoso(R) Analog Design Environment - GXL
Important
If you want to use amsDmv from an IC 5.1.41 session, ensure that you have a
95200 Virtuoso(R) Analog Design Environment L license, or upgrade
your 34510 Virtuoso(R) Analog Design Environment license to the 95200
license. The 95200 license is compatible with the IC 5.1.41 release. Hence, you can
continue using Analog Design Environment in IC 5.1.41 using the 95200 license.
For more information on licensing, see Virtuoso Software Licensing and Configuration
Guide.
For information on installing Cadence products, see the Cadence Installation Guide.
For information on the Virtuoso design environment, see the Virtuoso Design
Environment User Guide.
For information on database SKILL functions, including data access functions, see the
Virtuoso Design Environment SKILL Reference.
For information on library structure, the library definitions file, and name mapping for data
shared by multiple Cadence tools, see the Cadence Application Infrastructure User
Guide.
April 2011
Virtuoso Tools
Virtuoso Schematic Editor L User Guide and Virtuoso Schematic Editor XL User
Guide describe Cadences schematic editor.
Virtuoso Analog Design Environment GXL User Guide describes the ADE GXL
environment.
Virtuoso Spectre Circuit Simulator User Guide and Virtuoso Spectre Circuit
Simulator Reference describe Cadences Spectre analog circuit simulator.
Virtuoso AMS Designer Simulator User Guide describes Cadences AMS mixedsignal circuit simulator.
Virtuoso Visualization and Analysis Tool User Guide contains information for
viewing waveforms and post-processing simulation results.
Third-Party Tools
To view any .swf multimedia files, you need:
Flash-enabled web browser, for example, Internet Explorer 5.0 or later, Netscape 6.0 or
later, or Mozilla Firefox 1.6 or later. Alternatively, you can download Flash Player (version
6.0 or later) directly from the Adobe website.
Speakers and a sound card installed on your computer for videos with audio.
April 2011
argument (z_argument)
Words in italics indicate user-defined arguments for which you
must substitute a name or a value. (The characters before the
underscore (_) in the word indicate the data types that this
argument can take. Names are case sensitive. Do not type the
underscore (z_) before your arguments.)
[ ]
Three dots (...) indicate that you can repeat the previous
argument. If you use them with brackets, you can specify zero or
more arguments. If they are used without brackets, you must
specify at least one argument, but you can specify more.
argument
[argument]
If a command line or SKILL expression is too long to fit inside the paragraph margins of this
document, the remainder of the expression is put on the next line and indented.
When writing the code, put a backslash (\) at the end of any line that continues on to the next
line.
April 2011
10
g_arg1
( )
[ ]
=>
A right arrow points to the return values of the function. Also used
in code examples in SKILL manuals.
...
Three dots indicate that the preceding item can appear any
number of times.
Example 2
needNCells(
s_cellType | st_userType
x_cellCount
)
=> t/nil
Form Examples
Each form shows you the system defaults:
April 2011
11
April 2011
12
1
Getting Started with amsDmv
This chapter describes the following topics:
Introduction on page 14
April 2011
13
Introduction
Behavioral models may initially be validated by the designer against the original transistor
level design. However, as designs evolve and change over time, designers may not have the
time to continuously validate models against the modified designs. Using the original (out of
sync) model can result in errors such as pin list mismatches between the design and the
model, or worse, incorrect model behavior that hides design flaws. Because of this,
continuous model validation is mandatory in the design creation process.
AMS Design and Model Validation (amsDmv) is an integrated model validation solution that
allows you to validate differences in measured and simulated behavior and interfaces of
reference (for example, design) and compared (for example, model) blocks.
Note: amsDmv is supported in IC 5.1.41, IC 6.1.4 ISR 3, and later releases. However, before
you use amsDmv from the IC 5.1.41 release, you must setup your system as described in
Setting Up the Environment for Using amsDmv from an IC 5.1.41 Session on page 23.
amsDmv supports the following:
Ability to use models created using any modeling language, such as Verilog, VerilogAMS, wreal, VHDL-AMS, schematic, SPICE, SystemC, and so on. This is because
amsDmv compares only measured results and waveforms, and is independent of the
modeling language used.
Ability to reuse existing testbenches and simulation setup in ADE states and ADE XL
views.
Ability to save the amsDmv setup as an executable script and a SKILL file. These files
can be used to run the setup from the UNIX command line (using the script file) or from
the CIW (using the SKILL file) as part of a scheduled regression run.
April 2011
14
Application
Note: Automatic model validation is not a replacement for accurate modeling or detailed
manual model validation. Model validation complements the modeling process. Given that a
complete verification of the model was done when the model was created, it might be
sufficient to run a sanity check only as regression setup.
April 2011
15
16
The analysis of the measured results and waveform signals that have a fail status.
5. Running model validation again on the corrected design and model to verify that all
measured results and waveform signals have a pass status and that there are no
differences between the pin/module interfaces of the reference design and the compared
model.
SpectreVerilog
UltraSimVerilog
April 2011
17
Type the following command if you are using an IC 6.1or later installation:
virtuoso &
The CIW appears. You can start amsDmv from the CIW. See Starting amsDmv on
page 19 for more information.
April 2011
18
Starting amsDmv
You can start amsDmv from the Virtuoso environment or the command line.
Note the following:
Before you start amsDmv, ensure that the simulators you want to use with amsDmv are
setup in your path. For more information about the simulators supported by amsDmv, see
Simulators Supported By amsDmv on page 17
Important
Before you start amsDmv from an IC 5.1.41 session, you must setup your system
as described in Setting Up the Environment for Using amsDmv from an IC 5.1.41
Session on page 23.
The AMS Design and Model Validate form appears. For more information about this form, see
The amsDmv User Interface on page 24.
Note: Figure 1-2 and 1-3 show the AMS Design and Model Validate form that appears in the
IC 6.1 and IC 5.1.41 releases. The ADE XL run type is not displayed in the form for the IC
5.1.41 release because ADE XL is not available in the IC 5.1.41 release.
April 2011
19
April 2011
20
April 2011
21
Note the following when you start amsDmv from the command line:
The ADE L, ADE XL and SKILL run types are not displayed in the AMS Design and
Model Validate form because these run types are not supported in command line mode.
April 2011
22
Pin checking is not supported as this feature requires the Virtuoso environment.
The amsDmv.ile file is an encrypted SKILL file containing the procedures for using
amsDmv in Virtuoso.
Caution
If you use amsDmv from an IC 5.1.41 session, do not setup your
environment to use the IC 6.1.4 ISR 3 or later releases because this can
result in significant issues with the IC 5.1.41 software. You only need to
set the AMS_DMV_PATH environment variable and load the amsDmv.ile
file in your .cdsinit file as described in steps 3 and 4 above.
April 2011
23
The following sections describe the parts and features of the amsDmv user interface:
Toolbar on page 29
April 2011
24
Tabs on page 31
Menu Bar
The menu bar in amsDmv has the following menus.
File
Edit
Run
View
File
The options in the File menu are described below:
Description
New
Open View
Save View
Save as View
April 2011
25
Description
Open File
Save File
Saves the current amsDmv setup to a file so that you can load it
later.
For more information, see Saving the amsDmv Setup on
page 85.
Save As File
Save Log
Exit
April 2011
26
Description
Preferences
Pre/Post Run
Clear Log
Run
The options in the Run menu are described below:
Description
Run Simulations
April 2011
27
Description
Validate
View
The options in the View menu are described below:
Description
Show/Hide Options
Show/Hide Log
Displays the ADE L user interface for the last simulation run.
This allows you to debug the last simulation run if it failed for
some reason, or some waveforms or measured results are not
as expected.
April 2011
28
Toolbar
The buttons in the amsDmv toolbar are described below:
Icon
Name
Description
New Setup
Open Setup
Save Setup
Save Setup
As
Save Setup
As
Executable
Script
Save Log To
File
April 2011
29
Icon
Name
Description
Run
Runs simulations on the reference and compared data
Simulation
sources specified in the Source tab and displays the validation
and Validation results in the Measured Results and Waveform Signals tabs.
For more information, see Chapter 2, Setting Up and
Running Simulations.
Stop
Simulation
Load and
Validate
Results and
Waveforms
Validate
Currently
Loaded
Results and
Waveform
Signals
Show/Hide
Options
Edit
Preferences
April 2011
30
Icon
Name
Description
Show/Hide
Log
Tabs
The tabs in the AMS Design and Model Validate form are described below:
Tip
You can select the Advanced Mode check box in the Preferences for AMS Design
and Model Validation form to enable and use advanced amsDmv features in the
tabs. For more information about the Advanced Mode check box, see Specifying
amsDmv Options on page 35.
Tab
Description
Source
Measured Results
Waveform Signals
April 2011
31
Tab
Description
Pin Check
Allows you to verify whether there are any differences between the
pin/module interfaces of the reference design and the compared
model.
For more information about using this tab, see Chapter 5, Running
Pin Checks.
Status
April 2011
32
Click on the name of the column based on which you want to sort the data.
Note: Sorting may be inaccurate if the Use Engineering Notation check box is selected in
the Preferences for AMS Design and Model Validation form.
April 2011
33
Place the mouse pointer on a field to view the tooltip for the field.
Tooltip
April 2011
34
Click the
toolbar button.
The Preferences for AMS Design and Model Validation form appears.
April 2011
35
Option
Description
Advanced Mode
April 2011
36
Option
Description
Statistics
Run Update
SimVision
April 2011
37
Option
Description
Using icxx
Split Buses
DCM
Use Engineering
Notation
April 2011
38
amsDmv Examples
Examples for amsDmv are available in the /tools/dfII/samples/dcm/amsDmv/
directory of your IC 6.1 installation.
Note: These examples are not available in your IC 5.1.41 installation.
Each example contains:
A README file that describes the objective of the example and the steps to work through
it.
A files directory that contains the files saved or created by working through the
example.
The following examples can be run using amsDmv from an IC 6.1.4 ISR 3 or later installation:
Example
Description
amsDmvAdeXlRun.tar.Z
amsDmvAdeXlWreal.tar.Z
amsDmvAmsIrun.tar.Z
amsDmvAmsSst2.tar
amsDmvPinCheck.tar.Z
amsDmvPsfData.tar
amsDmvRdbData.tar.Z
April 2011
39
Example
Description
amsDmvAdeIC5141.tar.Z
amsDmvIC5141PinCheck.tar.Z
April 2011
40
2
Setting Up and Running Simulations
The Source tab in the AMS Design and Model Validate form allows you to setup and run
simulations on the reference (for example, design) and compared (for example, model)
blocks so that the resulting waveform signals and measured results can be compared and
validated using amsDmv. You can also specify an existing ADE XL result database and
waveform directory from which measured results and waveforms need to be loaded and
validated.
This chapter describes the following topics:
Running a Simulation to Compare with Existing Measured Results and Waveform Signal
Data on page 68
Comparing Existing Measured Results and Waveform Signal Data for Reference and
Compared Data Sources on page 72
Specifying a Different Run Type for the Compared Data Source on page 75
April 2011
41
Saving the amsDmv Setup as an Executable Script and a SKILL File on page 87
April 2011
42
Connect the floating digital output to some analog primitivefor example, to a 0 Amp
current source or a high ohm resistor.
Set the net to have the electrical discipline by doing one of the following:
Similarly, if the output of an analog design inside a digital testbench is connected to a net in
the testbench that is not used in the digital context, the wire will remain in the analog domain.
In such cases, you can do one of the following to force the AMS Designer simulator to make
the conversion from analog to digital:
Set the net to have the logic discipline by doing one of the following:
April 2011
43
For more information about disciplines, discipline resolution and connect modules, see
"Mixed-Signal Aspects of Verilog-AMS" in the Cadence Verilog-AMS Language
Reference.
April 2011
44
3. Right-click on the Value column in the Reference Data Source group box and choose
Browse to existing ADE setup.
April 2011
45
Click
To
Directory
April 2011
46
Click
To
Do the following:
1. Select the library, cell and view for the reference data source, then
click OK.
The Simulator form appears.
2. From the Select simulator drop-down list, select the simulator you
want to use, then click OK.
The Select optional top state directory form appears if the DCM
check box is selected in the Preferences for AMS Design and Model
Validation form. Select the directory containing the ADE state you
want to use and click Choose.The Select state form appears.
3. Select the ADE state you want to use to run simulations on the
reference data source and click Choose.
April 2011
47
Click
To
Library/
Cell/View
The names of the selected library, cell, view, simulator and state are displayed in the
Reference Data Source group box.
April 2011
48
Select
To
New View/
Config
Specify that the compared data source will use the setup in the ADE
state specified for the reference data source for simulation purposes,
but will use a different design or config view for simulation purposes.
To specify the config view for the compared data source, do the
following:
1. Right-click on the Value column in the Compared Data Source
group box and choose Browse Override view/config.
The Select override view/config form appears.
snapshot needs to be updated
April 2011
49
Select
To
Tip
You can also double-click on any row in the Value column in
the Compared Data Source group box to specify the library,
cell and view names. For more information, see Entering or
Modifying Values in Fields on page 32.
Tip
You can right-click on the Value column in the Compared
Data Source group box and choose Open ADE L to view
the simulation setup for the compared data source in ADE L.
New Settings Specify a different ADE state for the compared data source.
To specify the ADE state for the compared data source, do the
following:
1. Right-click on the Value column in the Compared Data Source
group box and choose Browse to existing ADE setup.
The Type of ADE Setup form appears.
Tip
You can double-click on any row in the Value column in the Reference Data Source
or the Compared Data Source group box to specify the library, cell, view,
simulator, alternate state directory and state names. For more information, see
Entering or Modifying Values in Fields on page 32.
April 2011
50
Tip
You can right-click on the Value column in the Reference Data Source or the
Compared Data Source group box and choose Open ADE L to view the
simulation setup for the data source in ADE L.
6. Run simulation by doing one of the following:
Click the
toolbar button.
For more information about running simulations, see Starting a Simulation on page 79.
7. The following message box appears after the simulation runs for the reference and
compared data sources are completed.
8. Click OK.
9. Use the Measured Results and Waveform Signals tabs to validate the differences
reported in the measured results and waveform signals for the reference and compared
data sources.
The measured results from ADE simulation runs are not saved to a persistent result
database. Because of this, you can use amsDmv to validate the measured results only
while the ADE simulation session is active. Therefore, if you run an ADE simulation using
amsDmv in regression mode, you cannot debug failures reported for measured results
April 2011
51
Open the amsDmv user interface and re-run the ADE simulation to debug the
failures reported for measured results.
For more information about running amsDmv in regression mode, see Running an
amsDmv Script File on page 88 and Running an amsDmv SKILL File on page 88.
The waveform data created from ADE simulation runs are stored in a SignalScan Turbo 2
(SST2) database. So, you can use amsDmv to validate waveform signals from ADE
simulation runs even after the ADE simulation session is closed.
April 2011
52
3. Right-click on the Value column in the Reference Data Source group box and choose
Browse to existing ADE XL view.
The Select ADE XL View form appears.
April 2011
53
5. From the Select ADE XL history to load and run drop-down list, select the history
item you want to use and click OK.
The names of the selected library, cell, view and history item are displayed in the
Reference Data Source group box. The settings in the history item are used for running
the simulation.
For more information about ADE XL history items, see the Virtuoso Analog Design
Environment XL User Guide.
April 2011
54
Tip
Rename the reference history item in ADE XL to, say,
amsDmvReferenceHistory, so that it is easy to remember the reference history
item. Also, lock the history item in ADE XL so that it does not get deleted accidently.
6. In the Compared Data Source group box, do one of the following:
Select
To
New View/
Config
Specify that the compared data source will use the setup in the
ADE XL view specified for the reference data source for simulation
purposes, but will use a different design or config view for
simulation purposes.
To specify the config view for the compared data source, do the
following:
1. Right-click on the Value column in the Compared Data
Source group box and choose Browse Override view/config.
The Select override view/config form appears.
April 2011
55
Select
To
Tip
You can also double-click on any row in the Value column
in the Compared Data Source group box to specify the
library, cell and view names. For more information, see
Entering or Modifying Values in Fields on page 32.
New Settings
April 2011
56
Select
To
3. From the Select ADE XL history to load and run drop-down
list, select the history item you want to use and click OK.
The names of the selected library, cell, view and history item are
displayed in the Compared Data Source group box. The
settings in the history item are used for running the simulation.
Tip
Rename the compared history item in ADE XL to, say,
amsDmvComparedHistory, so that it is easy to
remember the compared history item. Also, lock the history
item in ADE XL so that it does not get deleted accidently.
Tip
You can double-click on any row in the Value column in the Reference Data
Source or Compared Data Source group box to specify the library, cell, view, and
history item names. For more information, see Entering or Modifying Values in
Fields on page 32.
Tip
You can right-click on the Value column in the Reference Data Source or
Compared Data Source group box and choose Open ADE XL to open the ADE
XL view for the data source in ADE XL.
7. Run simulation by doing one of the following:
Click the
toolbar button.
For more information about running simulations, see Starting a Simulation on page 79.
April 2011
57
9. Click OK.
10. Use the Measured Results and Waveform Signals tabs to validate the differences
reported in the measured results and waveform signals for the reference and compared
data sources.
Running simulations using SKILL or OCEAN commands is supported only when you run
amsDmv from the Virtuoso environment(see Starting amsDmv from the Virtuoso
Environment on page 19). This is not supported when you run amsDmv from the UNIX
command line (see Starting amsDmv from the Command Line on page 21).
The SKILL or OCEAN commands can be directly specified in the Source tab, or you can
specify the path to a file containing the SKILL or OCEAN commands.
To setup and run simulation using SKILL or OCEAN commands, do the following:
April 2011
58
3. In the Reference Data Source group box, do the following to specify the options for
simulating the reference data source:
April 2011
59
April 2011
Click ADE XL view to specify the ADE XL view in which the result database
exists.
60
4. In the Compared Data Source group box, do the following to specify the options for
simulating the compared data source:
a. In the SKILL command field, type the SKILL or OCEAN commands required to
simulate the compared data source.
If the SKILL or OCEAN commands exist in a file, specify the path to the file.
Note: You can use the text AMSDMVDIR in the SKILL or OCEAN commands instead
of specifying the path to the current working directory (the directory in which you
started Virtuoso or amsDmv).
b. (Optional) To validate waveforms, right-click on the Value column next to the
Waveform directory field and choose Browse to waveform directory to select
the directory in which waveforms for the compared data source exist.
c. (Optional) To validate measured results from an ADE XL simulation run, right-click
on the Value column next to the ADE XL result database field and choose
Browse to ADE XL result database to specify the location of the ADE XL result
database for the compared data source.
April 2011
61
Click ADE XL view to specify the ADE XL view in which the result database
exists.
The Select Compared ADE XL view form appears. Select the ADE XL view and
click OK.
Click the
toolbar button.
For more information about running simulations, see Starting a Simulation on page 79.
April 2011
62
6. Click OK.
7. Use the Measured Results and Waveform Signals tabs to validate the differences
reported in the measured results and waveform signals for the reference and compared
data sources.
April 2011
63
3. In the Reference Data Source group box, do the following to specify the options for
simulating the reference data source:
April 2011
64
Note: If you started amsDmv from the UNIX command line (see Starting amsDmv
from the Command Line on page 21), the Open ADE XL reference result database
form appears instead of the Browser form. Select the ADE XL result database file
and click Open.
Do one of the following:
April 2011
Click ADE XL view to specify the ADE XL view in which the result database
exists.
65
4. In the Compared Data Source group box, do the following to specify the options for
simulating the compared data source:
a. In the System command field, type the system commands required to simulate the
compared data source.
If the system commands exist in a file, specify the path to the file. Alternatively, rightclick on the Value column next to the System command field and choose Browse
to script file to select the file.
Note: You can use the text AMSDMVDIR in the system commands instead of
specifying the path to the current working directory (the directory in which you
started Virtuoso or amsDmv).
b. (Optional) To validate waveforms, right-click on the Value column next to the
Waveform directory field and choose Browse to waveform directory to select
the directory in which waveforms for the compared data source exist.
c. (Optional) To validate measured results from an ADE XL simulation run, right-click
on the Value column next to the ADE XL result database field and choose
April 2011
66
Click ADE XL view to specify the ADE XL view in which the result database
exists.
The Select Compared ADE XL view form appears. Select the ADE XL view and
click OK.
April 2011
Click the
toolbar button.
67
For more information about running simulations, see Starting a Simulation on page 79.
The following message box appears after the simulation runs are complete.
6. Click OK.
7. Use the Measured Results and Waveform Signals tabs to validate the differences
reported in the measured results and waveform signals for the reference and compared
data sources.
April 2011
68
3. In the Reference Data Source group box, do the following to specify the paths to the
existing waveform signal data and ADE XL results database for the reference data
source:
a. (Optional) Right-click on the Value column next to the Waveform directory field
and choose Browse to waveform directory.
The Reference Waveform Directory form appears. Select the waveform directory for
the reference data source and click Choose.
b. (Optional) Right-click on the Value column next to the ADE XL result database
field and choose Browse to ADE XL result database.
April 2011
69
Select
To
ADE L
ADE XL
SKILL
System
For example, in the following figure, the path to an existing ADE XL result database file
is specified for the reference data source and an ADE XL simulation is setup for the
compared data source so that the ADE XL results database created for the compared
April 2011
70
Click the
toolbar button.
For more information about running simulations, see Starting a Simulation on page 79.
April 2011
71
6. Click OK.
7. Use the Measured Results and Waveform Signals tabs to validate the differences
reported in the measured results and waveform signals for the reference and compared
data sources.
April 2011
72
3. In the Reference Data Source group box, do the following to specify the paths to the
existing waveform signal data and ADE XL results database for the reference data
source:
April 2011
73
Choose Run Load and Validate to load and validate the measured results and
waveform signals.
Click the
signals.
Click the Measured Results tab to load and validate measured results.
Click the Waveform Signals tab to load and validate waveform signals.
toolbar button to load and validate the measured results and waveform
6. Use the Measured Results and Waveform Signals tabs to validate the differences
reported in the measured results and waveform signals for the reference and compared
data sources.
April 2011
74
April 2011
75
April 2011
76
Select
To
ADE L
ADE XL
SKILL
System
April 2011
77
April 2011
78
The system commands can be directly specified in this form. If the system
commands exist in a file, click the browse button to select the file.
The environment variables set by system commands are applicable only when the
commands are run. They will not be used by other system commands. For example,
the environment variables specified in the Prerun command field for the reference
data source will not be used when the commands specified in the Postrun
command field for the reference data source are run. This allows you to specify
different values for the same environment variable in different system commands.
In the Prerun command field, specify the commands that need to be run before the
simulation of the reference data source.
In the Postrun command field, specify the commands that need to be run after the
simulation of the reference data source.
In the Prerun command field, specify the commands that need to be run before the
simulation of the compared data source.
In the Postrun command field, specify the commands that need to be run after the
simulation of the compared data source.
4. Click OK.
Starting a Simulation
To start a simulation, do one of the following:
Click the
toolbar button.
Runs simulations for the reference and compared data sources. When simulations are
run, amsDmv performs the following actions, in the following order:
a. Runs the pre-run commands, if any, specified for the reference data source.
b. Simulates the reference data source.
c. Runs the post-run commands, if any, specified for the reference data source.
April 2011
79
Displays the progress and status of the simulation run in the Source tab and in the
amsDmv log.
For example, in the following figure, the progress and status of the simulation run is
displayed in the Source tab and in the amsDmv log.
Indicates simulations
are running
For more information about the amsDmv log, see Using the amsDmv Log on page 81.
April 2011
80
If you started amsDmv from the CIW (see Starting amsDmv from the Virtuoso
Environment on page 19), displays the progress and status of the simulation run, and
simulation errors, if any, in the CIW.
If you started amsDmv from the UNIX command line (see Starting amsDmv from the
Command Line on page 21), simulation errors, if any, are displayed in the terminal from
which amsDmv was started.
Displays a Simulations Finished message box after the simulation runs are complete.
Stopping a Simulation
To stop a simulation that is running, do the following:
Click the
toolbar button.
Note: A stopped simulation can be restarted but cannot be resumed from where it was
stopped.
April 2011
81
Click the
toolbar button.
amsDmv Log
Click the
April 2011
toolbar button.
82
Click the
toolbar button.
April 2011
83
Tip
You can also view the summary of the simulation and validation status in the report
(.rep) file that is located in the directory in which you started Virtuoso or amsDmv.
April 2011
84
Note: There are no refernces to views when the amsDmv is launched from a UNIX command
line.
April 2011
85
Note: Select the Filter checkbox to view the library names containing only the particular view
type.
April 2011
86
Click the
toolbar button.
The Save command line filename (to execute current setup) form appears.
2. Specify the path and name of the script file, then click Save.
A message box appears indicating that the current setup is saved to an executable script
file and to a SKILL file.
April 2011
87
Return Code
Description
April 2011
88
Virtuoso and amsDmv will be run in nograph mode. This allows you to run the script on
servers that don't have any displays.
The progress and status of the simulation run, and simulation errors, if any, are displayed
in the terminal.
You can view the progress of an ADE XL simulation run by viewing the latest Job*.log
file in the logs_<userName> directory that is created in the directory in which you run
amsDmv. For example, you can use the following command to view the progress of the
ADE XL simulation run:
tail -f logs_guest/Job0.log
A summary report of the validation status is displayed in the terminal after the simulation
run for the reference and compared data sources are complete.
The detailed simulation and validation status is written to a report (.rep) file that has the
same name as the amsDmv script file. For example, if you run an amsDmv script named
myamsDmvSetup, the report file will be named myamsDmvSetup.rep. You can view the
detailed validation status by opening the report file in a text editor.
For example, the following message that is displayed in the terminal after the simulation
is complete indicates that all simulations were completed successfully, all validation
checks have passed and that the detailed validation status is written to a report file
named myamsDmvSetup.rep.
amsDmv: PASS: Simulation completed successfully. 57 checks passed.
Created report file 'myamsDmvSetup.rep'
April 2011
89
The Virtuoso log file is written to a log (.log) file that has the same name as the
amsDmv script file. For example, if you run an amsDmv script named myamsDmvSetup,
the log file will be named myamsDmvSetup.log.
After the run is complete, you can use the following command in the UNIX terminal to
view the return code for the script:
echo $?
Return Code
Description
April 2011
90
3
Validating Measured Results
This chapter describes the following topics:
April 2011
91
April 2011
92
April 2011
93
Description
Result
Test
Name of the ADE XL test for which the result was saved
during the simulation run.
Note: The test names are displayed only for measured results
from ADE XL simulation runs. For more information, see
Setting Up and Running Simulations Using ADE XL on
page 52.
Status
April 2011
94
Column
Description
Options
April 2011
95
Option
Description
Absolute Tolerance
Enabled Results
Disabled Results
April 2011
96
Option
Description
Tests
Result Exclude
Result Window
Specifies that only the ADE XL results that fall within the
specified range of swept or corner points should be
included for validation.
For more information, see Including Only Specific Swept or
Corner Points of ADE XL Measured Results for Validation
on page 102.
3. Correct the design or the model based on the analysis of the results that have a Fail
status.
4. Run model validation again on the corrected design and model to verify that all measured
results have a Pass status.
April 2011
97
Excluding Specific Swept or Corner Points of ADE XL Measured Results from Validation
on page 102
Including Only Specific Swept or Corner Points of ADE XL Measured Results for
Validation on page 102
In the Relative Tolerance (%) field, specify the % maximum acceptable tolerance value
for the worst-case relative deviation reported for results.
In the Absolute Tolerance field, specify the maximum acceptable tolerance value for
the worst-case absolute deviation reported for results.
Note: If a reference result value is zero or very close to zero, the relative tolerance will not be
applied unless the compared result is identical to the reference result. In such cases, you
must specify some small absolute tolerance value, say, 1p, to ensure that the results are
compared.
April 2011
98
April 2011
99
(a|b|c)* to validate only the results whose names start with the letters a, b and c.
amp*out to validate only the results whose names start with the letters amp and end
with the letters out.
in[^d]* to validate only the results whose names start with the letters in but not
the results starting with letters ind.
Note: Only the results with matching names will be validated and displayed in the Measured
Results tab.
See also:
(a|b|c)* to disable the validation of results whose names start with the letters a,
b and c.
amp*out to disable the validation of results whose names start with the letters amp
and end with the letters out.
in[^d]* to disable the validation of results whose names start with the letters in
but not the results starting with letters ind.
April 2011
100
For more information about the Disabled Results field, see Disabling Validation of Results
With Specific Names on page 100.
Tip
To enable validation of a result that is disabled, delete the name of the result from
the regular expression that is displayed in the Disabled Results field. The enabled
result is then validated and displayed in the Measured Results tab.
101
timing to validate only the results for the test named timing.
(t1|t2) to validate only the results for the tests named t1 and t2.
*power* to validate only the results for the tests whose names contain the text
power.
Note: Only the results from the tests with matching names will be validated and displayed in
the Measured Results tab.
See also:
Specify the range of swept or corner points in the Result Exclude field.
Use the following syntax to specify a comma separated list of the range of points:
from:to[,from:to]
For example, specify 4:9,12:18 to exclude the results for the points that fall with the range
starting from 4 to 9 and 12 to 18. The Status column displays a Pass status for the results
that fall within the specified range, and a Fail status for the results that fall outside the
specified range.
April 2011
102
Specify the range of swept or corner points in the Result Window field.
Use the following syntax to specify a comma separated list of the range of points:
from:to[,from:to]
For example, specify 1:43,55:126 to include only the results for the points that fall with the
range starting from 1 to 43 and 55 to 126. The Status column displays a Pass status for the
results that fall outside the specified range, and a Fail status for the results that fall within the
specified range.
April 2011
103
Note: By default, this form displays the values specified in the Global Results Options
group box or the local options that had been previously saved for this result. You can
modify the values as required.
3. (Optional) Specify the maximum acceptable tolerance values for the result in the
Relative Tolerance (%) and Absolute Tolerance fields.
For more information about these fields, see Specifying Maximum Acceptable Tolerance
Values for Results on page 98.
4. (Optional) To exclude a specific range of ADE XL swept or corner points in the result from
validation, specify the range of points in the Result Exclude field.
For more information about the Result Exclude field, see Excluding Specific Swept or
Corner Points of ADE XL Measured Results from Validation on page 102
5. (Optional) To include only a specific range of ADE XL swept or corner points in the result
for validation, specify the range of points in the Result Window field.
For more information about the Result Window field, see Including Only Specific Swept
or Corner Points of ADE XL Measured Results for Validation on page 102
6. Click OK.
The Options column in the Measured Results tab indicates that local options are
specified for the result. For example, the text Local: reltol=2, abstol=0.5 in the
April 2011
104
April 2011
105
Right-click the result and choose Result Options Revert options for this result to
use global values.
April 2011
106
Right-click the result and choose Show point details for this result.
The <resultName> measured result form appears displaying the point details for the
result.
Note: The absolute or relative difference of a point that falls within the specified absolute or
relative tolerance value is displayed in green color indicating that the point is passing for the
result. The absolute or relative difference of a point that falls outside the specified absolute or
relative tolerance value is displayed in red color indicating that the point is failing for the result.
Right-click the result that has the Fail status and choose Show failing points for this
result.
April 2011
107
April 2011
108
After excluding a failing point for a result from validation, you can include it for validation by
doing the following:
April 2011
109
2. In the Result Exclude field, delete the range for the point you want to include for
validation.
The point is displayed as a failing point for validation. For information about viewing the
failing points for a result, see Viewing the Failing Points for ADE XL Results on page 107.
April 2011
110
Selecting Results
Note: Before you select results, ensure that the Advanced Mode check box in the
Preferences for AMS Design and Model Validation form is selected. For more information
about the Advanced Mode check box, see Specifying amsDmv Options on page 35.
To select a specific result, do the following:
Select the check box next to the result in the Selected column.
Deselecting Results
To deselect a specific result, do one the following:
Deselect the check box next to the result in the Selected column.
April 2011
111
Click the
toolbar button.
To show the Global Results Options group box, do one of the following:
Click the
April 2011
toolbar button.
112
4
Validating Waveforms
This chapter describes the following topics:
April 2011
113
Validating Waveforms
The Waveform Signals tab in the AMS Design and Model Validate form allows you to compare
and validate the analog and digital waveform signals for the reference (for example, design)
and compared (for example, model) data sources specified in the Source tab.amsDmv
supports validation of only waveform data that is in the SignalScan Turbo 2 (SST2) format.
To validate waveform signals, do the following:
1. On the Waveform Signals tab, select the Validate Waveform Signals check box.
The Analog group box in the Waveform Signals tab displays the following information for
analog signals:
Note: The Analog group box is displayed only if analog signals are loaded from the
April 2011
114
Column
Description
Signal
Test
Name of the ADE XL test for which the analog signal was
saved during the simulation run.
Note: The test names are displayed only for measured
results from ADE XL simulation runs. For more information,
see Setting Up and Running Simulations Using ADE XL on
page 52.
Type
Status
April 2011
115
Column
Description
Options
April 2011
116
Column
Description
Signal
Test
Name of the ADE XL test for which the digital signal was
saved during the simulation run.
Note: The test names are displayed only for measured
results from ADE XL simulation runs. For more information,
see Setting Up and Running Simulations Using ADE XL on
page 52.
Type
Status
Function
April 2011
117
Column
Description
Timing Difference
Field
Description
Analog Options
April 2011
118
Field
Description
Analog Relative
Tolerance (%)
Analog Absolute
Tolerance
Logic Options
Logic Time Tolerance
Common Options
Enabled Signals
April 2011
119
Field
Description
Disabled Signals
Signal Dataset
Tests
2. Correct the design or the model based on the analysis of the signals that have a Fail
status.
3. Run model validation again on the corrected design and model to verify that all waveform
signals have a Pass status.
April 2011
120
Specifying Maximum Acceptable Tolerance Values for Analog Signals on page 121
Specifying Logic Time Tolerance Values for Digital Signals on page 123
Excluding Specific Time Ranges of Waveform Signals from Validation on page 129
In the Analog Relative Tolerance (%) field, specify the % maximum acceptable
tolerance value for the worst-case relative deviation reported for analog signals.
April 2011
121
In the Analog Absolute Tolerance field, specify the maximum acceptable tolerance
value for the worst-case absolute deviation reported for analog signals.
Note: If a reference signal value is zero or very close to zero, the relative tolerance will not
be applied unless the compared signal is identical to the reference signal. In such cases, you
must specify some small absolute tolerance value, say, 1p, to ensure that the signals are
compared.
The Status column displays a Pass status for the analog signals that fall within the specified
tolerance value, and a Fail status for the analog signals that fall outside the specified
tolerance value. This allows you to validate only the analog signals with the Fail status.
For example, in the following figure, analog signals that fall within the specified relative
tolerance value of 5% have a Pass status. Analog signals that fall outside the relative
tolerance value have a Fail status.
April 2011
122
The default unit of time for the Logic Time Tolerance field is seconds.
The logic time tolerance value is applied only if there are no functional differences
between a reference and compared signal.
For example, in the following figure, the Timing Difference column indicates a pass status
(indicated by the green color text) for the top.clk signal because the maximum time
difference of 900p at a simulation time of 45n is less than the specified 1n logic time
tolerance value. However, the top.invOut signal has a timing failure (indicated by the red
April 2011
123
Note: The Timing Difference column in the above figure displays the Not Checked status
for the top.d[13:0] and top.pwlOut signals because the reference and compared
signals are functionally different (indicated by the text Different in the Function column).
April 2011
124
April 2011
125
April 2011
126
(a|b|c)* to validate only the signals whose names start with the letters a, b and c.
amp*out to validate only the signals whose names start with the letters amp and
end with the letters out.
in[^d]* to validate only the signals whose names start with the letters in but not
the signals starting with letters ind.
Note: Only the signals with matching names will be validated and displayed in the Waveform
Signals tab.
See also:
(a|b|c)* to disable the validation of signals whose names start with the letters a,
b and c.
amp*out to disable the validation of signals whose names start with the letters amp
and end with the letters out.
in[^d]* to disable the validation of signals whose names start with the letters in
but not the signals starting with letters ind.
Note: The signals with matching names will not be validated or displayed in the Waveform
Signals tab.
See also:
April 2011
127
For more information about the Disabled Signals field, see Disabling Validation of Signals
With Specific Names on page 127.
Tip
To enable validation of a signal that is disabled, delete the name of the signal from
the Disabled Signals field. The enabled signal is then validated and displayed in
the Waveform Signals tab.
April 2011
128
timing to validate only the signals for the test named timing.
(t1|t2) to validate only the signals for the tests named t1 and t2.
*power* to validate only the signals for the tests whose names contain the text
power.
Note: Only the signals from the tests with matching names will be validated and displayed in
the Waveform Signals tab.
See also:
For example, specify 70n:72n,110n:112n to exclude the time range starting from 70n to
72n and 110n to 112n when validating each signal.
April 2011
129
For example, specify 70n:72n,110n:112n to validate only the time range starting from 70n
to 72n and 110n to 112n for each signal.
April 2011
130
Tip
To specify local options for more than one signal at a time, select the signals, then
right-click on any of the selected signals and choose Signal Options Set options
for selected signals. For more information about selecting signals, see Selecting
Signals on page 146.
The Signal Options form appears.
Note: By default, this form displays the values specified in the Global Signal Options
group box in the Waveform Signals tab or the local options that had been previously
saved for this signal. You can modify the values as required.
3. (Optional) Specify the maximum acceptable tolerance values for the analog signal in the
Analog Relative Tolerance (%) and Analog Absolute Tolerance fields.
For more information about these fields, see Specifying Maximum Acceptable Tolerance
Values for Analog Signals on page 121.
4. (Optional) In the Signal Time Exclude field, specify the time ranges that should be
excluded when validating the signal. Only the time ranges that fall outside the specified
time ranges will be validated for the signal.
For more information about the Signal Time Exclude field, see Excluding Specific Time
Ranges of Waveform Signals from Validation on page 129.
5. (Optional) In the Signal Time Window field, specify the time ranges that should be
validated for the signal. The time ranges that fall outside the specified time ranges will not
be validated for the signal.
For more information about the Signal Time Window field, see Validating Only Specific
Time Ranges of Waveform Signals on page 130.
6. Click OK.
April 2011
131
April 2011
132
Note: By default, this form displays the values specified in the Global Signal Options
group box in the Waveform Signals tab or the local options that had been previously
saved for this signal. You can modify the values as required.
3. (Optional) Specify the maximum acceptable time difference (skew) between transition
times on the reference and compared digital signal in the Logic Time Tolerance field.
For more information about the Logic Time Tolerance field, see Specifying Logic Time
Tolerance Values for Digital Signals on page 123.
4. (Optional) Specify a time value in the Logic Glitch Filter field to filter any glitch that is
equal to or smaller in width than the specified time value from digital signals.
For more information about the Logic Glitch Filter field, see Filtering Glitches in Digital
Signals on page 124.
April 2011
133
April 2011
134
April 2011
135
Right-click the signal and choose Signal Options Revert options for this signal to
use global values.
Right-click the signal and choose Show failing areas for this signal.
The Signal Failing Areas form appears displaying the failing areas for the signal.
Right-click a failing area and choose Plot Signal Failing Area to plot the failing area.
April 2011
136
Reference
Signal
Compared
Signal
For more information about plotting signals, see Plotting Signals on page 143.
Right-click a failing area and choose Plot Signal Failing Area with other selected
signals to plot the failing area along with other signals that are selected in the Waveform
Signals tab. For more information about selecting signals in the Waveform Signals tab,
see Selecting Signals on page 146.
For example, the waveform window in the following figure highlights a failing area with
the time range from 71.09ns to 71.46ns for signal dn and also displays the plots for
the same time range for signals dnb and up that are selected in the Waveform Signals
April 2011
137
Exclude failing areas of signals from validation. For more information, see Excluding
Failing Areas of Signals from Validation on page 141.
April 2011
138
Right-click the signal and choose Show point details for this signal.
The <signalName> waveform signal form appears displaying the point details for the
signal.
Note: The absolute or relative difference of a point that falls within the specified absolute or
relative tolerance value is displayed in green color indicating that the point is passing for the
signal. The absolute or relative difference of a point that falls outside the specified absolute
or relative tolerance value is displayed in red color indicating that the point is failing for the
signal.
You can do the following in the <signalName> waveform signal form:
Right click the column for a failing point and choose Show failing areas for this signal
to view the failing areas for the signal at that point. For more information, see Viewing the
Failing Areas at a Point on page 140.
Right click the column for a failing point and choose Plot this signal to plot the signal.
For more information about plotting signals, see Plotting Signals on page 143.
April 2011
139
The <signalName> Signal Failing Areas form appears displaying the start and end
range of differences between the reference and compared signals that exceeded the
April 2011
140
April 2011
141
After excluding a failing area for a signal from validation, you can include it for validation by
doing the following:
1. Right-click the signal in the Waveform Signals tab and choose Signal Options Set
options for this signal.
April 2011
142
2. In the Signal Time Exclude field, delete the range for the failing area you want to
include for validation.
The area is displayed as a failing area for validation. For information about viewing the failing
areas at a point for a signal, see Viewing the Failing Areas at a Point on page 140.
Plotting Signals
You can plot signals for debugging purposes.
Note the following:
If you are running amsDmv from an IC 6.1 installation, you can plot signals using
SimVision or the Virtuoso Visualization and Analysis tool. If you are running amsDmv
from an IC 5.1.41 installation, you can plot signals using SimVision or WaveScan.
The Virtuoso Visualization and Analysis tool is used as the default plotting tool if you are
running amsDmv from an IC 6.1 installation, and WaveScan is used as the default
plotting tool if you are running amsDmv from an IC 5.1.41 installation.
To use SimVision as the default plotting tool, select the SimVision check box in the
Preferences for AMS Design and Model Validation form. For more information, see
Specifying amsDmv Options on page 35.
SimVision is used as the default plotting tool if digital signals exist in the waveform data
because plotting logic failing areas with SimVision is easier than with the Virtuoso
Visualization and Analysis tool or WaveScan (in IC 5.1.41). To use the Virtuoso
Visualization and Analysis tool or WaveScan for plotting waveform data that contains
digital signals, deselect the SimVision check box in the Preferences for AMS Design and
Model Validation form.
April 2011
143
By default, bus signals are plotted as a single waveform in SimVision. To plot each bit of
bus signals as separate waveforms in SimVision, select the Split Buses check box in
the Preferences for AMS Design and Model Validation form. For more information, see
Specifying amsDmv Options on page 35.
In the waveform window, the suffix (ref) is used to indicate signals in the reference data
source and the suffix (cmp) is used to indicate signals in the compared data source.
For example, in the following plot for signal dn, the red trace with the suffix (cmp) is for
the signal in the compared date source and the blue trace with the suffix (ref) is for the
signal in the reference data source.
Reference
Signal
Compared
Signal
144
April 2011
145
Selecting Signals
Note: Before you select signals, ensure that the Advanced Mode check box in the
Preferences for AMS Design and Model Validation form is selected. For more information
about the Advanced Mode check box, see Specifying amsDmv Options on page 35.
To select a specific signal, do the following:
Select the check box next to the signal in the Selected column.
Deselecting Signals
To deselect a specific signal, do the following:
Deselect the check box next to the signal in the Selected column.
Click the
April 2011
toolbar button.
146
Click the
toolbar button.
Click OK to close the message box and do one of the following to view the updated
validation results in the Waveform Signals tab:
Click the
toolbar button.
Tip
Choose Run Validate or click the
toolbar button only after you make all the
required changes in the options. This saves time because validation is run only
once.
April 2011
147
April 2011
148
5
Running Pin Checks
Pin checking allows you to verify whether there are any differences between the pin and
module interfaces of the reference design and the compared model. You can verify whether:
Pin names, pin order and pin direction are the same between the reference design and
the compared model.
Module names are the same between the reference design and the compared model.
April 2011
149
April 2011
150
5. Select the library, cell, and view for the reference design and click OK.
The reference library, cell, and view names are displayed in the Reference column.
Tip
You can right-click the Reference column in the Library, Cell and Views group
box and choose Open to open the reference view for editing. If the reference view
is a schematic view, it is opened in Virtuoso Schematic Editor. If the reference view
is a text view, such as a verilog view, it is opened in a text editor.
6. Right-click the Compared column in the Library, Cell and Views group box and
choose Browse.
April 2011
151
7. Select the library, cell, and view for the compared model and click OK.
The library, cell, and view names for the compared model are displayed in the
Compared column.
Tip
You can right-click the Compared column in the Library, Cell and Views group
box and choose Open to open the compared view for editing. If the compared view
is a schematic view, it is opened in Virtuoso Schematic Editor. If the compared view
is a text view, such as a verilog view, it is opened in a text editor.
8. In the Validate group box, select the Views Exist check box to verify that the reference
and compared library, cell, and views:
The Status column displays the Passed status if the checks are successful.
Note: The other pin checks in the Validate group box are enabled only if the Views
Exist check is successful.
April 2011
152
Select
To check whether
Pin Names
Pin Order
Pin names and pin order are the same in the reference and
compared views
Pin Direction
Module name
The Status column in the Validate group box displays the status for each check as
Passed or Failed. The Report group box displays the errors identified for each check
April 2011
153
Progress
Indicator
10. Correct the pin check errors and perform a pin check again to verify that all the errors are
corrected.
Tip
To open the compared or reference view for editing from amsDmv, right-click the
Compared or Reference column in the Library, Cell and Views group box and
choose Open.
April 2011
154
6
amsDmv Command Reference
The amsDmv command allows you to run amsDmv from the UNIX command line. The
amsDmv command syntax is given below:
amsDmv [-help] [optional_arguments]
Use the following command to view information about all the options available in the amsDmv
command:
amsDmv -help
April 2011
155
Description
-cmppostrun 'value'
-cmppostruntype 'value'
-cmppostruntype
-cmpprerun 'value'
-cmppreruntype 'value'
-cmppreruntype
-load 'value'
April 2011
156
Description
-localoptionsfile 'value'
-pinscmpcell 'value'
-pinscmplib 'value'
-checkpins
-pinscmpview 'value'
-checkpins
-pinsrefcell 'value'
-checkpins
April 2011
-checkpins
157
Description
-pinsreflib 'value'
-pinsrefview 'value'
-checkpins
-refpostrun 'value'
-checkpins
-refpostruntype 'value'
-refprerun 'value'
-refpreruntype 'value'
-repfile 'value'
April 2011
158
Description
-resabstol 'value'
-rescmp 'value'
-resexclude 'value'
-simcmpnone
-resref 'value'
-resreltol 'value'
-simrefnone
-restest 'value'
April 2011
159
Description
-results 'value'
-resultsdisable 'value'
-reswindow 'value'
-simaxlcmpcell 'value'
-simaxlcmphistory 'value'
-simaxlcmplib 'value'
-simaxlcmpview 'value'
April 2011
160
Description
-simaxlconfigcmpcell 'value'
-simaxlconfigcmplib 'value'
-simaxlconfigcmplib
-simaxlconfigcmpview
-simaxlconfigcmpview 'value'
-simaxlconfigcmpcell
-simaxlconfigcmpview
-simaxlconfigcmplib
-simaxlconfigcmpcell
-simaxlrefcell 'value'
-simaxlrefhistory 'value'
-simaxlreflib 'value'
April 2011
161
Description
-simaxlrefview 'value'
-simskillcmp 'value'
-simskillref 'value'
-simstatecmpcell 'value'
-simstatecmpdir 'value'
-simstatecmplib 'value'
-simstatecmpname 'value'
-simstatecmpsim 'value'
-simstatecmpview 'value'
-simstateconfigcmpcell 'value'
April 2011
-simstateconfigcmplib
-simstateconfigcmpview
162
Description
-simstateconfigcmplib 'value'
-simstateconfigcmpview 'value'
-simstateconfigcmpcell
-simstateconfigcmpview
-simstateconfigcmplib
-simstateconfigcmpcell
-simstaterefcell 'value'
-simstaterefdir 'value'
-simstatereflib 'value'
-simstaterefname 'value'
-simstaterefsim 'value'
-simstaterefview 'value'
April 2011
163
Description
-simsyscmp 'value'
-simsysref 'value'
-simcmpsys
-wavabstol 'value'
-simrefsys
-wavcmp 'value'
-wavdataset 'value'
-simcmpnone
April 2011
164
Description
-wavexclude 'value'
-wavglitchtime 'value'
-wavref 'value'
-wavreltol 'value'
-simrefnone
-wavsignals 'value'
April 2011
165
Description
-wavsignalsdisable 'value'
-wavtest 'value'
-wavtimetol 'value'
-wavwindow 'value'
April 2011
166
Description
-advanced
-allplots
-batch
April 2011
167
Description
-checkpins
-pinscmpcell
-pinscmplib
-pinscmpview
-pinsrefcell
-pinsreflib
-pinsrefview
-pinsdirection
-pinsexist
-pinsmodulename
-pinsnames
-pinsorder
-dcm
-exit
-help
-icxx
-interactive
April 2011
168
Description
-keepsims
-pinsdirection
-pinsexist
-pinsmodulename
-pinsdirection
-pinsmodulename
-pinsnames
-pinsorder
-pinsnames
-pinsorder
Checks whether the pin names and pin order are the
same in the reference and compared views.
-run
-runupdate
April 2011
169
Description
-simcmpade
-simcmpadexl
-simstatecmpcell
-simstatecmpdir
-simstatecmplib
-simstatecmpname
-simstatecmpsim
-simstatecmpview
April 2011
-simaxlcmpcell
-simaxlcmphistory
-simaxlcmplib
-simaxlcmpview
-simaxlconfigcmpcell
-simaxlconfigcmplib
-simaxlconfigcmpview
170
Description
-simcmpnone
-simcmpsys
Uses system commands specified using the simsyscmp option to simulate the compared data
source.
For more information, see Setting Up and Running
Simulations Using System Commands on page 63.
-simconfig
-simdiff
April 2011
171
Description
-simrefade
-simrefadexl
-simstaterefcell
-simstaterefdir
-simstatereflib
-simstaterefname
-simstaterefsim
-simstaterefview
-simrefnone
-simaxlrefcell
-simaxlrefhistory
-simaxlreflib
-simaxlrefview
April 2011
172
Description
-simrefskill
-simrefsys
Uses system commands specified using the simsysref option to simulate the reference data
source.
For more information, see Setting Up and Running
Simulations Using System Commands on page 63.
-simsame
-simvision
-splitbuses
April 2011
173
Description
-statistics
April 2011
174
Description
-virtuoso
-wavfromrdb
-wavtest
amsDmv -repfile '-simcmpsys -simrefsys -run -simsame -simsyscmp 'rsh icspvlnx78 'cd
AMSDMVDIR; mod_irun_cmd'' \
-simsysref 'rsh icspvlnx78 'cd AMSDMVDIR; ref_irun_cmd'' -wavcmp './
waves_mod.shm' -wavref './waves_ref.shm'
April 2011
175
April 2011
176