Library Requirements to Support Analysis in the EE Flow

dehisceforkΗλεκτρονική - Συσκευές

2 Νοε 2013 (πριν από 3 χρόνια και 11 μήνες)

93 εμφανίσεις











Library Requirements to Support Analysis
in the EE Flow













Modified Date:
11/2/2013

Document Revision: 2.0













Rev. 2.0

Page:
2

of
27


Date Modified:
11/02/13


Table of Contents

1

Introduction

................................
................................
................................
......................

4

1.1

Supported Types of Analysis

................................
................................
.....................

4

1.2

Methodology

................................
................................
................................
...............

4

2

Requirements for Analysis

................................
................................
.............................

4

2.1

Analog/Mixed Signal Simulation

................................
................................
................

4

2.1.1

Recommended Methodology
................................
................................
..............

5

2.2

Signal Integrity Analysis

................................
................................
.............................

5

2.2.1

Required Properties

................................
................................
............................

5

2.2.2

Model Mapping in HyperLynx

................................
................................
.............

6

2.3

Power Integrity Analysis
................................
................................
.............................

6

2.4

RF Analysis

................................
................................
................................
................

7

2.4.1

Required Properties

................................
................................
............................

7

2.4.2

Additional RF Simulation Requirements
................................
.............................

7

2.4.3

RF Library and Configuration Files

................................
................................
.....

7

2.5

Thermal Simulation

................................
................................
................................
....

7

2.6

Mechanical Integration

................................
................................
...............................

7

3

Required Properties for VHDL/AMS Simulation

................................
...........................

8

3.1

Required Symbol or Component Properties
................................
..............................

8

3.2

VHDL/AMS in Sub
-
circuits

................................
................................
.........................

8

3.3

VHDL
-
AMS Standard Passive Models

................................
................................
......

8

4

Required Component Database

Properties (DMS)

................................
....................

10

4.1

SPICE Simulation Properties in the DMS/DxDataBook Database

.........................

10

4.2

VHDL
-
AMS Properties

................................
................................
.............................

10

4.3

Signal Integrity Properties

................................
................................
........................

11

5

Simulation Database Files

................................
................................
............................

11

5.1

SimDB structure

................................
................................
................................
.......

11

5.2

Set Simulation Data Dialog

................................
................................
......................

12

5.3

Using SimDB to Map Property Names

................................
................................
....

14

5.4

Specifying SimDB Files

................................
................................
............................

14

5.5

Applying SimDB Files to a Schematic

................................
................................
.....

14

6

Simulation Model Repository

................................
................................
.......................

15

6.1

Simulation Model Repository Location

................................
................................
....

15

6.2

Model Files

................................
................................
................................
...............

16

6.3

Managing the Simulation Model Repository

................................
............................

16

7

Library and Project Considerations
................................
................................
.............

16

7.1

Integrated Expedition Flow and Netlist Flow

................................
...........................

16

7.2

Properties for Simulation
................................
................................
..........................

16

7.3

Library Structure

................................
................................
................................
.......

18

7.4

Adding Ground References

................................
................................
.....................

18

7.5

Using the Expedition Central Library Structure

................................
.......................

18

7.6

SPICE Library Searches

................................
................................
..........................

19

7.6.1

Mentor
-
supplied SPICE Simulation Models

................................
.....................

19

7.7

VHDL Libraries

................................
................................
................................
.........

19

7.7.1

VHDL Source Files

................................
................................
...........................

19

7.7.2

Compiled VHDL
-
AMS Libraries

................................
................................
........

20

7.8

Importing Simulation Symbols

................................
................................
.................

21

7.9

Switching Between Libraries in Expedition Integrated Flow

................................
...

22

8

Additional Considerations

................................
................................
............................

22

8.1

Configuration Files

................................
................................
................................
...

22

8.2

SystemVision Considerations

................................
................................
..................

22

Rev. 2.0

Page:
3

of
27


Date Modified:
11/02/13


8.3

Editing Simulation Properties

................................
................................
...................

23

8.4

Pin Properties

................................
................................
................................
...........

23

9

Summary

................................
................................
................................
.........................

23

9.1

Steps Required to Support Simulation

................................
................................
....

23

10

Appendix

................................
................................
................................
.........................

24

10.1

Required Properties for SPICE Simulation

................................
..............................

24

10.1.1

Resistors

................................
................................
................................
...........

25

10.1.2

Capacitors

................................
................................
................................
.........

25

10.1.3

Inductors
................................
................................
................................
............

25

10.1.4

Diodes

................................
................................
................................
...............

25

10.1.5

Bi
-
Polar Transistors

................................
................................
..........................

26

10.1.6

JFET Transistors
................................
................................
...............................

26

10.1.7

MOSFET Transistors

................................
................................
........................

26

10.1.8

Ideal Transformers

................................
................................
............................

26

10.1.9

Subcircuits
................................
................................
................................
.........

26

10.2

Terms and definitions:

................................
................................
..............................

27




Change Record


Rev

Description of Change

Date Released

Authored By

1.0


Initial release


11/17
/2009

Bruce Caryl


1.1


Changed description of how
Height is passed for mechanical
integration
. Added note on Value
with REF files.

Added QPL
usage with capacitors in HL PI

6/22
/2010

Bruce Caryl

1.2


1.3


2.0

Corrected ELDO_PARAMS$ in
Resistor Order property

Added information on HyperLynx
models to section 2.4

Revised to foc
us on
SystemVision and DMS


12/3/2010


2/28/2012


8/8
/2013

Bruce Caryl


Bruce Caryl


Bruce Caryl




Rev. 2.0

Page:
4

of
27


Date Modified:
11/02/13


1

Introduction

The Expedition Enterprise flow provides comprehensive board design and analysis
capability. This document describes how to modify a corporate library and how to create the
library
infrastructure to support simulation and analysis
, where the required model
s are
specified from

the CAD library
.

It is assumed that the reader already understands how to
set up and use DxDesigner, Library Manager, and the analysis tools that are referenced.
The purpose of the document is to assist the user in modifying an Exped
ition
Enterprise
/DMS

corporate library so that it can be used for both board design and analysis.
Details of tool usage and design editors are not included.

The focus is on suppo
rt of
SystemVision

to enable analog/
mixed signal
analysis.

1.1

Supported Types o
f Analysis

