• 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. ADE: is it possible to select DSPF nodes for PNOISE simulation...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 13906
  • 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

ADE: is it possible to select DSPF nodes for PNOISE simulation?

dontpanic
dontpanic over 5 years ago

Hi! I am trying to run a triggered PNOISE analysis on a extracted design using a DSPF view, but I'm unable to specify in ADE the triggering nodes.

In my original PNOISE settings (run over the pre-layout schematic) the trigger event is defined on the following nodes (which I selected with the mouse on the schematic view):

/DUT/LATCH<5>.vOUTp and /DUT/LATCH<5>.vOUTm

which the netlister translates into the following directive in the netlist:

pnoise pnoise start=SIM__FREQDOMAIN__Fstart stop=SIM__FREQDOMAIN__Fstop \
    dec=SIM__FREQDOMAIN__Npoints_per_decade pnoisemethod=fullspectrum \
    noisetype=sampled measurement=[pm0] annotate=status
 pm0 jitterevent trigger=[DUT.LATCH\<5\>.vOUTp \
    DUT.LATCH\<5\>.vOUTm] triggerthresh=(PNOISE__vREGENd) \
    triggernum=1 triggerdir=rise target=[DUT.LATCH\<5\>.vOUTp \
    DUT.LATCH\<5\>.vOUTm]

However, when I try to switch to the DSPF view for my DUT (using a config view), I cannot specify anymore the above nets for defining the PNOISE trigger.

I tried, without success:

  • To manually type the node names in the ADE PNOISE dialog; but when I press the "change" button, ADE complains (e.g. "Couldn't find net named "DUT.LATCH\<5\>.vOUTp" in the design")
  • To copy the pnoise analysis definition in a text file and pass it to ADE as a .scs model file; but the netlister includes it in the netlist before the PSS definition, so Spectre ignores it (because it didn't run first a PSS)

Any helps is greatly appreciated!!!

Thanks and regards, Jorge.

P.S. Apparently someone had the same problem long time ago:

https://community.cadence.com/cadence_technology_forums/f/rf-design/35039/unable-to-select-extracted-view-nets-for-pnoise-simulation

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    The other post was more about an extracted view, but customer support would be your best bet (I don't have time to put together an example to try this myself). A workaround might be to create an include file (with .scs suffix) with both the pss and pnoise analyses in.

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • dontpanic
    dontpanic over 5 years ago in reply to Andrew Beckett

    Hi Andrew! Thanks so much for the idea, adding the PSS analysis also in the include file did the trick!
    (I'll try to file a case anyway; hopefully support for DSPFs nodes in the PNOISE dialog window could added in the future)

    Thanks and regards, Jorge.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Marc Heise
    Marc Heise over 5 years ago

    Hi Jorge,

    ADE/Maestro tries to verify the existence of the nodes you specify in the forms. This is failing in your case since the DSPF isn't mapped to the schematic names and parsed. ( We are working on that part )

    What you can try is to:

    1. Disable this check in the unix env before starting virtuoso with:

    setenv ADE_SKIP_NODE_CHECK YES

    2. Finding the right nodes in your DSPF and adding the net name into the pss form using the spice syntax.

    You would need to run IC6.1.8 / ICADVM18.1 ISR6  or above , since the Pnoise form was ignoring that env switch before this release !

    Kind regards,

    Marc

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • dontpanic
    dontpanic over 5 years ago in reply to Marc Heise

    Thanks for this alternative solution, Marc; it totally works!!! Smiley

    Best regards, Jorge.

    • 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