• 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 SKILL
  3. current in subckt cannot be saved, if the subckt is a PEX...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 17492
  • 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

current in subckt cannot be saved, if the subckt is a PEX netlist in Spectre lang format.

rickyuexu
rickyuexu over 8 years ago

Dear all,

I have a test bench for just one inverter, as shown below:

I want to run postlayout simulation for this inverter, specifically want to save the current flowing into the drain of T0. The parasitics extracted netlist (in Spectre format) of the inverter contains 3 files, and was generated by Calibre xRC:

inv.spectre.pex.netlist

inv.spectre.pex.netlist.inv.pxi

inv.spectre.pex.netlist.pex

 

 

First, I created the netlist of the test bench using ADE L, and modified it to include the parasitics extracted netlist of the inverter (I0). The netlist is like follows:

Second, I saved an ocean script from ADE L, and it looks like this:

Note: NMOS T0 in the original cell becomes becomes XMT0 in the extracted netlist, as can be seen in the file "inv.spectre.pex.netlist":

When I run this script, the current at terminal "/I0/XMT0/D" is not saved, even though I have specified that in the script.

The log file says

Output and IC/nodeset summary:

                 save   3       (voltage)

And these are just "/OUT" "/CK" "/I0/N_OUT_MT0_d", as specified in the script. No current is saved. I checked that in the result browser as well.

Could anybody tell me how to make it work? I found that I can save current in a subckt if the subckt is in Calibre view. However, for a big layout, it takes too much time to generated a Calibre view. To generated a Spectre format extracted netlist is much faster. This is why I want to use Spectre extracted netlist instead.

Thank you very much!

  • Cancel
  • rickyuexu
    rickyuexu over 8 years ago
    PS:
    I've verified the terminal name "D" in "/I0/XMT0/D" is the name used by the model file.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rickyuexu
    rickyuexu over 8 years ago
    And my Virtuoso version is IC6.1.7-64b.500.1
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    If using a name which starts with a "/", you are specifying a schematic name (well, it doesn't have to be a schematic, but it's a name in Virtuoso's namespace). This needs to be mapped (during netlist assembly) to the name that actually appears in the netlist. Given that the subckt for the inv cell is coming from a netlist, it's a name that isn't in the schematic and so can't be mapped by the netlister - you can only use such names for things that were actually netlisted.

    I think it would work if you used "I0.XMT0:D" or "I0.XMT0:1" (i.e. the native spectre hierarchical names). If a name doesn't begin with a "/" it is assumed to be in the simulator namespace and so isn't mapped.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rickyuexu
    rickyuexu over 8 years ago
    As you suggested, "I0.XMT0:1" worked! Thank you so much for helping me to resolve this problem that has plagued me for a long time!
    • Cancel
    • Vote Up 0 Vote Down
    • 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.

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

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