The following types of analysis are covered in this document:



Analog/Mixed Signal Simulation



Signal Integrity Analysis



Power Integrity Analysis



RF Simulation



Thermal Analysis



Mechanical Integration

1.2

Methodology

Rather than detailing all of the op
tions available, one primary recommended environment
will be presented. Variations of this

setup are possible depending upon

requirements.


This methodology requires minimal modifications to the existing CAD library or
DMS/DxDataBook. Experience has prov
en that maintenance of simulation data is best
supported outside of the main library processes, so Mentor has developed technology in
SystemVision to support a separate
, but still centrally managed
, simulation support
environment.

2

Requirements for Analysis

The following steps are required to support each type of simu
l
ation.

2.1


Analog/Mixed Signal Simulation



The
recommended simulation tool is

SystemVision



The s
imulator

engines

embedded in SystemVision

are

versions of

Eldo

for
Analog and
ADMS

for mixed signal.
It is also possible to direct SystemVision to
use the full
, standalone
ADMS/Eldo software if this is required.



Generic s
imulation properties based on part type

(IC, passive, etc.)

must be
added to the
component instance

(or could be on
the CAD symbol)

to enable the
SystemVision
netlister to work correctly.



Model names, model paths, and Pin Order mapping may be added to DMS or a
DxDataBook database to customize

parts on instantiation.


Rev. 2.0

Page:
5

of
27


Date Modified:
11/02/13


2.1.1


R
ecommen
ded Methodology



Basic properties that are required on a type of part to make it netlist properly
for
simulation
should be added through
Simulation Database, or
SimDB files. An
example of this would be the Prefix property, which is set equal to R for all
SPICE resistors.

SimDB files can be centrally located so that all users can
access them. They can also be design
-
specific, in case a user needs to develop
mappings that are new or unique to a certain design.


Note: These properties can also reside on the CAD symbol, but
this requires
more complex maintenance.




Properties that define a model and model mapping should be located in
DMS/DxDataBook. These properties include the model name, model location,
and pin mapping. Since these values
are unique

for each component, the
y can
be added at the same time as properties such as Part Number are added.

The
characteristics
that hold the properties

should exist in DMS/DxDataBook for each
part, and can be populated when the part is created or at a later time.



Some properties exist

in DMS/DxDataBook for reasons other than simulation, but
may be used for simulation. An example of this would be the Value property on a
resistor. These properties will be added to the component instance, and can be
mapped to another name

(through SimDB

files) if

required by the simulation
model.



Simulation sources, such as voltage sources or other stimulus, can be added
directly to the schematic or through a spreadsheet. The spreadsheet method
does not display the source
symbol
on the schematic.



Compon
ent instances that do not have simulation properties will not be included
in the simulation netlist.



Components can be directly excluded from the simulation netlist by adding the
Exclude=Yes property to the component instance.



SystemVision library parts wi
ll not affect the packager and will not be passed to
layout

2.2

Signal Integrity Analysis

HyperLynx SI

is recommended

for signal integrity

(SI)

analysis. All model assignme
nts can
be done within the tool
. The following properties can be used to control model

selection
from the corporate library. They may be added to the symbol, or added on instantiation.


Note: Part Number in the schematic maps to Part name in the Assign Models dialog box in
HyperLynx BoardSim.

2.2.1

Required Properties

Component Property

Name

Com
ponent Property

Value

Part Number

<unique index into central library>

IBIS

<IBIS

component
model name
>

Value

Value of discrete components


Pin Property

Name

Pin Property

Value

Pin Number

<pin number that matches IBIS model>

Pin Type

IN, OUT, BI, TRI,

ANALOG, OEM, OCL


Rev. 2.0

Page:
6

of
27


Date Modified:
11/02/13


2.2.2

Model Mapping in HyperLynx

Signal Integrity models ar
e mapped to components using one of two types of mapping files.
The QPL file maps a Part Number property on a component to an SI model, and a REF file
maps a Ref Designator property
on a component to an SI model.


Qualified Parts List File (QPL file)

The QPL fi
le maps a Part Number to an SI

model. It has the following format:


IC, CLOCK
-
701V, "National CGS701V", 701V.IBS, CGS701V

IC, RAM
-
512, "MemWell SDRAM512", MEMS.EBD, SDRAM512


The QPL file
could

be located in the Central Library
IBISModels

folder. Each user
could then point

to this file from HyperLynx BoardSim.


Ref Desig
nator mapping file (REF file)

The REF file maps a Ref Designator to an SI model. It has the following form
at
:


U1, 701V.IBS, CGS701V

U2, MEMS.EBD, SDRAM512


From the library perspective, the QPL file should be used because it can map a Part
Number to an SI model. If all SI models are in the IBISModels folder

of the central library
,
and the QPL file is also in

this folder, then each user will have a mapping between the
components in his design and the appropriate SI model.


Another approach would be to add the IBIS property to each component on instantiation
through the DMS/DxDataBook database. This property v
alue will be added to the IBIS

Component Name

column

of CES on packaging.
You will then have to add
the path the
IBIS

file through the IBIS Model Browser in CES.
Then, when the design is exported from
Expedition, a REF file will automatically be generated

for HyperLynx BoardSim
.

Because of
the additional step of adding the IBIS models to the IBIS Model Browser, which is not related
to HyperLynx (it

is used with
ICX Pro), this methodology is not currently recommended
.


Note: In order to pass the Value of d
iscrete components (resistors, capacitors, etc.) to the
REF file, the type of these parts in the Central Library Part definition must be set to the
correct part type, such as Resistor or Capacitor. If the Value is defined in the PDB, then that
value will
override the schematic Value.

2.3

Power Integrity Analysis

HyperLynx PI is used f
or power integrity analysis. A
QPL file may be used to assign models
to capacitors. The model is assigned based on the Part Number property on the
component, which maps to Part
Name in the decoupling wizard. However in EE2007.8, the
hyp file will not contain a Part Name for any capacitor that h
as a Value defined in the PDB.



The only other property from the library used by HyperLynx PI is the Value property on
discrete componen
ts. The Value is only used for grouping capacitors, and is not used as
the actual simulation value. Models for capacitors must be assigned within the HyperLynx
PI tool, or through the QPL file.


PDB Property

Name

PDB Property

Value

Value

<capacitance>

Rev. 2.0

Page:
7

