Difference between revisions of "Simulation Tutorial"

From Vlsiwiki
Jump to: navigation, search
(→‎Setting Up Manual Stimulus)
m (→‎Adding Model Library Files)
 
(90 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
There are many ways to simulate from Virtuoso. Which one is best depends on your PDK and your final goals.
 +
 +
== Setting up analogLib ==
 +
 +
Before you start virtuoso, make sure to add the analogLib to your libraries. Do this by editing cds.lib in your home directory (or in the project directory). You should see something like this:
 +
 +
DEFINE analogLib $CDSHOME/tools/dfII/etc/cdslib/artist/analogLib
 +
DEFINE US_8ths  $CDSHOME/tools/dfII/etc/cdslib/sheets/US_8ths
 +
DEFINE basic    $CDSHOME/tools/dfII/etc/cdslib/basic
 +
DEFINE cdsDefTechLib $CDSHOME/tools/dfII/etc/cdsDefTechLib
 +
DEFINE NCSU_TechLib_FreePDK45  $PDK_DIR/ncsu_basekit/lib/NCSU_TechLib_FreePDK45
 +
DEFINE NCSU_Devices_FreePDK45  $PDK_DIR/ncsu_basekit/lib/NCSU_Devices_FreePDK45
 +
DEFINE cmpe_222_lib /mada/users/rsankara/cmpe_222_lib
 +
 +
 +
In case your cds.lib does NOT have analogLib or one of the above libraries, then add it as follows:
 +
DEFINE  analogLib $CDSHOME/tools/dfII/etc/cdslib/artist/analogLib
 +
 +
Save the file and start virtuoso. You should see a new library in the library manager.
 +
 
== Select Analog Environment ==
 
== Select Analog Environment ==
−
With the schematic file open, Ultrasim can be invoked from within Virtuoso.  
+
With the schematic file open, hspice can be invoked from within Virtuoso.  
−
:Select <b>Launch &rarr; Simulation &rarr; Spectre</b>. <br>  
+
:Select <b>Launch &rarr; ADE L</b>. <br>
−
This creates a new menu item called "Spectre" next to "NCSU".
+
  
−
== Select Simulator (<nowiki>Spectre</nowiki>) ==
+
== Select Simulator (<nowiki>hspiceD</nowiki>) ==
−
Virtuoso Analog Design Environment supports various simulators such is hSpice, Spectre, and Ultrasim. Spectre was previously chosen. Now, run     
+
Virtuoso Analog Design Environment supports various simulators such as hspiceD, Spectre, and Ultrasim. hspiceD was previously chosen. Now, run     
−
:Select<b> <nowiki> Spectre &rarr; Initialize. </nowiki> </b>  
+
:Select<b> <nowiki> Setup &rarr; Simulator/Directory/Host. </nowiki> </b>  
−
A follow up window will pop up giving your simulator options. Press ok.
+
A follow up window will pop up giving your simulator options. Select '''hspiceD'''. Also specify a run directory. Press ok.
  
−
[[Image:ultrasim_setup3.jpg|400px]]
 
  
  
 
<b>Simulation Run Directory</b> indicates where your simulation files will be stored.
 
<b>Simulation Run Directory</b> indicates where your simulation files will be stored.
−
The generated netlist file will be stored within in a file called "netlist". All of the other options are stored in this directory as well.
+
The generated netlist file will be stored within in a file called "netlist".  
−
 
+
All of the other options necessary for running the simulation are stored in this directory as well in the form of separate files like netlistHeader, netlistFooter.
−
== Setting Up Manual Stimulus ==
+
When you run the simulation, all the options are put together by the simulator.
−
If you did not add voltage sources to drive the inputs and outputs, you can edit a stimulus file directly by choosing:
+
This is useful for storing separate simulation setups for different parts of your design.
−
Ultrasim &rarr; Stimulus &rarr; Edit Stimulus File
+
−
This will open a file in vi where you can add something like this:
+
−
+
−
// Spectre Source Statements
+
−
vdd (vdd! 0) vsource dc=1.8
+
−
gnd (gnd! 0) vsource dc=0
+
−
vin (A 0) vsource type=pulse val0=0 val1=1 period=100n delay=10n rise=0.1n fall=0.1n width=50n
+
  
  
−
To save in vi, press escape and then type ":wq". These options are saved in a file in your simulation directory called spectre.inp
 
  
 
== Choosing Analysis Type and Length ==
 
== Choosing Analysis Type and Length ==
 
From the Analog Environment window  
 
From the Analog Environment window  
−
:Select <b>Spectre &rarr; Stimulus &rarr; Edit Analysis/Options File </b>  
+
:Select <b>Analysis &rarr; Choose </b>  
  
−
This will bring up a smaller window where you should uncomment the line shown here and change it with an appropriate simulation length:
+
Make sure to select tran and specify an appropriate stop time and time step (example 1ns).
 +
The start time is typically 0.
 +
Be sure to choose a stop time that is greater than the period of the input signal.
 +
Hspice supports the SI prefixes so 500n would be 500 nano seconds.
  
−
// Analyses
 
−
// dc1 dc oppoint=logfile homotopy=all
 
−
tran1 tran stop=300n errpreset=moderate
 
  
−
These options are saved in a file in your simulation directory called spectre.sim.
+
== Adding Model Library Files ==
 +
The next step is to add the spice data for the simulator.  
 +
:Select <b> Setup &rarr; Model Library Setup </b>.
 +
We will be adding the data for the NMOS and PMOS transistor.
  
 +
 +
If you are using FreePDK as your Process Design Kit,
 +
 +
Click on <i>Add File</i> and add these files:
 +
 +
$PDK_DIR/ncsu_basekit/models/hspice/tran_models/models_nom/NMOS_VTL.inc
 +
$PDK_DIR/ncsu_basekit/models/hspice/tran_models/models_nom/PMOS_VTL.inc
 +
 +
 +
Select <b> OK </b> when finished.
 +
 +
These paths will be automatically written as ".include" into a file called input.ckt
 +
 +
 +
If you are using SCMOS(TSMC_02d) as your Process Design Kit,
 +
 +
Click on <i>Add File</i> and add these files instead:
 +
 +
/mada/software/techfiles/ncsu/models/hspice/public/tsmc18dP.m
 +
/mada/software/techfiles/ncsu/models/hspice/public/tsmc18dN.m
 +
 +
 +
Select <b> OK </b> when finished.
 +
 +
 +
 +
Perform this '''Adding Model Library Files''' step only for the process you are supposed to use. Adding multiple process files may lead to simulation problems.
 +
 +
== Running Simulation ==
 +
 +
To run a simulation, first select the type of analysis in <b>Analysis &rarr; Choose...</b> For a transient, specify the stop time (e.g. 1n).
 +
 +
It is easier to not add voltage sources to the inputs directly and instead make stimulus in a file. You can edit a stimulus file directly and include it in your simulation.
 +
Create a text file named ''stimulus.sp'' in your simulation directory and create something like this in it:
 
   
 
   
−
Be sure to choose a stop time that is greater than the period of the input signal.
+
// Stimulus Statements Hspice format
−
Spectre supports the SI prefixes so 500u would be 500 micro seconds.
+
.global VDD! vdd! GND! gnd!
 +
vdd vdd! 0 vhigh
 +
.param vhigh=1200mV
 +
.param vlow=0
 +
.param tdelay=0n
 +
.param trise=5p * pick a reasonable value
 +
.param tfall=5p * pick a reasonable value
 +
.param tpulse = 10n
 +
v_A  A  0 pat (vhigh vlow tdelay trise tfall tpulse  b01010101  rb=1 r=1)
 +
C_Z Z    0 100fF * pick a reasonable value
  
−
== Adding Model Library Files ==
+
The above statements define the global signals, define the '''vdd''' voltage using a parametrized statement and also some timing values.
−
The next step is to add the spice data for the simulator.  
+
These statements may also be written in the netlist file itself if you wish to have it all in a single file.
−
:Select <b> Setup &rarr; Model Libraries </b>.
+
The '''.param''' statements above are used for parameterizing simulation variables. This way, if you wish to change some values for simulation, you only need to change it in the '''.param''' statement and it will take effect throughout.
−
We will be adding the data for the Nmos and Pmos transistor using the TSMC 180nm process.
+
The '''v_A''' is a voltage source statement producing a bit stream of 01010101 as stimulus with rise,fall and pulse width times defined in the '''.param''' statements.
 +
Save the file you have now created as stimulus.sp and store it in your simulation directory.
  
−
[[Image:ultrasim_setup5.jpg|400px]]
+
To specify the stimulus, select <b>Setup &rarr; Simulation Files..</b>. and provide the path to your ''stimulus.sp''.  
  
  
 +
For more information on Hspice commands you can look at the manual:
  
−
:Click on <i>browse</i> and go to: <b>/mada/software/techfiles/NCSU_CDK_1.5.1/models/hspice/public</b><br>
+
/projects/cmpe122/software/I-2013.12-1/hspice/docs_help/hspice_sa.pdf
−
Make sure you click the .. first all the way till you see mada
+
  
−
:Select files
+
== Ouput Window ==
−
:/mada/software/techfiles/ncsu/models/hspice/public/tsmc18dN.m
+
Before Running, select <b>Output &rarr; Save All...</b> to save all schematic data. (Note, this might not be best on big designs!) Or, you can select <b>Outputs &rarr; To Plot &rarr; Select on Schematic</b> and then click on all of the items on the schematic.
−
:/mada/software/techfiles/ncsu/models/hspice/public/tsmc18dP.m
+
−
:/mada/software/techfiles/ncsu/models/ground.sp
+
  
−
Be sure to click on add after selecting each file.  Select <b> OK </b> when finished.
+
Then,
 +
:Select <b> Simulation  &rarr; Run</b>
 +
This will generate the netlist file, run the simulation, and save the results for the waveform viewer. You should re-run this every time you change your schematic.
  
−
== Selecting Outputs to be Plotted ==
+
You can also select <b>Simulation &rarr; Create Raw</b> to create the raw simulation file for debugging. You should be able to see your include stimulus, netlist, and a bunch of other stuff.
−
From the Ultrasim menu
+
−
:Select <b>Outputs To Be Plotted &rarr; Select on Schematic </b>  
+
−
Now refer back to your schematic (or layout) and click on various parts to add it to the output section of the Analog Design Environment Window (for example, the output pin Z) in your schematic that you want to be plotted. Repeat this as necessary for all nets you want to see (for example, the input pin IN).
+
  
−
== Running Simulation and Ouput Window ==
+
If this pops up a window that says it failed, fix the previous options. You need to debug this by looking at the output of the simulator in si.log (which is the output of running the simulator, if the simulator failed to run) or si.out (which is the actual simulator output if it ran successfully, but simulation may have failed). This will show you if it even got to the point of running the simulator.  
−
:Select <b> Ultrasim  &rarr; Netlist/Simulate </b>
+
−
This will generate the netlist file, run the simulation, and feed the results to the waveform viewer.
+
  
 +
 +
If it succeeded, you can select <b> Tools &rarr; Waveform  </b>. When you do this, you get three windows:
 +
 +
[[Image:waveform_graph.jpg|400px]]
 +
[[Image:waveform_browser.jpg|400px]]
 +
[[Image:waveform_results.jpg|400px]]
 +
 +
Select the "File Open" icon and then find the appropriate "raw" result file in the browser. This should open the data in the browser. Double click on the transient simulation directory and you should see signal names that correspond to your design. Double click on "A" to add it. Change the upper right option to "Append" and double click on "Z" to add it as well. If you don't change the option, it will replace the A waveform with Z. If there are problems with vdd! and gnd! you can debug that here.
 +
 +
You should get something that looks similar to this in the graph window:
  
 
[[Image:output_waveform.jpg|400px]]
 
[[Image:output_waveform.jpg|400px]]
 +
 +
Note that your signals should always rise to full vdd (1.2V) and down to gnd (0V) or else something is wrong with your logic. This is CMOS so everything is "rail to rail". It is likely an unconnected supply voltage or floating body.
  
 
== Waveform - Zooming and Trace ==
 
== Waveform - Zooming and Trace ==
Line 89: Line 153:
 
:Click on one of the waveforms in the window. This places a small label on the waveform. You can drag this marker anywhere on the waveform.
 
:Click on one of the waveforms in the window. This places a small label on the waveform. You can drag this marker anywhere on the waveform.
  
−
== Power/Energy Analysis with UltraSim ==
+
=== Separate Windows ===
 +
:Sometimes the window will get too cluttered. You can plot each signal in a separate window by clicking the 4th icon in the toolbar from the left to put it in "Strip Mode".
  
−
To enable power analysis in Ultrasim
+
=== Reloading ===
−
:1) go to Simulation->Options->Analog
+
:If you make a change and resimulation, you can simply click <b> File &rarr; Reload </b>
−
:2) In the "Advanced Checks" section, check the button near "Power analysis" and click on '''Setting'''
+
−
:3) In the window that opens up
+
−
:      3.1) Enter '''*''' for the "subckt name"
+
−
:      3.2) Select '''max''' in the "Output Sorting" section
+
−
:      3.3) Click on the power and enabled button
+
−
:      3.4) Click on '''Add''' at the top
+
−
:      3.4) Click '''OK''' to close the window
+
−
:4) Click '''OK''' to close the "Simulator Options" window
+
−
:5) Simulate as usual (Simualte->Netlist and Run)
+
−
:6) Look for a file called "input.pa", most likely under  /cse/grads/'''USERNAME'''/cadence/simulation/comb_adder/UltraSim/schematic/psf/input.pa
+
  
