Download S-Edit User Guide

Chapter 8: Importing and Exporting Netlists and Schematics
Importing a Design
Overwrite existing views
If cells of the same name exist in the SPICE file and the design it is
being imported to, a check in this box causes the SPICE file to
overwrite the views in the existing cell.
SPICE format type
Choose from T-Spice, HSPICE, PSpice and CDL.
Pin type from CDL is imported via the .PININFO command.
Prepend device character
to model names
When checked, SPICE device characters will be prepended to model
names in the netlist.
Include SPICE prefix
characters in instance
names
When checked, SPICE prefix characters will be included in model
names so that the entire word becomes the instance name rather than
stripping the first character.
Parse connectivity
When checked, parses connectivity from a SPICE netlist including
files referenced by .include statements. Spice views are then
generated from the connectivity views.
Preserve text
When checked, creates a Spice view cell for each subcircuit under
the subcircuit name, and pastes in the entire subcircuit text including
comments, include files and formatting. Comments written between
subcircuit definitions are included in the subcircuit cell below them.
Creates “cell0” for the top-level cell.
It is recommended that you check the model files of commercially available device, as they may have
critical parameters included with the model parameters rather than in the device parameters as T-Spice
expects, or they may include parameters that are not valid for your model level.
Importing EDIF Files
The EDIF import operation creates SPICE views. As with importing a SPICE file, since the views are
saved with the design, the imported EDIF is saved. Importing a hierarchical netlist creates separate cells
for each subcircuit in the netlist. New libraries created by importing EDIF are opened with the settings
editing allowed and with exclusive access.
If you wish to create a new design from an EDIF file, you should create a design with the same name as
the top level or root library in the EDIF file, and then import the EDIF file into that design. The root
library is often written near the bottom of the EDIF file with a “design ROOT” entity as:
(design ROOT
(cellRef rootcell
(libraryRef rootlibrary)))
Where rootlibrary is the name of the root library. The root library is the one nearest the bottom of the
EDIF file, so you can also identify it by locating the entity “library libraryname” that is nearest the
bottom of the file.
Another way to create a new design from an EDIF file is to create a design with any name, import the
EDIF file, and save the design and its libraries. Use the Top-level filter in the Libraries navigator to
assist in finding the toplevel library. You can then open the toplevel library directly (in this context it
becomes the design) and you can delete from disk the placeholder design that you initially created.
Note that standard cell place and route (SPR) in L-Edit requires either a flattened EDIF netlist or one
with only one level of hierarchy.
S-Edit 16 User Guide
169