of
27


Date Modified:
11/02/13


2.4

RF Analysis

2.4.1

Required
Properties

Agilent ADS and Microwave

Office

AWR are the supported simulators in the RF flow. The
following properties should be added to the RF components to enable simulation.


Agilent ADS Properties

Component Property

Name

Component

Property

Value

ADS_MODEL

<ADS model name>

ADS_MODEL_LIBRARY

<ADS
library

path>

Value

<component electrical value>


Microwave Office AWR Properties

Component Property

Name

Component Property

Value

AWR_MODEL

<AWR model name>

AWR_MODEL_LIBRARY

<AWR
library

path>

Value

<component electrical value>


2.4.2

Additional RF Simulation Requirements



The Mentor RF symbol library must be read into the corporate

Central L
ibrary
and placed into symbol pa
rtitions of the same name as the names

in the Mentor
library.



The
symbol

value
from the schematic
is always used for simulation. The PDB
value is not read.



Support

files used for RF simulation include:

o

library_elements, library_elements.awr

o

s
ubstrates, substrates.awr

o

ads_ini or awr.ini (automatically generated)



The
library_elements file has RF symbol parameters and must be copied to the
project folder.

2.4.3

RF Library and Configuration Files



Mentor RF library is located at:

o

$SDD_HOME
\
Standard
\
RF
\
AWRShapesLibrary



The library_elements and substrates files are located at:

o

$SDD_HOME
\
Standard
\
config
\
pcb

2.5

Thermal Simulation

HyperLynx Thermal is used for the thermal simulation of a PC board.

No special library
properties are supported at this time.

The Part Number is used for model mapping.

Thermal properties, such as power dissipation, can be added in the Parts tab of CES and
will be passed to HyperLynx Thermal.

2.6

Mechanical Integration

The Height property is used to assign the height of
a
component.

Modifying the value of the
Height proper
ty has no effect on placement or design rules

check
ing

in Expedition. When
exporting to IDF from
Expedition
, the H
eig
ht value is read from the
Parts Database (PDB)
. If
it does not exist in the Parts Database, it is read from the Cell. The Height is not
read from
Rev. 2.0

Page:
8

of
27


Date Modified:
11/02/13


the part instance in Expedition, so it cannot be passed from the schematic or from DMS
.
For infor
mation on creating cells in Library M
anager, refer

to Creating Cells in t
he Library
Manager Process Guide.


3

Required Properties for VHDL/AMS Simulat
ion

SystemVision supports the ability to add VHDL
-
AMS properties to physical components and
use them in simulation. It is also common for VHDL
-
AMS models to be used on
components that are used only for simulation, and not for PCB layout. If VHDL
-
AMS mode
ls
are used for PCB layout, the following properties can be added to the
symbol

(if the symbol
defines a unique part) or to the DMS/DxDataBook Database (if the symbol is generic).

3.1

Required Symbol or Component Properties


Property

Name

Property

Value

VHDL
Model

<library>.<entity>(<architecture>)

VHDL File

<filename>.vhd

<VHDL Generic parameter>


Pin Order

<pin name> <pin name>

Simulation Model

VHDL


Notes:



Pin Order should match the name and position of the pins declared in the VHDL
Entity



The <
VHDL Generic parameter>
represents any Generic
property that is in the
VHDL model generic list
that should be passed to the model.



VHDL Generic
properties typically
are

real numbers
, but
engineering units such
as K, MEG, etc.
are supported with SV5.10



VHDL

File can be a complete path designation.


3.2

VHDL/AMS in Sub
-
circuits

VHDL/AMS models can also be instantiated in SPICE sub
-
circuits. Often the best
methodology is to put the VHDL/AMS model in a sub
-
circuit and then reference the sub
-
circuit from the
schematic.

3.3

VHDL
-
AMS Standard Passive Models

SystemVision provides a library of models that
are based on VHDL
-
AMS and can be
characterized with properties commonly found in datasheets. These datasheet models can
be used when a vendor
-
specific model is not
available. The passive models (RLC) have
more parameters than the equivalent SPICE models, so it is recommended that these
models be used for passive parts. The symbols for the models are included in the SVLIB
library partition, and all end with _datashe
et.







Rev. 2.0

Page:
9

of
27


Date Modified:
11/02/13


Resistor Parameters:



Inductor Parameters:



Capacitor Parameters:


Rev. 2.0

Page:
10

of
27


Date Modified:
11/02/13



SimDB
(see Simulation Database Files section of this document)
can be used to assign the
required properties to the components in the schematic. Properties from DMS/DxDataB
ook
can be used to assign values such as ESR or ESL. SimDB property mapping can be used
to map the DMS/DxDataBook property names to the model property names.


4

Required Component Database Properties

(DMS)

These properties should be added to

the DMS/
DxDataB
ook database. They are unique for
each instantiated component and are applied when the component is placed on the
schematic.


Within DMS, a component object has properties (called characteristics in DMS) that are
unique to the component type. This set of

properties can be added to a tab in the
component area of DMS, or a new tab can be created to specifically hold simulation
properties. A new tab is recommended, since it makes the properties easy to find and
separates them from the properties that have o
ther functions.

4.1

SPICE

Simulation Properties in the DMS/DxDataBook Database

These properties should be included for all types of components that will need models. This
includes ICs, transistors, diodes, and all parts modeled with a subcircuit. Passive
components do not require
external
models, but they can be assigned if desired
.



$Sim
Rep is an environment variable that

represents a path to
the
simulation
model
repository
.


Property Name

Property

Value

SPICEFILE

$SimRep
\
<model folder>
\
<library name .lib>

Model

<model or subcircuit name>

Pin Order

Space delimited list of
symbol pin names that map by position
to the pins in the SPICE model or subcircuit declaration.
Default is alphabetical order.


Note: In some cases, it may be necessary to assign the Simulation Model property from
DMS. This would be required if the mode
l needs to be changed from a SPICE model to a
VHDL/AMS model (or vice
-
versa) because multiple models are supported.

4.2

VHDL
-
AMS Properties

If VHDL
-
AMS models are used, the following key properties will need to be assigned to the
component.


Property

Name

Property

Value

VHDL Model

<library>.<entity>(<architecture>)

VHDL File

<filename>.vhd

<VHDL Generic parameter>


Pin Order

<pin name> <pin name>