−
:The file will list Max,Avg and RMS power for each pin in your design, and the time in which the maximal power consumption occurred.
+
=== Exporting Tip ===
 +
:If you intend to export the plot, it would be wise to change the background color to something other than black. In addition you can change the width of the lines by right clicking on the line and selecting properties.
  
−
Energy is simply the RMS power multiplied by time
+
== Power/Energy Analysis ==
−
<p>
+
 
−
[[Image:Power.jpg|400px]]
+
To enable power analysis in hspice, add this statement to your stimulus file:
 +
 
 +
.measure tran toplvl_avg_power avg  power from=0ns to=100ns
 +
.measure tran toplvl_avg_energ integ power from=0ns to=100ns
 +
.measure tran toplvl_avg_current avg I(VDD) from=0ns to=100ns
 +
 
 +
For more information on the .measure syntax, please refer hspice user guide at:
 +
/projects/cmpe122/software/synopsys/I-2013.12-1/hspice/docs_help/hspice_sa.pdf
 +
 
 +
You can then plot the power in the waveform viewer. It will be shown with all the other signals. In order to find the average power, you select :pwr and click on the calculator option instead of the plot option. In the calculator window, select "average" in the special functions. Then select the "Evaluate" button. (It is on the right of the "Clip" option and to the left of the Table and Append options). This will give you the average power in Watts.
 +
 
 +
