• 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. axlMapInstTermToNet() and DSPF view

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 14360
  • 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

axlMapInstTermToNet() and DSPF view

twen
twen over 7 years ago

Here is my Vituoso version: "@(#)$CDS: virtuoso version ICADV12.3-64b 11/21/2017 19:22 (sjfhw308) $"

I am trying to save and plot the signal connected to the gate terminal to a transistor by using axlMapInstTermToNet(). This function works well with the schematic. It also works well with the StarRC view. Since netlisting of the StarRC view takes really long time for larger designs, I use the extracted DSPF views instead. My problem now is that axlMapInstTermToNet() does not work with DSPF views.

Here is my question: Are there any other skill functions or customised skill scripts to map the terminal name to a net name in the final netlist including the dspf view?

What I am doing now is to dump the final netlist from the Spectre simulator by adding this

    nodesinfo info what=nodes where=file file="nodes.info"

in the netlist and run a empty simulation to dump nodes.info. Now I can parse the nodes.info so that I can map any terminal to a net name including the DSPF views. However, this approach need me to dump this file first before I can do the map properly and the terminal names in nodes.info are different from the schematic terminal names, i.e, "g" vs "G" or "GATE," and I do not know how to map the schematic terminal names to Spectre terminal names. I checked asiMapTerminalName(), ciMapTerm(), ciMapTermName(), and hnlMapTermName() and still could not figure out how to do the terminal map properly. I feel that it has something to do with how the PDK names the terminals vs how Cadence schematic names the terminals and how the netlister translates and maps them.

Thanks,

TJ

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    TJ,

    The problem is that the DSPF file is a bit of a black box as far as the netlister is concerned. With extracted views (both those from Cadence extractors and other similar tools), the netlister still traverses an OA database and writes out a netlist; because of this it can know something about the mapping. However, with DSPF it's harder.

    That said, there has been work to support "out of context probing" for DSPF views (I think it's only when using DSPF views, rather than an including DSPF file). Not sure the current status of this with regard to APIs (sorry - I'm catching up from a week of vacation and now am travelling with work for 2 weeks, so my opportunity to do detailed investigation is low). So I'd suggest contacting customer support on this and then we can work through your requirements in a bit more detail.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • twen
    twen over 7 years ago in reply to Andrew Beckett

    Hi, Andrew,

    Thank you for the reply. I've already created a Case# 46265777 for this. I am using DSPF views and I do not see how I can do the "out of context probing" with them.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to twen

    Hi TJ,

    I see that customer support are filing a CCR on your behalf for this.

    BTW, the Forum Guidelines respectfully ask for you to not post the same question in the forums if you have an open case on the topic with customer support. I see you filed the case at about the same time as posting your question here. This guideline is really to prevent duplication of work with people who respond here as well as the application engineer assigned to the support case.

    Kind Regards,

    Andrew.

    • 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