Notes:



It is recommended t
hat the <library> be defined as “W
ork”, and t
he source be
compiled into the W
ork

library for each project.

Rev. 2.0

Page:
11

of
27


Date Modified:
11/02/13




Pin Order should match the name and position of the pins declared in the VHDL
Entity.



VHDL generic properties can be any property name that matches the name in
the Generic list of the VHDL source.



VHDL generic properties are typi
cally real numbers, but can now use SPICE
units such as u, n, p, k, etc.



VHDL File can

be a complete path designation to the simulation model
repository.

4.3

Signal Integrity Properties

The Part Number and Value are typically annotated from the DMS/DxDataBook

database on
instantiation. The Value is passed through to HyperLynx

on passive parts

and is used in the
analysis. The Part Number is used if a QPL file has been selected for model mapping.


5

Simulation Database Files

Parts from a corporate library will typically not have simulation properties associated with
their symbols. In order to make a component on a schematic
capable of being

simulated
, a
base set of properties needs to be added. While these properties could b
e added directly to
the CAD symbol, it is more effective and flexible to add the properties through simulati
on
database files, called SimDB.

Using SimDB provides the added flexibility of being able to
change a model type just by calling a different SimDB
file. For example, all resistor models
could be changed from SPICE to VHDL
-
AMS with a single command.

5.1

SimDB structure

The SimDB is based on text files that contain an index key and a set of property name and
value pairs that will be added to the component

instance on the schematic. The
key can be
based on any property, and is typically either the name of the symbol or the Part Number.
The following is an example of a SimDB file that is used to add a set of simulation properties
to any sym
bol that has the

name

discretes:
RES
.


[discretes:RES]

Prefix=R

Order=Value$

Model&

Pin Order=N1 N2

Model
=


For VHDL
-
AMS models, the following
set of properties
could be used. In this example, it is
assumed that the VHDL source is compiled into the local Work library.


[
discretes:res]

Simulation Model=VHDL

VHDL File=RESISTOR_DATASHEET.VHD

VHDL Model=WORK.RESISTOR_DATASHEET(DEFAULT)

RES=NORMALPDF(1E3,0.1)

POWER_SURGE_MAX=0.3

POWER_AVG_MAX=POWER:=0.1

TC:=0.0

Prefix=Y


Rev. 2.0

Page:
12

of
27


Date Modified:
11/02/13


The partition name
must be included

in the symbol refere
nce
, and wild cards can
not

be
used.
The symbol name is not case sensitive. Note that with the SystemVision 5.10.1
release and later, the type of the parameter and the VHDL_GENERIC_ prefix is no longer
needed (but can still be included), since the netlist
er
now
gets these values form the
Generic section of the model.


It is also possible to use the SimDB to map a part number to a set of properties. In this
case, the value or model could be included, since the part number specifies a specific part.


[13
-
23828
-
03]

Prefix=R

Order=Value$

Pin Order=N1 N2

Value=10k

Simulation Model=SPICE


The SystemVision menu item SystemVision
-
>Set Simulation D
ata

opens a dialog box that
will generate
a SimDB file with
either of these formats for all the parts in a design
. The
output is saved to a project.simdb file in the project folder.

The project.simdb file is always
the highest priority SimDB file that is used when the Tools
-
>Update Simulation Data menu
pick is run.
If the field between the brackets [] contains a c
olon, then it is interpreted as
being matched to a symbol name. A combination of this structure can be used to specify a
base set of properties for one type of symbol, and a specific set of properties for a

part
based on

part number.
If the same property

is specified in both the symbol and Part
Number sections, then the Part Number section is the value that will be applied.
For
example, the above entries could be combined as follows.


[13
-
23828
-
03]

Symbol=discretes:RES

Value=10k

[discretes:RES]

Prefix=R

Order=Value$

Pin Order=N1 N2

Simulation Model=SPICE

5.2

Set Simulation Data Dialog

The SystemVision
-
>Set Simulation Data menu pick opens a dialog box that provides design
-
specific SimDB output. This methodology could be used to build up a library of SimDB fil
es
by first adding the part to a schematic and then using this tool.


Rev. 2.0

Page:
13

of
27


Date Modified:
11/02/13




The list can be managed by selecting only the required parts, or by selecting a part type in
the drop
-
down box. The part type mapping is defined by the SVdefaultPropByType.simdb

file located in the “s
tandard


folder in SDD_HOME

(or the WDIR path)
.
If a project.simdb file
already exists, then new data will be added to the file.
The following is an example of how
the part types map to a set of properties

in the SVdefautPropByType
.simdb file
. This could
be configured by the user to match the types of models that are desired.


[REFDES:Resistor:R?]

Prefix=R

Order=Value$

Pin Order=N1 N2

Value=


[REFDES:Capacitor:C?]

Simulation Model=VHDL

VHDL File=CAPACITOR_DATASHEET.VHD

VHDL Model=W
ORK.CAPACITOR_DATASHEET(DEFAULT)

CAP=NORMALPDF(4.7E
-
9,0.01)

VOLTAGE_MAX=VOLTAGE:=50

TC=0.0

ESR=0.03

ESL=0.25E
-
12

I_LEAK=0.0

POWER_AVG_MAX=0.1

Prefix=Y

Rev. 2.0

Page:
14

of
27


Date Modified:
11/02/13


5.3

Using SimDB to Map Property Names

Within a SimDB file, properties can be mapped from one name to another. For example, if
in DMS/DxDataBook, a property is called Resistance, but in the simulation netlist it needs to
be called Value, the following mapping can accomplish this.


[discretes:
RES]

Prefix=R

Order=Value$

Pin Order=N1 N2

Value=Resistance$


The value of Resistance could be directly defined in the same file, and strings with spaces
need to be surrounded by curly braces.


Resistance=10k

IND
={
Inductance

Total}$


At this time, the subs
tituted value cannot be in the middle of a string. The $ property has to
completely replace the property value.

5.4

Specifying SimDB Files

The sysvis.simdb file
, located in the WDIR path or project folder,

contains the information
about where the SimDB files
are located, and what property is used as the index. For
example, the following file calls our several SimDB files and uses Part Number and then Ref
Designator to assign the properties.


[SimDB Files]

%WDIR%
\
SVSharedLibrary
\
SimDB
\
Resistors.simdb

