• 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. Analysis on the extracted view

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 5281
  • 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

Analysis on the extracted view

sidm
sidm over 1 year ago

Hello All,

I wish to seek some advice on running STB analysis on the extracted view of the design. Running STB analysis on the schematic works fine where I have a probe instance selected as MOSFET gate terminal I1/M1/G. The same technique gives incorrect results when I use the extracted version of the MOSFET I1/MM1/G.


Any suggestions on possible ways to use the extracted version of the MOSFET for STB analysis instead of using metal resistor or other additions as described in the below link ?
https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1Od0000000tt0rEAA&pageName=ArticleContent
thanks
  • Cancel
Parents
  • sidm
    sidm over 1 year ago

    Hello All,

    Any suggestions  will be very helpful. 

    regards

    Sidm

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to sidm

    Does the device on the schematic have a multiplier or multiple fingers? If so, you're only going to end up probing one of the devices (the stb analysis needs either a probe device - iprobe or vsource - or a single pin of a single device). If that's the case, I think you will need to use the metal resistor approach.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to sidm

    Does the device on the schematic have a multiplier or multiple fingers? If so, you're only going to end up probing one of the devices (the stb analysis needs either a probe device - iprobe or vsource - or a single pin of a single device). If that's the case, I think you will need to use the metal resistor approach.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • sidm
    sidm over 1 year ago in reply to Andrew Beckett

    thanks a lot for the reply Andrew. Yes the MOSFET has multiplier of 2 and finger=3. I see the extracted view having multiple instantiations of that MOSFET with MM1__1, MM2__2.... MM6__6 notations 

    As you mentioned stb analysis needs either a probe device - iprobe or vsource - or a single pin of a single active device. Is there a way to use the Pin of a passive device pin instead of active device for STB analysis ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to sidm

    Oh, hang-on - I've noticed from your picture above that you've used the Probe Instance (I assume that /I1/MM1/G isn't an instance but a pin). You should have used Probe Terminal (although that still wouldn't have worked because of your m-factor and increased finger count). 

    You can use the pin of a passive device pin - it doesn't matter whether it's a passive or an active device. You give it the pin of a device and then (in essence) an iprobe is inserted within the simulator in series with that device pin, and the loop gain is measured through that inserted probe. In other words, there's nothing special you need to do to enable this - provided that you use Probe Terminal. Probe Instance is fine when probing an iprobe or a vsource, but less useful when probing an active device directly because that then uses the device-based algorithm (see "spectre -h stb") which gives you the feedback within the active device rather than a more usual feedback loop. 

    The only restrictions on using device pins (when using Probe Terminal) are when using differential and common-mode  stability because they have to (currently) be a leaf device terminal (so it's no good if the device is in a subckt). There are enhancement CCRs to change this behaviour.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sidm
    sidm over 1 year ago in reply to Andrew Beckett

    thanks a lot Andrew for the details. In the past when I tried the Probe Terminal option it wasn't working for me, in the sense that stability analysis form doesn't show the probe terminal after hitting the apply/Ok button. Screenshot below.

    Probe terminal text box entry doesn't show in the analysis in test setup : 

    I am using IC618 ISR31 and Spectre 21.1 ISR17

    regards 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to sidm

    What appears next to the stb line in the list of analyses is just a "summary" of the setup. It's not possible to fully include all details of the analysis setup in a few characters, but it doesn't mean that the settings have not been accepted. It will work - it's just that the function used to try to summarise the setup for visual display hasn't been updated to cope with Probe Terminal. You can still use, and the proof of the pudding is what is in the netlist.

    So it almost certainly was working (as this has worked for some time). Never use the summary info next to the analysis as an indication of anything important!

    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