• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. spectre nodes info: pin names different than what is in...

Stats

  • Replies 3
  • Subscribers 132
  • Views 513
  • Members are here 0

spectre nodes info: pin names different than what is in schematic or input.scs

marcelpreda
marcelpreda 1 month ago

Hi *,

I'm trying to get the instances connectivity through hierarchy, the mapping hier.inst_name:pin to hier.net_name
I'm using the spectre  "info what=nodes"
It works, but I have two problems with some device models (the real model names were hidden, so I've use "abc", "xyz", ...)

#1 issue - for some devices instead of pin names in nodes.info, I get the the pin numbers.
It seems to happen for all capacitor and resistor types.

capacitor: C0 of zzz
1 : net392
2 : 0
Instead of "1", "2" preferable to have "p", "n".

#2 - Some devices are netlisted in input scs as caps C2 (net1 0 v_pwell) xyz value=11f wlratio=1 but on the nodes.info file I get a different type and a numbers of pins.

bsim4: C2 of abc
d : 0
g : net1
s : 0
b : 0

I had a look in the model files and the reason is that xyz 3 pins capacitor model is derived from a MOS card model (bsim4), like below (xyz - xyz_p - abc card model) :
xyz (p n b) xyz_p ...
* ...
* ...
ends xyz

xyz_p (n p n n) abc ...
*...
*...
ends xyz_p

abc (d g s b) abc_modelcard l=l w=w ad=ad as=as pd=pd ps=ps nrd=nrd nrs=nrs trise=trise
ends abc

model abc_modelcard bsim4 ....


Is there any option to get the pin names as they are in the .scs ?

  • for caps/res to get (p n)
  • for the other to get the pins from "top" model , e.g "(p n b) of xyz" insetad of "(d g s b) of abc"

Preferable some other spectre param/option , and then to parse 1-2 files, if there is a need to parse multiple files/db I'm OK with that too.
I have no control on models definition.

Thank you,
Marcel

Sorry for bad formatting, but when try to use "code" tags, the post was not submitted .

  • Cancel
  • Sign in to reply
Parents
  • marcelpreda
    marcelpreda 1 month ago

    Added the specre options

    saveOptions options save=all currents=all subcktprobelvl=3simulatorOptions options psfversion="1.4.0" reltol=1e-2 vabstol=1e-4 \
    iabstol=1e-10 temp=27 tnom=27 scalem=1.0 scale=1.0 gmin=1e-12 rforce=1 \
    note=yes maxnotes=5 warn=yes maxwarns=5 digits=5 cols=80 pivrel=1e-3 \
    sensfile="../psf/sens.output" checklimitdest=file \
    inlinesubcktcurrent=subckt useterms=name
    tran tran stop=100n write="spectre.ic" writefinal="spectre.fc" \
    method=euler annotate=status maxiters=20
    subckts info what=subckts where=rawfile
    designParamVals info what=parameters where=rawfile
    asserts info what=assert where=rawfile
    nodes_2 info what=nodes where=file
    terminals info what=terminals where=file
    saveOptions options save=all currents=all subcktprobelvl=3

    Maybe I've miss some useful option.

    Thank you,
    Marcel

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to marcelpreda

    Hi Marcel,

    I've checked, and I don't think there's any way to dump the nodes for subckt instances; it only outputs the leaf device information.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to marcelpreda

    Hi Marcel,

    I've checked, and I don't think there's any way to dump the nodes for subckt instances; it only outputs the leaf device information.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • marcelpreda
    marcelpreda 1 month ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks a lot.


    Best Regards,

    Marcel

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel

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.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information