%WDIR%
\
SV
SharedLibrary
\
SimDB
\
Capacitors.simdb

%WDIR%
\
SVSharedLibrary
\
SimDB
\
Inductors.simdb

..
\
Library
\
SimDB
\
Transistors.simdb

C:
\
Library
\
SimDB
\
Analog_ICs.simdb

[Ignore Properties]

[Association Properties]

Part Number

Ref Designator


This file can be located in the project folder or in the WDIR search path.
The
relative path
notation (..
\

)

is referenced from the project folder.


Additional information about the SimDB can be found in the SystemVisio
n User Guide
appendix PCB flow area.

5.5

Applying SimDB Files to a Schematic

Once configured, parts will get properties added to them when they are added to a
schematic. It is also possible to initiate a SimDB update for parts that are already on a
schematic. This is done by executing the Tool
s
-
>Update Simulation Data
-
>Active
Schematic (or All Schematics).


Rev. 2.0

Page:
15

of
27


Date Modified:
11/02/13


6

Simulation Model Repository

Simulation models need to be located where users can access them from SystemVision.
They also need to be under some type of document control
.

6.1

Simulation Model Re
pository

Location

A Simulation Model Repository (SMR) should be created in a common network location
where it can be accessed by all users. At the top level of the file structure there should be a
single folder that contains the repository. Under this fo
lder a file structure holds the types of
models. The following structure is recommended.




The SYM folder is used to hold the symbols that are specific to the models. The spice folder
holds spice models, the hdl folder holds VHDL files, and the simd
b

folder holds the SimDB
files
. Inside the model folders, such as the spice folder, sub
-
folders can be used to define
model categories. The following is a suggested group of model types for the spice folder.



If there are
many
symbols to be stored in th
e library, then an alternative structure would be
to have the categories at the top level, and the SYM, spice, and hdl folders under each
category. The structure is flexible, so alternatives can be considered to meet the user’s
needs. One consideration i
s that for each SYM folder you will need to have a separate
library entry in the schematic symbol search path. A structure with parts distributed like this
would only work in the Netlist flow, since the integrated flow requires one library. Models
can al
ways be distributed in the most efficient way, since they are not tied to the CAD library
structure.

Rev. 2.0

Page:
16

of
27


Date Modified:
11/02/13


6.2

Model Files

Models can be stored as individual files or as one of many models in one file. In general, it
is recommended that a single file contain a sing
le model. This makes it easier to manage
the model files because they have a one
-
to
-
one correlation to a part.

6.3

Managing the Simulation Model Repository

DMS can be used to manag
e the files that make up the Simulation Model Repository
.

The
entire SMR can b
e zipped into a single file and checked into DMS. DMS can then be
configured to write out an update to the SMR when required.



Through Mentor
’s
c
onsulting
d
ivision
, DMS can be customized to manage the simulation
models and model repository.

Models can be associated with part objects, and the model
repository can be updated when a model changes. Models can also be lifecycle managed.
Please see a representative of the
DMS consulting division for further information.


7

Library

and Project

Con
siderations

The Central L
ibrary contains all the symbol and cell data. DMS or a DxDataBook database
contains the instance
-
specific properties.

7.1

Integrated Expedition Flow and Netlist Flow

There are two main types of projects that can be created in SystemVi
sion/DxDesigner. The
Integrated Expedition flow is used when the schematic design is going to be packaged and
sent to Expedition for layout. The Integrated flow only supports one central library, so only
one library can be active at a time. The other ty
pe of flow is the Netlist flow, which is used
when the design is not going to be used for board layout in Expedition (or is going to be
used with PADS or other third party layout tool). The Netlist flow is more flexible than the
Integrated flow, because i
t allows for an unlimited number of symbol libraries to be included,
and the libraries can be located anywhere in the file system.

If a design is started in the
Netlist flow, it can be migrated to the Integrated Expedition flow by using the menu
command F
ile
-
>Import
-
>Netlist Project….
It is not possible, however, to migrate from an
Integrated Expedition flow to a netlist flow.


For users who need to be in the Integrated Expedition flow, but also need access to the
SystemVision library, a script is availab
le for switching between the SystemVision and
corporate CAD library. Since the symbol data is cached, no data is lost. This is the
recommended approach for mixing CAD library parts and SystemVision library parts. While
the SystemVision library could be
imported into the corporate CAD library, the library would
need to be maintained, and there would be many new partitions to search through when
selecting parts.

7.2

Properties

for Simulation

All properties used for analy
sis
should

be added to the property defi
nitions
associated with a
Central Library. These properties are stored in the CentLib.prp file in the Central Library
folder. If a property is not in this list, it will not be editable in the schematic

property editor
,
and
will
only
be
editable in System
Vision through

the
Edit Model Properties dialog
.

Many of
the parts used for simulation have properties that are not in a typical Expedition library. The

properties from the S
ystemVision libraries
may

be merged into the corporate library so that
they are all included.

Properties can be import
ed from the
SystemVision library by opening
Rev. 2.0

Page:
17

of
27


Date Modified:
11/02/13


the Property Definition Editor in Library Manager, and clicking on the Advanced button, and
then the Import… button at

the bottom center of the form.






Navigate to the Mentor

SystemVision EDULIB

library and check all the properties you want
to import. If you check one that already exists, the tool will prompt you to append a new
name to it or to ignore it. By impor
ting these simulation properties, you will be able to edit
the properties that are on the Mento
r
-
provided
SystemVision components.


Rev. 2.0

Page:
18

of
27


Date Modified:
11/02/13


The SystemVision library is located at:


$
SDD_HOME
\
standard
\
templates
\
SystemVision
\
CentralLibrary
\
EDULIB
\
EDULIB.lmc

7.3

Library
Structure

The corporate CAD library and SystemVision

library

both have their own organization.
While they could be merged together, it is recommended that they be kept separate.


SystemVision supports the concept of a shared library. By default, the sysv
is.ini file
contains a path to a location where models can be saved. The user can add more shared
libraries if needed. When a model is generated in a SystemVision project, the option is
available to the user to save the model to the local project or
to
o
ne of the shared libraries.
One of the shared libraries could be part of the Simulation Model Repository. However, it
may be preferable to keep the Simulation Model Repository a read
-
only and data managed
area, while the shared library is used to enable
small groups to share models and symbols
within a project. The following is an example of a shared library entry in the sysvis.ini file.