[[Image:spectrePower.jpg|400px]]
 +
 
 +
 
 +
To enable power analysis in hspice
 +
:1) go to Simulation->Analog Options->All
 +
This will open a dialog box listing various Hspice analysis commands and fields for their values.
 +
Refer to Hspice documentation before using any of these options
  
 
== Documentation ==
 
== Documentation ==
Line 114: Line 187:
 
Finally, for more help...
 
Finally, for more help...
  
−
 
+
:Open file: /projects/cmpe122/software/synopsys/I-2013.12-1/hspice/docs_help/hspice_sa.pdf
−
:Open file:///home/cadence/MMSIM61/doc/UltraSim_User/UltraSim_UserTOC.html in your web browser on firedance.
+

Latest revision as of 22:37, 24 December 2020

There are many ways to simulate from Virtuoso. Which one is best depends on your PDK and your final goals.

Setting up analogLib

Before you start virtuoso, make sure to add the analogLib to your libraries. Do this by editing cds.lib in your home directory (or in the project directory). You should see something like this: 

DEFINE analogLib $CDSHOME/tools/dfII/etc/cdslib/artist/analogLib
DEFINE US_8ths   $CDSHOME/tools/dfII/etc/cdslib/sheets/US_8ths
DEFINE basic     $CDSHOME/tools/dfII/etc/cdslib/basic
DEFINE cdsDefTechLib $CDSHOME/tools/dfII/etc/cdsDefTechLib
DEFINE NCSU_TechLib_FreePDK45  $PDK_DIR/ncsu_basekit/lib/NCSU_TechLib_FreePDK45
DEFINE NCSU_Devices_FreePDK45  $PDK_DIR/ncsu_basekit/lib/NCSU_Devices_FreePDK45
DEFINE cmpe_222_lib /mada/users/rsankara/cmpe_222_lib


