Files Needed for Simulation in the Command-Line Interface

Before you start a simulation in the UNIX environment, you must create the following files in the simulation run directory:

• si.env file
• control file

The system creates these files automatically when you run a simulation using the Netlist and Simulate form in the SE GUI, but you must manually create the files if you want to use the command-line interface to run a simulation.

si.env file

The si.env file directs SE on which design to simulate and what simulator to use.

The following table lists the variables you must define in the si.env file. Each interface might store additional simulator-specific variables in the si.env file.

Variables to be defined in the si.env file

Variable	Description
simSimulator	Simulator to be run
simLibName	Name of the library containing the top-level cellview
simCellName	Name of the top-level cell to be simulated
simViewName	View name of the top-level cell to be simulated
simHost	Host name of remote simulator. This is optional.

A sample si.env file:

simLibName = "testLib"
simCellName = "74169"
simViewName = "schematic"
simSimulator = "silos"
simHost = "cds642"

control file

You can directly specify all your customizations in the control file or you can use SE substitution functions to translate names and merge the changes in other files. For example, to merge an input stimulus file named simsub.inp into the control file, prefix the file name with an exclamation mark and enclose the text in square brackets. For example:

[!simsub.inp] 

If simsub.inp is not in the current simulation run directory, specify the full path as follows:

[!/<level1InstName/.../levelnInstName>/simsub.inp]

Related Topics

simSimulator (SKILL Function)

simLibName (SKILL Function)

simCellName (SKILL Function)

simViewName (SKILL Function)

simHost (SKILL Function)

Sample si.inp File Generated for Cadence SILOS II

Return to top