; Locations to save models

; path relative to WDIR, Central Library, or full path with env variables

;
SVSharedLibrary (relative to user WDIR location)

; C:
\
WDIR
\
MySharedModelFolder

; %MY_SITE_PATH%
\
SharedModelFolder

[SharedModelLocations]

SVSharedLibrary

7.4

Adding Ground References

By default, SystemVision maps some common net names, such as GND and
ELECTRICA
L_REF
, to node 0 in the SPICE cir file. If additional ground names are used,
they can be added to the svspice.cfg file (located in the in
stallation area “
standard
” folder
)
and the file can be copied to the WDIR search path folder. The following is an exa
mple of
this file with AGND and DGND added as ground nodes.



7.5

Using the Expedition Central Library Structure

The standard structure of an Expedition Central Library contains folders for storing
simulation models. It is possible to use the Expedition Cent
ral Library as the Simulation
Model Repository if there is a desire to keep CAD library parts and simulation models in the
same folder structure. However, CAD library parts are managed differently than simulation
models, since they do not change as often
and have a more well
-
defined structure and
Rev. 2.0

Page:
19

of
27


Date Modified:
11/02/13


lifecycle. The CAD library area is also used by non
-
simulation users, and has tight controls
to support the manufacturing process. For these reasons, it is recommended that the
simulation models be stored in a s
eparate area outside of the Expedition Central Library.

7.6

SPICE Library Searches

SystemVision will look for models in the <p
roject>
\
sym folder by default.

Models located in
this folder are added to the simulation netlist (.cir file) through an “.include” st
atement.
Models that are not located in the sym folder will be resolved by the simulator through .lib
statements. All parts with SPICEFILE property cause the SystemVision netlister to add a .lib
statement to the .cir file.

7.6.1

Mentor
-
supplied
SPICE
Simulatio
n Models

Mentor provides a library of SPICE simulation models with
SystemVision
.

The HyperLynx Analog spice libraries are located at:


The SystemVision spice libraries are located at:

$SDD_HOME
\
sim
\
systemvision
\
SpiceLibs

7.7

VHDL Libraries

In general, it is recommended that VHDL
-
AMS models be compiled into the Work library for
each project.
The source can be pointed to by the sysvis.ini file, or it can be copied into the
local project.

7.7.1

VHDL Source Files

For SystemVision to find a VHDL source file, the full path needs to be accessible. The
VHDL F
ile path on the component should
typically

call out

only

the file name. The path to
the folder that contains the VHDL source file should be located in the sysvis
.ini file in the
WDIR search path. Below is an example of an en
try in the sysvis.ini file that points to the
VHDL source for custom models.


; The list of model source directories to search for vhdl & spice files

[ModelSourceFolders]

C:
\
projects
\
SV
\
MySVL
ib
\
hdl


The folders are searched in order, so care should be taken to not have duplicate names in
multiple folders.


VHDL source files that are in the hdl folder of a DxDesigner library added to the search
order will be found with the Push
-
VHDL command,
but they will not be able to be compiled.
The compiler will be expecting the file at the root of the project, since there is no path on the
symbol. So it is up to the user to add the path

to the DxDesigner library hdl folder

to the
[
ModelSourceFolders
] s
ection

of the sysvis.ini file, or save
-
as or copy the VHDL source to
the local project hdl folder.


Another option is to add the VHDL source to the current project. This action copies the
VDHL source to the hdl folder, where it can then be compiled. This

has the advantage of
allowing the source to be edited for the project without modifying the original
source
which is
typically located in the shared Simulation Model Repository. To add

custom models (those
not already compiled in the SystemVision
EDULIB l
ibrary
)
go

to the VHDL Files area under
Rev. 2.0

Page:
20

of
27


Date Modified:
11/02/13


the Files area of the TestBenches

branch

on the SystemVision tab of the Navigator, as
shown below.




The user can then right click the file and select compile. The compile dialog box will pop up
and the model ca
n be compiled into the Work folder by using the default settings.


By compiling the source for custom models, the issue of having to recompile all the models
with each new SystemVision release is avoided. However, if there are some commonly
used models
that the user wants to manage in a central compiled library location, the
following section details how to support that methodology.

7.7.2

Compiled VHDL
-
AMS Libraries

Compiling VHDL/AMS models into a corporate library is not recommended, because the
library has
to be recompiled for each SystemVision release, and adding models requires
knowledge of how to do the library compilation step. However, if this is the desired
approach, c
ustom
VHDL
-
AMS models can
be compiled into a corporate library and then
used in desi
gn simulations.

When a part is added to a schematic, DMS/DxDataBook will
add the

VHDL Model


property. The value of

this property should be in the following
format:
library.entity(architecture).

By
controlling

the library name, a model can be pointed
to the corporate VHDL library. The following process is recommended for creating a
corporate VHDL library with VHDL
-
AMS models.


1

Create a SystemVision project called “
CORP_
VHDL”

(or other user
-
supplied name)
in
th
e
simulation model repository
.

2

Copy the VHDL files you want to compile into the
CORP_
VHDL project hdl folder.

3

In the Navigator under the SystemVision tab, expand Model Libraries and right click
HDL Libraries and select “Edit Project HDL Library”.

4

Enter the Library Name (e.g. CORP_VHDL), and add files from the hdl folder.

Click OK.


Rev. 2.0

Page:
21

of
27


Date Modified:
11/02/13




5

A
compiled VHDL
library will be created under the lib folder

in the project

that contains
the
compiled versions of these models
.

6

To make this available to all users,

c
opy the sysvis.ini file from th
e installation s
tandard
folder to the

local

WD
IR folder (e.g. Config_WDIR). In sysvis.ini, a
dd the path to the
new compiled library


; The list of model libraries to be added

[CompiledModelLibraries]

C:
\
demonstrations
\
EEFl
ow
\
Libraries
\
CentralLibrarySV
\
Models
\
VHDL
\
CORP_VH
DL
\
lib
\
%admsver%
\
CORP_VHDL

; The list of vhdl source directories to search for vhdl files

[VHDLSourceDirectories]

C:
\
demonstrations
\
EEFlow
\
Libraries
\
CentralLibrarySV
\
Models
\
VHDL
\
CORP_VH
DL
\
hdl


7