In case your cds.lib does NOT have analogLib or one of the above libraries, then add it as follows: 

DEFINE   analogLib $CDSHOME/tools/dfII/etc/cdslib/artist/analogLib

Save the file and start virtuoso. You should see a new library in the library manager.

Select Analog Environment

With the schematic file open, hspice can be invoked from within Virtuoso.

Select Launch → ADE L.

Select Simulator (hspiceD)

Virtuoso Analog Design Environment supports various simulators such as hspiceD, Spectre, and Ultrasim. hspiceD was previously chosen. Now, run

Select Setup → Simulator/Directory/Host.

A follow up window will pop up giving your simulator options. Select hspiceD. Also specify a run directory. Press ok.


Simulation Run Directory indicates where your simulation files will be stored. The generated netlist file will be stored within in a file called "netlist". All of the other options necessary for running the simulation are stored in this directory as well in the form of separate files like netlistHeader, netlistFooter. When you run the simulation, all the options are put together by the simulator. This is useful for storing separate simulation setups for different parts of your design.


Choosing Analysis Type and Length

From the Analog Environment window

Select Analysis → Choose

Make sure to select tran and specify an appropriate stop time and time step (example 1ns). The start time is typically 0. Be sure to choose a stop time that is greater than the period of the input signal. Hspice supports the SI prefixes so 500n would be 500 nano seconds.


