Stats

Locked Locked
Replies 4
Subscribers 144
Views 16622
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SpiceIn reference library list

I have trouble getting SpiceIn utility to properly read in my reference library list, somehow only the first library in my list is properly included. This is how I call the command: spiceIn -param spiceIn.params

Here's how the output (spiceIn.log) header looks like: (notice only analogLib is in the library list; a weird "boaDMFileSys.so" library also appears in the list even though it is not specified in my param file)

=================== Spice In Log File ===================
Parameter file: /tmp/spiceInPa07316
Import Parameters: Netlist file name: /home/yyeo/and1_2x1.hsp
        Output library name: sandbox_yyeo
        Output View Type: schematic
        Schematic view name: schematic
        Netlist view name: netlist_tmp
        Reference Library List: analogLib boaDMFileSys.so sandbox_yyeo
        Import Sub-circuit List: top
        Top cell: top
        Device-mapping file name: dev.map
        Master Cell for Ground: gnd
        Cells to be Overwritten: <all>
        Schematic Generation parameter file: /tmp/schOpts_spiceInPa07316
        Simulator: spectre
        Output Simulator: spectre
        paramCaseValue: default
        Language: Spectre

The library sandbox_yyeo already exists.
Total number of files: 1.

Netlist File: /home/yyeo/and1_2x1.hsp.

...

Here's how my param file (spiceIn.params) looks like:

spiceInParams = list(nil
        'conn2schArgs   "-MIN_CROSSOVERS -FAST_LABELS"
        'language       "HSpice"
        'netlistFile    "/home/yyeo/and1_2x1.hsp"
        'outputLib      "sandbox_yyeo"
        'refLibList     "analogLib basic primitives esdLib"
        'devMapFile     "dev.map"
        'overwriteCells "all"
)

My Cadence version is IC 6.1.4.485. Thank you!

Parents

Yaosan Yeo over 13 years ago

I have some new issues with the SpiceIn utility. When I spice in a circuit, all the subckt will be created in the output library even if they can be found in one of my reference libraries listed. It seems to me that only primitives works with the reference library list.
For example, this is what I have (cell_a is a subckt of cell_b):
lib_a/cell_a/layout
lib_a/cell_a/schematic
lib_a/cell_a/symbol
lib_b/cell_b/schematic
If I try to spice in cell_b and specify lib_b as the output library, even if cell_a can be found in lib_a, which I have listed in the reference library list, the utility will not use it and will simply create a new cell_a in my lib_b.
Is there any easy way to NOT create a redundant cell_a in my lib_b and have the cell_b's schematic references lib_a/cell_a/symbol instead of lib_b/cell_b/symbol? Thanks!
Cancel
Vote Up 0 Vote Down

Cancel

Reply

Yaosan Yeo over 13 years ago

I have some new issues with the SpiceIn utility. When I spice in a circuit, all the subckt will be created in the output library even if they can be found in one of my reference libraries listed. It seems to me that only primitives works with the reference library list.
For example, this is what I have (cell_a is a subckt of cell_b):
lib_a/cell_a/layout
lib_a/cell_a/schematic
lib_a/cell_a/symbol
lib_b/cell_b/schematic
If I try to spice in cell_b and specify lib_b as the output library, even if cell_a can be found in lib_a, which I have listed in the reference library list, the utility will not use it and will simply create a new cell_a in my lib_b.
Is there any easy way to NOT create a redundant cell_a in my lib_b and have the cell_b's schematic references lib_a/cell_a/symbol instead of lib_b/cell_b/symbol? Thanks!
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.