Add the follow
ing to the svnetlister.ini file to automate adding the library reference to the
output


; All ContextClauses get inserted before each entity and configuration.

; The user may extend or modify this list as desired.

[ContextClauses]

LIBRARY CORP_VHDL;

USE
CORP_VHDL.all;


New SystemVision projects will now have the corporate library included. Models used in the
projects can point to the CORP_VHDL library.

7.8

Importing
Simulation Symbols

Mentor provides
script that can be used to import symbols from the SystemV
ision library to
the Expedition Central Library
.
While this is not generally a recommended practice, it can
be done if the user wants to avoid switching between the corporate library and the
SystemVision lib
rary. Copies of the SystemVision library are in
cluded with the scripts. The
scripts and a README.txt file are located in the install area at:



\
SDD_HOME
\
standard
\
SV_Custom

Rev. 2.0

Page:
22

of
27


Date Modified:
11/02/13



The contents of the README file are shown below.



7.9

Switching Between Libraries in
Expedition
Integrated Flow

In the Expedition Integrated flow,
only one central library can be referenced in a project. If a
user wants to use parts from the corporate library, and from the SystemVision library, there
are two options. One option would be to import all of the System
Vision parts into the central
library or DMS. This is not recommended because it makes the corporate

library large and
difficult to maintain. The preferred way to manage this is to use a script to switch between
libraries. Since the symbols are cached w
hen used, no data is lost. The script can be
provided by your local application engineer.


8

Additional Considerations

8.1

Configuration Files

Configuration files should be located in a common area on a file server that is accessible by
all users. The path to
this area should be included in the WDIR environment variable search
path (typically the second path, after the user path). The speccomps.ini, borders.ini, and
DxDesigner project templates (along with other DxDesigner configuration files) should be
locate
d in this area. The DxDesigner templates are used to set up a project configuration
that points to the desired Central Library, borders, and special components (e.g. VCC, GND,
ON/OFF Sheet).

8.2

SystemVision
Considerations



To exclude parts from a Syste
mVision

netlist, add the Exclude=Yes

property

to the
component instance.

Exclude=No will put the part back in the netlist.



To exclude parts from
being included in a
PCB in a SystemVision design, change the
“Forward to PCB” property t
o F
alse
. SystemVision librar
y parts are set to this by
default.



When adding distributions for Monte Carlo analysis, SystemVision modifies the
Value property by adding a distribution
-
formatted property, which may not be
Rev. 2.0

Page:
23

of
27


Date Modified:
11/02/13


desirable for PCB schematics.

The user may optionally set the Monte Carlo
distributions in a model file and add the model to the SPICE components.



Schematics used for simulation may need additional source components or loading.
One way of achieving this is to create a top
-
level test

bench schematic, and
encapsulate the CAD schematic in a block symbol. The block symbol can then be
used on the test bench schematic, and ports on the symbol can be connected to
various sources and loads. Alternatively, sources can be added to a schemati
c
through a spreadsheet.

8.3

Editing Simulation Properties



SystemVision VHDL
-
AMS components
and
SPICE components
have many
properties that cannot be edited unless the

SystemVision

Edit Model Properties
dialog box is used. To change the properties with the st
andard property editor, they
must be added to the property definitions in the CentLib.prp file.

8.4

Pin Properties

The correct pin properties should also be added to all symbols. While this requirement is
not unique to simulation, it should be considered when

updating the corporate library.



The Pin Type property should be set to the correct type.
Two
-
pin analog parts
should be set to type ANALOG, not BI. The pin direction is also used
in the
constraint editor system (CES) for

defining from
-
to relationships,
and is used by the
Verify operation
in DxDesigner to determine driver and load conflicts.



VHDL
-
AMS parts have 3 classes of ANALOG pins: TERMINAL, IN_QUANTITY, and
OUT_QUANTITY. These are specified in the VHDL_PORT property. If this property
is not specifi
ed, the default VHDL_PORT class of an ANALOG pin is assumed to be
TERMINAL by the SystemVision netlisters.



The
VHDL Type property
, which should be on every VHDL
-
AMS symbol pin,
specifies the “nature
” of the analog signal, such as
ELECTRICAL, MAGNETIC, etc.



The Pin Number property should be set to the correct pin number so that IBIS
models will be mapped to the right pins.




9

Summary

A corporate library designed to support schematic capture and layout can be modified to
also support the analysis tools that are

part of the Expedition Enterprise flow. Standard
properties that do not change often or that are
used to enable netlisting are

added to the
component instances through the SimDB
, while

part
-
specific properties are

added through

DMS/DxDataBook
. This all
ows a single schematic to be used for both design engineering
(simulation), and layout.


9.1

Steps Required to Support Simulation

The following is a summary of the steps that need to be taken to enable simulation in a
corporate CAD library:




Add characteristi
cs (properties) to DMS/DxDataBook to support the name of the
model, the path to the model, and the pin order mapping. Add these for all part types
that require SPICE models or sub
-
circuits, such as diodes, transistors, opamps, etc.

Rev. 2.0

Page:
24

of
27


Date Modified:
11/02/13




Determine how you want
to model passive components (resistors, capacitors,
inductors). The options are SPICE models or VHDL
-
AMS models. VHDL
-
AMS
models have more capability and can be used to calculate stress values such as
power or voltage.



Create SimDB database files that
add the required simulation properties to all parts.
Create symbol
-
name
-
based entries for generic parts such as resistors, capacitors,
inductors, diodes, transistors, etc. Create Part Number
-
based entries for ICs and
more complex models.

Create a SimDB
file that maps any property names from
DMS/DxDataBook to the required model parameter name (e.g. Value to Resistance).



Cr
eate a Simulation Model Repository, which is a folder located

on a common server
where all models and some
reusable
symbols will be sto
red. The top level of the
repository should be a folder, and the structure

in the folder

should match a
SystemVision project structure. Simulation models can be stored in any

sub
-
folders.
The sub
-
folders should be named in a way that organizes the model
s (e.g. Diodes,
BJTs, MOSFETs)
. SimDB files, organized by part type, should be stored in this
repository

under a folder called SimDB.



Define a methodology to support the population and maintenance of the Simulation
Model Repository. A model submission pr
ocess should be defined and implemented
in DMS or other data management environment. The model
versions

and access

rights

