Stats

  • Replies 2
  • Subscribers 125
  • Views 471
  • Members are here 0

Netlisting 'config' view with SPICE source file... CDF parameter m= on symbol is not printed in netlist instance call

JeffBeck

Hello,

I am successfully netlisting and simulating a testbench 'config' view for Spectre with the primary instance pointing to a SPICE source file... (an extracted netlist w/ parasitics).

However, the CDF m= parameter on the symbol in the testbench schematic does not get printed in the netlisted instance call to the subckt.  I could use iterated instances, instead, to enlarge the circuit load (this works), but makes for a huge simulation when iterations are 1000's.  This is why I would like to use m= instead.

Below is the symbol instance within the schematic.  When netlisting the 'config' view, I0<1:0> is expanded appropriately to two instance calls I0<1> and I0<0>, but the mfactor (m=6) is not netlisted.

The interesting thing is - if I netlist 'schematic' view instead of 'config' view, the m=6 is printed at the end of the instance calls, as a parameter, just as expected, and simulates fine.

Any ideas on how to print m= in the netlist instance calls when pointing to a SPICE source file in the 'config' view?

Thanks,

Jeff

  • Hi,

    Can you update the CDF properties of this block and add 'm' in instParameters field? This prints out 'm' in the instance calls of the cell specified as external Spice netlist.

  • Hi Saloni,

    Thank you very much.  This worked, although I also needed to add the term list from the Spice subckt netlist to the termOrder field as well as the 'm' to the instParameters field.

    Part of my confusion about this was that the m= parameter is added as the Library Scope for my library, so that it shows up as an option for every cell's properties.

    So, when I was adding the m to the instParameters field, I was doing this, also, in the Library Scope.

    For the solution to work, though, I needed to add the m and the terminal list to the Cell Scope instead.

    Thanks again!

    Jeff Beck

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.