Hspice Integ
Hspice Integ
Hspice Integ
Cadence Virtuoso
Analog Design Environment
User Guide
Version E-2010.12, December 2010
Disclaimer
SYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH
REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Registered Trademarks ()
Synopsys, AMPS, Astro, Behavior Extracting Synthesis Technology, Cadabra, CATS, Certify, CHIPit, CoMET, Design
Compiler, DesignWare, Formality, Galaxy Custom Designer, HAPS, HapsTrak, HDL Analyst, HSIM, HSPICE, Identify,
Leda, MAST, METeor, ModelTools, NanoSim, OpenVera, PathMill, Physical Compiler, PrimeTime, SCOPE, Simply Better
Results, SiVL, SNUG, SolvNet, Syndicated, Synplicity, the Synplicity logo, Synplify, Synplify Pro, Synthesis Constraints
Optimization Environment, TetraMAX, UMRBus, VCS, Vera, and YIELDirector are registered trademarks of Synopsys,
Inc.
Trademarks ()
AFGen, Apollo, Astro-Rail, Astro-Xtalk, Aurora, AvanWaves, BEST, Columbia, Columbia-CE, Confirma, Cosmos,
CosmosLE, CosmosScope, CRITIC, CustomExplorer, CustomSim, DC Expert, DC Professional, DC Ultra, Design
Analyzer, Design Vision, DesignerHDL, DesignPower, DFTMAX, Direct Silicon Access, Discovery, Eclypse, Encore,
EPIC, Galaxy, HANEX, HDL Compiler, Hercules, Hierarchical Optimization Technology, High-performance ASIC
Prototyping System, HSIMplus, i-Virtual Stepper, IICE, in-Sync, iN-Tandem, Jupiter, Jupiter-DP, JupiterXT,
JupiterXT-ASIC, Liberty, Libra-Passport, Library Compiler, Magellan, Mars, Mars-Rail, Mars-Xtalk, Milkyway,
ModelSource, Module Compiler, MultiPoint, Physical Analyst, Planet, Planet-PL, Polaris, Power Compiler, Raphael,
Saturn, Scirocco, Scirocco-i, Star-RCXT, Star-SimXT, StarRC, System Compiler, System Designer, Taurus, TotalRecall,
TSUPREM-4, VCS Express, VCSi, VHDL Compiler, VirSim, and VMC are trademarks of Synopsys, Inc.
ii
Contents
1.
2.
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
12
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
Quick-Start Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
19
23
26
32
36
38
40
44
46
54
61
68
75
75
75
78
80
80
92
Contents
3.
4.
5.
Environment Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
Environment Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
94
Verilog-A Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
106
107
109
109
Multi-Dimensional Sweeps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110
Transient Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111
113
DC Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
117
AC Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
121
Noise Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
122
124
127
128
DCMatch Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
129
ACMatch Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
131
132
133
134
Pole/Zero Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
146
147
148
Design Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
Saving-Plotting Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
152
Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
To Be Saved. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
Contents
6.
7.
8.
To Be Plotted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
Save Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
156
159
159
160
161
161
162
Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
163
Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
163
Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
164
Netlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
167
Output Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
168
Convergence Aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
169
173
173
174
184
185
188
189
194
196
199
200
200
202
Using the Options Tab of the HSPICE Monte Carlo Analysis Form. . . . . . . . .
203
207
Simulation Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
207
Contents
Outputs Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
208
209
210
Corners Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213
214
214
217
217
224
225
227
Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
227
Plotting Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
230
231
233
235
235
236
239
Available Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
240
243
245
246
246
247
248
249
249
249
250
9.
Contents
251
Setting Up Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
252
253
254
255
257
257
258
Trig/Targ Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
261
262
Find/When Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
263
Equation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
264
264
265
268
269
271
MOSRA Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
271
272
Main Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
275
275
277
278
284
288
288
Simulation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
289
289
294
298
301
Contents
303
303
GUI Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
305
310
313
314
314
315
321
321
323
328
331
331
334
Version 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
335
Version 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
349
365
Using the HSPICE-Provided OCEAN API for HSPICE Monte Carlo Runs . . .
365
373
373
1. snpsAnalysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
373
2 snpsProbe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
386
391
391
A.
B.
C.
D.
Contents
E.
407
407
413
413
425
425
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
435
F.
G.
Contents
Audience
This user guide is written for the designers who use HSPICE for analog and/or
mixed signal design. With this Synopsys HSPICE integration interface, users
get a full-featured simulation environment that facilitates the efficient use of
HSPICE in creating and verifying the performance of analog and mixed signal
designs. The HSPICE integration provides an upgraded interface to the many
long-standing features of HSPICE that are not supported in even the latest
versions of the Virtuoso Analog Design Environment.
Description
Chapter 1, Quick-Start
Tutorial
Chapter 2, Updating
Libraries and Tool Filter
Chapter 3, Environment
Setup
Chapter 5, Saving-Plotting
Outputs
Chapter 6, Running
Simulations and Using
Control Options
Chapter 9, Corners
Analysis
10
Chapter
Description
Appendix A, Adding a
CustomExplorerTM Menu
to the HSPICE Integration
11
Chapter
Description
12
Manual
Description
HSPICE Reference
Manual: Commands and
Control Options
HSPICE Reference
Manual: Elements and
Device Models
HSPICE Reference
Manual: MOSFET
Models
Manual
Description
AMS Discovery
Simulation Interface
Guide for HSPICE
You can also invoke HSPICE and HSPICE RF command help by entering
-help on your terminal command line when the HSPICE tool is open. This
opens a browser-based help system for fast navigation to commands and
options used in HSPICE and the HSPICE RF flow.
13
Related Publications
Related Publications
For additional information about HSPICE see:
The Release Notes for the HSPICE integration are available in the HSPICE
release notes published with each release and service pack, and is available
on SolvNet (see Accessing SolvNet on page 15).
Conventions
The following conventions are used in Synopsys documentation.
Convention
Description
Courier
Italic
Bold
[]
...
14
Customer Support
Convention
Description
Control-c
Customer Support
Customer support is available through SolvNet online customer support and
through contacting the Synopsys Technical Support Center.
Accessing SolvNet
SolvNet includes an electronic knowledge base of technical articles and
answers to frequently asked questions about Synopsys tools. SolvNet also
gives you access to a wide range of Synopsys online services, which include
downloading software, viewing Documentation on the Web, and entering a call
to the Support Center.
To access SolvNet:
1. Go to the SolvNet Web page at http://solvnet.synopsys.com.
2. If prompted, enter your user name and password. (If you do not have a
Synopsys user name and password, follow the instructions to register with
SolvNet.)
If you need help using SolvNet, click Help on the SolvNet menu bar.
The link to any recorded training is
https://solvnet.synopsys.com/trainingcenter/view.faces
Access recent release update training by going to
https://solvnet.synopsys.com/search/advanced_search.faces
15
Customer Support
Open a call to your local support center from the Web by going to
http://solvnet.synopsys.com/EnterACall (Synopsys user name and
password required).
16
1
Quick-Start Tutorial
This chapter provides a quick-start tutorial to get you up and running with the
Synopsys HSPICE integration to the Cadence Virtuoso Analog Design
Environment.
Note:
All required files for this quick-start tutorial are available at:
/demo/hspice/aa_integ/
Depending on which software version you have, select either PLL_Demo_51/
or PLL_Demo_61/. This chapters screen shots are based on the version 6.1.
Licensing
The only licenses required for running the HSPICE Integration to Virtuoso are:
From Cadence, one license each for: ADE-L and OASIS (the OASIS license
is ONLY needed when doing a netlist in HSPICE-ADE before invoking
HSPICE to execute an operation in IC6xx or IC5xx.
This tutorial assumes that you have already installed the software according to
the installation directions README file, which is available in:
/global/apps3/hspice_release_version_date/interfaces
The purpose of this chapter is to get you started quickly in setting up a design
for simulation using the full-range HSPICE simulator in an analog/mixed signal
simulation environment. This integration minimizes the simulator language
expertise required since the interface includes GUI selections that are the
equivalent of the command-line statements and control options.
The HSPICE integration also recognizes that many designers specify their
stimulus by placing library components directly in their designs using the
17
Finally, for information on use of the HSPICE Measurement Utility see Chapter
12, HSPICE Measurement Utility.
This quick-start tutorial contains the following tasks:
18
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
3. Select Tools > Library Manager to display the Library Manager dialog.
4. In this window, open PLL/test_vco/config by selecting PLL from the Library
column, test_vco from the Cell column, and then double-click on config in
the View column. A dialog opens asking if you wish to open both the
schematic and configuration. Accept the default, just the schematic2 view,
which displays the Schematic Editor window.
19
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
20
Click to highlight
Shift-e to open
Descend form
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Use the
controls and the keyboard arrows to move and
view the areas of interest.
21
Figure 1
6. Open the Environment: In the Schematic window select Launch > ADE L.
The Environment Console (with banner text PLL test_vco config) opens.
22
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permissio
23
2. Double-click in the top row of the table and then click the browse button to
open the Choose model file browser and locate the file cmos90nm.l, which
is in the current directory. Click Open.
3. Click in the Section column cell to display the dropdown list and select the
section TT. Then OK the dialog.
4. View the Simulation Files Setup dialog: Setup > Simulation Files.
24
Cancel both the Unix Browser and the Simulation Files Setup dialogs.
5. View the Environment Options dialog: Select Setup > Environment to open
the Environment Options dialog.
25
It provides the Command Line Opt field. Use this field to append HSPICE
executable command line options to the command issued by the
Environment. This is only necessary for command line options that are not
supported by the GUI. In addition you can enable the Print Comments
check box and Popup Output Log check box (selected on by default). See
Environment Options in the Setup section of Chapter 3 for more
information on this form. Leave the Popup Output Log checked and
Cancel this dialog.
26
2. Transient Analysis: Click the tran radio button. The dialog provides the
ability to specify multiple Intervals. Test this by selecting a different value
from the Number of Intervals list. Enter a few step/stop values, and click the
Enabled check box.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
3. DC Analysis: The HSPICE integration specifies Linear Steps for the Sweep
Type dropdown list. Click the Select Source button to automatically fill in the
Source name by clicking on the component in the schematic.
27
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
4. AC Analysis: The AC HSPICE user interface has the additional feature of the
single point frequency sweep. The figure shows all GUI elements when the
Design Variable radio button is selected.
28
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
If you select Design Variable as the sweep variable, click the Select
Design Variable button and select a variable from the list dialog that
opens.
Specify the sweep type and enable the analysis by clicking the Enabled
check box.
29
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Select OUT as the output net by clicking the Select Node button and
then left-click on the schematic to select the wire connecting the vco fout
terminal with the pin OUT.
30
Select /OUT as the positive input node by clicking the Select Node
button and then left-click on the schematic to select the wire connecting
the vco fout terminal with the pin OUT.
Do not enter anything for the negative input node, as it defaults to gnd!.
Start and stop can be the same as what was specified for the tran
analysis, and number of points can be 1024.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
31
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
32
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
The radio button options: all, level, and selected control the value of
the .OPTION PROBE command in HSPICE.
If you choose level for the first option you can specify the Post Level and
Post Top options (.OPTION POSTLVL to limit data written to your
waveform file to a specified level of nodes, and .OPTION POSTTOP to
limit the data written to the waveform file to data from only the top n level
nodes.
33
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
4. Select Results > Plotting Assistant to open the HSPICE Plotting Assistant
dialog and explore the dropdown lists:
34
On the schematic window, click on the wire attached to pin OUT, and
then the wire attached to pin OUTN to display these two nets the
Currently selected items listbox of the HSPICE Plotting Assistant. See
also that the Expression (v("/OUT" ?result "tran") - v("/
OUTN" ?result "tran")) is added to the Expression field
HSPICE Integration to Cadence Virtuoso Analog Design Environment User Guide
E-2010.12
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
The built-in Environment waveform viewer ViVA Graph Window plots the
waveform at the same time.
Click the Add to Outputs button (not the check box) and notice that the
signals as well as the expression are added to the Outputs table in the
main ADE Console window.
35
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
36
to do this with every new session, the Environment provides the ability to save
and restore state files.
Note: When you load a previously saved state, all current window
settings are overwritten and the active design and data reflect
the loaded state.
1. On the ADE Console window, select Session > Load State. Notice that
States can be stored to directories or to cellviews so that they can be
managed with design data. You are going to load a State from a directory.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
2. Change the State Load Directory to ./artist_state. Tab out of this field.
Also ensure that the Library, Cell and Simulator are set to PLL, test_vco and
HSPICE.
3. Select demostate from the list of states.
37
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
38
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
2. Check your netlist: When netlisting succeeds, the netlist appears in a text
viewer. Examine the contents.
3. Pay special attention to the instance statement for m3 within the vco
subcircuit:
m3 net5 nbias vss! vss! str(nmodel) w=10e-6 l=250e-9
39
7. Return to the top design with the Ctrl-e binding, and select the vco block.
8. Use the q binding to bring up the Object Properties dialog. Notice that the
value of nmodel is set to nch.
9. Now return to the netlist, and locate the instance statement for the vco:
xi5 out outn net034 vco nmodel=str('nch')
10. You can use the Property Editor (q bindkey) to change the nmodel value at
the vco block level to control the model that is used by M3 in the vco design.
40
In the window that opens, enable Auto Add to Outputs and plot a
single voltage (select a voltage node on the schematic). For example:
New Output
Added
41
Then change Method back to Net. Click the down arrow of the
dropdown list labeled Currently selected item to show the history of
items plotted. Select any of the items listed and instantaneously view
the plot.
3. In the Plotting Assistant, change the Data Mode to Current ADE and
Reference Results. In the Results Directory field type
./Results_at_1v.
42
4. Now plot the differential voltage again and see the difference in the
frequency of oscillation.
43
44
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
2. In the Library Manager window, select PLL from the Library column,
test_vco from the Cell column, and then double-click on config in the
View column.
3. In the Open Configuration or Top CellView window, click yes for both the
Configuration and Top Cell View radio buttons and then click OK to open
both the schematic and Hierarchy Editor.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
4. In the Hierarchy Editor, right-click the View Found column cell of the vco
cell to display the menu, and select Set Cell View, then select veriloga in
the expanded menu.
45
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
5. Continue on to launch ADE L (In the Schematic Editor, Launch > ADE L to
set up HSPICE for simulation).
6. Save the Configuration.
46
Select Tools > Library Manager to display the Library Manager dialog.
2. Open the Environment: In the Schematic window select Launch > ADE L.
The Environment Console (with banner text Monte montetest schematic)
opens.
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
47
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
4. In the HSPICE Monte Carlo Analysis form, select File > Load Setup to open
the Loading State window and select montedemostate1. After the state is
loaded, the state information is displayed in the HSPICE Monte Carlo
Analysis form. It contains monte information in the Setup tab for DC, AC
and Tran analyses, the AGAUSS parameter deltaL, and includes a
measurement file in the Outputs tab.
48
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
49
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
5. Click the Outputs tab; then click Get Outputs From Console. The current
setup of outputs (/M1/D and /out) is displayed. These outputs will be
automatically plotted after the Monte Carlo simulation is completed.
50
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
6. In the Outputs tab, click the Run Sim button to run the Monte Carlo
simulation. The tool starts netlisting and invokes the HSPICE simulator to
run this Monte Carlo simulation. The netlist file and HSPICE simulation log
are displayed during the run. After the simulation succeeds, the output
/M1/D and /out waveforms are automatically plotted to a ViVA waveform
window.
51
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
7. On the Outputs tab, use the Get Variation Statistics button to load the
simulation measurement results. To plot the measurement results, combine
the use of the
Curve type
Bins and
Plotting As button
The variation statistics shown on the following Outputs tab are plotted in the
succeeding waveform.
52
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
In the following graphic, the scatter waveform of trise VS. m1@delta with
tran simulation results is plotted.
53
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
8. In the HSPICE Monte Carlo Analysis form, select File > Save Ocean Script
to save this entire simulation session to an OCEAN script (.ocn) in order to
rerun it in a batch Ocean mode. See Appendix B, OCEAN API Functions for
HSPICE Monte Carlo Analysis.
54
Select Tools > Library Manager to display the Library Manager dialog.
2. Launch the Environment: In the Schematic window select Launch > ADE L
to open the Environment Console (with banner text Cornertest Top
schematic).
3. To properly initialize the Environment session, in the Environment Console,
select Setup > Simulator/Directory/Host, and use the dropdown list to
specify HSPICE as the Simulator. Leave the other fields as defaults and OK
the form.
4. In the Environment Console, select Tools > HSPICE Corner Analysis to
display the HSPICE Corner Analysis form.
55
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
5. In the HSPICE Corner Analysis form, select File > Load Setup to open the
Loading State window. Select corner_state and click OK to load Corners
and Measurements data into the fields of the Setup tab.
56
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
6. Edit or add measure statements by clicking the Add Measures button under
the Measurements section (lower section in the setup window). The
following measure statements become readily available in the
Measurements section during the state load:
*----- measure statements for rise, fall, and propagation
delays
.meas risetime trig par('v(3) -0.1*vdd') val=0 rise=1
+
targ par('v(3) -0.9*vdd') val=0 rise=1
.meas falltime trig par('v(30)-0.9*vdd') val=0 fall=1
+
targ par('v(30)-0.1*vdd') val=0 fall=1
.meas tplh
trig par('v(2) -0.5*vdd') val=0 fall=1
+
targ par('v(3) -0.5*vdd') val=0 rise=1
.meas tphl
trig par('v(20)-0.5*vdd') val=0 rise=1
+
targ par('v(30)-0.5*vdd') val=0 fall=1
.measure delayr trig at=0 targ v(voutr) val=2.5 rise=1
goal=100ns weight=10
57
Click Add Measures to open the Corners Measurements form where you
can add/edit measure goals for existing measures.
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
7. Click the Open button to launch the HSPICE Measure Utility (also available
from the Environment Console under the Tools menu) to input or modify the
measures.
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
58
8. On the HSPICE Corner Analysis form, click the Outputs tab, then click the
Get Outputs From Console button. The current setup of outputs (/30, /
net6, /3 and /net016) is displayed. These outputs are automatically plotted
after the Corner simulation is completed.
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
9. On the Simulation pane of the Outputs tab, click the Run Sim button to run
the Corner simulation. The tool starts netlisting and invokes the HSPICE
simulator to run the simulation. The netlist file and HSPICE simulation log
are displayed during the run. After the simulation succeeds, the output /30,
/net6, /3 and /net016 waveforms are automatically plotted to a ViVA
waveform window.
59
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
10. In the Outputs tab, select multiple outputs and multiple corners by pressing
the Ctrl key to plot them as required. Select the plot mode using the Plot
Mode button.
11. Using the Measurements section of the Outputs tab, choose
measurements from the Measurements Summary section to plot
measurement variables and print measure values in separate windows (see
below).
60
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
61
Follow these steps to invoke and run the demonstration case for RF.
1. Locate Mixer_Demo_61 and open the case design:
Select Tools > Library Manager to display the Library Manager dialog.
2. Open the Environment: In the Schematic window select Launch > ADE L.
The Environment Console (with banner text Mixer ne600_mixer_test
schematic) opens.
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
62
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
4. In the HSPICE RF Analysis form, select File > Load Setup to open the
Loading State window and select rfdemohbac. After the state is loaded, the
states information will be displayed in the HSPICE RF Analysis form as
displayed in the following graphic. It contains hb, hbac and hbnoise
analyses in the Analysis tab for use in HSPICE RF simulation to come.
63
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
The Outputs tab also is populated with output data on the Outputs tab.
64
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
5. In the Outputs tab, click the Run Sim button to run the HSPICE RF
simulation. The tool starts netlisting and invokes the HSPICE simulator to
run this HSPICE RF simulation. The netlist file and HSPICE simulation log
are displayed during the run. After the simulation succeeds, the output
waveforms are automatically plotted to a ViVA waveform window as shown
in the following image.
65
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
6. On the Outputs tab, select an output in the Output Reports field; then click
the Plot as button to plot a single signal or expression. For example, the
following graphic shows the /ifout waveform:
66
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
7. In the HSPICE RF Analysis form, select File > Save Ocean Script to save
this entire simulation session to an OCEAN script (.ocn) in order to rerun it
in a batch Ocean mode. See Appendix B, OCEAN API Functions for
HSPICE Monte Carlo Analysis.
Note: This RF demo also includes another state, rfdemosnac,
which demonstrates an example for Shooting Newton,
including .SN analysis, .SNAC analysis, and .SNNOISE
analysis. In addition, the PLL_Demo_61 and PLL_Demo_51
cases also include an HSPICE RF state demonstrating
examples of .HBOSC, .SNOSC and PHASENOISE HSPICE
RF analyses. You can follow the preceding tutorial procedure
to become familiar with use of the HSPICE RF feature in the
HSPICE-ADE integration for these analyses.
67
Select Tools > Library Manager to display the Library Manager dialog.
2. Launch the Environment: In the Schematic window select Launch > ADE L
to open the Environment Console (with banner text Optimize Opti_opamp
schematic).
3. To properly initialize the Environment session, in the Environment Console,
select Setup > Simulator/Directory/Host, and use the dropdown list to
specify HSPICE as the Simulator. Leave the other fields as defaults and OK
the form.
4. In the Environment Console, select Tools > HSPICE Corner Analysis to
display the HSPICE Optimization Analysis form.
68
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
5. In the HSPICE Optimization Analysis form, select Session > Load Setup
to open the Loading State window. Select Full_Demo_state and click OK
to import all setup data (optimization model and optimization variables and
measurements into the Setup tab of the HSPICE Optimization Analysis
form.
The Optimization model section corresponds to following line in the final
netlist:
.model opt opt itropt=40 close=10 relin=1e-5 relout=1e-5
69
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
70
The HSPICE Measure Utility provides a convenient tool to edit or add more
measurements. See Chapter 12, HSPICE Measurement Utility for a detailed
description of this feature.
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
7. In the HSPICE Optimization Analysis form, click the Analysis tab and then
click on Get Outputs From Console. The current setup of outputs (/Voutr,
/Voutf, and /Vin+) is displayed. These outputs are automatically plotted after
the Optimization simulation is completed.
71
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
8. As shown in the Analysis tab, above, you can select multiple measure
parameters in the optimization statement by using the More Results button.
Press the Ctrl key and select the desired measure parameters from a list
such as the following accessed from the tutorial load state you are using:
.tran 2.5n 300n sweep optimize=opt1
+ results=delayr,delayf,tot_power,area_min
model=opt
In the printed measure report shown following Step 10 you can see resulting
values for the selected measure parameters (above) in the section called
Other measures.
9. In the Analysis tab, clickNetlist & Run to run the Optimization simulation.
The tool starts netlisting and invokes the HSPICE simulator to run the
simulation. The netlist file and HSPICE simulation log are displayed during
the run. After the simulation succeeds, the output /Voutr, /Voutf, and /Vin+
waveforms are automatically plotted to a ViVA waveform window.
72
2009, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
10. On the Analysis tab below the Output section, click the Optimization
Result button to see optimization parameter values and measure values as
shown below.
73
74
2
Updating Libraries and Tool Filter
This chapter discusses the HSPICE library conversion script, as well as the
changes to the library and any migration issues (such as incompatibilities with
existing states) It also addresses the need to add HSPICE to the Tool Filter.
75
steps to update it from which you are instantiating simulation primitives in your
designs.
Note:
Follow these steps to update your libraries from which you are instantiating
simulation primitives in your designs.
1. Start icms and in the CIW, select Tools > HSPICE Library Update Utility.
Note: If you don't have this item in the Tools pulldown, your .cdsinit
file may not be properly updated.
2. Select the name of the library that you wish to update in the Library
dropdown list.
76
3. You can instruct the Library Update Utility directly to update existing
'analogLib' or Update to a new path before updating. To do this, enable
Update to a New Path and specify a new path. Your library will be copied
to the new path and updates will be applied to the new 'anaogLib'.
Note: A. If directly updating the 'analogLib' in the Cadence Virtuoso
installation tree, make sure you have 'write' permission.
(Normally, this is done by a CAE for a onetime conversion.
Other end users need not update it.)
B. If you update the 'analogLib' through Update to a New
Path, the 'analogLib' in cds.lib or lib.defs is automatically
updated with the new path you specified.
For example, before updating your 'analogLib' in your cds.lib
would read as:
DEFINE analogLib
/remote/apps/ic61/linux/tools/dfII/cds/
artist/analogLib
After updating, it would be
DEFINE analogLib
/remote/home/zyx/newpath/analogLib
4. If you want to include HSPICE-specific cells such as PAT/LFSR sources and
so on, please select Include HSPICE specific cells.
5. Click OK or Apply to run the Update Utility.
6. Check the CDS.log file for unrecognized cells. If any were encountered, you
will see a message such as:
Cell: nsoi unable to create HSPICE simInfo because there
is no reference simInfo.
7. Select Tools > Library Path Editor to verify the 'analogLib' new path if you
selected Update to a New Path.
8. Once the Library Update Utility has completed, you can continue to use
icms or you may exit.
Troubleshooting
If you don't see HSPICE listed in the Simulator choices pulldown, your .cdsinit
file may not be properly updated.
77
78
During processing, the status of each cell conversion is given for each cell in
the library as it is processed.
This status can be:
Doesn't require conversion (schematic only symbol that doesn't netlist, such
as gnd symbols).
Unsupported cell
79
Cell
Name
Compnt
HSPICE
Description/Notes
integration
bcs
hspiceDCompPrim
bcs
Augment
bjt504tnpn
Augment
bjt504tpnp
Augment
bsim4
Augment
80
Table 1
Cell
Name
Compnt
bvs
hspiceDCompPrim
bvs
cap
hspiceDCompPrim
cap
Augment
cccap
New
cccap
HSPICE
Description/Notes
integration
cccs
hspiceDCompPrim
cccs
Augment
ccvs
hspiceDCompPrim
ccvs
Augment
core
hspiceDCompPrim
core
Augment
delay
diode
hspiceDCompPrim
diode
Augment
New
hspice_sparam
iam
hspiceDCompPrim
iam
Augment
idc
hspiceDCompPrim_idc
isrc
Augment
ideal_balun
iexp
hspiceDCompPrim_iexp
ibis_buffer
ind
hspiceDCompPrim
transformer New
isrc
Augment
ibis_buffer
New
ind
Augment
81
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
iopamp
hspiceDCompPrim
iopamp
Augment
E-element: OpAmp
ipat
ipat
New
iprbs
iprbs
New
iprobe
hspiceDCompPrim_vdc
vsrc
Augment
ipulse
hspiceDCompPrim_ipulse
isrc
Augment
ipwl
hspiceDCompPrim_ipwl
isrc
Augment
ipwlf
hspiceDCompPrim_pwlf
isrc
Augment
isffm
hspiceDCompPrim_isffm
isrc
Augment
isin
hspiceDCompPrim_isin
isrc
Augment
Augment
ivmrf
New
isource
ivmrf
ixfmr
hspiceDCompPrim
ixfmr
Augment
mind
hspiceDCompPrim
mind
Augment
mos_a2d
Augment
Verilog-A support
mos_d2a
Augment
Verilog-A support
82
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
mtline
Augment
W-element: Distributed
Transmission Line; Added simInfo
and missing CDF parameters
n1port
Augment
n2port
Augment
n3port
Augment
n4port
Augment
nbsim
hspiceDCompPrim
nmos
Augment
nbsim4
hspiceDCompPrim
nmos
Augment
ncs
New
ncs
njfet
hspiceDCompPrim
njfet
Augment
nmes
hspiceDCompPrim
mesfet
Argument
nmes4
hspiceDCompPrim
mesfet
Augment
nmos
hspiceDCompPrim
nmos
Augment
83
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
nmos4
hspiceDCompPrim
nmos
Augment
npn
hspiceDCompPrim
npn
Augment
Augment
nport
nsoip
nsoip
New
ntft
ntft
Augment
nvs
nvs
New
pbsim
hspiceDCompPrim
nmos
Augment
pbsim4
hspiceDCompPrim
nmos
Augment
pcapacitor
hspiceDCompPrim
cap
Augment
pcccs
Augment
pcccs2
New
pcccs3
New
pccvs
Augment
84
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
pccvs2
New
pccvs3
New
pdc
Augment
Augment
Augment
pdiode
hspiceDCompPrim
diode
pexp
pinductor
hspiceDCompPrim
ind
Augment
pjfet
hspiceDCompPrim
njfet
Augment
pmes
New
pmes4
New
pmind
hspiceDCompPrim
mind
Augment
pmos
hspiceDCompPrim
pmos
Augment
pmos4
hspiceDCompPrim
pmos
Augment
pnp
hspiceDCompPrim
npn
Augment
85
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
port
Augment
ppulse
Augment
ppwl
Augment
ppwlf
Augment
Augment
Augment
New
presistor
hspiceDCompPrim
res
psin
psoip
psoip
Level 57 BSIM3SOI
ptft
ptft
Augment
pvccs
hspiceDCompPrim
vccs_poly
Augment
pvccs2
hspiceDCompPrim
vccs_poly
Augment
86
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
pvccs3
hspiceDCompPrim
vccs_poly
Augment
G-element: Three-input
Polynomial Voltage Controlled
Current Source
pvcvs
hspiceDCompPrim
vccs_poly
Augment
pvcvs2
hspiceDCompPrim
vccs_poly
Augment
pvcvs3
hspiceDCompPrim
vccs_poly
Augment
E-element: Three-input
Polynomial Voltage Controlled
Voltage Source
res
hspiceDCompPrim
res
Augment
schottky
hspiceDCompPrim
diode
Augment
sp1tswitch
sp1tswitch
Augment
sp2tswitch
sp2tswitch
Augment
sp3tswitch
sp3tswitch
Augment
sp4tswitch
sp4tswitch
Augment
svccs
pole/laplace Augment
svcvs
pole/laplace Augment
switch
switch/relay Augment
tline
hspiceDCompPrim
tline
Augment
u1wire
hspiceDCompPrim
u1wire
Augment
87
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
u2wire
hspiceDCompPrim
uwire
Augment
u3wire
hspiceDCompPrim
uwire
Augment
u4wire
hspiceDCompPrim
uwire
Augment
u5wire
hspiceDCompPrim
uwire
Augment
usernpn
hspiceDCompPrim
bjt
Augment
userpnp
hspiceDCompPrim
bjt
Augment
vam
hspiceDCompPrim
vam
Augment
Augment
vbic
vccap
hspiceDCompPrim
vccap
Augment
vccs
hspiceDCompPrim
vccs
Augment
vccsp
New
New
Augment
vccsp
vclock
vcres
88
hspiceDCompPrim
vcres
Table 1
Cell
Name
Compnt
HSPICE
Description/Notes
integration
vcvs
hspiceDCompPrim
vcvs
Augment
vcvsp
New
vcvsp
vdc
hspiceDCompPrim_vdc
vsrc
Augment
vexp
hspiceDCompPrim_vexp
vsrc
Augment
vpat
New
vnpn
Augment
vpnp
Augment
vprbs
New
vpat
vprbs
vpulse
hspiceDCompPrim_vpulse
vsrc
Augment
vpwl
hspiceDCompPrim_vpwl
vsrc
Agument
vpwlf
hspiceDCompPrim_pwlf
vsrc
Augment
vsffm
hspiceDCompPrim_vsffm
vsrc
Augment
vsin
hspiceDCompPrim_vsin
vsrc
Augment
89
Table 1
Cell
Name
Compnt
vsource
vvmrf
HSPICE
Description/Notes
integration
Augment
vvmrf
New
winding
hspiceDCompPrim
winding
Augment
xfmr
hspiceDCompPrim
xfmr
Augment
K-element: Transformer
zener
hspiceDCompPrim
Augment
zvccs
ztrans
Augment
zvcvs
ztrans
Augment
hspice_vec_inc
Augment
hspice_veriloga_inc
Augment
91
+ [PERJITTER=val SEED=val]]
The parameter SEED enables you to generate different random number
sequences. For details, see Clock Source with Random Jitter in the HSPICE
RF Analysis User Guide, and Periodic Jitter Effect in Chapter 18, Statistical Eye
Analysis in the HSPICE User Guide: Simulation and Analysis.
3. Make HSPICE your default simulator as follows: edit the .cdsenv file and
add HSPICE to the list of default simulators. For example:
auCore.toolFilter defaultTools string "spectre spectreS auCdl
auLvs HSPICE" nil
92
3
3
Environment Setup
Environment Console
Session
Setup
Verilog-A Support
Environment Console
You can display the Environment Console from either the CIW window or from
the Schematic Editor.
1. From the CIW:
For version 5.1xx... select Tools > Analog Environment > Simulation.
93
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 2
If you open the Environment Console from the Schematic Editor, the resulting
onscreen cell view in the Schematic Editor is the design simulation candidate.
94
The data you enter in many of the fields of the various menu
dialogs can be saved and reloaded as State data under the
HSPICE integration. You can also save these values to
the .cdsenv file with the Options > Save Defaults selection in the
CIW > Options > Save Defaults... menu dialog, and to initialize
them at startup with that same file. In addition, the values in these
fields can be set using the .cdsinit SKILL file.
Session
This HSPICE integration maintains the user interface with which users of the
Environment are familiar.
Schematic Window: This selection brings the design layout of the current
state to the top of your display.
Save State and Load State: Launches either the Save State or Load State
form. You can save and restore all or part of the simulation environment
setup using these menu options. States can be stored to directories or to
cellviews so that they can be managed with design data.
Note: Users of Virtuoso hspiceD can expect to have their State data
read by the new HSPICE integration.
Saved states are simulator-dependent for analyses, simulator options, and
convergence setup (if the convergence commands you saved are not
supported by the other simulator).
You can restore saved states from different simulators. The analog circuit
design environment restores as much as possible despite simulatordependent settings. Saving the waveform setup using the Saving State form
saves the same information as the File > Save as command in the waveform
window. If AWD (Analog Waveform Display) is your waveform viewer,
Window > Save is the command.
As seen in the bottom portion of the Save State form (Figure 3 on page 96)
you can select which data you want to keep for the saved state. Before
closing a session you are prompted as to whether or not you wish to save
the current state.
95
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 3
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
96
load (prependInstallPath("local/HSPICE/HSPICE.ini"))
in the directory from where you run ocean. When the command
ocean is executed, it automatically loads the content of .oceanrc. It is
similar to .cdsinit when you launch icms/icfb.
envSetVal("asimenv.misc" "preSaveOceanScript"
'string "myPreSaveProc")
procedure(myPreSaveProc(session fp)
prog(()
fprintf( fp "load( prependInstallPath( \"local/HSPICE/
HSPICE.ini\" ))\n" )
drain(fp)
)
)
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
97
Setup
The Setup menu maintains the same menu items as the other simulators
supported by the Environment. It also includes the HSPICE distributed
processing solution for Monte Carlo and corner analyses. See Chapter 15 on
page 321.
Figure 4
98
Setup menu
Design: Opens the Choosing Design dialog for changing the design
simulation candidate of the ADE session.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 5
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Model Libraries: Opens the Model Library Setup dialog to enable you to
add a model file by browsing, manually typing, or copying and pasting a
model file name and path. When you specify a model file, you can then
select the library section from the Section column pulldown, which is
populated by section names. Model library files will be printed as userspecified and HSPICE will resolve the paths using the .option search
commands.
99
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
100
Stimulus: Opens the Setup Analog Stimuli dialog for you to set inputs and
global sources for your design. These pins and global nets must exist in your
design and are activated as independent sources to drive your circuits
through the stimuli setup. The form changes dynamically when you select a
different input pin, function, or type.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Text box identifies the signal names with the currently selected
highlighted.
Function enables choice of the function for the selected signal with
stimulus option properties and values. The possible functions include:
Function
Stimulus Option
dc
direct current
pulse
pulse stimulus
sin
sinusoidal
exp
exponential
pwl
piecewise linear
sffm
single frequency FM
101
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Definition Files, which can specify functions and global variables that
are not design variables. These files can contain model parameters or
simulator parameters. Definition files will be printed as user-specified
and the simulator will resolve the paths using the .option search
commands.
An example of setting a definitions file follows:
In the Environment Console, select Setup > Simulation Files.
In the Simulation Files Setup form, Definition Files field, enter the
full path of the definitions file (including extension). For example:
/install_dir/tools/dfII/examples/artist/hspice/
models/models.sp
102
Vector Files (unique to the HSPICE integration). You can enter multiple
space-delimited *.vec files in this field to be used on the .VEC card.
Enter the vector file paths fully qualified. Vector files will be printed as
user-specified and the simulator will resolve the paths using the .option
Environment Options: Opens the dialog for you to specify command line
options, check boxes to choose to print commands, automatically display an
output log file (on by default) onscreen while the simulation is running,
specify 64-bit simulation, and controls to set up a multithread count,
HSPICE Precision Parallel technology, specify a top level schematic as a
subcircuit, and enable case sensitivity in netlists.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 6
Environment Options
Stop View List: Field to specify list of views that identify the stopping
view to be netlisted. Both hspice and hspiceD are available by default.
Print Comments: Check box When off, comments are not printed.
When on, extra comments are placed in the netlist regarding
component location and name.
103
Command Line Opt: Specify command line options that many not be
supported by the GUI on the call to HSPICE which are appended to the
list that the Environment normally sends to the simulator. For
example: You can invoke multithreading:
% hspice -mt=2
You can specify Verilog-A files using the-hdl option in the Command
Line Option field (see Verilog-A Support below). This field allows you to
take advantage of current and future capabilities that HSPICE may offer.
By default, the HSPICE invocation is done with the following command:
% hspice input.ckt >& ../psf/hspice.out
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 7
104
You can also set the following environment option to enable this feature.
Either of the following commands needs to be set in the .cdsinit or the
icms console.
envSetVal("HSPICE.envOpts" "setTopLevelAsSubckt" 'boolean
t)
envSetVal("HSPICE.envOpts" "setTopLevelAsSubckt" 'boolean
nil)
105
However, this has to be set each time the session starts. Clicking the
check box in the Environment Options form is the recommended
method.
Node Names
Parameter Names
Instance Names
Model Names
Subcircuit Names
Data Names
Measure Names
Library Entry Names
File Names and Paths (case sensitive by default)
Alternatively, you can use the SKILL function to set an environment variable in
the initialization file to turn on/off this feature manually.
envSetVal("HSPICE.envOpts" "hspCaseSensitive 'boolean
nil)
t/
Verilog-A Support
HSPICE integrates the ability to use Verilog-A simulator capability. The
HSPICE integration provides the .hdl statement that points to the module to
include:
.hdl "/remote/home/usrA./cdn_oa/adeLib/res/veriloga/
veriloga.va"
xi7 0 net6 res r=500e3
106
In this example, one of the resistors is placed from the library adeLib, and the
other from devLib. They both have the cell name res, which means that the
default master name on the instance line, as well as the module name, will be
res. Both have the view name veriloga. But since these two modules are
found in different libraries, they may differ in functionality. To bind each module
to the correct instance, an aliasing capability associates the real module name
with a name that is formed by concatenating the library, cell, and view names
together. This handles same-named modules in different libraries, as well as
modules in the same library and cell, but different views.
Using Verilog-A files in the HSPICE integration assumes that you have brought
your Verilog-A modules into the OpenAccess (OA) or the Cadence CDBA
library structures. You can also use a method for including modules that are
outside of the library structure, by creating a stopping view which causes an
instance statement with the proper pinout and module name, and then invoking
the -hdl veriloga_file option in the Command Line Option field. This
method currently works in any integration, and continues to work in the
HSPICE integration.
107
108
4
Analysis Setup and Design Variables
This chapter describes the Analysis capabilities available through the HSPICE
integration interface and introduces the editor for design variables.
Transient Analysis
DC Analysis
AC Analysis
Noise Analysis
DCMatch Analysis
ACMatch Analysis
Pole/Zero Analysis
Design Variables
109
NOISE, FFT, LIN, DCMATCH, ACMATCH, LSTB, and PZ. (Postprocessing for
these analyses is discussed later in this user guide.)
Users can save field values to the .cdsenv file with the Options > Save Defaults
menu in the session Environment Console, and initialize them at startup with
that same file. The values in these fields can be set via the .cdsinit SKILL file.
To open the analyses GUI, in the Environment Console window select
Analyses > Choose to display the Choosing Analyses dialog window.
Note:
The following sections describe the supported HSPICE analyses and the
enhancements to the existing Environment simulation implementations.
For Monte Carlo trials and HSPICE RF analyses see Chapter 8, Monte Carlo in
the HSPICE Integration and Chapter 10, HSPICE RF Analysis.
Multi-Dimensional Sweeps
Although the HSPICE simulator itself supports multi-dimensional sweeps
directly on some analysis lines, a multi-dimensional sweep via ADE requires
the use of the parametric analysis tool.
In order to use a second sweep, you must use parametric analysis, which is
available from the Tools menu (Tools > Parametric Analysis) (Figure 8).
110
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 8
Transient Analysis
The HSPICE integration for transient analysis supports multiple timestep
increments in a single analysis. This reflects the Synopsys HSPICE ability to
specify multiple time steps (max time step) values on the .tran analysis
command line. For example:
.TRAN 1e-9 100e-9 1e-12 150e-9 1e-9 200e-9 START=0.0
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 9
111
The HSPICE integration Transient Analysis form provides the following controls
and fields:
Multiple timesteps are useful for saving time in simulating circuits where
start-up behavior is not of interest, or for tightening up the timestep in
regions of the transient response where areas of high curvature exist. Step
1, 2, 3, etc. and equivalent Stop 1, 2, 3, etc. fields are provided to specify
the number of timestep regions (intervals) that you wish to set up. Manually
enter multiple step and stop values in these fields.
The Start field allows you to enter a time in the simulation when printing or
plotting begins.
If you turn the UIC button on, you specify the UIC parameter in the .TRAN
statement, HSPICE does not calculate the initial DC operating point, but
directly enters transient analysis. When you use .TRAN UIC, the .TRAN
node values (at time zero) are determined by searching for the first value
found in this order: from .IC value, then IC parameter on an element
statement, then .NODESET value, otherwise use a voltage of zero.
Figure 10
112
In addition, the values for the most common fields are displayed in the
Analyses table on the Environment Console. This behavior occurs for all the
analysis forms.
Since an FFT analysis requires that a transient analysis must be specified and
enabled, a warning appears on the FFT Analysis form. The warning does not
appear if a transient analysis has been enabled.
Monte Carlo analysis can be run with transient analysis either through the
HSPICE Integration UI (see Chapter 8, Monte Carlo in the HSPICE Integration)
or by creating an OCEAN script for non-GUI batch runs (see Appendix B,
OCEAN API Functions for HSPICE Monte Carlo Analysis).
For full information regarding HSPICE Transient Analysis, see the .TRAN
command in the HSPICE Reference Manual: Commands and Control Options
and Transient Analysis in the HSPICE User Guide: Simulation and Analysis.
The following section discusses
See Transient Noise Analysis in the HSPICE User Guide: RF Analysis for
details on these methods.
To invoke the HSPICE Trannoise Analysis form, select Analyses > Choose on
the Environment Console to open the Choosing Analyses form. The Transient
Analysis form opens with tran as the default-selected analysis. To initiate a
transient noise analysis, click the Trannoise check box. The Transient Analysis
form expands to allow setup of transient noise analysis, as shown Figure 11 on
page 114.
113
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 11
114
The Output field entry is the source node if the Output Type is not selected
to be two-terminal instance, otherwise, it is filled with the source instance
name.
If Output Type is two nodes, the Output (2nd node) field becomes
enabled and is filled with the 2nd node of the output source.
The Select button can be used to choose the node/instance from the design
schematic editor.
2. Choose the method of trannoise simulation from the Monte Carlo single run
(Default), multiple runs or SDE (Stochastic Differential Equation) for
advanced usage. As shown in Figure 11 on page 114 the method is
defaulted to Monte.
Under the Monte Carlo method, you can enter values for Monte NUM
and Seed. The seeded first run sets the first simulation sample. Use
Monte NUM to specify the simulation samples. For example, for Monte
NUM, you can enter 20 30 40 or 20:30 40. 20:30 40 means
samples from 20 to 30 inclusive and sample 40.
Under the SDE method, you can also set values for Time (time points)
for the stochastic simulation.
3. Optionally, for both methods, you can set Scale (amplification factor for
noise), Fmin (minimum frequency for frequency dependent noise), and
Fmax (maximum frequency for frequency dependent noise).
4. Autocorrelation on enables autocorrelation function calculation at the
specified output (default is off).
5. probe Nets (optional) Lists the nets that can be probed for noise with the
VRMS function (VRMS: The output of RMS noise voltages at other nodes
(i.e., the output for general nodal noise voltage values).
6. The Select button allows you to automatically select autocorrelation outputs
and/or nets to be probed using VMRF from the design schematic editor.
Limitation
The HSPICE ADE Trannoise feature currently does not support transient noise
summary.
115
In the Environment console select Results > Plotting Assistant to display the
HSPICE Plotting Assistant utility.
Select the tran radio button for the Analysis.
Figure 12
116
Figure 13
DC Analysis
The interface for DC analysis supports the sweeps of temperature, design
variables, or unparameterized voltage sources (voltage value is swept).
117
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 14
118
DC Analysis form
Selecting the Source (default) radio button allows you to pick a source by
clicking the Select Source button and then clicking on a legitimate
component on the schematic to auto-fill the Source Name field. You can
also manually specify the source name.
Selecting the Design Variable radio button expands the DC analysis form
for you to specify a design variable from the list of currently established
design variables, as shown on the Environment Console. (See the Design
Variables section later in this chapter for more information.) Click the Select
Design Variable button to open the Select Design Variable for dc window.
Highlight the variable of choice and click OK to auto-fill the Variable Name
field on the DC Analysis form. Alternatively, you can manually enter a design
variable acceptable to HSPICE.
You can select the Sweep Type as a range of linear steps, linear points,
points per octave, points per decade, or space-separated points of interest.
Monte Carlo analysis can be run with DC analysis either through the HSPICE
Integration UI (see Chapter 8, Monte Carlo in the HSPICE Integration or by
creating an OCEAN script for non-GUI batch runs (see Appendix B, OCEAN
API Functions for HSPICE Monte Carlo Analysis.
For full information regarding HSPICE DC Analysis, see the .DC command in
the HSPICE Reference Manual: Commands and Control Options and
Initializing DC-Operating Point Analysis in the HSPICE User Guide: Simulation
and Analysis.
AC Analysis
In addition to a simple frequency sweep, the AC Analysis form allows you to run
the AC analysis at a specific frequency in conjunction with a temperature or
parameter sweep.
119
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 15
120
AC Analysis Form
The Frequency (default) radio button specifies the sweep variable in Hz.
Selecting the Design Variable radio button expands the DC analysis form
for you to specify a design variable from the list of currently established
design variables, as shown on the Environment Console. (See the Design
Variables section later in this chapter for more information.) Click the Select
Design Variable button to open the Select Design Variable for dc window.
Highlight the variable of choice and click OK to auto-fill the Variable Name
field on the DC Analysis form. Alternatively, you can manually enter a design
variable acceptable to HSPICE. You can add design variables one at a time
by this selection process and click OK or Apply on the analysis form to add
this design variable data for the simulation.
You can select the Sweep Type as a range of linear steps, linear points,
points per octave, points per decade, or space-separated points of interest.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 16
121
The Format drop-down provides options for: all, brief, current, debug, none,
and voltage. Only one format can be run per simulation.
debug: Usually invoked only if a simulation does not converge. Debug prints
the non-convergent nodes with the new voltage, old voltage, and the
tolerance (degree of non-convergence). It also prints the non-convergent
elements with their tolerance values.
Use the Times field to specify the time points for which HSPICE prints the
report. The times must be space-separated, for example: 1.2n 1.5n 2n.
For full information, see the .OP command in the HSPICE Reference Manual:
Commands and Control Options and Initializing DC-Operating Point Analysis in
the HSPICE User Guide: Simulation and Analysis.
Noise Analysis
A noise analysis calculates the output noise generated based on the
contributions from all noise sources within the circuit. Noise may be from
passive elements, such as thermal noise in resistors, or from sources such as
shot, channel, and flicker noise present within transistors.
122
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 17
The Output Node and Source Name Select... buttons make the Schematic
Editor active for selection of wires or components; after clicking the Select
Node or Select Source button and then clicking on an appropriate
component in the schematic, the name value/value is automatically written
to the fields in the analysis form. Alternatively, you can manually enter the
node and source names.
Note:
123
Hand-enter
data for times,
number of
points, and
frequencies,
if required
One of 8 window
types can be
specified
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 18
124
The Output Variable can be selected from the dropdown and can be either:
Voltage: The UI for Voltage provides fields for Positive Output Node and
Negative Output Node. Clicking the accompanying Select buttons brings
the Schematic Editor to the top of the window stack and you can make
selections directly on the schematic nodes to auto-fill the fields; or you can
manually enter the component node names.
Power: Shows the same UI as the previous selection for current (the single
Output Instance field).
The next pane in the form specifies data selection having to do with how the
analysis and plot will be constructed.
Start and Stop fields: start of the output variable waveform to analyze
(defaults to the START value in the .TRAN statement, which defaults to 0)
and end of the output variable waveform to analyze (defaults to the TSTOP
value in the .TRAN statement).
Window Type
One of eight window types can be selected:
HANNHanning window
HAMMHamming window
BLACKBlackman window
HARRISBlackman-Harris window
GAUSSGaussian window
125
KAISERKaiser-Bessel window
When either the Gaussian or Kaiser-Bessel window is chosen, the UI
adds a field called Alfa for the parameter to control highest side-lobe
level and bandwidth. The Alfa parameter has a legal range of 1.0 to 20.0
inclusive; the default is 3.0.
If there is no transient analysis run as part of the simulation, then the .FFT
computation is not run. By default, .FFT will use the time points calculated by
the transient analysis to perform a DFT, which extracts frequency content from
the circuit. As an alternative, users can run a transient analysis and use the
DFT function of the Environment calculator.
Note:
Using the calculator will always be slower because it is a postprocessing step. The .FFT calculates the Fourier Transforms onthe-fly. If you forgot to set up the .FFT and you performed a very
long transient simulation you can use the calculator or a third
party application to retrieve the FFT.
For full information regarding HSPICE Spectrum Analysis, see the .FFT
command in the HSPICE Reference Manual: Commands and Control Options
and Spectrum Analysis in the HSPICE User Guide: Simulation and Analysis.
126
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 19
The Model Name field is for specifying the model name to be listed in
the .MODEL statement in the .sc# model output file.
You can specify the Format to save the extracted parameters as a Selement (*.sc#), Citi, or Touchstone file.
A Group Delay check box allows you to extract group delay (perform group
delay analysis).
The Perform Noise Analysis pane offers yes and no options for Noise
analysis to be run as part of a .LIN analysis. The .LIN analysis can compute the
127
The .LIN analysis can be run with or without the extraction of noise
parameters.
Selecting yes expands the pane to include a Level dropdown list for:
Two-port (1):
Multi-port (2)
This message can be ignored, but be aware that noise voltages will not be
plotted under these conditions.
Similarly, trying to plot any of the following from the Results > Direct Plot menu
will produce an error message similar to the one shown above:
128
For full information regarding HSPICE Linear Networks Analysis, see the .LIN
command in the HSPICE Reference Manual: Commands and Control Options
and Linear Network Parameter Analysis in the HSPICE User Guide: Simulation
and Analysis.
DCMatch Analysis
The DCMatch Analysis form is unique to the HSPICE integration to make use
of the Variation Block functionality. In order for this analysis to be functional a
library file with a Variation Block section must be set up for the session (see
Model Libraries in the Setup section).
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 20
DCMatch Form
129
When you change the output type to Current the two voltage fields change
from Positive and Negative Output Node to an Output Instance field.
When voltage is the output variable, the Select buttons for Positive Output
Node and Negative Output Node make the Schematic Editor active for
selection of nodes; after clicking the Select button and then clicking on an
output node in the schematic, the value is automatically written to the field
in the analysis form.
When current is the output variable, the Select button for Output Instance
enables the same behavior as above.
Each set of values is transferred one at a time by clicking the Add button so
that you can create a matrix of values for Output Variables.
The Delete button removes the output variable data if it is highlighted.
If you need to change a value either manually or by selecting a component
on the schematic, use the Change button to replace a highlighted row of
output variable data as follows:
Click Select then select a valid node on the schematic and click
Change.
Alternatively, you can type the name of the node in the Positive or
Negative Output Node field and then click Change.
For full information regarding HSPICE DCMatch Analysis, see the .DCMATCH
command in the HSPICE Reference Manual: Commands and Control Options
and DCMatch Analysis in the HSPICE User Guide: Simulation and Analysis.
130
ACMatch Analysis
The ACMatch Analysis form is unique to the HSPICE integration to make use of
the Variation Block functionality. In order for this analysis to be functional a
library file with a Variation Block section must be set up for the session (see
Model Libraries in the Setup section).
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 21
ACMatch Form
131
The Modifier pulldown allows you to select a quantity type of output voltage
or current. For example, you can select from several output voltages,
difference voltages, or branch current through an independent voltage
source. In the HSPICE syntax, the voltage or current specifier is followed by
an identifier of the AC quantity of interest: magnitude, phase, real, or
imaginary.
When voltage is the output variable, the Select buttons for Positive Output
Node and Negative Output Node allow you to make the Schematic Editor
active for selection of nodes; after clicking the Select button and then
clicking on an output instance in the schematic, the value is automatically
written to the fields in the analysis form.
When current is the output variable, the Select button for Output Instance
enables the same behavior as above.
Click Select then click on a valid node on the schematic and click
Change.
Alternatively, you can type the name of the node in the Positive or
Negative Output Node field and then click Change.
For full information regarding HSPICE ACMatch Analysis, see the .ACMATCH
command in the HSPICE Reference Manual: Commands and Control Options
and ACMatch Analysis in the HSPICE User Guide: Simulation and Analysis.
132
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 22
For detailed information on HSPICE loop stability analysis see Using .LSTB for
Loop Stability Analysis in the HSPICE User Guide: Simulation and Analysis.
The Mode types include single (default), diff (differential), and common.
The vlstb/vlstbp field allows you to input a single mode vsource or invoke
either a diff or comm mode as one of the two vsources.
The vlstbn input field can be used to input either diff or comm mode as the
other of the two vsources. When in single mode, this field is disabled.
The Select buttons allow you to select the voltage source from the
schematic editor which will input the sources directly from the schematic.
133
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 23
134
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 24
135
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 25
After setup, select Analysis > Start All or Start Selected to netlist and run a
simulation.
Plotting LSTB Analysis Results Using the Plotting Assistant
Select Results > Plotting Assistant in the Environment console to launch the
utility that helps you plot the waveform of HSPICE output after a simulation
completes.
The Plotting Assistant form can be used to plot LSTB analysis output and
measurement results after running a simulation. Figure 26 on page 137 shows
the lstb radio button selected in the Analysis group.
The Function group displays six functions. The Loop Gain choice is used to
plot LSTB analysis outputs with the Modifier group. The other functions are
used to use to display loop stability measurement results (or plot a waveform if
LSTB analysis is run with Parametric analysis).
136
Figure 26
When you click the Plot button with the setup shown in Figure 26 you can plot
the waveform of Loop Gain with any of the different Modifiers. Figure 27 on
page 138 shows the waveform phase of Loop Gain.
137
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 27
When you select other LSTB functions such a Gain Margin, Phase Margin,
GM Frequency, PM Frequency, and Gain@miniFreq, the Plotting Assistant
form is prepared to generate the related measure results of LSTB analysis.
138
Figure 28
Plot Ass sit ant showing LSTB analysis Gain@miniFreq measure variable
value
You can print LSTB analysis measure results using the Environment console by
selecting Results > Print > Loop Stability Summary. Figure 29 shows the
calculated results in the Results Display Window. Note that when you use the
Environment console to run a simulation of LSTB analysis measure results, the
print window can only show one row of results.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 29
139
Figure 30
Plotting Assistant for Monte Carlo run and LSTB analysis Loop Gain
magnitude waveform
140
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 31
You also can print the HSPICE Monte Carlo simulation lstb analysis
measurement results summary; Figure 32 shows the print window:
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 32
141
analysis measure results shows a print window that displays more Monte
Index columns and the print results include many more rows.
Checking HSPICE Corner Analysis Simulation LSTB Analysis Results
After running an LSTB analysis simulation using the HSPICE Corner Analysis
tool (see Chapter 9, Corners Analysis), open the HSPICE Plotting Assistant
form and select lstb analysis. The form looks like Figure 33 with the Group
Data and Corner Group shown. Use the Replot button in this form to plot the
waveform of Loop Gain with different modifiers. Figure 33 shows the Plotting
Assistant window and waveform window of the magnitude Loop Gain of
HSPICE corner analysis/LSTB analysis simulation results.
Figure 33
142
results. The Instructions advise clicking the Replot button to plot the
measurement results waveform.
Figure 34
You also can print the HSPICE Corner analysis simulation lstb analysis
measurement results summary; Figure 35 shows the print window:
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 35
143
Figure 36
144
You can use the Plotting Assistant to generate a plot of the Parametric/LSTB
analysis measurement variable results. The Instructions advise to click the
Replot button to plot the measurement results waveform. See Figure 37.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 37
You also can print the Parametric lstb analysis measure results summary
(Figure 38).
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 38
145
Pole/Zero Analysis
On the Choosing Analyses form click the pz radio button to set up a Pole/Zero
analysis.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 39
146
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 40
147
Figure 41
Design Variables
The Variables menu item provides options to edit and copy to or from the
cellview in the Schematic Editor. To open the Editing Design Variables form, on
the Environment Console select Variables > Edit.
148
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 42
The Name field allows you to enter is a name for the variable, which is listed
in the Design Variables Name column when you click Apply or OK.
The Value (Expr) field is for entering a value or expression for the design
variable, and it too is registered in the Design Variables table under the
Value when applied or OKd.
Add creates the variable you specified in the Selected Variable fields.
Change updates the highlighted variable from the Selected Variable fields
to the Design variable table.
Clear erases the Selected Variable fields so you can enter a new variable.
Find works with selection in the table and will hierarchically highlight the
instance that uses that variable.
Copy From copies the variables in the schematic cellview into the
Environment Console.
149
The Design Variables table lists the name and value of each variable in the
design. Note that variables can be set to real values, to string values, and
even to built-in expressions supported by HSPICE. The netlister will netlist
what is there and let the simulator handle any evaluation.
Clicking the Apply & Run Simulation button initiates a simulation with the
enabled or netlisted analyses and any design variables on the form.
150
5
Saving-Plotting Outputs
This chapter describes the Outputs menu selections from the Setting Outputs
form available to the HSPICE integration.
Before you simulate a circuit, you can decide which data outputs you want to
save and plot or save only. The Outputs menu lets you save a selected set of
voltages and currents from the schematic. For example, in Figure 43 the names
of the signals or expressions to be saved and plotted are listed in the Outputs
table along with designations of Plot, Save, and Save Options, up to 999
outputs. Outputs you want to plot must be saved to disk in the HSPICE
integration.
Note:
Saving all the node voltages and terminal currents for a large
design produces a very large data set.
Figure 43
151
The Outputs menu on the Environment Console offers the following options:
Setup
Delete
To Be Saved
To Be Plotted
Save Options
Figure 44
Outputs Menu
Setup
The HSPICE integration to the Cadence Virtuoso Analog Design
Environment keeps track of two sets of nets and terminals:
The content of these sets of outputs is listed in the Outputs matrix of the
Environment Console (Figure 43 on page 151), and in the Setting Outputs form
in the Table Of Outputs. Signals marked as Plot must also be marked Save in
the Outputs matrix before they can be plotted.
152
Figure 45
The Name field is optional for manual entry, since a set of output nodes and
terminals you select from the schematic can be automatically entered in the
Table Of Outputs. A name entered here appears on the Table of Outputs and
the Waveform window.
The Expression field lets you build an expression using one of the following
methods:
Use the calculator to build the expression and then retrieve it by clicking
Get Expression.
The Plotted check box is automatically checked for the /OUTN signal.
153
The Open button launches the tools built-in calculator. See Cadence
documentation for information.
The Delete button clears one or more selected expressions from the Table
of Outputs and from the Selected Outputs area.
154
Click Change. As a result, when you select Results > Plot Outputs
following the simulation, the expression you deactivated remains
unplotted.
The New Expression button clears all previous entry the Selected Output
section so you can type in a new output.
Clicking Apply or OK sets up the specified outputs for saving and plotting in
the results phase of post-processing.
Delete
Clicking Delete when a row is selected in either the Table of Outputs of the
Setting Outputs form or the Environment Console Outputs matrix, immediately
removes the entry from both forms.
To Be Saved
The To Be Saved menu option expands to present three sub-options.
Add To checks off the check box to schedule the schematic-selected net or
terminal to be saved.
To Be Plotted
The To Be Plotted menu option expands to present a three sub-options.
155
Save Options
Selecting the Save Options menu option launches the Save Options form. This
dialog allows you to make multiple choices prior to simulation for the saving of
voltages, and current and power signals. The Save Options column on the
Environment Console adds a yes for each signal that is scheduled to be
saved. Making selections and clicking Apply or OK will change the standing of
previously checked Plot or Save options in the Setting Outputs Table of Outputs
and Environment Console Outputs matrix. You must click the OK or Apply
button for your choices to take effect.
156
Figure 46
The dialog consists of two sections. The upper section provides three radio
buttons that allow you to specify which voltages and independent source
currents signals to save to output according to the categories of all, level, or
selected. These buttons only refer to voltages and independent source
currents signals.
The lower section provides check boxes for choices to:
You can save a combination of signals by using both portions of the Save
Options dialog.
In the scenario below, the Save Options form specifies that the following signals
will be saved to output:
All individual current signals listed in the Outputs matrix on the Environment
Console.
157
158
The Save Options form limits the data written to your waveform file to the
third level of nodes for voltages and independent source currents, plus the
other checked options, below. (Setting Post Top to 1 limits the saved data to
the top level nodes only.)
All current signals across the design (not limited to the top three levels)
Total power
In the scenario below, because the selected radio button has been selected,
the Save Options form is scheduled to save:
Total power
The individual subckt current signals and the individual current signals
specified in the Outputs matrix
The list of saved and plotted outputs itself (including output expressions).
159
160
6
Running Simulations and Using Control Options
Describes the interface for running simulations and use of control options.
Run
Options
Netlist
Output Logs
Convergence Aids
The simulator input file, input.ckt, contains both the netlist and the simulator
control information required. The input.ckt data is passed to the HSPICE
simulator.
161
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 47
load("hook_function_file")
Then click Netlist and run in ADE. It automatically runs after the
netlist has been created, but before it is simulated. For example:
procedure(customerHook()
print(asiGetNetlistDir(session))
)
162
In Figure 48 on page 163, note that four analyses were run, Operating Point,
DC sweep, AC and transient analyses. shows the waveform generated for the
transient sweep of voltage for the expression /OUT and /OUTN.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 48
Run
The Run menu option does not run the ihnl. The /projectdirectory/topCellName/
HSPICE/<view>/netlist/netlist file will not change. Run updates the input.ckt file
with environment changes(i.e., analyses setup, design variable changes,
simulator option changes, etc.,). It does not update any changes in the
schematic nor does it update the changes in the stop and switch view lists in
Environment Options form.
Stop
The Stop menu command aborts a running simulation.
163
Options
Selecting any of the Simulation > Options sub-menus opens the Simulation
Options form with the listing of HSPICE options set to their defaults.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 49
The defaults can be of two types, HSPICE simulator defaults and defaults that
come from the Cadence environment via the .cdsenv preferences files. The
Analog Options form includes the buttons Cdsenv and HSPICE, which will
restore the values in the form to the default values set by the Cadence
environment or the Synopsys HSPICE tool. For anyone unfamiliar with the
Cadence environment, the cdsenv value is the result of a .cdsenv file loading
process. This is done based on a default sequence (installation, then project,
then user), but can be impacted by setting the CDS_LOAD_ENV environment
variable.
164
Analysis
The expanded Analysis menu item includes:
Transient
DC/OP
Matrix Control
Tolerance
Pole/Zero
RC Reduction
SI setting
Online html help is available for each labeled option by clicking the Help button
of the Simulator Options form.
Clicking OK or Apply adds the control option and value to the simulation input
file. To verify that your selected options are added, select Simulation > Netlist
> Recreate and view the circuits netlist file. Each of the Simulator Options
forms contain the UI controls shown and described in Figure 50 on page 166:
165
Figure 50
166
Netlist
The netlist contains component information but no simulation control data. (The
simulator input file, which contains both the netlist and the required simulator
control information, is passed to the HSPICE simulator.)
You can Create, Display, and Recreate the simulation input file using the menu
options for Netlist.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 51
167
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 52
Sample Netlist
Recreate allows you to create the simulation input file using full hierarchical
netlisting (all schematics are forced to re-netlist).
Output Logs
When the Popup Output Log option is turned on in the Environment Options
form (Setup > Environment), the tool automatically opens an HSPICE Log
Files window that displays simulator messages. You can select from a Logfiles
menu to display a listing file *.lis, standard out *.st0, or warning/error file.
168
Convergence Aids
When convergence issues arise, users of the HSPICE integration can employ
various techniques to bias or force a circuit towards a particular solution.
Convergence issues occur frequently in designs where MOSFETs have gate
voltages below the threshold needed to turn them on (such as an inverter with
an input voltage at midway between the supplies) and therefore the internal
node(s) might have an infinite number of solutions.
The ability to bias a node to a particular value is also important in analysis of
oscillators, as it enables the designer to start the oscillation. The convergence
aids options may help the simulator find a solution when it fails to achieve
convergence. Once you get the simulation to converge, you can save the DC
and Transient solutions. When you re-simulate, you can save time by restoring
the saved solutions.
For the HSPICE integration, the interface for setting up nodesets (.NODESET)
and initial conditions (.IC) is opened on the Environment Console by Selecting
Simulation > Convergence Aids. Node Set, provides an initial guess for nodes
in any DC analysis or the initial condition calculation for the transient analysis
and Initial Condition provides initial conditions for nodes in a transient
analysis.
For detailed information solving convergence issues in HSPICE see the section
Diagnosing Convergence Problems in the HSPICE User Guide: Simulation and
Analysis.
169
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 53
170
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 54
4. To set other nodes to the same voltage, select them, one at a time, on the
schematic.
5. To set other nodes to a different voltage, change the voltage, and select
other nodes.
6. OK the form before you run or re-run your simulation. (Click Cancel to clear
the form and dismiss it.)
You can select nodes at any level of the hierarchy. When you select a node at a
lower level in the schematic, the node is highlighted, but the voltage value is
annotated only on the higher-level.
While the select node commands are active, the system highlights selected
nodes and labels them with the voltages you set. After you close the form, the
UI removes the highlighting and the labels from the schematic. Re-opening a
form with voltage entries restores the highlights and annotation.
171
If the node voltage setting forms are closed during your session and you want
to change or release voltage values, re-open the form by selecting Simulation >
Convergence Aids > Node Set or Initial Condition.
For further information about the available convergence assistance through the
UI, refer to the Cadence documentation.
172
7
7
173
Plot Outputs
Direct Plot
Plotting Assistant
Annotate
Save
Select
Delete
Printing/Plotting Options
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 55
Results menu
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 56
175
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
New SubWin plots the new expression or waveform in a new sub window
Offturns off the plotting mode function; this feature allows you to generate
waveform expressions without creating a plot. This is typically used when
the expression needs to be further defined within either the console
Outputs section or the calculator.
The Window Functions pulldown list provides controls to manage the various
windows and plotting dialogs on-screen:
176
Schematic - Raise brings the Schematic Editor to the top of the stack of
windows.
Waveform - Raise brings the waveform window to the top of the stack of
windows.
Waveform - Clear Subwindow clears all waveforms from the current subwindow of the current waveform window.
ADE - Raise brings the Environment Console to the top of the stack of
windows.
HSPICE Integration to Cadence Virtuoso Analog Design Environment User Guide
E-2010.12
The Data Mode dropdown allows you to select the simulation results on which
to operate:
Current ADE Results mode uses the data currently loaded for the current
ADE session. This is the default mode.
The Results Directory field is where the user specifies the path to the desired
results directory. In addition, any valid results directories previously declared for
this field are added to the pulldown choices of this combo field. Clicking the
Remove Pick button removes the alternate results path field value from both
the field and its combo choices list and restores the path to the first found
previous results specified.
remote/mach3/usr6/
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Current ADE Results and Reference Results is the third Data Mode
dropdown item. This mode is a combination of the other two modes. In this
case, two waveforms are created where one references the current ADE
results and the other the Reference Results. The waveforms generated from
each data set are appended on the same graph window, to allow for
convenient results comparison.
177
The Analyses that have an asterisk (*) appended to their name are the ones
that currently have data in the selected results. Analyses without corresponding
data are provided as valid picks so that you can use the Plotting Assistant to
build expressions prior to running a simulation. A check box allows you to filter
these analyses, to show only the collection with valid current results.
Function this field allows the user to choose from a set of most
commonly used plot function expressions. Each analysis has its own set of
plot functions.
Selection this section provides the user the ability to choose from several
methods of selecting the signals on the schematic. The set of methods to
choose from varies on a per-plot function basis.
In addition, the Currently Selected Item(s) field shows the currently selected
signal set for the function. The choices pulldown for this combo field shows the
five previous selection sets used on this function. This combo pulldown allows
the user to quickly redo previous plots without having to go to the schematic for
re-selection. This section also warns when selected schematic items are not
found in the simulation data, thus informing the user when a plot cannot be
produced.
Because the Plotting Assistant shares the same core selection engine with the
other plotting utilities in Direct Plot, it is possible for the PA to get out of sync
with the selection engine when multiple plotting utilities are used concurrently.
When the Plotting Assistant does not appear to respond to schematic
selections, the Re-Start button is provided to restore the selection
synchronization of the PA.
178
Plot Type this field allows the user to specify the format in which a plots
axis are displayed.
Modifier this field allows the user to select a modifier function that wraps
the generated waveform expression.
Instructions this label helps guide the user through the necessary steps
needed to create a successful waveform expression. This label will
sequentially explain selection requirements, form field value requirements,
and the status of the required simulation data.
Plot/Replot these mutually exclusive buttons are used for two main
purposes. Use Plot when a plot is not dependent on performing a selection
in the schematic. Use Replot to quickly repeat a plot using the previous
selection set.
179
Function: Current
Function: Voltage
Function: Power
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 58
180
Net
Differential Nets
Terminal
Differential Terminals
Terminal
Total Power: Since the total power function does not require schematic
canvas input, the plot is created by clicking the Plot button.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 59
181
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 60
As with all functions, multiple selection methods are available to further define
what is to be plotted. For example, with current selected, three choices are
available through the pulldown list of selection methods. Four modifier choices
are available.
Plotting Noise Analysis Signals
The Noise Analysis functions include output noise, input noise, and gain.
See Figure 61 on page 183.
182
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 61
183
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 62
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
184
The following picks are available using the Plot Outputs sub-menus
Transient Plots: the transient response for the transient signal(s), etc. For
this menu item to be active, transient data must be present and some
signals on the Environment Console Outputs table must have both Plot and
Save options activated.
AC Plots: the AC response for the AC signal(s). For this menu item to be
active, ac data must be present and some signals on the Environment
Console Outputs table must have both Plot and Save options activated.
DC Plots: the DC sweep response for the DC signal(s). For this menu item
to be active, dc data must be present and some signals on the Environment
Console Outputs table must have both Plot and Save options activated.
Noise Plots: the squared noise voltage for the noise signals. For this menu
item to be active, noise data must be present.
Expressions: Plots the waveforms for expressions you define in the Setting
Outputs form (see Chapter 5, Saving-Plotting Outputs).
185
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
For example, using the state shown in the Environment Console in Figure 55
on page 174, if you select AC Phase on the Direct Plot menu the message on
the Schematic Editor status line instructs you to select nodes and terminals and
then press the Esc key. A waveform such as the one below is generated based
on selecting the ground nodes and the OUT terminal.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 64
186
The Direct Plot options and the curves they will plot are:
Transient Sum Multiple signals added together and plotted (the status line
message prompts you for the signals)
AC Magnitude & PhaseThe db20 gain and phase of selected signals are
plotted together
187
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
An active menu option implies that a data file has been generated. Click an
available option for the results to be displayed. Then select the nodes for which
you want the data displayed. For example:
To print data for DC Operating points:
1. Select DC Operating Points on the Print menu
2. On the Schematic Editor, select any number of appropriate nodes to
populate the display window with the nodes DC operating point data.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
188
For further information about the Print menu, refer to the Cadence
documentation.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
189
Figure 65
Back-annotation in the HSPICE interface can be performed with the Results >
Annotate > DC Operating Points for time=0 results, or Transient Operating
Points for final transient timepoint results.
Once annotated with operating points, a device is displayed as in Figure 66 on
page 191:
190
Figure 66
The three operating points to display (in the example above id, vgs, and vds)
can be defined on the cell CDF, and can be changed on a per-instance/master/
library level in the Component Display dialog. The functionality of that dialog is
not impacted by the HSPICE integration.
191
.ends
Note that there is one real device instance nch1 defined in this macro model.
Then HSPICE outputs the operating point information based on the real device
instance nch1 as follows:
'Xm0.nch1:Vgs', 'Xm0.nch1:Vth', 'Xm0.nch1:gds'
So there is data name difference here between HSPICE outputs in the PSF file
and annotation function calls in ADE.
Use either of the following methods to create a mapping to handle this issue.
Using the Edit Properties Form
This method is designed to annotate a current selected instance ('m0') only on
a schematic for DC or transient operating points.
Use the Edit Object Properties form to add an instance property of m0 named
mapDeviceName as a string type, then fill in the actual device instance name
nch1 as its Value as shown in Figure 67 on page 193. Access the Edit
Properties form using the Schematic Editor menu: Edit > Properties >
Objects.
192
Figure 67
193
Figure 68
Note:
194
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Save Results
The Save Results form shows the results of the latest simulation with the
default name schematic-save. To save a results directory under a different
name, manually change the name and add a comment if you wish, and
navigate to a directory of your choice, then click OK. For more information
regarding the Save Results form, see the Cadence documentation.
Select Results
Selecting Results > Select launches the Select Results form. You can use this
form to update and restore results.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
195
Check that the Results Directory field displays the correct information. You can
select results in a different location by clicking the Browse button and
navigating to the proper directory.
Note:
The proper directory is two levels up from the psf/ directory. For
example, if your results directory is: simulation/test_vco/
HSPICE/schematic/psf/, use the browser to navigate to
simulation/test_vco/HSPICE/.
Delete Results
You can clear your existing results by invoking the Delete Results form. The
Results Directory field lists the default directory in which results are saved. To
delete a set of simulation results, select the name of the results in the list field
and click OK. If the results you want to delete are in a different location, click
the Browse button to open the Unix Browser and navigate to the target
directory, highlight and click OK. Clicking the Update Results button
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
196
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 69
For detailed discussion of this form, see the documentation available directly
from Cadence.
197
198
8
8
Describes the Monte Carlo Analysis capabilities available through the HSPICE
integration interface.
The Monte Carlo Analysis form in the HSPICE Interface to the Cadence
Virtuoso Analog Design Environment allows easy access to HSPICEs
advanced analysis capabilities without additional license control.
Note:
For paths to Monte Carlo analysis demonstration cases available with this
release, see HSPICE Integration to ADE Demonstration Examples.
For information on using HSPICE distributed processing for Monte Carlo
simulations, see HSPICE Monte Carlo Distributed Simulation in Chapter 15,
Distributed ModeMonte Carlo/Corner Analyses.
The following topics are discussed in these sections:
Using the Options Tab of the HSPICE Monte Carlo Analysis Form
199
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 70
200
2. Enter the number of sweeps (Number of Run) to specify the Monte Carlo
sweeps.
3. Specify the starting sweep number in the Start Run field.
4. Click the List check box to enable the input field to type in the effective
points in the simulation.
5. Click the Enabled check box to enable the Monte Carlo for the selected
analysis.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 71
201
6. For Variation Mode, select either the self-defined param for variation
parameters used in the circuit, or the statistical model to do variations. To
do variation on the self-defined parameter, use the variation parameters
according to the HSPICE-supported variation functions/arguments.
Function
Description
UNIF
AUNIF
GAUSS
AGAUSS
LIMIT
Random-limit distribution function by using absolute variation. Adds +/abs_variation to nominal_val based on whether the random outcome of
a -1 to 1 distribution is greater than or less than 0.
Nomi_val
Nominal value in Monte Carlo analysis and default value in all other
analyses.
Abs_val
Sigma
Multiplier
To set up measurements see Setting up Measurements, PostPlotting, and Analyzing the Simulation Results Using the Outputs
Tab.
page 203. You can set up the multiprocess count according to the instructions
in the form. For details on HSPICE multiprocessing, see Running Multithread/
Multiprocess HSPICE Simulations in the HSPICE User Guide: Simulation and
Analysis. The count selected in the window is in effect only for Monte Carlo
session. See also, HSPICE Monte Carlo Distributed Simulation on page 323.
Figure 72
203
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 73
204
MCBRIEF=2: Outputs the Monte Carlo parameters into a .lis file only.
SEED, starting seed number for the random generator; minimum value is 1;
the maximum value of is 259200.
Run a simulation
Get and view measurement variation statistics and plot them as curves,
scatter plots, or histograms.
205
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 74
206
Outputs tab
Measurements Pane
Use the Measurements pane as follows:
1. Click the Browser button to navigate to a measurement file.
Simulation Pane
Control the simulation from the Monte Carlo form as follows:
1. Click Netlist-Run or Run to begin a simulation.
2. Use the Netlist button to generate a netlist only from the Setup tab.
3. Click the Output Log to generate an on-screen running account of the
progress of the simulation.
4. Select the type of analysis to be run from the Analysis selection box.
5. Select the Plotting Mode for waveforms from three options: open a new
graph window, append to existing window, or replace an existing graph
window.
6. Pre-set the plotting mode option for the waveview window.
207
Result: The HSPICE simulation log file is displayed after the simulation
finishes and the job concluded message in the log file indicates a
successful simulation.
Outputs Pane
Use the Outputs controls to specify output attributes.
1. Click Get Outputs from Console to use either the output signals or the
expressions from the Environment Console which are set up previously, and
which will populate the field below.
208
Note: You must have input the measurement file for HSPICE to
calculate the statistical information. Otherwise, no statistical
information is displayed, even if you click the button.
2. Select the X and Y axes names from the selection boxes and enter the
number of Bins to be plotted.
3. Click Plotting As and plot the arbitrary combination of variation parameters
and measured results as a Histogram, Scatter, or Curve graph to analyze
the Monte Carlo simulation results.
4. Alternatively, use the Plot menu on the HSPICE Monte Carlo Analysis form
to plot the combination of variation parameters and measured results.
Figure 75
209
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 76
File menu
1. To Save/Load Statistics, under the File menu, select either the Save Setup
or Load Setup option. Alternatively, select the Save State or Load State
option in the Environment Console to perform the same operation.
2. Create an OCEAN script based on your Monte Carlo session by either:
210
Use the provided OCEAN API functions directly to write your own
OCEAN script to do batch simulation. For detailed OCEAN API
functions, please refer to the descriptions in Appendix B, OCEAN API
Functions for HSPICE Monte Carlo Analysis.
Alternatively, use the Help button on the HSPICE Monte Carlo Analysis
form to assess an html user guide for the Monte Carlo feature or the
reference guide for OCEAN API functions
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 77
Help menu
211
212
9
9
Corners Analysis
213
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 78
The Corners setup tab displays information about the currently defined corners
and output measurements, and setup function controls.
214
Each column in the Corners report field characterizes a corner; each row
characterizes an environment variable. The column headings identify each
corner name. The name of the environment variable is displayed on the left
side of each row. For example, if the environment variable represents the model
file, the row states the name of the model file followed by the sections to be
used in each corner. If the environment variable represents the design variable,
then the row lists the name of the design variable followed by the values of the
design variable to be used in each corner. The temperature variable appears as
one row by default.
The Measurements field displays the information about the currently defined
measurements.
Corner Menus
The menus on the Corner Analysis Window contains the commands needed to
setup, run and plot the results of a corners analysis.
File
Simulation
Help
215
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 79
The Corner contents section displays the following controls and buttons:
216
Add Variables
Add Models
Add Temperature
Add Combination
Remove All
Enable/Disable Corner
Delete Corner
Get Measurements (from the utility) and Delete (to remove any selected
row).
217
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 80
2. Click Add Models to bring a model file into the HSPICE Corner Analysis
environment. The Select File browser opens (Figure 81 on page 219).
218
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 81
3. Add a single model file if all models for all corners are located in a single file
or add multiple model files if the models are located in the multiple model
files.Your model files are added to the Corners report field on the Setup tab.
If you have already added some corners, the added model file values will be
nil.
4. Use the Add Temperature button to add a temperature parameter. When
Temperature parameter exists, this button is disabled. The ADE
environment default includes the Temperature parameter.
5. To delete a design variable row (model file, design variable, or temperature),
select it on the report field, then click Delete Model File|Variables|
Temperature. A deletion removes these variables from the Corners
environment, but they remain in the ADE environment.
Setting up Corners
Use the Add Combination Form to change or add values to the variables
parameters.
To make changes or modify values to variables/parameters:
1. Click Add Combination to open the Add Combination Form (Figure 82 on
page 220).
219
Figure 82
2. Enter values for each parameter; when you input multiple values for a
parameter, use commas , or empty spaces as delimiters between values.
3. On the Add Combination Form, click Clear if you wish to delete all entries or
click Add to create corners based on the values you input and add them to
the Corners report field (Figure 83 on page 221).
Note: The added corners are named cornerXX in which XX is the
corner index number.
220
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 83
4. To remove all corners, parameters, and their values from the Corners report
field, click the Remove All button.
Modifying Corners
You can further modify a corner by using the group of controls beginning with
the Corner Name selection box.
Uses the Corner buttons as follows:
1. Click Edit Corner to set all the values for its model files (or section of the
file), design variables, and temperature. See Editing a Corner on page 222
for discussion of methods to edit a corner.
2.
221
3. Select an existing corner name in the Corner Name field and modify it by
using these buttons:
Copy Corner: Select a corner's contents and values. The default for the
new corner's name is Corner_name_Copy. For example, if the selected
corner name is cor1, then the copied corner name is cor1_Copy. To
copy a corner, select an existing corner from the Corner Name
selection box and click the Copy Corner button. The copied corner
appears in both the Corners report and Corner Name selection fields.
Delete Corner: Used to delete a corner from the current corner analysis
environment. To delete a corner, select it in the Corner Name field and
click the Delete Corner button.
Editing a Corner
There are two methods to edit a corner:
1) Select a corner and edit all values to do with model files, design variables,
and Temperature; or
2) Edit different corners within the model file, design variable, or temperature
parameter.
Corner Editing Method 1
1. Select the corner in the Corner Name 1. Either click Edit Corner after selecting a
field and click the Edit Corner button to row in the Corners report field or doubleopen the Corner Edit Form.
click the row to open the Corners Edit form
(Figure 85 on page 224).
2. Modify all values shown on this form. 2. Modify any values shown on this form
For example, Figure 84 shows the edit to and click Apply or OK on the form to save.
the Corner7 vdd value to 3.2
222
3. Click Change to repopulate the Setup 3. Use the radio buttons at the top of the
tab with the updated value.
form to edit corners for other Variables,
Models, or Temperature. After successfully
editing, the corners information in the
Corners report field automatically
updates.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 84
223
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 85
224
Figure 86
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 87
225
226
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 88
Outputs tab
Simulation
You can use either the Simulation pane or the Simulation menu on the
Corners Analysis form to prepare a netlist and run a corners simulation.
227
Netlist & Run SimRecreates the netlist file and starts a simulation.
RunStarts a simulation.
Sequential run - create netlist for each corner and simulation them one by
one
Multiprocess run create one netlist file making use of HSPICE .alters
and use the HSPICE -mp option to simulate the netlist file (see Setting Up
Multiprocessing of Corner Analysis).
Distributed Process run create a netlist file for each corner and assign
corners simulation to several jobs to finish all corner simulations (see
Chapter 15, Distributed ModeMonte Carlo/Corner Analyses).
Set up the multiprocess count according to the instructions in the form. The
count selected in the window is in effect for the Corner analysis session
only.(For details on HSPICE multiprocessing, see Running Multithread/
Multiprocess HSPICE Simulations in the HSPICE User Guide: Simulation
and Analysis.)
228
Figure 89
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 90
229
Plotting Outputs
After successfully netlisting and simulation, you can plot outputs in the using
the Output Plots pane.
To plot an output signal or expression:
1. Click Get Outputs From Console or Plot Assistant to load the existing
outputs into the Ouputs report field
2. Select one row in the Outputs report field.
3.
Select the required corners in the Corners list box and click the Plot button.
The tool plots the output in a waveform. For example, Figure 91 plots the
/out signal for Corner1 and Corner3.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 91
230
Figure 92
231
You can also click the Get Measurements Summary button to reload them.
Plotting a Measurement Variable
To plot a measurement variable simulation result based on corners:
1. Select the measurement variable row in the Measurement Summary
report field.
2. Click the Plot button.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 93
3. Click Print With to generate a text file containing all measurements results.
4. Enable the Corners check box to include corners information in the
generated text file, as shown in Figure 94.
232
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 94
Selecting File >XXX and Saving all the operations as a single OCEAN
script to do a post batch run simulation with corner analysis, or
Use the provided OCEAN API functions directly to write your own
OCEAN script to do batch simulation. For detailed OCEAN API
functions, refer to the descriptions in Appendix D, OCEAN API
Functions for HSPICE Corner Analysis.
Alternatively, use the Help button on the HSPICE Corners Analysis form
to assess an html user guide for the corners feature or the reference
guide for OCEAN API functions
233
234
10
HSPICE RF Analysis
10
235
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 95
236
Analysis
Report section
Main analysis
input section
Sub-type
analysis
input section
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 96
237
1. Select the desired analysis option (HB, HBOSC, SN, or SNOSC) from the
Analysis radio buttons. The appropriate analysis-related fields are displayed
for required user input. For example, Figure 97 shows the Analysis form for
an HBOSC simulation.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 97
238
2. Input Steady state analysis information in the main analysis input section.
3. Check the Sweep button to display and input analysis sweep information.
4. Click the Add button in the main analysis input section to add a steady state
analysis to HSPICE RF simulation.
Result: If the steady-state analysis is successfully added, the detail is
added to the analysis report field and all the input fields are cleared; if the
steady-state analysis is not added successfully, an error or warning
message appears in the icms window. You can correct and continue add
the analysis.
5. Click the Sub-types button to display the Sub-type analyses input section
for you to set up a small-signal analysis. Analyses types include HBAC,
HBNOISE, SNAC, and SNNOISE.
6. Click the Add button in the Sub-types analysis section to add a small-signal
analysis to HSPICE RF simulation.
Result: If the small-signal analysis is successfully added, the detail is
added to the analysis report field and all the input fields are cleared; if the
steady-state analysis does not add successfully, an error or warning
message appears in the icms window. The related steady-state analysis
must be added before a sub-type small signal analysis is added. You can
correct and continue the add procedure.
7. Select the analysis item in the analysis report field to restore its detail
information back to the input fields so that you can change it.
8. In the analysis report (top) section, use the Enable/Disable or Delete
controls to enable, disable, or delete the selected analysis.
239
Result: Selecting a different group in the Options Filter displays its related
group options in the Options tab with their default value in the input field.
You can modify or input each displayed option with appropriate values.
2. To change the default values, use the Reset All From Cdsenv or HSPICE
buttons to reset all options field values to either the HSPICE integration
default values (Cdsenv) or HSPICE options default values.
3. When you complete any changes to the option defaults, click Apply to
ensure that the change is added to the simulation run.
Available Options
The Commonly used options for RF are:
240
PHASENOISETOL: Specifies the error tolerance for the phase noise solver.
HBTRANINIT: Selects transient analysis for initializing all state variables for
HB analysis of a ring oscillator.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 98
241
242
PHASENOISETOL: Specifies the error tolerance for the phase noise solver.
243
Outputs report
General outputs
input
Noise outputs
input
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 99
Outputs tab
3. Use the Noise outputs input section to add or change Noise-specific outputs
in the outputs report field. These input outputs are added to the netlist and
the HSPICE RF Simulation generates psf data for the outputs to plot
waveforms.
4. In the outputs report field select and data you wish to exclude and click
Delete to permanently removed them form the simulation.
5. Use Run Sim or Stop Sim button to directly invoke or abort an HSPICE RF
simulation.
6.
Use the Plot As button and Waveform window mode to plot a waveform of
outputs after successfully running an HSPICE RF simulation. The window
options include: open a new graph window, append to existing window, or
replace an existing graph window.
The HSPICE RF simulation log file is displayed after the simulation finishes;
and the hspicerf done message in the output log file indicates a successful
simulation.
245
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
246
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
1. To Save/Load Statistics, under the File menu, select either the Save Setup
or Load Setup option. Alternatively, select the Save State or Load State
option in the Environment Console to perform the same operation.
2. Create an OCEAN script based on your RF Analysis session by either:
Use the provided OCEAN API functions directly to write your own
OCEAN script to do batch simulation. For detailed OCEAN API
functions, please refer to the descriptions in Appendix C, OCEAN API
Functions for HSPICE RF Analysis.
247
248
.ACPHASENOISE, .STATEYE
In a frequency sweep analysis such as .HBAC, some sweep types are not
supported in the current release. For example: sweepblock, data sweep:
DATA=dataname.
11
11
For paths to corner analysis demonstration cases available with this release,
see HSPICE Integration to ADE Demonstration Examples.
These topics are discussed in the following sections.
249
Optimization Model
Optimization Variable
Measurements
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
3. You can modify the selected statement in the report by clicking Change.
4. Click Delete to delete one useless selected statement or Enable/Disable to
disable/enable the selected statement.
5. Click Clear to remove the model from the UI.
6. When the Default button is enabled, click it to use the default parameter
value.
Setting Up Measurements
To launch the Measurement Utility:
1. In the Measurements pane click Open (see Chapter 12, HSPICE
Measurement Utility for a detailed description of the utility).
2. Click Get Measurements to load all enabled measurement variables into
the measurement report field.
3. Click Close to dismiss the HSPICE Measure Utility window.
251
252
Simulation
Output
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
253
4. Select the OPT model which you defined in the optimization model field on
the Setup tab.
5. Click Add to add the Analysis setup into the report.
6. Click Delete to delete a selected statement.
7. Click Enable/Disable to disable/enable the selected statement.
8. Click More Results to choose more results.
9. Click Data Files to load the data file. Use the Select Data to choose one
data to be included in the Data field.
10. Click Change to enable modification of the selected setup.
11. Click Clear to remove all entries on the Analysis UI.
254
Use the provided OCEAN API functions directly to write your own
OCEAN script to do batch simulation. For detailed OCEAN API
functions, please refer to the descriptions in TBD.
255
256
12
HSPICE Measurement Utility
12
Trig/Targ Setup
Find/When Setup
257
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
The main tab of the utility window opens without checking out any additional
licenses. The main page of the HSPICE Measure Utility opens as shown in
(Figure 104 on page 259).
258
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
259
Figure 105 Upper section Measure Utility form; lower two show HSPICE RF analyses
Trigger-Target
Function
Find/When
Equation
Error
Special-Meas.
260
Trig/Targ Setup
The Trig/Targ setup panel (Figure 106) is divided into two sections, Trigger
and Target.
261
262
Find/When Setup
The Find/When tab (Figure 109) displays controls and parameters as noted.
Figure 109 Find/When setup form (top) and when doing an FFT measurement (bottom)
2. Input the value on the right blank text field. If TRAN analysis is selected in
the Measure Analysis selection box, the right blank is for Time; for AC
analysis, the right blank is for frequency (Freq), for DC analysis, it is for
Parameter.
3. Select the variable type and input the variable name. You can choose to use
the Schematic button to choose the variable name from the design
schematic editor.
263
4. Select the signal type and input the signal. You can use the Schematic
button to choose the signal name from the design in the schematic editor.
After that, the signal value must be specified on the right blank field.
5. Select the event type. If it is the last event, click the Last check box,
otherwise input the value in the field to the left of the Last check box.
6. Optionally, input the time delay (TD) before HSPICE enable the measures.
7. If you select FFT in the Measure Analysis selection box, then the Find/
When tabbed section changes to the lower section of Figure 109 on
page 263. You only need to set the Freq value and select the signal type.
The signal is reserved during FFT setup.
Equation Setup
Use the Equation setup (Figure 110) for measurement to specify the HSPICE
parameter measure statements directly into the text field.
264
265
3. If you select the function SFDR, the setup form is refreshed to Figure 114.
Input values for maxfreq and minfreq, as necessary.
266
267
268
269
270
13
13
MOSRA Overview
MOSRA Overview
MOSFET reliability analysis (MOSRA) is an HSPICE advanced feature to
simulate MOSFET lifetime and reliability after an extended period of service.
This feature is essential in maintaining the long-term reliability of these
devices for the highest quality IC designs. MOSRA is also available in
271
First install HSPICE ADE interface and configure the 'cdsinit' file
to load the HSPICE context file. After invoking ADE, check for the
current configured simulator. If the default simulator is not
HSPICE, you must change it to HSPICE for this feature.
272
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 120 Environment Console Tools menu with Reliability Analysis selected
273
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
274
Main Menus
The three menus on the HSPICE Mosra Analysis window are Session,
Simulation, and Help.
Session menu options include the following. The first two options invoke the
Save/Load States command in the Environment console.
Save Setup Saves the user setup states generated in the Mosra Analysis
window
Save Script Saves all user operations into one OCEAN script file for use
in non-graphic mode.
Netlist and Run Netlists current analysis setup and invokes HSPICE to
run simulation.
275
The MOSRA model setup section provides two options: HSPICE MOSRA
models (built-in, default models) and Custom MOSRA models (usersupplied).
Options Page
The Options page (Figure 122 on page 276) lists all MOSRA analysis-related
command options used for running an HSPICE simulation.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Output Page
The Outputs page displays four sections: Outputs Plot, Measurements
(measure results), Simulation, and Radeg Files information. Use these
sections to plot analysis outputs, measure and print results, netlist and run
simulations, and view radeg (Reliability Analysis Degradation) file parameters
information in a table format.
276
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
277
SimMode Select from the following simulation flows: pre-stress, poststress, both flows (default), or the simulation mode to support battery
degradation in a stress calculation.
278
Temperature
Model Corner Use different model parameter files for pre-stress and
post-stress simulation. When selected, the section displays a Model
File select field and a Model Section field (Figure 125). You can use
these two fields to define models for each MOSRA simulation. The
choices in the Model File select field come from the settings in
Environment console. Select Setup > Model Files in the Environment
console to open the Model Library Setup form (Figure 126 on
page 280). Locate the model Section for the Model Files in this form to
populate the Mosra Analysis Model Corner field.
279
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 125 Model Corner selected, model files populated from Model Library Setup
form
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
280
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Radeg File Enables selection of a specific degradation file for poststress MOSRA simulation. The Radeg File choice displays a file path
input field and Browser button.
281
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
282
The basis for the Monte Carlo simulation is determined by the setup in
the HSPICE Monte Carlo Analysis window where a transient analysis
and 20 trials have been specified in the example (Figure 130).
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 130 Monte Carlo Analysis utility setup for MOSRA run
Sweep Select and input DEC (decade variation) or LIN (linear variation)
value.
283
Add Adds the MOSRA command into the simulation environment after
user input of the above information. The MOSRA command is added to the
MOSRA Statement report field and assigned a value of AlterIndex.
284
If you select the HSPICE MOSRA Model radio button this section includes the
following fields and controls:
HCI Params Reliability model parameter for HCI; (1) select the
parameter name from the choices; (2) input its value.
NBTI Params - Reliability model parameter for NBTI; (1) select the
parameter name from the choices; (2) input its value.
Add Make additions to the MOSRA model following inputs to the above
fields; successful additions are shown in the MOSRA Model report.
Change Use to modify the selected model in the MOSRA Model report.
Default All Removes only the values in the HCI Params or NBTI Params
fields.
285
The following fields and controls are displayed in the Custom MOSRA Model
section:
MOSRA Model File Selects the MOSRA models definition file. Note: The
relative path in Shared-Library Path and MOSRA Model File is based on
the current working directory.
MOSRA Model Name Use to select from the choices of the MOSRA
Model Name field in the Appending Models section.
After you select the MOSRA Model File, the file is parsed to load all the defined
MOSRA libraries as choices for the MOSRA Model Name field.
If the value of MOSRA Model Name in this section is All, then the choices of
the MOSRA Model Name field in the Appending Models section are all the
defined MOSRA libraries in the MOSRA Model File.
The Appending Models report shows all the Custom MOSRA models'
related .APPENDMODEL commands.
The following are the Appending Models section fields and controls:
287
APPENDALL
DEGFN
DEGFP
MOSRALIFE
MOSRASORT
MRAEXT
MRAPAGED
RADEGOUTPUT
The values displayed in the fields are the defaults supported by HSPICE. For
the detailed information on the options, refer to HSPICE and RF Netlist
Simulation Control Options in the HSPICE Reference Manual: Commands and
Control Options.
Alternatively, clicking the button on the left side of each option pops up the help
information about the option. When you change the value of an option, a
changes pending asterisk, *appears on the upper right side of the page.
Note:
288
Simulation Control
After setting up the MOSRA commands and models, adjusting options, and
specifying measurements, you can do netlisting and simulation.
Use either the Simulation menu in the HSPICE Mosra Analysis window or the
Simulation controls section in the Outputs page. The following are the
simulation control buttons:
Note that you need to set up a Tran, DC, or AC analysis before running HSPICE
Reliability analysis. See Chapter 4, Analysis Setup and Design Variables for
discussion of the three analyses in the HSPICE integration to ADE.
289
degradation period waveforms, select the All value below the Degradation
Period field.
Following a successful netlisting and simulation, plot outputs from the Outputs
page using the procedure below.
To plot an output signal or expression:
1.
Click Get Outputs from Console or Plot Assistant to load the existing
outputs into the Outputs report field. (See HSPICE Plotting Assistant in
Chapter 7, Printing and Plotting Results for details on using the Plotting
Assistant.)
290
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
291
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Note: Only VT, IT, VF, IF, VS, and IS expressions are supported in
MOSRA outputs plots.
Adding Expressions Using the Calculator
Use the following procedure to add expressions into MOSRA with the
Calculator.
1. In the Environment console, select the Outputs menu and open the Setting
Outputs form.
2. Enter the expression by selecting the signal on the schematic editor.
3. In the Setting Outputs form Calculator click the Get from Schematic
button.
292
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
293
294
The Measure Files field value is a measure results file which combines
the .mt/.ms/.ma measure result file suffix string with the alter index and
simMode. (*.mt is the transient analysis measure results file suffix, *.ms is the
DC analysis measure results file suffix, and *.ac is the AC analysis measure
results file suffix.) For example: .mt0 means alter 0, pre-stress simulation
measure results file; .mt1@ra means alter1, post-stress simulation measure
result file.
The Reltime field to the right of the Measure Files field is used for MOSRA +
Monte Carlo co-simulation, which outputs multiple measure results file. This
field shows the suffix of these results files. If there are no Monte Carlo
simulations, the field is disabled. (The default selection is All.)
The Waveform type field and Bins field are used to specify how to plot
measure variable results. Possible choices are Curve, Histo, and Scatter. For
Histo, the Bins field becomes enabled and requires input.
Select Measure Files to show measure variables results in the Measurements
report. Select a measure variable row in the report field and click Plot to
HSPICE Integration to Cadence Virtuoso Analog Design Environment User Guide
E-2010.12
295
The screen capture in Figure 142shows a plot for a MOSRA + Monte Carlo
measure variable of alter 1 which runs a transient Monte Carlo simulation:
296
To print all the measurement results in a measure file, select Measure Files
and click Print. The tool prints measure results information from the measure
file in a Results Display Window using a table format (Figure 143 on page 298).
297
Figure 143 Result Display Window with measure results in tabular format
298
To show and plot the degradation parameters for each user-specified MOS
element after doing MOSRA analysis use the Outputs page controls. The
Radeg Files section enables you to easily evaluate and analyze the degraded
parameters. Multiple degradation files (.radeg#) can be generated by HSPICE
through multiple .MOSRA statements set up in the previous tabs. Here, one
selection list is available for user to select actual degradation file to analyze and
plot.
The choices in the Radeg Files field are automatically loaded after a
successful simulation.
The Radeg Files field value is composed of the radeg file suffix combined with
the .radeg suffix string with the alter index. For example: .radeg0 means alter
0, radeg file.
To show the element information in the radeg file in the Radeg Information
report:
1. Select Radeg Files and MOS Element Name to show the element
information in the radeg file in the Radeg Files information report.
2. Select Degradation Param.
3. Click Plot to plot the element parameter information with Degradation
Time.
299
4. Click Print to open a Results Display Window which reports the radeg file
information in a table format.
300
301
302
14
14
To invoke the HSPICE Violation Check form, on the Environment console select
Tools > HSPICE Violation Check (Figure 147).
303
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 147 HSPICE Violation Check menu item on the Tools menu
The HSPICE Violation Check form opens (Figure 148). This interface supports
all HSPICE .BIASCHK command usages.
304
The form enables the monitoring of general elements, model, subckt, region,
length and width, and expression; it can also monitor associated voltage,
current, w and l. The form changes according to the Type (of element under
study), and the specified parameter selected to be monitored (Monitor).
These topics are discussed in the following sections:
GUI Controls
GUI Controls
For a detailed description of the use of the .BIASCHK command and use
models see .BIASCHK in the HSPICE Reference Manual: Commands and
Control Options.
.BIASCHKs Report Field
The .BIASCHKs report field is a table that lists all the BIASCHK commands
that have been set up (added) and their summary information. It also provides
selections for specific BIASCHK run modes and handling of outputs.
Control Buttons
The control buttons on the right side of the form are:
305
306
Name field: .BIASCHK command name; if you do not specify a name, the
name biaschkn, where n is an incremental number, is assigned. For
example, if you do not specify a name, the name, biaschk1 is assigned to
the .BIASCHK command.
Monitor selection box: Type of value you want to monitor. You can specify v
(voltage), i (current), w, and l (device size) for the element type. The
Monitor selection box is removed for Expression and Region bias checks.
For a Region bias check, check boxes are added for transitions to and from
a region including cutoff, linear, and saturation.
Simulation selection box: Specify op, dc, tr (transient), or all (op, dc, and
tr). The tr option is the default simulation type.
Model Names field: Input model names for all except expression-type bias
check. The element model can also include wildcard characters * or ?. It
can also be input multiple names by using delimiter space or ,.
Exception field: Input element or instance names that you do not want to
have bias checked. These can also be selected from a schematic using the
Select button. Multiple names can be input using delimiter spaces or
commas ,.
Subckt Instance Names field: When Type indicates the bias check
element is a SUBCKT, values for Pin1, 2 can be input using the Select
button to import from the schematic design. When the instance names are
an input directory, use the backward slash / as delimiters.
Subckt Definition Names field: Input subckt names (except for expressiontype bias checks). These names can include wildcard characters * or ?.
Multiple definition names can be input by using delimiter spaces or commas
,.
Limit field: Bias check limit that you define. Reports an error if the bias
voltage (between appointed terminals of appointed elements and models) is
larger than the limit.
Noise field: Bias check noise that you define. The default is 0.1v. Noise-filter
some of the results (the local maximum bias voltage that is larger than the
limit). The next local max replaces the local max if all of the following
conditions are satisfied:local_max-local_min noise. next
local_max-local_min noise. This local max is smaller than the next
local max. For a parasitic diode, HSPICE ignores the smaller local max
biased voltage and does not output this voltage. To disable this feature, set
the noise detection level to 0.
Tstart, Tstop - used to define duration for bias check. Used only for
transient analysis.
307
Utility Buttons
The following buttons enable you to prepare to simulate according to your setup
parameters.
Add: Click this button when you have completed the input fields and
selection boxes to create a new bias check. If all parameters are successful,
it will be displayed in the BIASCHKs report table.
Change: Click this button to edit any selected bias check in the BIASCHKs
table.
Clear: Click to clear all of the input fields to create a new bias check.
Options: Click to open the HSPICE Options form (Figure 149 on page 309)
and locate the BIASCHK section of bias check options for you to
automatically add options to the violation check.
These options include:
BIASFILE
BIASINTERVAL
BIASNODE
BIASPARALLEL
BIAWARN
308
309
310
311
Length and Width: When your violation setup is to monitor a length or width
of an element, the UI is configured as shown in Figure 153 for a PMOS
circuit. Select the transistor circuit Type field value. Select l or w from the
Monitor selection box. The Terminal1, Terminal 2 input fields are removed
from the form.
312
313
Figure 155 Status and Violation Number columns with biaschk6 highlighted
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
315
The HSPICE Violation Details window shows detailed outputs of the selected
.BIASCHK command with in table format. This HSPICE Violation Details form
shows the biaschk1 violation details.
The form features the following UI controls. A list of steps follows.
316
Color: Select a highlight color, from the choices of Yellow, Red, Blue,
Orange, and Green. The selected color will be used to identify the device or
element in violation of design rules. In the example below, the selected color
is red.
Highlight button: Links the selected device in the .BIASCHKs Details table
to the schematic. (The schematic window must be open.) The highlighting
color is the one selected in the Color selection box. You can apply different
colors to various violations in the schematic by changing the .BIASCHK
command under study in the .BIASCHKs Details selection box.
Clear button: Removes all highlight violation devices from the schematic.
317
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
5. Click the Clear button on the HSPICE Violation Details form to remove the
violation from the schematic.
318
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
319
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 160 Results Display Window using the HSPICE Violation Details format
320
15
Distributed ModeMonte Carlo/Corner Analyses
15
Describes how to set up distributed jobs for these analyses in the HSPICE
integration to the Cadence Virtuoso Analog Design Environment.
This chapter describes how to generate the netlist files and scripts to submit
jobs on a distributed environment and provides a method to integrate a userdistributed environment into the HSPICE integration to ADE and enable
submission of distributed jobs.
The following topics are discussed in these sections:
321
The form opens by default to the Load Sharing Facility (LSF) Distributed
Mode.
When you click the following input fields, the Description text changes to usercustomized description text.
After you complete HSPICE Distributed Setup form, the Enable Distributed
Jobs feature becomes available on the Monte Carlo Setup form. (See HSPICE
Monte Carlo Distributed Simulation in this chapter for usage model after setting
up HSPICE distributed processing.)
Manually Setting Distributed Mode Environment Variables
Alternatively, you can use the following method to add HSPICE DP information
by setting HSPICE Distributed Mode partition variables. Add these HSPICE
environment variables to the HSPICE.cdsenv:
HSPICE.DM
HSPICE.DM
HSPICE.DM
HSPICE.DM
322
mode
custSubCmd
custChkCmd
custMoniCmd
string
string
string
string
"LSF"
""
""
""
nil
nil
nil
nil
These can be set locally through envSetVal() after loading the HSPICEADE interface. For example:
envSetVal("HSPICE.DM" "custSubCmd" 'string "bsub -P bnormal -M
`whoami`@synopsys.com -m e -b y -cwd -l
arch=glinux,os_version=\"WS4.0\",emt64=1")
Figure 162 Setup tab on the HSPICE Monte Carlo Analysis main window
323
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
The HSPICE netlist file window displays the difference for each HSPICE
Distributed Job Netlist file.
324
3. Click the Run menu or the Run button in the Outputs tab to submit the
parallel jobs and pop-up the HSPICE Distributed Task form (Figure 164) to
submit jobs.
4. Use the HSPICE Distributed Tasks form to submit HSPICE Monte Carlo
distributed task jobs; it also can show the existing task status.
The Submit button is used to submit the input or any of the selected
tasks listed under the Task Name column.
The Check Task button is used to check the task status of selected task
in the HSPICE DP Tasks report field.
The Task Log button is used to check the jobs status of selected task
in the HSPICE Distributed Tasks report field.
The Output Log button is used to show each jobs output log window,
(Figure 165 on page 326).
5. Click the Output Log button to display the HSPICE DP job Simulation log.
325
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 165 HSPICE DP Log Files of task# window showing Logfiles Dropdown with Job
Index selected
326
3. Automatically invokes the Check Task command for all running tasks when
displayed
Figure 165 shows an HSPICE Distributed Log Files of task6 (job index = 3, .lis
file). You can use these windows to view all jobs' simulation output files
including: .lis, .st0, and warnerr files. Use the HSPICE Distributed Job Select
form Figure 166 to switch between different jobs.
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
Figure 166 The HSPICE Distributed Log Files window overlaid with the HSPICE
Distributed Job Select form
327
2007, Cadence Design Systems, Inc. All rights reserved worldwide. Printed with permission.
328
2. Click the Netlist menu or the related button in the Outputs tab to do
netlisting and display the HSPICE DP netlist file (Fig. 9) generated for
parallel HSPICE Corner Analysis simulations (which are ready to be run
through submitting jobs).
329
330
A
A
Set up the SX-CDS-Link first and then modify the menu files.
Read the {sx_install_path} /packages/SX-CDS-Link/sxcds.pdf
documentation for instructions on how to set up WaveView for
ADE. Essentially, you need to put the following in your .cdsinit
file:
load("/path_to/sx_link.ile" "sandwork")
load("/path_to/sx_menu.il")
load("/path_to/sx_user.il")
331
Use the following procedure to update the HSPICE.menus file to enable the
display of the SX-ADE menu.
1. Locate and edit the file:
$CDSHOME/tools/dfII/local/menus/HSPICE.menus
2. On line 160 (containing "&Help"), add the following line:
"S&X-ADE"
3. On line 171 (containing "))", add the same line:
"S&X-ADE"
4. On line 464 (containing "("&Help"", add the following lines:
332
("S&X-ADE"
`(
("Setup Environment"
sxAASetup())
("Display Probes" ?disable (sevNoResults ',session) ?subMenu
(
("Transient" sxAADisplay(?session ',session ?type 1))
("DC"
sxAADisplay(?session ',session ?type 2))
("AC"
sxAADisplay(?session ',session ?type 3))
)
)
("Multi-Net Probe" ?disable (sevNoResults ',session)
?subMenu
(
("Transient" sxAADirect(?session ',session ?type 1))
("DC"
sxAADirect(?session ',session ?type 2))
("AC"
sxAADirect(?session ',session ?type 3))
)
)
("Instant Probe" ?disable (sevNoResults ',session)
?subMenu
(
("Transient" sxAAQuick(?session ',session ?type 1))
("DC"
sxAAQuick(?session ',session ?type 2))
("AC"
sxAAQuick(?session ',session ?type 3))
)
)
("Noise Analysis" ?disable (sevNoResults ',session)
?subMenu
(
("Equivalent Output Noise" sxAANoise(?session
',session ?type 1))
("Squared Output Noise"
sxAANoise(?session
',session ?type 2))
("Equivalent Input Noise"
sxAANoise(?session
',session ?type 3))
("Squared Input Noise"
sxAANoise(?session
',session ?type 4))
("Noise Figure"
sxAANoise(?session
',session ?type 5))
)
)
("Load Additional Files" ?subMenu
(
("Transient" sxAddAAFile(?session ',session ?type 1))
("DC"
sxAddAAFile(?session ',session ?type 2))
("AC"
sxAddAAFile(?session ',session ?type 3))
)
)
("Output List"
?disable (sevNoResults ',session)
333
?subMenu
(
("Transient" sxAAOutputList(?session ',session
?type 1))
("DC"
sxAAOutputList(?session ',session ?type 2))
("AC"
sxAAOutputList(?session ',session ?type 3))
)
)
("Clear Probes"
sxAAClearProbe(?session ',session))
("New SX Window" sxAAStart(?session ',session))
("Clear Highlight" sxCleanHilight())
))
5. Save and restart the session. The Environment Console should now display
a menu in HSPICE-ADE called SX-ADE.
334
Version 51
Version 61
Version 51
/*
*
Copyright (C) 1995
*
Cadence Design Systems, ICDG - Analog Division
*
All Rights Reserved.
*
*
*
* $Source: /cvsrep/group/artist/src/simui/simui.menus,v $
*
* $Author: amit $
* $Revision: 1.3.2.5 $
* $Date: 2005/04/04 08:51:13 $
* $State: Exp $
*
*/
/
***************************************************************
*******
*
* DESCRIPTION
* ----------*
* This file contains the menu definitions for the Analog Artist
* Simulation Environment. Menus appear on the banner of the
Main Window,
* on the banner of the Schematic Window, when in Analog Artist
mode,
* on the banner of the "Command Type-In" window, and on the side of
* the Main Window as a row of icons.
*
* Banner menus are defined in two steps. First, for each window
banner,
* the list of pulldowns is defined using commands
* sevSetMainWindowPulldownMenus, sevSetSchematicPulldownMenus,
and
* sevSetTypeInWindowPulldownMenus. Second, lists of menu items
for all
* pulldowns are defined using the command sevSetMenuItemLists.
The icon
* menu only needs its list of items defined using
sevSetMenuItemLists
* ("Fixedmenu").
*
* Menu definitions can be in one of two forms, the "simple form" or
* the "complete form". Even though the default menu definitions
given
335
* later in this file follow the complete form, the simple form is
* adequate for most user menu customizations.
*
* Simple Custom Menu Form
* ----------------------*
* The list of pulldowns is given simply as the list of the names
(strings)
* of the pulldowns. For example,
*
*
(sevSetMainWindowPulldownMenus '(
*
"Setup"
*
"Simulation"
*
"Results"
*
))
*
* The list of menu items is given as a list of item-lists, with each
* item-list composed of two strings, the name (text) of the
item and
* its callback. In the following example the given callbacks
may not
* be real functions. Also, the first line needs to be there as
given.
*
*
(sevSetMenuItemLists (lambda (session name) (case name
*
*
( "Setup"'(
*
( "Design ""setDesignCB()")
*
( "Analyses""setAnalysesCB()")
*
( "Variables""setVariablesCB()")
*
( "Environment""SetEnvironmentCB()")
*
))
*
*
( "Simulation"'(
*
( "Run
""runSimulationCB()")
*
( "Stop
""stopSimulationCB()")
*
))
*
*
( "Results"'(
*
( "Plot
""plotResultsCB()")
*
( "Print ""printResultsCB()")
*
( "Save
""saveResultsCB()")
*
))
*
)))
*
* In order to specify a slider (second-level) menu, the second
string
* of the menu item can be replaced by a list of name-callback
string
336
* pairs. For example, the last pulldown from the previous example
* could take the following form:
*
*
( "Results"'(
*
( "Plot
""plotResultsCB()")
*
( "Print"
*
(
*
( "Tran""printTranResultsCB()")
*
( "AC
""printACResultsCB()")
*
( "DC
""printDCResultsCB()")
*
))
*
( "Save
""saveResultsCB()")
*
))
*
*
* Complete Custom Menu Form
* ------------------------*
* The complete custom menu form allows users to specify the
following:
* For each pulldown, an optional menu-items pointer name when
different
* from the pulldown's name (text). For each menu item, an optional
* disabling (greying-out) condition, an optional flag on whether
the
* item brings up a form and an optional submenu (slider) argument.
* Also, callbacks and disabling conditions can be specified either
* as strings or as (function-call) lists. For examples, look at the
* actual default menu definitions below.
*
*
* Multi-Level Customization
* ------------------------*
* In addtion to using the command sevSetMenuItemLists which
(re)defines
* all menu item lists, users may use the command
sevAddMenuItemLists
* (same format as sevSetMenuItemLists) to add to the existing
item-list
* definitions. In this way, users may add private pulldowns on
top of site
* customizations, without having to repeat the site definitions.
*
*
* Direct-Plot Menu Customization
* -----------------------------*
* The special command sevDirectPlotMenu is provided for easier
337
"SX-ADE"
))
(sevSetTypeInWindowPulldownMenus
`(
("Window
"?items "Session_Encap")
))
(sevSetMenuItemLists
(lambda
(session name)
(case
name
("Session_Common"
`(
("Save State" ?callback (sevSaveState ',session) ?form t
?disable (sevNoEnvironment ',session))
("Load State" ?callback (sevLoadState ',session) ?form t
?disable (sevNoEnvironment ',session))
("Save Script" ?callback (snps_sevSaveOceanScript ',session)
?form t ?disable (sevNoEnvironment ',session))
("Options" ?callback (sevEditOptions ',session) ?form t)
))
("Session"
(cons
`("Schematic Window" ?callback (sevOpenSchematic ',session)
?form t)
(append
(sevMenuItems session "Session_Common")
`(
("What's New" ?callback (HSPICEDisplayNew) ?form t
?disable nil)
("Reset" ?callback (sevReset ',session))
("Quit" ?callback (sevQuit ',session))
))
))
("Session_Schematic"
(cons
`("Simulation Window" ?callback (sevCreateMainWindow
',session) ?form t)
(append
(sevMenuItems session "Session_Common")
`(
("Quit" ?callback (sevQuit ',session))
))
))
("Session_Encap"
`(
("Close" ?callback (hiCloseWindow (hiGetCurrentWindow)))
))
("Setup_Common"
339
`(
("Simulator/Directory/Host" ?callback (sevChooseSimulator
',session) ?form t)
("Model Libraries" ?callback (sevHSPICEEditModels ',session)
?form t ?disable (sevNoEnvironment ',session))
("Temperature" ?callback (sevChooseTemperature ',session)
?form t)
;("Model Path" ?callback (sevMpuTool ',session) ?form t
?disable (sevNoEnvironment ',session))
("Environment" ?callback
(sevChooseEnvironmentOptions ',session) ?form t ?disable
(sevNoEnvironment ',session))
("Simulation Files" ?callback
(_HSPICESetupSimulationFiles ',session) ?form t ?disable
(sevNoEnvironment ',session))
))
("Setup"
(cons
`("Design" ?callback (sevChooseDesign ',session) ?form t)
(sevMenuItems session "Setup_Common"))
)
("Setup_Schematic"
(append
`(
("Analyses" ?callback (sevEditSelectedAnas ',session) ?form
t)
("Variables" ?callback (sevEditSelectedVars ',session) ?form
t)
("Outputs" ?callback (sevEditSelectedOuts ',session) ?form
t)
("Select On Schematic"
?subMenu
(
("Outputs To Be Plotted" ?callback
(sevChangeOutsOnSchematic ',session 'plot))
("Outputs To Be Saved" ?callback
(sevChangeOutsOnSchematic ',session 'save))
))
("Save Options" ?callback (sevSaveOptions ',session) ?form t)
)
(sevMenuItems session "Setup_Common")
))
("Analyses"
`(
("Choose" ?callback (sevEditSelectedAnas
',session) ?form t ?disable (sevNoEnvironment ',session))
("Delete" ?callback (sevDeleteSelectedAnas ',session)
?disable (sevNoAnaSelections ',session))
("Enable" ?callback (sevActivateSelectedAnas ',session t)
340
341
)
)
)
("All" ?callback (setSimulatorOptions ',session "All") ?form t
)
)
)
("Netlist" ?disable (sevNoEnvironment ',session)
?subMenu
(
("Create" ?callback (sevNetlistFile ',session 'create))
("Display" ?callback (sevNetlistFile ',session 'display)
?form t)
("Recreate" ?callback (sevNetlistFile ',session 'recreate))
))
;("Command Type-In" ?callback (sevOpenEncap ',session)
?form t ?disable (sevNoEnvironment ',session))
("Output Log" ?callback (sevViewSimulatorOutput ',session)
?form t ?disable (or (sevNoEnvironment ',session) (sevNoOutputLog
',session)))
("Convergence Aids" ?disable (sevNoEnvironment ',session)
?subMenu t)
))
("Convergence Aids"
`(
;("Store/Restore" ?callback (sevConvergence ',session
'storeRestore) ?form t)
;("Transient Store/Restore" ?callback (sevConvergence
',session 'transientStoreRestore) ?form t)
("Node Set" ?callback (sevConvergence ',session 'nodeSet)
?form t)
("Initial Condition" ?callback (sevConvergence ',session
'initialCondition) ?form t)
;("Force Node" ?callback (sevConvergence ',session
'forceNode) ?form t)
))
("Results"
`(
; ("Select Signals To Be Plotted" ?callback
(sevChangeOutsOnSchematic ',session 'plot) ?disable
(sevNoEnvironment ',session))
("Plot Outputs" ?disable (or (sevNoResults ',session)
(sevNoPlottableOutputs ',session)) ?subMenu t)
("Direct Plot" ?disable (sevNoResults ',session) ?subMenu t)
("Plotting Assistant ..." ?disable (or (sevNoEnvironment
',session) (sevNoDesign ',session)) ?callback
(snps_hspa_display_form ',session))
("Print" ?disable (sevNoResults ',session) ?subMenu t)
("Annotate" ?disable (sevNoEnvironment ',session) ?subMenu t)
;("Circuit Conditions" ?callback (sevCircuitCond ',session)
HSPICE Integration to Cadence Virtuoso Analog Design Environment User Guide
E-2010.12
343
344
_HSPICEPlotEquivalentInputNoise noise)
;("Squared Output Noise" asiiPlotNoiseCB
noise)
("Squared Output Noise"
_HSPICEPlotSquaredOutputNoise
noise)
;("Squared Input Noise"
asiiPlotSquInputNoiseCB noise)
("Squared Input Noise"
_HSPICEPlotSquaredInputNoise
noise)
;("Noise Figure"
asiiPlotSpectreNoiseFigureCB noise)
("DC
"asiiPlotDCCBdc)
))
)
("Print"
`(
("DC Node Voltages" ?callback (sevPrintResults ',session
'dcNodeVoltages) ?disable (sevNoResults ',session 'dc_op))
("DC Operating Points" ?callback (sevPrintResults ',session
'dcOpPoints) ?disable (sevNoResults ',session 'dc_op))
;("Model Parameters" ?callback (sevPrintResults ',session
'modelParameters) ?disable (sevNoResults ',session 'dc_op))
("Transient Node Voltages" ?callback (sevPrintResults
',session 'tranNodeVoltages) ?disable (sevNoResults ',session
'tran))
("Transient Operating Points" ?callback (sevPrintResults
',session 'tranOpPoints) ?disable (sevNoResults ',session 'tran))
("S-Parameter" ?disable (not (xor (sevNoResults ',session 'sp )
(sevNoResults ',session 'lin )))
?subMenu
(
("1 port" ?callback (sevPrintResults
',session 'sparam1p) )
("2 port" ?callback (sevPrintResults ',session 'sparam2p) )
("3 port" ?callback (sevPrintResults ',session
'sparam3p) )
)
)
("Noise Parameters" ?callback (sevPrintResults ',session
'noiseParameters) ?disable (sevNoResults ',session 'noise))
("Noise Summary" ?callback (sevHSPICEPrintResults ',session
'noiseSummary) ?form t ?disable (sevNoResults ',session 'noise))
("DCMatch" ?callback (sevHSPICEPrintResults ',session
'dcmatch) ?disable (sevHSPICENoResults ',session 'dcmatch))
("ACMatch" ?callback (sevHSPICEPrintResults ',session
'acmatch) ?disable (sevHSPICENoResults ',session 'acmatch))
))
("Annotate"
`(
("DC Node Voltages" ?callback (sevAnnotateResults ',session
'dcNodeVoltages) ?disable (sevNoResults ',session 'dc_op))
("DC Operating Points" ?callback (sevAnnotateResults
345
346
347
)
("Noise Analysis" ?disable (sevNoResults ',session) ?subMenu
(
("Equivalent Output Noise" sxAANoise(?session ',session
?type 1))
("Squared Output Noise"
sxAANoise(?session ',session
?type 2))
("Equivalent Input Noise" sxAANoise(?session ',session
?type 3))
("Squared Input Noise"
sxAANoise(?session ',session
?type 4))
("Noise Figure"
sxAANoise(?session ',session
?type 5))
)
)
("Load Additional Files" ?subMenu
(
("Transient" sxAddAAFile(?session ',session ?type 1))
("DC"
sxAddAAFile(?session ',session ?type 2))
("AC"
sxAddAAFile(?session ',session ?type 3))
)
)
("Output List"
?disable (sevNoResults ',session) ?subMenu
(
("Transient" sxAAOutputList(?session ',session ?type 1))
("DC"
sxAAOutputList(?session ',session ?type 2))
("AC"
sxAAOutputList(?session ',session ?type 3))
)
)
("Clear Probes"
sxAAClearProbe(?session ',session))
("New SX Window" sxAAStart(?session ',session))
("Clear Highlight" sxCleanHilight())
))
)))
348
Version 61
/*
*
Copyright (C) 1995
*
Cadence Design Systems, ICDG - Analog Division
*
All Rights Reserved.
*
*
*
* $Source: /cvsrep/group/artist/src/simui/simui.menus,v $
*
* $Author: meghrajk $
* $Revision: 1.16 $
* $Date: 2006/05/10 13:30:12 $
* $State: Exp $
*
*/
/
***************************************************************
*******
*
* DESCRIPTION
* ----------*
* This file contains the menu definitions for the Analog Artist
* Simulation Environment. Menus appear on the banner of the
Main Window,
* on the banner of the Schematic Window, when in Analog Artist
mode,
* on the banner of the "Command Type-In" window, and on the side of
* the Main Window as a row of icons.
*
* Banner menus are defined in two steps. First, for each window
banner,
* the list of pulldowns is defined using commands
* sevSetMainWindowPulldownMenus, sevSetSchematicPulldownMenus,
and
* sevSetTypeInWindowPulldownMenus. Second, lists of menu items
for all
* pulldowns are defined using the command sevSetMenuItemLists.
The icon
* menu only needs its list of items defined using
sevSetMenuItemLists
* ("Fixedmenu").
*
* Menu definitions can be in one of two forms, the "simple form" or
* the "complete form". Even though the default menu definitions
given
349
* later in this file follow the complete form, the simple form is
* adequate for most user menu customizations.
*
* Simple Custom Menu Form
* ----------------------*
* The list of pulldowns is given simply as the list of the names
(strings)
* of the pulldowns. For example,
*
*
(sevSetMainWindowPulldownMenus '(
*
"Setup"
*
"Simulation"
*
"Results"
*
))
*
* The list of menu items is given as a list of item-lists, with each
* item-list composed of two strings, the name (text) of the
item and
* its callback. In the following example the given callbacks
may not
* be real functions. Also, the first line needs to be there as
given.
*
*
(sevSetMenuItemLists (lambda (session name) (case name
*
*
( "Setup"'(
*
( "Design ""setDesignCB()")
*
( "Analyses""setAnalysesCB()")
*
( "Variables""setVariablesCB()")
*
( "Environment""SetEnvironmentCB()")
*
))
*
*
( "Simulation"'(
*
( "Run
""runSimulationCB()")
*
( "Stop
""stopSimulationCB()")
*
))
*
*
( "Results"'(
*
( "Plot
""plotResultsCB()")
*
( "Print ""printResultsCB()")
*
( "Save
""saveResultsCB()")
*
))
*
)))
*
* In order to specify a slider (second-level) menu, the second
string
* of the menu item can be replaced by a list of name-callback
350
string
* pairs. For example, the last pulldown from the previous example
* could take the following form:
*
*
( "Results"'(
*
( "Plot
""plotResultsCB()")
*
( "Print"
*
(
*
( "Tran""printTranResultsCB()")
*
( "AC
""printACResultsCB()")
*
( "DC
""printDCResultsCB()")
*
))
*
( "Save
""saveResultsCB()")
*
))
*
*
* Complete Custom Menu Form
* ------------------------*
* The complete custom menu form allows users to specify the
following:
* For each pulldown, an optional menu-items pointer name when
different
* from the pulldown's name (text). For each menu item, an optional
* disabling (greying-out) condition, an optional flag on whether
the
* item brings up a form and an optional submenu (slider) argument.
* Also, callbacks and disabling conditions can be specified either
* as strings or as (function-call) lists. For examples, look at the
* actual default menu definitions below.
*
*
* Multi-Level Customization
* ------------------------*
* In addtion to using the command sevSetMenuItemLists which
(re)defines
* all menu item lists, users may use the command
sevAddMenuItemLists
* (same format as sevSetMenuItemLists) to add to the existing
item-list
* definitions. In this way, users may add private pulldowns on
top of site
* customizations, without having to repeat the site definitions.
*
*
* Direct-Plot Menu Customization
* -----------------------------*
351
("Sim-&Tools"?items "&Tools")
"SX-ADE"
))
(sevSetTypeInWindowPulldownMenus
`(
("&Window "?items "Session_Encap")
))
(sevSetMenuItemLists
(lambda
(session name)
(case
name
("Session_Common"
`(
("&Save State" ?callback (sevSaveState ',session) ?form t
?disable (sevNoEnvironment ',session))
("&Load State" ?callback (sevLoadState ',session) ?form t
?disable (sevNoEnvironment ',session))
("Save S&cript" ?callback
(snps_sevSaveOceanScript ',session) ?form t ?disable
(sevNoEnvironment ',session))
("&Options" ?callback (sevEditOptions ',session) ?form t)
))
("S&ession"
(cons
`("Schematic &Window" ?callback (sevOpenSchematic ',session)
?form t)
(append
(sevMenuItems session "Session_Common")
`(
("What's New" ?callback (HSPICEDisplayNew) ?form t
?disable nil)
("&Reset" ?callback (sevReset ',session))
("&Quit" ?callback (sevQuit ',session))
))
))
("Session_Schematic"
(cons
`("Sim&ulation Window" ?callback
(sevCreateMainWindow ',session) ?form t)
(append
(sevMenuItems session "Session_Common")
`(
("&Quit" ?callback (sevQuit ',session))
))
))
("Session_Encap"
`(
("&Close" ?callback (hiCloseWindow (hiGetCurrentWindow)))
353
))
("Setup_Common"
`(
("&Simulator/Directory/Host" ?callback (sevChooseSimulator
',session) ?form t)
("&Temperature" ?callback (sevChooseTemperature ',session)
?form t)
;("&Model Path" ?callback (sevMpuTool ',session) ?form t
?disable (sevNoEnvironment ',session))
("Model Libraries" ?callback (sevEditModels ',session)
?form t ?disable (sevNoEnvironment ',session))
("Simulation Files" ?callback (_HSPICESetupSimulationFiles
',session) ?form t ?disable (sevNoEnvironment ',session))
("&Environment" ?callback (sevChooseEnvironmentOptions
',session) ?form t ?disable (sevNoEnvironment ',session))
;("Stim&ulus" ?disable (sevNoEnvironment ',session)
;?subMenu
;(
;("Edit &Analog" ?callback (sevEditStimulus ',session
'analog) ?form t)
;("Edit &Digital" ?callback (sevEditStimulus ',session
'digital) ?form t ?disable (sevNonMixedSignal ',session))
;))
;("Simulation &Files" ?disable (sevNoEnvironment ',session)
;?subMenu
;(
;("Edit &Include File" ?callback
(sevEditSimulationFile ',session 'include) ?form t)
;("Edit &Model File" ?callback (sevEditSimulationFile
',session 'model) ?form t)
;))
))
("Set&up"
(cons
`("&Design" ?callback (sevChooseDesign ',session) ?form t)
(sevMenuItems session "Setup_Common"))
)
("Setup_Schematic"
(append
`(
("Anal&yses" ?callback (sevEditSelectedAnas ',session) ?form
t)
("&Variables" ?callback (sevEditSelectedVars ',session)
?form t)
("&Outputs" ?callback (sevEditSelectedOuts ',session) ?form
t)
("Select On S&chematic"
?subMenu
(
354
355
357
358
'(
("&Transient Signal"asiiPlotTranSignalCBtran)
("Transient Min&us DC"asiiPlotTranSignalNoDcCB (tran
dc_op))
("Transient &Sum"asiiPlotTranAddCBtran)
("Transient Diff&erence"asiiPlotTranSubtractCBtran)
("AC &Magnitude"asiiPlotACMagCBac)
("AC dB&10
"asiiPlotACDb10CBac)
("AC dB&20
"asiiPlotACDb20CBac)
("AC &Phase
"asiiPlotACPhaseCBac)
("&AC Magnitude & Phase"asiiPlotACMagAndPhaseCBac)
("AC &Gain & Phase"asiiPlotBodeAnalysisCBac)
;("Equivalent &Output Noise"asiiPlotEqOutputNoiseCBnoise)
("Equivalent &Output Noise
"_HSPICEPlotEquivalentOutputNoisenoise)
;("Equivalent &Input Noise"asiiPlotEqInputNoiseCBnoise)
("Equivalent &Input Noise"
_HSPICEPlotEquivalentInputNoisenoise)
;("S&quared Output Noise"asiiPlotNoiseCBnoise)
("S&quared Output Noise"_HSPICEPlotSquaredOutputNoise
noise)
;("Squared Input &Noise"asiiPlotSquInputNoiseCBnoise)
("Squared Input &Noise"_HSPICEPlotSquaredInputNoisenoise)
;("Noise &Figure"asiiPlotNoiseFigureCB(ac noise))
("&DC
"asiiPlotDCCBdc)
))
)
("Pr&int"
`(
("DC Node &Voltages" ?callback (sevPrintResults ',session
'dcNodeVoltages) ?disable (sevNoResults ',session 'dc_op))
("DC &Operating Points" ?callback (sevPrintResults ',session
'dcOpPoints) ?disable (sevNoResults ',session 'dc_op))
;("&Model Parameters" ?callback (sevPrintResults ',session
'modelParameters) ?disable (sevNoResults ',session 'dc_op))
("&Transient Node Voltages" ?callback (sevPrintResults
',session 'tranNodeVoltages) ?disable (sevNoResults ',session
'tran))
("Transient Operating &Points" ?callback (sevPrintResults
',session 'tranOpPoints) ?disable (sevNoResults ',session
'tran))
("&S-Parameter" ?disable (not (xor (sevNoResults ',session 'sp
) (sevNoResults ',session 'lin )))
?subMenu
(
("&1 port" ?callback (sevPrintResults ',session
'sparam1p) )
("&2 port" ?callback (sevPrintResults ',session
'sparam2p) )
359
'sparam3p)
)
)
\ ("&Noise Parameters" ?callback (sevPrintResults ',session
'noiseParameters) ?disable (sevNoResults ',session 'noise))
("Noise S&ummary" ?callback (sevHSPICEPrintResults ',session
'noiseSummary) ?form t ?disable (sevNoResults ',session 'noise))
("&DCMatch" ?callback (sevHSPICEPrintResults ',session
'dcmatch) ?disable (sevHSPICENoResults ',session 'dcmatch))
("&ACMatch" ?callback (sevHSPICEPrintResults ',session
'acmatch) ?disable (sevHSPICENoResults ',session 'acmatch))
))
("&Annotate"
`(
("DC Node &Voltages" ?callback (sevAnnotateResults ',session
'dcNodeVoltages) ?disable (sevNoResults ',session 'dc_op))
("DC &Operating Points" ?callback (sevAnnotateResults
',session 'dcOpPoints) ?disable (sevNoResults ',session 'dc_op))
;("&Model Parameters" ?callback (sevAnnotateResults ',session
'modelParameters) ?disable (sevNoResults ',session 'dc_op))
("&Transient Node Voltages" ?callback (sevAnnotateResults
',session 'tranNodeVoltages) ?form t ?disable (sevNoResults
',session 'tran))
("Transient Operating &Points" ?callback
(snpsAnnotateTransientOperatingPoints ',session) ?disable
(sevNoResults ',session 'tran) )
("Net &Names" ?callback (sevAnnotateResults ',session
'netNames))
("&Component Parameters" ?callback (sevAnnotateResults
',session 'componentParameters))
("Design &Defaults" ?callback (sevAnnotateResults ',session
'defaults))
))
("&Tools"
nconc(
`(("&Parametric Analysis" ?callback (sevParametricTool
',session) ?form t ?disable (sevNoEnvironment ',session)))
(if _axlIsAdeEDFMallowed() then ; 811559
`(("Corners" ?callback (sevCornersTool ',session) ?form
t ?disable (sevNoEnvironment ',session))
("Monte Carlo" ?callback (sevMonteCarloTool ',session)
?form t ?disable (sevNoEnvironment ',session))
("Optimization" ?callback (sevOptimizationTool ',session)
?form t ?disable (sevNoEnvironment ',session)))
else
nil
)
'(("separator")
("&Calculator" ?callback (sevOpenCalculator) ?form t)
360
361
name
("SX-ADE"
`(
("Setup Environment"
sxAASetup())
("Display Probes" ?disable (sevNoResults ',session) ?subMenu
(
("Transient" sxAADisplay(?session ',session ?type 1))
("DC"
sxAADisplay(?session ',session ?type 2))
("AC"
sxAADisplay(?session ',session ?type 3))
)
)
("Multi-Net Probe" ?disable (sevNoResults ',session) ?subMenu
(
("Transient" sxAADirect(?session ',session ?type 1))
("DC"
sxAADirect(?session ',session ?type 2))
("AC"
sxAADirect(?session ',session ?type 3))
)
)
("Instant Probe" ?disable (sevNoResults ',session) ?subMenu
(
("Transient" sxAAQuick(?session ',session ?type 1))
("DC"
sxAAQuick(?session ',session ?type 2))
("AC"
sxAAQuick(?session ',session ?type 3))
)
)
("Noise Analysis" ?disable (sevNoResults ',session) ?subMenu
(
("Equivalent Output Noise" sxAANoise(?session ',session
?type 1))
("Squared Output Noise"
sxAANoise(?session ',session
?type 2))
("Equivalent Input Noise" sxAANoise(?session ',session
?type 3))
("Squared Input Noise"
sxAANoise(?session ',session
?type 4))
("Noise Figure"
sxAANoise(?session ',session
?type 5))
)
)
("Load Additional Files" ?subMenu
(
("Transient" sxAddAAFile(?session ',session ?type 1))
("DC"
sxAddAAFile(?session ',session ?type 2))
("AC"
sxAddAAFile(?session ',session ?type 3))
)
)
("Output List"
?disable (sevNoResults ',session) ?subMenu
(
("Transient" sxAAOutputList(?session ',session ?type 1))
362
("DC"
("AC"
)
)
("Clear Probes"
sxAAClearProbe(?session ',session))
("New SX Window" sxAAStart(?session ',session))
("Clear Highlight" sxCleanHilight())
))
)))
363
364
B
B
365
Description: Sets up run information for one Monte Carlo analysis. You can
set up Monte Carlo information for DC, AC, or TRAN analysis.
Note: If startRun and numRun are needed, they must be input
together; otherwise, you can only input listRuns.
Argument
Description
s_analysis
?startRun
?numRun
?listRuns
Value Returned:
t
Monte Carlo setting succeeded.
nil
One or more errors; note details in the printed report.
Example:
snpsMonte('tran ?startRun 1 ?numRun 30)
=>t
snpsMonte('tran ?listRuns "1:5 10:15")
=>t
2. snpsMonteAddParam function:
Syntax:
snpsMonteAddParam(S_paramName s_distrFunc
+ t_absOrRelVal [t_sigma] [t_multipler])
=>t/nil
t_nomiVal
366
Description
S_paramName
s_distrFunc
t_nomiVal
t_absOrRelVal
t_multipler
Value Returned:
t The parameter setting succeeded with distribution function.
nil One or more errors; note details the printed report.
Example:
Adding the parameter deltaW to the different distribution functions for Monte
Carlo simulation runs:
snpsMonteAddParam('deltaW
snpsMonteAddParam('deltaW
snpsMonteAddParam('deltaW
snpsMonteAddParam('deltaW
snpsMonteAddParam('deltaW
3.
snpsMonteRun function:
Syntax:
snpsMonteRun(@rest arglist)
367
Note: Before using the function to run Monte Carlo simulation, the
snpsMonte() function must be used for setting the distribution
parameters for simulation.
Argument
Description
Same as run()
Value Returned
Same as run()
Examples:
Only run a tran analysis Monte Carlo simulation.
snpsMonteRun(tran)
4. snpsMonteGetMeas function:
Syntax
snpsMonteGetMeas([analysisList])
=>l_measResults/nil
368
Argument
Description
analysisList
Value Returned:
L_measResults The variables statistical value list.
nil One or more errors; note details the printed report.
Examples:
Loads TRAN, DC analysis Monte Carlo simulation measurement results and
returns variables and statistical value list.
snpsMonteGetMeas('tran 'dc)
Loads all Monte Carlo simulation measurement results and the statistical
values list.
snpsMonteGetMeas()
5. snpsMontePlotMeas function:
Syntax:
snpsMontePlotMeas(s_analysis ?yAxis
+ t_yAxis ?xAxis t_xAxis ?plotAs s_plotAs
[?doPlot g_doPlot][?plotMode s_plotMode])
=>o_waveform/nil
Description
s_analysis
?yAxis
369
Argument
Description
?xAxis
Description
?bins
?plotAs
scatter
histo
curve
?doPlot
?plotMode
Value Returned:
o_waveform New created waveform.
nil One or more errors; note details the printed report.
Examples:
This example uses the trise variable to create and plot a histogram waveform.
wave=snpsMontePlotMeas('tran ?xAxis "trise" ?plotAs 'histo
+ ?bins 5 ?doPlot nil)
plot wave
370
This example uses trise and m1@deltaw variables to create a scatter plot
and plot it in a newly created waveform window.
snpsMontePlotMeas('tran ?yAxis "trise" ?xAxis "m1@deltaw"
+ ?plotAs 'scatter ?plotMode "newWin")
371
372
C
C
1. snpsAnalysis
snpsAnalysis function:
Syntax:
snpsAnalysis(s_analysis ?parameter t_value [?parameter t_value
] )
=>t/nil
373
Description: Sets up run information for an HSPICE RF analysis. You can set
up HSPICE RF information for HB, HBAC, HBOSC, HBPHASE, SN,
SNAC, SNOSC, SNPHASE and PHASENOISE analyses.
Note:
Arguments for HB
Description
"fundTones"
"harmNums"
"interMaxOrder"
"ssTone"
"sweepStart"
"sweepType"
Type of the sweep, valid values are LIN, DEC, OCT and POI
"sweepStop"
"sweepStep"
"sweepVariable"
"sweepListPoints" Sweep point list, applied only when sweep type is "POI".
Arguments for
HBAC and SNAC
Description
"sweepStart"
"sweepType"
Type of the sweep, valid values are LIN, DEC, OCT, and POI.
"sweepStop"
"sweepStep"
"sweepListPoints" Sweep point list, applied only when sweep type is "POI".
374
Arguments for
HBOSC
Description
"fundTones"
"harmNums"
"interMaxOrder"
"probeNodeN1"
"probeNodeN2"
"probeNodeVP"
"ssTone"
"stpsNum"
"stpsMin"
"stpsMax"
"stability"
Valid values are: "0","1", "2", "-2", "-1". Refer to the HSPICE User
Guide: RF Analysis for their meanings.
"subharms"
"sweepStart"
"sweepType"
Type of the sweep, valid values are LIN, DEC, OCT, and POI.
"sweepStop"
"sweepStep"
"sweepVariable"
"sweepListPoints" Sweep point list, applied only when sweep type is "POI".
375
Arguments for
HBNOISE and
SNNOISE
Description
"fundTones"
"harmNums"
"interMaxOrder"
"ssTone"
"sweepStart"
"sweepType"
Type of the sweep, valid values are LIN, DEC, OCT and POI
"sweepStop"
"sweepStep"
"sweepVariable"
"sweepListPoints" Sweep point list, applied only when sweep type is "POI".
376
Arguments for SN
Description
"fundTones"
"harmNums"
"interMaxOrder"
"ssTone"
"sweepStart"
"sweepType"
Type of the sweep, valid values are LIN, DEC, OCT and POI
"sweepStop"
"sweepStep"
Arguments for SN
Description
"sweepVariable"
"sweepListPoints" Sweep point list, applied only when sweep type is "POI".
Arguments for
SNOSC
Description
"fundTones"
"harmNums"
"interMaxOrder"
"ssTone"
"sweepStart"
"sweepType"
Type of the sweep, valid values are LIN, DEC, OCT and POI
"sweepStop"
"sweepStep"
"sweepVariable"
"sweepListPoints" Sweep point list, applied only when sweep type is "POI".
Arguments for
PHASENOISE
Description
"type"
Valid values are "net", "dnet" and "instance", where the "dnet"
means the "differential net"
"sweepStart"
"sweepType"
Type of the sweep, valid values are LIN, DEC, OCT and POI
"sweepStop"
377
Arguments for
PHASENOISE
Description
"sweepStep"
"sweepVariable"
"sweepListPoints" Sweep point list, applied only when sweep type is "POI".
"listFreq"
"listCount"
"listFloor"
"listSource"
Valid values are "ON" and "OFF". "ON" means print the
contribution from each noise source and "OFF" disables this
operation
"probeNodeN1"
"probeNodeN2"
"inSrc"
Input source
"spurious"
Selects phase noise spur analysis. Valid values are "0" and "1". "0"
= No spurious analysis (default). "1" = Activates additional SPUR
source analysis
"method"
"carrierIndex"
t_value
Value Returned:
t
RF setting succeeded.
nil
One or more errors; note details in the printed report.
378
HB Examples
Example 1(for HB): Sets up the "HB" analysis with fundamental tone of 2G and
harmonic of 13.
snpsAnalysis('HB
Example 3: Sets up the "HB" analysis with fundamental tone of 1G, 1.1G, 1.2G,
1.3G, 1.4G, and their harmonics of 5, 6, 7, 8, 9, respectively.
"
snpsAnalysis('hb ? fundTones "1G,1.1G,1.2G,1.3G,1.4G" ?
harmNums "5,6,7,8,9")
Example 4: Sets up the "HB" analysis with fundamental tone of 1G, 1.1G, 1.2G,
1.3G, 1.4G, and their harmonics of 5, 6, 7, 8, 9, respectively. The maximum
inter-modulation order is 12.
snpsAnalysis('hb ?fundTones "1G,1.1G,1.2G,1.3G,1.4G" ?
harmNums "5,6,7,8,9" ?intermMaxOrder "12")
Example 5: Sets up the "HB" analysis with fundamental tone of 1G, 1.1G, 1.2G,
1.3G, 1.4G, and their harmonics of 5, 6, 7, 8, 9, respectively. The maximum
inter-modulation order is 12. The small signal tone is 5.
snpsAnalysis('hb ?fundTones
"1G,1.1G,1.2G,1.3G,1.4G" ?harmNums "5,6,7,8,9" ?
intermMaxOrder "12" ?ssTone "5" )
Example 6: Sets up the "HB" analysis with fundamental tone of 1G, 1.1G, 1.2G,
1.3G, 1.4G, and their harmonic of 5, 6, 7, 8, 9, respectively. The maximum
inter-modulation order is 12. The small signal tone is 5. The temperature sweep
is from 200k to 350k with the step of 10 and the sweep type is "LIN".
snpsAnalysis('hb ?fundTones "1G,1.1G,1.2G,1.3G,1.4G" ?
harmNums "5,6,7,8,9" ?intermMaxOrder "12" ?
ssTone "5" ?sweepVariable "Temperature" ?
sweepType "LIN" ?sweepStart "200k" ?
sweepStop "350k" ?sweepStep "10")
Example 7: This setup will result in an error message generated noting that
"fund" is an unknown parameter.
snpsAnalysis('HB
379
Value Returned
Same as run()
HBNOISE Examples
Example 1: Sets up the "HBNOISE" analysis with reference net of "/OUT". The
input source is "/V12". The sweep is from 1K to 1M with 10 steps of "LIN" type.
snpsAnalysis('HBNOISE ? nodeType "net" ?
probeNodeN1 "/OUT" ?inSrc "/V1" ?sweepType "LIN" ?
sweepStart "1k" ?sweepStop "1M" ?sweepStep "10")
Example 4: Sets up the "HBNOISE" analysis with reference net of "/OUT". The
input source is "/V1". The sweep is from 1K to 1M with 10 steps of "LIN" type.
The output frequency is small signal harmonic 3, 4, 5, plus the fundamental
frequency. The "listfreq" for noise is 2K and 4K. The "listsource" mean not to
print element source noise.
snpsAnalysis('HBNOISE ? nodeType "net" ?
probeNodeN1 "/OUT" ?inSrc "/V1" ?sweepType "LIN" ?
sweepStart "1k" ?sweepStop "1M" ?sweepStep "10" ?
outputFreqIdx "3 4 5 +1" ?listFreq "2K, 4k" ?listSource "off" )
380
Example 6:This setup will issue an error message that "node" is an unknown
parameter.
snpsAnalysis('HBNOISE ? node "net" ?probeNodeN1 "/OUT" ?
inSrc "/V1" ?sweepType "LIN" ?sweepStart "1k" ?
sweepStop "1M" ?sweepStep "10")
HBAC Examples
Example 1: Sets up "HBAC" analysis. The sweep is from 1k to 1M with 10
steps. The sweep type is "DEC".
snpsAnalysis('HBAC ?sweepType "DEC" ?sweepStart "1k" ?
sweepStop "1M" ?sweepStep "10" )
Example 2: Sets up "HBAC" analysis. The sweep type is "POI" and the sweep
is 1k and 1M with 2 points.
snpsAnalysis('HBAC
HBOSC Examples
Example 1: Sets up the "HBOSC" analysis with reference frequency of 1G and
harmonic of 4. The reference positive net is "/OUT" and negative one is
"/OUTN". The separate current source is 1.
snpsAnalysis('HBOSC
"/OUT" ?probeNodeN2
381
Example 5: This setup will issue an error message that vp is not set up.
snpsAnalysis('HBOSC ?fundTones "1G" ?harmNums "4" ?
probeNodeN1 "/OUT" ?probeNodeN2 "/OUTN" )
SN Examples
Example 1: Sets up the "SN" analysis under time domain. Its time resolution is
1e-6 and period is 2u.
snpsAnalysis('SN
Example 3: Sets up the "SN" analysis under time domain. Its time resolution is
1e-6 and period is 2u. The transient time is 3u.The maximum transient
initialization time is 6 clock cycles.
snpsAnalysis('SN ?timeReso "1e-6" ?
basePeriod "2u" ?trinit "3u" ?maxTrinitCycs "6" )
382
SNNOISE Examples
Example 1: Sets up the "SNNOISE" analysis with reference net of "/OUT". The
input source is "/V1". The sweep is from 1K to 1M with 10 steps of "Lin" type.
snpsAnalysis('SNNOISE ?nodeType "net" ?
probeNodeN1 "/OUT" ?inSrc "/V1" ?sweepType "LIN" ?sweepStart "1k"
?sweepStop "1M" ?
sweepStep "10")
Example 3: Sets up the "SNNOISE" analysis with reference net of "/OUT". The
input source is "/V1". The sweep is from 1K to 1M with 10 steps of "Lin" type.
The output frequency is small-signal harmonic 3, 4, 5, plus the fundamental
383
frequency. The "listfreq" for noise is 2K and 4K. The "listsource" means not to
print element source noise.
snpsAnalysis('SNNOISE ? nodeType "net" ?
probeNodeN1 "/OUT" ?inSrc "/V1" ?sweepType "LIN" ?
sweepStart "1k" ?sweepStop "1M" ?sweepStep "10" ?
outputFreqIdx "3 4 5 +1" ?listFreq "2K, 4k" ?listSource "off"
SNOSC Examples
Example 1: Sets up the "SNOSC" analysis under time domain. Its time
resolution is 1e-6 and period is 2u.
snpsAnalysis('SNOSC
"/OUT")
Example 3: Sets up the "SNOSC" analysis under time domain. Its time
resolution is 1e-6 and period is 2u. The transient time is 3u.The maximum
transient initialization time is 4 clock cycles.
snpsAnalysis('SNOSC ?timeReso "1e-6" ?basePeriod "2u" ?oscnode
"/OUT" ?trinit "3u" ?maxTrinitCycs "4" )
384
SNAC Examples
Example 1: Sets up "SNAC" analysis. The sweep is from 1k to 1M with 10
steps. The sweep type is "DEC"
snpsAnalysis('SNAC ?sweepType "DEC" ?sweepStart "1k" ?sweepStop
"1M" ?sweepStep "10" )
Example 2: Sets up "SNAC" analysis. The sweep type is "POI" and the sweep
is 1k and 1M with 2 points.
snpsAnalysis('SNAC
PHASENOISE Examples
Example 1: Sets up the "PHASENOISE" analysis with the node of "/OUT" as
phase noise calculation reference. The sweep is from 1k to 1M and with steps
of 10 and type of "LIN". The method is 1 and carrier index is 2 for phase noise
calculation. The listfreq is "all" and listcount is 5 for element phase noise
frequencies number. The minimum dumped noise value is -200 dBc/Hz. The
listsource is "ON" which means to dump all the element sources. The spurious
is 1, which activates the additional "SPUR' analysis.
snpsAnalysis('PHASENOISE ?nodeType "net" ?
probeNodeN1 "/OUT" ?sweepType "LIN" ?sweepStart "1k" ?
sweepStop "1M" ?sweepStep "10" ?method "1" ?
carrierIndex "2" ?listFreq "all" ?listCount "5" ?
listFloor "-200" ?listSource "on" ?spurious "1" )
385
2 snpsProbe
snpsProbe function:
Syntax:
snpsProbe(s_outputType ?parameter t_value [?parameter t_value
] )
=>t/nil
Description
Sets up the information to save the signal data for HSPICERF analysis. It can
save the result for current, voltage, power and hertz information, as well as the
noise for plotting. It supports HB and SN-related large signal and small signal
analyses. The function works similar to the "save()" function from ADE.
Note:
Arguments
Description
S_outputType"
386
'i = current
'v = voltage
'p = power
'h = hertz
'PHASENOISE = phase noise plotting
'HBNOISE = noise plotting when doing HB-related analysis
'SNNOISE = noise plotting when doing SN-related analysis
Arguments
Description
parameter
The parameter name that is set up with the saved signal. According
to s_outputType value, they are as follows:
For i
For v
For 'p
387
Arguments
Description
For h (hertz)
"anatype": Analysis type. Valid values are hb, sn, snac, snfd
"indexTones": Tone index
"plotEnable": Plotted or not
For PHASENOISE
t_value
Value Returned:
t
RF setting succeeded.
nil
One or more errors; note details in the printed report.
Examples for i, v, p, hertz, SNNOISE, HBNOISE, PHASENOISE
Example 1: For i Sets up the "/I0/CLK" current output of "HBTRAN" analysis
type.
snpsProbe('i ?nodeType "terminal" ?
anatype "HBTRAN" ?signal "/V1/PLUS" )
Example 2: Sets up the "/ V1/PLUS " current output of "hb" analysis type.
snpsProbe('i
PLUS" )
Example 3: For vSets up the "/OUT" voltage output of "HB" analysis type .
snpsProbe('v
388
Example 7: For 'p Sets up the "/V1" power output of "hb" analysis.
snpsProbe('p
?anatype "hb" )
Example 11: Sets up the "INOISE" output in default unit for "SNNOISE"
analysis.
snpsProbe('SNNOISE
Example 12: Sets up the "INOISE" output in "db" unit for "SNNOISE" analysis.
snpsProbe('SNNOISE
Example 13: Sets up the "NF" output in "dbm" unit for "HBNOISE" analysis
snpsProbe('HBNOISE
389
Example 14: For 'PHASENOISESets up the "/V3" phase noise output for "hb"
analysis.
snpsProbe('PHASENOISE ?nodeType "instance" ?
anatype "hb" ?signal "/V3" )
snpsProbe('PHASENOISE
?noiseTerm "JITTER" )
390
D
D
391
Description
Value Returned:
t
The model file addition succeeded.
nil
One or more errors; note details in the printed report.
Example:
snpsCorAddModelFile("/remote/user/bjt90nm.lib") =>t
2. snpsCorAddDesignVar function:
Syntax:
snpsCorAddDesignVar (t_varName) => t/nil
Description
t_varName
Value Returned:
t
nil
Example:
Adding "vdd" to the HSPICE Corner Analysis simulation run:
snpsCorAddDesignVar("vdd")
3.
snpsCorAddTemperature function:
Syntax:
snpsCorAddTemperature() => t/nil
392
Description
none
Value Returned:
t
nil
4. snpsCorDeleteModelFile function:
Syntax
snpsCorDeleteModelFile (t_modelFileName) => t/nil
Description
Value Returned:
t
nil
Example:
snpsCorDeleteModelFile("/remote/user/bjt90nm.lib") => t
5. snpsCorDeleteAllModelFiles function:
Syntax:
snpsCorDeleteAllModelFiles () => t/nil
Description: Deletes all model files that have been added with
snpsCorAddModelFile.
Argument
Description
none
393
Value Returned:
t
nil
6. snpsCorDeleteDesignVar function:
Syntax:
snpsCorDeleteDesignVar (t_varName) => t/nil
Description
t_varName
Value Returned:
t
nil
Example:
Deleting "vdd" from the HSPICE Corner Analysis simulation run:
snpsCorDeleteDesignVar("vdd")
7.
snpsCorDeleteDesignVars function:
Syntax:
snpsCorDeleteDesignVars () => t/nil
Description
none
Value Returned:
t
nil
Example:
none
8. snpsCorDeleteTemperature function:
394
Syntax
snpsCorDeleteTemperature () => t/nil
Description: Deletes the environment variable for the temperature that had
been added with snpsCorAddTemperature
Argument
Description
none
Value Returned:
t
nil
Example:
none
9. snpsCorAddCorner function:
Syntax:
snpsCorAddCorner (t_cornerName ?vars l_vars ?models l_models
?temp f_temp) => t/nil
Description
t_cornerName
l_vars
Design variables
l_models
Model files
f_temp
Temperature
Value Returned:
t
nil
395
Description
t_fromCorner
Corner to be copied
t_toCorner
Value Returned:
t
nil
Example:
Copies "cor1" to "cor2"; "cor2" has the same setting as "cor1":
snpsCorCopyCorner("cor1" "cor2")
396
Description: Sets the design variable to the given value for the specified
corner.
Arguments
Description
t_cornerName
t_varName
t_value
Value Returned:
t
nil
Example:
none
Description: Sets the section name in the model file to be used for the
specified corner.
Note: The model file parameter uses the model file name (not the
include path); therefore, do not use the model file which has
the same model file name, but different path.
Argument
Description
t_cornerName
Section name.
Value Returned:
t
nil
397
Description: Sets the value of the temperature to be used for the specified
corner.
Argument
Description
t_cornerName
t_value
Temperature value.
Value Returned:
t
nil
Example:
none
Description
none
Value Returned:
t
nil
Example:
none
398
Description
none
Value Returned:
t
nil
Example:
none
Description
t_measName
Value Returned:
t
nil
Example:
none
399
Description
t_measName
g_value
Value Returned:
t
nil
400
Argument
Description
t_measName
Argument
Description
t_goalType
t_lowValue
t_value
Value Returned:
t
nil
401
Description
t_measFile
Value Returned:
t
nil
Example:
none
Description
none
Value Returned:
t
nil
Example:
none
402
Note: The measurement variable must have been added into the
Corner Analysis environment with the snpsCorAddMeas
function.
Arguments
Description
none
Value Returned:
t
nil
Example:
none
Description
Values Returned:
Same as those returned by Ocean run()
Example: Run all analysis settings specified in the HSPICE Corner Analysis:
snpsCorRun()
403
Description
t_output
s_type
s_cornerSelect
l_corners
t_plotMode
Specify the window mode of plotting window, it's valid value are:
"Append" (Default): Adds new waveform to the existing waveform
window
"Replace": Replaces existing window's waveform
"New Subwin": Opens a new subwindow in the existing
waveform window and appends new waveform
"New Win": Opens a new waveform window in the existing
waveform window and appends new waveform
Value Returned:
t
nil
Example: Plot the "cor1" and "cor3" analyses "/out" signal waveforms:
snpsCorPlotOutputs("/out" ?type 'net ?analysis "TRAN"
?cornerSelect 'select ?corners '("cor1" "cor3"))
404
Description: Prints out the measurement variables all corners results and
summarize information using a table format.
Argument
Description
none
Value Returned:
t
The printing of the measurement variables corners results
and summarization succeeded.
nil One or more errors; note details the printed report.
Example:
none
Description
t_measName
t_plotMode
405
Value Returned:
t
nil
Example:
none
406
E
OCEAN API Functions for HSPICE Optimization
Analysis
407
Description
parameter
t_value
Value Returned:
t
nil
Examples
Example1: Sets up the optimize model. Its name is "opt" with the parameter
"relin" of "1e-5", "close" of "10"and "relout" of "1e-5"
"snpsOptimizeModel(?name "opt" ?relin "1e-5" ?close "10"
?itropt "40" ?relout "1e-5")
408
Example 2: Sets up the optimize model. Its name is "optmod" with the
parameter "relin" of "1e-4". It is a "PASSFAIL" timing analysis.
"snpsOptimizeModel (?name "optmod" ?relin "1e-4" ?method
"passfail")
Example 3: Sets up the optimize model. Its name is "optmod" with the
parameter "relin" of "1e-4". It is a "BISECTION" timing analysis.
"snpsOptimizeModel (?name "optmod" ?relin "1e-4" ?method
"bisection")
Example 4: Sets up the optimize model. Its name is "optmod" with the
parameter "relin" of "1e-4". The "dynacc" is "1".
"snpsOptimizeModel (?name "optmod" ?relin "1e-4" ?dynacc "1")
Example 5: Sets up the optimize model. Its name is "optmod" with the
parameter "relin" of "1e-4". It is a "BISECTION" timing analysis.
"snpsOptimizeModel (?name "optmod" ?relin "1e-4" ?method
"bisection")
Example 7: Error reveals that the valid value for "dynacc" is "0" and "1".
"snpsOptimizeModel (?name "optmod" ?relin "1e-4"
?dynacc "-1")
2. snpsOptimizeVariable function:
Syntax:
snpsAnalysisVariable( ?parameter t_value [?parameter t_value
] )
=>t/nil
409
Description
parameter
t_value
Value Returned:
t
nil
Examples
Example 1: Sets up the optimization parameter named "wml" with the
parameter "upper" of "100u", "low" of "20u"and "initial" of "60u" . It belongs to
the "opt1" group.
"snpsOptimizeVariable(?name "wml" ?upper "100u" ?low "20u"
?initial "60u" ?optGroup "opt1")
3.
410
snpsOptimizeAnalysis function:
Syntax:
snpsAnalysisAnalysis( ?parameter t_value [?parameter t_value
] )
=>t/nil
Description
parameter
t_value
Value Returned:
t
nil
Example: Sets up the optimization analysis. The analysis is transient with the
"opt1" optimize group. It uses the measures of "area_min", "delayf", "delayr"
and "tot_power" and the optimization model named "opt".
"snpsOptimizeAnalysis(?name "TRAN" ?optimize "opt1"
?results "area_min,delayf,delayr,tot_power" ?model "opt")
4. snpsOptimizeDisplay function:
Syntax
411
snpsOptimizeDisplay ( [session] )
=> t/nil
Description
session
Value Returned:
t
The Optimization display setting succeeded. A new terminal
window with optimization results is shown.
nil One or more errors; note details the printed report.
412
F
OCEAN API Functions for the HSPICE Measure
Utility
413
Description
s_name
parameter
414
Argument
Description
Value Returned:
t
The model file addition succeeded.
nil
One or more errors; note details in the printed report.
Examples
Example 1. Sets up the trig/targ measure. The analysis is transient. The
measure name is time1. The trig and targ specifications are all v(net06)
val=0.1 RISE=2.
snpsMeasureTrigTarg('time1 ?analysis "TRAN" 'trig ?type "V"
?var "/net6" ?val "0.1" ?event "RISE" ?eventValue "2" 'targ
?type "V" + ?var "/net6" ?val "0.1" ?event "RISE" ?eventValue
"2")
2. snpsMeasureFunc function:
Syntax:
snpsMeasureFunc('s_name ?parameter t_value [?parameter
t_value ...])
Description
s_name
415
Argument
Description
parameter
parameter
t_value
416
Value Returned:
t
nil
Example1:
Sets up the 'AVG measure. The analysis is transient. The measure name is
"val2". The measurement is taken when V(/net6) is from 0 to 50m:
snpsMeasureFunc('val2 ?analysis "TRAN" ?func "AVG" ?var "/
net6" ?from "0" ?to "50m" )
Example 2:
Sets up the 'deriv measure. The analysis is transient. The measure name is
"val2". The derivation takes place for V(/net6) at 50m.
snpsMeasureFunc('val2 ?analysis "TRAN" ?func "deriv" ?var "/
net6" ?type "V" 'deriv ?at "50m" )
Example 3:
Sets up the 'deriv measure. The analysis is transient. The measure name is
"val2". The derivation takes place for V(/net6) when V(/net5) = 2
under and FALL = last.
snpsMeasureFunc('val2 ?analysis "TRAN" ?func "deriv" ?var "/
net6" ?type "V" 'deriv ?type "V" ?var "/net5" ?event "FALL"
?eventValue "yes" ?td "3" ?val "2" )
Example 4:
Sets up the 'AVG power measurement. The analysis is transient. The measure
name is "val2".
snpsMeasureFunc('val2 ?analysis "TRAN" ?func "AVG" ?var
"power" )
417
3.
snpsMeasureFind function:
Syntax:
snpsMeasureFind('s_name ?parameter t_value [?parameter
t_value ...])
Description
s_name
parameter
418
Argument
Description
Value Returned:
t
nil
Examples
Example 1:
Sets up the 'When measurement. The analysis is transient. The measure name
is "time2". The measurement is taken when V(/net6) = 0.98
snpsMeasureFind('time2 ?analysis "TRAN" 'find ?type "V" ?var
"/net6" ?val "0.98" )
Example 2:
Sets up the 'Find/At measure. The analysis is transient. The measure name is
"time2". The measure finds V(/net6) at time of "1e-2" .
snpsMeasureFind('time2 ?analysis "TRAN" 'find
?type1 "V" ?var1 "/net6" ?at "1e-1" )
Example 3:
Sets up the 'Find/At measure. The analysis is transient. The measure name is
"time2". The measure finds V(/net5) when V(/net6) = "0.98".
snpsMeasureFind('time2 ?analysis "TRAN" 'find ?type1 "V"
?var1 "/net5" ?type "V" ?var "0.98" )
419
Example 4:
This setup will report the error that ?var, ?var1 and ?at can not appear in
the same measure statement.
snpsMeasureFind('time2 ?analysis "TRAN" 'find ?type1 "V"
?var1 "/net5" ?type "V" ?var "0.98" ?at "1")
4. snpsmeasEqua function:
Syntax
snpsMeasureEqua('s_name ?parameter t_value [?parameter
t_value ...])
Description
s_name
parameter The parameter of the equation measurement in the HSPICE Measure Utility.
1. goal Goal in the measure; optional
2. minval Minimum value in the measure; optional
3. weight Weight in the measure; optional
4. analysis Analysis in the measure. Valid values: "TRAN," "DC," AC"
5. precision MEASDGT option. Valid values are [1, ... , 10]
6. param Keyword preceding equation in expression form
t_value
420
Value Returned:
t
nil
5. snpsMeasureError function:
Syntax:
snpsMeasureError's_name ?parameter t_value [?parameter
t_value ...])
Description
s_name
parameter
421
Argument
Description
Value Returned:
t
nil
6. snpsMeasureSpec function:
Syntax:
snpsMeasureSpec('s_name ?parameter t_value [?parameter
t_value ...])
Description:
Sets up Special measure information.
422
Note:
Argument
Description
s_name
parameter
423
Argument
Description
11. binsiz Index for the noise calculation; optional. Refer to .MEASURE FFT in
the HSPICE Reference Manual: Commands and Control Options for more
information. Valid for functions "SNR", "SNDR", and "ENOB"
12. maxfreq Upper limit of frequency to carry out the measure; optional
Value Returned:
t
nil
424
G
G
425
Syntax:
snpsMosra(t_simMode t_relTotalTime
[?mosraArgument1 t_mosraArgumentValue1]
[?mosraArgumentN t_mosraArgumentValueN]
?temperature temperature ?designVariables
l_designVariables) => t/nil
Description
t_simMode
?mosraArgument1
t_temperature
426
Argument
Description
l_designVariables
The design variables name and value pair list. For example:
'(("vdd" "0.1")("vcc" "0.2"))
Value Returned:
t
The MOSRA Command addition succeeded.
nil One or more errors; note details in the printed report.
Example
The two commands below add two MOSRA commands; the first MOSRA
command simulates as alter 0, the second MOSRA command simulates as
alter 1.
snpsMosra("0" "315360000" ?relStepTime "31536000"
+ ?degradationtime "31536000")=>t
snpsMosra("1" "315360000" ?relStepTime "31536000"
+ ?degradationtime "31536000" ?temperature "100"
+ ?designVariables '(("vdd" "1.8")))=>t
2. snpsMosraModel function:
Syntax:
snpsMosraModel(t_modelName ?hciParams l_hciParams
+ ?nbtiParams l_nbtiParams)=> t/nil
Description
Reliability model parameter for HCI. See the HSPICE User Guide:
Simulation and Analysis for sections on HCI parameters.
l_nbtiParams
Reliability model parameter for NBTI. See the HSPICE User Guide:
Simulation and Analysisfor sections on NBTI parameters.
Value Returned:
t
427
3.
snpsCustomMosraModel function:
Syntax:
snpsCustomMosraModel(t_shareLibPath t_modelFile) => t/nil
Description: Adds Custom MOSRA shared library path and Model File into
HSPICE Reliability Analysis simulation environment.
Argument
Description
t_shareLibPath
t_modeFile
4. snpsMosraAppendModel function
Syntax
snpsMosraAppendmodel(s_mosraModelType
t_modelName t_genModelName s_modelKeyword) => t/nil
428
Description: This command appends the parameter values from the source
model card (SrcModel) to the destination model card (DestModel). All
arguments are required.
Argument
Description
s_mosraModelType
t_modelName
t_genModelName
Destination model name, e.g., the original model in the model library.
s_modelKeyword
Value Returned:
t
5. snpsMosraRun function:
Syntax:
snpsMosraRun(s_mosraModelType @rest run_args)
Description
Value Returned:
The same as for run().
429
Example
Runs all settings for a MOSRA analysis simulation using a Custom MOSRA
Model setup.
snpsMosraRun('cusmdl)
6. snpsMosraOutputsPlot function:
Syntax:
snpsMosraOutputsPlot(t_output ?type s_type
+ ?wavFile t_wavFile ?degradationPeriod
+ t_degradationPeriod ?plotMode t_plotMode)=> t/nil
Description
t_output
s_type
t_wavFile
Outputs psf file; combines ".tr" file string with alter index and
simMode. For example: ".tr0" means alter 0, pre-stress simulation psf
output file plot; ".tr1@ra" means alter1, post-stress simulation psf
output file plot.
430
Value Returned:
t
Example 2: Plot the net "/i1" signal, degradation time "1e+07" waveform of
alter 1 pre-stress simulation output.
snpsMosraOutputsPlot("/i1" ?type 'net ?waveFile ".tr1@ra"
+ "1e+07")
Example 3: Plot the net "/i1" signal, all degradation time waveforms of alter 1
pre-stress simulation output.
snpsMosraOutputsPlot("/i1" ?type 'net ?waveFile ".tr1@ra"
+ "All")
7. snpsMosraMeasPlot function:
Syntax:
snpsMosraMeasPlot(t_measResultsFile
t_measVariable ?plotMode t_plotMode) =>t/nil
Description
t_measResultsFile
Measure results file that combines ".mt" string with alter index and
simMode. For example: ".mt0" means alter 0, pre-stress simulation
measure results file plot; ".mt1@ra" means alter1, post-stress
simulation measure result file plot.
t_measVariable
431
Argument
Description
t_plotMode
Value Returned:
t
8. snpsMosraMeasPrint function:
Syntax:
snpsMosraMeasPrint(t_measResultsFile) => t/nil
Description
t_measResultsFile
Measure results file that combines ".mt" string with alter index and
simMode. For example: ".mt0" means alter 0, pre-stress simulation
measure results file plot; ".mt1@ra" means alter1, post-stress
simulation measure result file plot.
Value Returned:
t
432
9. snpsMosraRadegPlot function:
snpsMosraRadegPlot(t_radegFile t_mosElemName
+ t_mosElemParamName
+ ?plotMode t_plotMode) =>t/nil
Description
t_radegFile
t_mosElemName
Value Returned:
t
433
Example
Plot MOS element "m2" parameter "delvth0" of alter 1 radeg file.
snpsMosraRadegPlot("input.radeg1" "m2" "delvth0" "New Win")
Description
t_radegFile
Value Returned:
t
434
Index
A
AC analysis 119
ACMatch analysis 131
AGAUSS keyword 202
Analog Options forms 165
analogLib 78
analyses
AC 119
ACMatch 131
DC 117
DCMatch 129
FFT 122, 124
Linear Network Parameter 127
Loop Stability 132
Noise 122
Operating Point (OP) 121
Pole/Zero 146
Transient 110
transient noise 113
analyses forms setup, tutorial 24, 26
analysis
Linear Network Parameter 124
annotation, Results menu 189
AUNIF keyword 202
automatic output log 103
B
.BIASCHK analysis 303
C
calculator 153
cdsenv file 94
cdsinit SKILL file 94
CIW window 93
clock source, random jitter 92
command line option 103
command line option control 104
component reference library 78
D
data outputs 151
DC analysis 117
DCMatch analysis 129
DEBUG keyword 122
default simulator, HSPICE 92
definition files 102
demo directory 17
demostate, tutorial 40
design variable 148
design, configuring, tutorial 23
DFT calculation 122, 124
Direct Plot, Results menu 185
distributed jobs
corner analysis 328
environment setup 321
Monte Carlo 323
DM 321, 323, 328
downloading tutorial demo directory 17
E
editing design variables 148
editing session options 97
environment console 93, 94
environment console setup 93
Environment Options
command line options 104
435
Index
F
multithreading 105
output log files 104, 168
print netlist comments 103
stop view list 103
subsckt, top level 105
switch view list 103
environment options
form 103
setup, tutorial 24
error-warning file 104, 168
F
FFT analysis 122, 124
form sections commonly shared across functions in
Plotting Assistant 178
G
GAUSS
keyword 202
H
HSPICE
components added/converted 80
Whats New window 97
HSPICE 64-bit simulation 104
HSPICE components ,added or converted 80
HSPICE integration
Verilopg-A 106
HSPICE measures 257
HSPICE Plotting Assistant 174
HSPICE Plotting Assitant, tutorial 33
HSPICE, as default simulator 92
HSPICE.menus file 331
I
include path 102
incremental netlisting, netlisting, incremental 167
initial conditions 169
initial conditions, setting 170
installtion README 17
K
keywords
DEBUG 122
L
library
conversion messages 79
library conversion 75
library update utility 76
licenses required 17
LIMIT keyword 202
LIN analyses 127
LIN analysis 124
.listing file *.lis 104, 168
loading tutorial files 17
log files 104, 168
LSTB analysis 132
M
Measurement Utility 257
mismatch analyses 129, 131
Model Library Setup form 99
model setup, tutorial 23
Monte Carlo analysis
configuring 200
invoking 200
multiprocessing 202
OCEAN scripting 210
results, measuring, plotting 205
session saving, loading 210
setting options 203
tutorial example 47
Monte Carlo distributed jobs 323
MOSFETmodels reliability 271
MOSRA analysis 271
multi-dimensional sweeps 110
multi-port/two-port noise 127
multiprocessing 202
multithreading 105
N
J
jitter
random, with clock source 92
436
Index
O
O
OCEAN script API
Monte Carlo 365
RF 373, 391, 407, 413, 425
OCEAN scripts 96
OP analysis 121
optimization analysis 249
options menu, HSPICE-specific controls 162
Other options field 165
output log files 104, 168
output log, automatic 103
outputs 151
outputs menu, tutorial 32
P
parametric analysis form 110
PDKs, 3rd party 78
PLL_Demo 17
plot outputs, Results menu 184
Plotting Assistant
common form section shared across functions
178
plotting assistant form, tutorial 33
plotting assitant usage, tutorial 40
plotting expressions 153
plotting preferences 196
Pole/Zero analysis 146
post-processing 173
print comments (netlist) checkbox 103
print, Results menu 188
print/plot options 196
printing/plotting results 173
PSF output, 64-bit simulation 104
PZ analysis 146
Q
quick-start tutorial 17
R
README, installation 17
reliability analysis 271
restoring states 95
Results menu
Annotate 189
Direct Plot 185
Plot Outputs 184
Print 188
printing/plotting options 196
save, select, delete 194
Results menu overview 173
results, printing/plotting 173
RF analyses
invoking 235
OCEAN script API 365, 373, 391, 407, 413,
425
OCEAN scripting 233, 247, 254
results analysis 246
running and post-processing 245
selecting and configuring 236
session, saving and loading 233, 247, 254
setting options 239
tutorial example 61
using the Outputs tab 243
S
Save Options form 156
save options window, tutorial 32
saving or restoring a list of outputs 159
saving, selecting,deleting results 194
saving/plotting outputs 151
Schematic Editor 93
session menu 95
setting outputs form 151
setup for saving/plotting nets and terminals 152
setup menu
design 98
Model Libraries 99
Simulation Files 102
Simulator/Directory/Host 99
simulation files setup, tutorial 24
simulation menu overview 161
437
Index
T
T
table of outputs 153
Tool Filter, HSPICE simulator 92
top level, subckt 105
transient analysis 110
transient noise analysis 113
tutorial 17
tutorial demo directory 17
438
U
UNIF keyword 202
update script 78
update utility, library 76
updating HSPICE.menus file to add SX menu 331
V
variables, design 148
vector files 102
vector files, tutorial 24
Verilog-A 106
Verilog-A support 106
Verilog-A,example, tutorial 44
version 5.1 93
version 6.1 93
violation check 303
W
warning-error file 104, 168