Stats

  • Locked Locked
  • Replies 4
  • Subscribers 127
  • Views 15370
  • 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

Pins are not annotated using subcircuit (netlist)

Johanny Saenz

Hi all.

I'm following the procedure depicted on https://community.cadence.com/cadence_blogs_8/b/rf/archive/2009/01/07/tip-of-the-week-how-to-simulate-a-subcircuit-netlist-with-spectre-in-ade 

My subckt declaration on the netlist matches with the pins on the symbol. 

subckt adc_sh_comparator DVDD VDDA1 VDDA2 VSS VSSA1 \
VSSA2 cfg_cmp_i\(7\) cfg_cmp_i\(6\) cfg_cmp_i\(5\) cfg_cmp_i\(4\) \
cfg_cmp_i\(3\) cfg_cmp_i\(2\) cfg_cmp_i\(1\) cfg_cmp_i\(0\) \
cmp_3v3_o en_i isnk0_i isnk1_i isnk2_i isnk_pa1_i isnk_pa2_i \
isnk_pa3_i isrc_pa1_o isrc_pa2_o isrc_pa3_o track_i vdac_i vin_i \
vout_db_o vout_o vrefp_i

I tried the procedure with another schematic and it worked.

So I suspected that I have to clean or redefine some pin order.

Thanks in advance

  • Andrew Beckett

    That's very interesting, but did you have a question or something that didn't work? If so, what was it?

    Andrew.

  • Johanny Saenz
    Excuse me, for some reason I deleted the error line. When I run the simulation it gives me the following error:
    ERROR (SFE-45): "input.scs" 68: `COMP': An instance of `adc_sh_comparator' needs at least 31 terminals (but has only 0).

    The netlister is not annotated my pin order. So I suspect that I need to clean or redefine something on my view.
  • moralope

    Did you find a solution for this problem? I am facing the same issue when following that procedure to simulate a .spi netlist. It would be nice to know how you solved it.

    Thanks!

  • Johanny Saenz
    No. I didn't. You could try to recreate the symbol with the connectivity information from layout/schematic.

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.