Adding Model Library Files

The next step is to add the spice data for the simulator.

Select Setup → Model Library Setup .

We will be adding the data for the NMOS and PMOS transistor.


If you are using FreePDK as your Process Design Kit,

Click on Add File and add these files: 

$PDK_DIR/ncsu_basekit/models/hspice/tran_models/models_nom/NMOS_VTL.inc
$PDK_DIR/ncsu_basekit/models/hspice/tran_models/models_nom/PMOS_VTL.inc


Select OK when finished.

These paths will be automatically written as ".include" into a file called input.ckt


If you are using SCMOS(TSMC_02d) as your Process Design Kit,

Click on Add File and add these files instead: 

/mada/software/techfiles/ncsu/models/hspice/public/tsmc18dP.m
/mada/software/techfiles/ncsu/models/hspice/public/tsmc18dN.m


Select OK when finished.


Perform this Adding Model Library Files step only for the process you are supposed to use. Adding multiple process files may lead to simulation problems.

Running Simulation

To run a simulation, first select the type of analysis in Analysis → Choose... For a transient, specify the stop time (e.g. 1n).

It is easier to not add voltage sources to the inputs directly and instead make stimulus in a file. You can edit a stimulus file directly and include it in your simulation. Create a text file named stimulus.sp in your simulation directory and create something like this in it: 

// Stimulus Statements Hspice format 
.global VDD! vdd! GND! gnd!
vdd vdd! 0 vhigh
.param vhigh=1200mV
.param vlow=0
.param tdelay=0n
.param trise=5p * pick a reasonable value
.param tfall=5p * pick a reasonable value
.param tpulse = 10n
v_A  A  0 pat (vhigh vlow tdelay trise tfall tpulse  b01010101  rb=1 r=1)
C_Z Z     0 100fF * pick a reasonable value

The above statements define the global signals, define the vdd voltage using a parametrized statement and also some timing values. These statements may also be written in the netlist file itself if you wish to have it all in a single file. The .param statements above are used for parameterizing simulation variables. This way, if you wish to change some values for simulation, you only need to change it in the .param statement and it will take effect throughout. The v_A is a voltage source statement producing a bit stream of 01010101 as stimulus with rise,fall and pulse width times defined in the .param statements. Save the file you have now created as stimulus.sp and store it in your simulation directory.