should also be managed by data management software. While DMS could
perform these functions, it would require a custom implementatio
n through Mentor
consulting.



Create a corporate WDIR folder if one does not exist already. Locate the
key
SystemVision support files in the corporate WDIR folder. These include:

o

Copy sysvis.ini file to
the
corporate WDIR folder to set
the
list of corpora
te
SPICE file libraries to include in SystemVision
. Also set the path to the
default shared libraries used by SystemVision. This is typically another local
area where a project team can share models.

o

Create sysvis.simdb file that includes the path to all

the SimDB files, as well
as the property name used as an index (typically Part Number).

o

Copy the svspice.cfg file to the corporate WDIR folder, and add mappings for
ground names used in typical designs (like AGND, DGND).



Once the SimDB files are in place,

the properties will be added when a part is
instantiated on a schematic. The part will get the base simulation properties from
SimDB, and the unique model properties from DMS. Sources can then be added to
the schematic. Parts in the schematic without s
imulation properties will simply be left
out of the simulation netlist. SystemVision can then be used to simulate the
corporate library schematic

10

Appendix

10.1

Required Properties for SPICE Simulation

Based on the type of the component, different sets of prope
rties are required to enable
SPICE simulation with SystemVision.


Note:

The Pin Order property is a space delimited list of symbol pin names that map by
position to the pins in the SPICE model or sub
-
circuit declaration. The default Pin Order, if
no prop
erty exists, is in alphabetical order. This property can be put on the symbol if the
symbol is only used with one model or one common positional mapping. On two pin devices
such as resistors, Pin Order will affect the reported direction of current flow.

Rev. 2.0

Page:
25

of
27


Date Modified:
11/02/13



Note:

The Pin Order attribute is critical to the correct function of devices with more than one
pin.

10.1.1

Resistors

Property

Name

Property

Value

Model


Order

MODEL$ VALUE$ TC1=

Pin Order

<pin name> <pin name>

Prefix

R

TC1


Value


Simulation Model

SPICE


10.1.2

Capacitors

Property

Name

Property

Value

IC


Model


Order

MODEL= VALUE$ TC1=

Pin Order

<pin name> <pin name>

Prefix

C

TC1


Value


Simulation Model

SPICE


10.1.3

Inductors

Property

Name

Property

Value

IC


Model


Order

MODEL= VALUE$

IC= TC1=

Pin Order

<pin name> <pin name>

Prefix

L

TC1


Value


Simulation Model

SPICE

10.1.4

Diodes

Property

Name

Property

Value

Model

<model name>

Order

MODEL$

Pin Order

<pin name pos node> <pin name neg node>

Prefix

D

SPICEFILE

<path to SPICE library or model
file>

Simulation Model

SPICE

Note: Model value is required and should name a model from a library

Rev. 2.0

Page:
26

of
27


Date Modified:
11/02/13


10.1.5

Bi
-
Polar Transistors

Property

Name

Property

Value

Model

<model name>

Order

MODEL$

Pin Order

<pin name C> <pin name B> <pin name E>

Prefix

Q

SPICEFILE

<path to SPICE library or model file>

Simulation Model

SPICE

Note: Model value is required and should name a model from a library

Note: Pin Order should be pin names for Collector, Base, Emitter in that order

10.1.6

JFET Transistors

Property

Name

Property

Value

Model

<model name>

Order

MODEL$

Pin Order

<pin name D> <pin name G> <pin name S>

Prefix

J

SPICEFILE

<path to SPICE library or model file>

Simulation Model

SPICE

Note: Model value is required and should name a model from a library

Note: Pin Order should be pin names for Drain, Gate, Source in that order

10.1.7

MOSFET Transistors

Property

Name

Property

Value

Model

<model name>

Order

MODEL$

Pin Order

<pin name D> <pin name G> <pin name S> <pin name B>

Prefix

M

SPICEFILE

<path to SPICE
library or model file>

Simulation Model

SPICE

Note: Model value is required and should name a model from a library

Note: Pin Order should be pin names for Drain, Gate, Source, Bulk in that order

10.1.8

Ideal Transformers

Property

Name

Property

Value

A


Order

"JTRAN PIN: " N1[ N2[ N3[ N4[ " PARAM: " A=

Pin Order

N1 N2 N3 N4

Prefix

Y

SPICEFILE

<path to SPICE library or model file>

Simulation Model

SPICE

Note: A is the turns ratio

Note: Pin names on symbol should be N1, N2, N3, and N4, or Order and Pin
Order property
must also be changed to reflect symbol pin names.

10.1.9

Subcircuits

Property

Name

Property

Value

Model


Rev. 2.0

Page:
27

of
27


Date Modified:
11/02/13


Order

MODEL$

Pin Order

<pin name> <pin name…>

Prefix

X

SPICEFILE

<path to SPICE library or model file>

Simulation Model

SPICE

Note:
Model value is required and should name a model from a library

Note: Pin Order should match order of pins in SPICE subcircuit declaration

Note: Any property name that matches the parameter list will be passed to the instance of
the subcircuit (e.g. GAIN=2)


10.2

Terms and definitions:


HyperLynx

Mentor’s family of signal and power integrity products

SystemVision

Mentor’s System
-
Level simulator, which includes most ADMS
features

Eldo

Mentor’s SPICE simulation engine

ADMS

Mentor
’s mixed
-
signal simulator, which includes Eldo and
ModelSim

VHDL
-
AMS

Analog Mixed Signal extensions to the VHDL language. Used for
behavioral simulation modeling of multiple domains (electrical,
mechanical, thermal, fluidic, rotational, etc.)

Symbol

The

CAD symbol file associated with a CAD part

Component Instance

An instance of a symbol on a schematic sheet

EDULIB

A library of VHDL
-
AMS and SPICE models provided with
SystemVision. The VHDL
-
AMS models are open source.

SimDB

Simulation Database. These

files are used to add simulation
properties to component instances based on symbol name or Part
Number.

WDIR

This is an environment variable used by DxDesigner and
SystemVision to locate configuration files. The WDIR value is a
series of semi
-
colon
separated paths that are searched to locate
the required files. Upon installation, a WDIR environment variable
is created with a path to the installation area “standard” folder, and
to a local writeable folder. Most companies add a path to a
corporate fo
lder on a server in the middle of the WDIR value string
so that they can configure DxDesigner and SystemVision for their
entire organization.