B

---

Migrating from CDL In to Spice In

---

CDL In has been replaced with Spice In on OpenAccess to import CDL netlists into Virtuoso. In addition to CDL, Spice In can import HSpice, Spectre, and SPICE netlists into Virtuoso.

Spice In Advantages over CDL In

Spice In offers the following advantages over CDL In:

• Using Spice In, you can import both kinds of CDL netlists — those created from an analog component-based schematic using an analog CDL netlister and those created from a digital component-based schematic using a digital CDL netlister.
  CDL In is capable of importing CDL netlists created only from a digital component-based schematic using a digital CDL netlister.
• Spice In saves CDF and Simulation Information data, which helps integration of ADE with VSE and VLE.
  CDL In does not save CDF and Simulation Information data.

If you still want to use CDL In, you can run it from the command line in the batch mode by using the following command:

nino cdlin templateFile

You must specify a template file when you use the nino command to run CDL In. The nino command is the non-interactive, batch mode version of CDL In.

Differences Between Spice In and CDL In

This section describe how the Spice In parameter and device-map files are different from those of CDL In.

Differences in Parameter File

The following table provides a sample CDL In parameter file and a sample Spice In parameter file for comparison.

cdlInKeys = list(nil
  ’searchPath   "."
  ’cdlFile   ""
  ’opusLib   ""
  ’usrSkillFile   ""
  ’primaryCell   ""
  ’caseSensitivity   "preserve"
  ’hierarchy   "full"
  ’cellTable   ""
  ’viewName   "netlist"
  ’viewType   ""
  ’refLibList   ""
  ’pr   nil
  ’skipDevice   nil
  ’globalNodeExpand   "full"
  ’schGenOption         t 
  ’schGenParamFile      "conn2sch_param"
  ’devMapFile     "/usr1/home/devMap"
  ’overwriteExistingCVs   "selected"
  ’overwriteExistingCVsList   "RSLATCH "
)

spiceInParams = list(nil
  ’simName "spectre" 
  ’netlistFile ""
  ’netlistViewName "netlist"
  ’schematicViewName "schematic"
  ’language "auto"
  ’devMapFile ""
  ’targetLib ""
  ’topCell "top"
  ’logFile "spiceIn.log"
  ’importDesignAs "schematic"
  ’errMsgFile "spiceIn.err"
  ’refLibList ""
  ’overwriteCells "all"
  ’overwriteCellsList ""
 )

Differences in Device-Map File

The format of the device-map file for Spice In is different from that required by CDL In. In CDL In, among other properties you can also specify propMatch, termOrder, propMap, and addProp properties to correctly map a device to a primitive device. Spice In requires only the devSelect statement. See Creating a Device-Map File in Chapter 4, “Netlist Import Using Spice In” for details on device-map file format that Spice In expects.