Stats

  • Locked Locked
  • Replies 2
  • Subscribers 63
  • Views 6464
  • 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

Getting Operating Point Data in PEX (extracted)

FPMKh

Hi,
My virtuoso and spectre version: ICADVM20.1-64b.NYISR30.2
This is no longer a question. I had a question and I found the answer so I edit the post in case it might be helpful for others.
When I want to check a voltage inside the hierarchy, I usually use a deepprobe. For example, in a schematic view, I type "I0.ICH_I.I_OPAMP_RC.I11.vip" in a Hierarchical Node of the instance deepprobe from analogLib and it brings me the node vip to the top level. Now if I want to do the same in an extracted view, if I use a DSPF file, I type: "I0.XICH_I\/XI_OPAMP_RC\/XI11\/vip" and it again shows me the net voltage. I added an "X" in front of the cell name and used "\/" instead of ".". 
If I want to see the DC operating point of a device, say region or Vth, I use the following expression in the Assembler: OP("/I0/ICH_I/I_OPAMP_RC/I11/Mip" "region") and it works fine both for schematic and extraction and no edit will be needed.

Parents

  • It's a bit overkill to use deepprobe just to monitor an internal node in the hierarchy; the original intention of this component (which was created by me in the first place) was to allow you to make connections down in the hierarchy - i.e. to inject signals or add loads, or potentially add test bench-level components inserted into the hierarchy. 

    There's a couple of approaches that could be taken here:

    1. If you're extracting with Quantus, then you could create a smartView instead of a DSPF file and then ADE would translate the out-of-context schematic name into the corresponding point in the smartView (smartViews have efficient storage of the parasitics and netlist, quickly, to a DSPF for simulation).
    2. If using a third-party (non-Cadence) extractor then we have some other flows that could work with a DSPF file - you should contact customer support or your account team for details; these too can handle mapping of schematic names to the name used in the DSPF.

    Failing that, you can use the netlist name syntax (i.e. using dot as hierarchy separator rather than /) and you can check this in the results browser for example. Looking at the name you showed for a voltage, it would appear to be:

    OP("I0.XICH_I\/XI_OPAMP_RC\/XI11\/Mip" "region")

    Oh, I just saw that you'd edited the post after submitting it. I hate it when that happens as I spend time writing the answer having seen the email only to find the question is no longer what I thought it was (I much prefer people reply to the original post explaining that they found the solution, as at least then there's an indication it's been dealt with).

    So feel free to ignore what I've just written!

    Andrew

Reply

  • It's a bit overkill to use deepprobe just to monitor an internal node in the hierarchy; the original intention of this component (which was created by me in the first place) was to allow you to make connections down in the hierarchy - i.e. to inject signals or add loads, or potentially add test bench-level components inserted into the hierarchy. 

    There's a couple of approaches that could be taken here:

    1. If you're extracting with Quantus, then you could create a smartView instead of a DSPF file and then ADE would translate the out-of-context schematic name into the corresponding point in the smartView (smartViews have efficient storage of the parasitics and netlist, quickly, to a DSPF for simulation).
    2. If using a third-party (non-Cadence) extractor then we have some other flows that could work with a DSPF file - you should contact customer support or your account team for details; these too can handle mapping of schematic names to the name used in the DSPF.

    Failing that, you can use the netlist name syntax (i.e. using dot as hierarchy separator rather than /) and you can check this in the results browser for example. Looking at the name you showed for a voltage, it would appear to be:

    OP("I0.XICH_I\/XI_OPAMP_RC\/XI11\/Mip" "region")

    Oh, I just saw that you'd edited the post after submitting it. I hate it when that happens as I spend time writing the answer having seen the email only to find the question is no longer what I thought it was (I much prefer people reply to the original post explaining that they found the solution, as at least then there's an indication it's been dealt with).

    So feel free to ignore what I've just written!

    Andrew

Children

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.