To specify the stimulus, select Setup → Simulation Files... and provide the path to your stimulus.sp.


For more information on Hspice commands you can look at the manual: 

/projects/cmpe122/software/I-2013.12-1/hspice/docs_help/hspice_sa.pdf

Ouput Window

Before Running, select Output → Save All... to save all schematic data. (Note, this might not be best on big designs!) Or, you can select Outputs → To Plot → Select on Schematic and then click on all of the items on the schematic.

Then,

Select Simulation → Run

This will generate the netlist file, run the simulation, and save the results for the waveform viewer. You should re-run this every time you change your schematic.

You can also select Simulation → Create Raw to create the raw simulation file for debugging. You should be able to see your include stimulus, netlist, and a bunch of other stuff.

If this pops up a window that says it failed, fix the previous options. You need to debug this by looking at the output of the simulator in si.log (which is the output of running the simulator, if the simulator failed to run) or si.out (which is the actual simulator output if it ran successfully, but simulation may have failed). This will show you if it even got to the point of running the simulator.


If it succeeded, you can select Tools → Waveform . When you do this, you get three windows:

Waveform graph.jpg Waveform browser.jpg Waveform results.jpg

Select the "File Open" icon and then find the appropriate "raw" result file in the browser. This should open the data in the browser. Double click on the transient simulation directory and you should see signal names that correspond to your design. Double click on "A" to add it. Change the upper right option to "Append" and double click on "Z" to add it as well. If you don't change the option, it will replace the A waveform with Z. If there are problems with vdd! and gnd! you can debug that here.

You should get something that looks similar to this in the graph window:

Output waveform.jpg

Note that your signals should always rise to full vdd (1.2V) and down to gnd (0V) or else something is wrong with your logic. This is CMOS so everything is "rail to rail". It is likely an unconnected supply voltage or floating body.

Waveform - Zooming and Trace

With the waveform window open, you can zoom in and find exact values.

Zoom

Select Zoom → X Zoom .
Now click and drag in the waveform window to select the x-range you want to zoom to.

Tracing

Select Marker → Place → Trace Marker

Zoom waveform.jpg

Click on one of the waveforms in the window. This places a small label on the waveform. You can drag this marker anywhere on the waveform.

Separate Windows

Sometimes the window will get too cluttered. You can plot each signal in a separate window by clicking the 4th icon in the toolbar from the left to put it in "Strip Mode".

Reloading

If you make a change and resimulation, you can simply click File → Reload

Exporting Tip

If you intend to export the plot, it would be wise to change the background color to something other than black. In addition you can change the width of the lines by right clicking on the line and selecting properties.

Power/Energy Analysis

To enable power analysis in hspice, add this statement to your stimulus file: 

.measure tran toplvl_avg_power avg   power from=0ns to=100ns
.measure tran toplvl_avg_energ integ power from=0ns to=100ns
.measure tran toplvl_avg_current avg I(VDD) from=0ns to=100ns

For more information on the .measure syntax, please refer hspice user guide at: 

/projects/cmpe122/software/synopsys/I-2013.12-1/hspice/docs_help/hspice_sa.pdf

You can then plot the power in the waveform viewer. It will be shown with all the other signals. In order to find the average power, you select :pwr and click on the calculator option instead of the plot option. In the calculator window, select "average" in the special functions. Then select the "Evaluate" button. (It is on the right of the "Clip" option and to the left of the Table and Append options). This will give you the average power in Watts.

SpectrePower.jpg


To enable power analysis in hspice

1) go to Simulation->Analog Options->All

This will open a dialog box listing various Hspice analysis commands and fields for their values. Refer to Hspice documentation before using any of these options

Documentation

Finally, for more help...

Open file: /projects/cmpe122/software/synopsys/I-2013.12-1/hspice/docs_help/hspice_sa.pdf
Retrieved from "https://vlsiwiki.soe.ucsc.edu/index.php?title=Simulation_Tutorial&oldid=5431"