Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 16087
  • 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

Importing spectre netlist with arrayed net names

Steven Mikes

I have a netlist that I would like to import to a schematic. It contains subcircuits that have arrayed pins, e.g.

I0 (VDD VSS A\<2\> A\<1\> A\<0\>) myInstance

The schematic/symbol for myInstance in Cadence have the pins as  VDD VSS A<2:0>

I'm getting an error when importing that would look like this for this example:

Hush! For master cell 'refLib.myInstance:symbol' terminal order has less terminals than on instance. Expected: 5 Found: 3

How do I make the tool assign the terminals properly?

Thanks!

Parents

  • Hi Steven,

    You'd need to modify your netlist so as to have the A terminals placed in a bus that match the CDF termOrder:

    I0 (VDD VSS A<2:0>) myInstance

    I myself use a script to do this (when extracting a layout to a .dspf spice-equivalent netlist, before I spice-it-in to get the extracted schematic).
    This script also proceeds to the '< >' and '( )' to=> '[ ]' changes wherever necessary in the spice netlist (usually where there's ':' or '#' right after the '>').

    I mention this because one might get the same "Expected:5 Found:3" error in case a line in the netlist is in the form:
    Xinst(1):Instance pin1 pin2 pin3 InstanceName
    The '()' brackets act like a separator and Spice-In would consider '1' and ':Instance' as 2 extra terminals. Whereas the following causes no problem:
    Xinst[1]:Instance pin1 pin2 pin3 InstanceName

    Regards,
    Matthieu

Reply

  • Hi Steven,

    You'd need to modify your netlist so as to have the A terminals placed in a bus that match the CDF termOrder:

    I0 (VDD VSS A<2:0>) myInstance

    I myself use a script to do this (when extracting a layout to a .dspf spice-equivalent netlist, before I spice-it-in to get the extracted schematic).
    This script also proceeds to the '< >' and '( )' to=> '[ ]' changes wherever necessary in the spice netlist (usually where there's ':' or '#' right after the '>').

    I mention this because one might get the same "Expected:5 Found:3" error in case a line in the netlist is in the form:
    Xinst(1):Instance pin1 pin2 pin3 InstanceName
    The '()' brackets act like a separator and Spice-In would consider '1' and ':Instance' as 2 extra terminals. Whereas the following causes no problem:
    Xinst[1]:Instance pin1 pin2 pin3 InstanceName

    Regards,
    Matthieu

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.