• 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. How to know that ALL MOS are in saturaion region by running...

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 127
  • Views 17200
  • 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

How to know that ALL MOS are in saturaion region by running ocean script?

MOSMOS
MOSMOS over 12 years ago

I want to know how to write a ocean script that can create a file to display all MOS' region,but I don't know the function.

How to know that where are All MOS in ??

THANKS! 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    If you're using OCEAN, and you've run a DC operating point simulation, then you can use the report() function to do this.

    For example:

    analysis('dc ?saveOppoint t)
    run()
    selectResult('dcOpInfo)
    report(?param "region")

    You'll get the region of each device returned as a number. If you look at "spectre -h modelType" - e.g. "spectre -h bsim4" you get:

     1       region=triode     Estimated operating region. Spectre outputs the number (0-4) in a rawfile.
                              Possible values are off, triode, sat, subth, and breakdown.

    and for "spectre -h bjt" you get:

     3       region=fwd        Estimated operating region. Spectre outputs number (0-4) in a rawfile.
                              Possible values are off, fwd, rev, sat, and breakdown.

    So the numbers correspond to the various regions. So for a MOS, 2 means it is in the saturation region.

    The previous reply talking about CDF parameters is not relevant - that was (presumably) talking about the instance parameter region - which is merely a hint to the simulator as to which region the device is in, to help with DC convergence (an option that is rarely set, because it's not that practical to set it on each transistor, and anyway it's not the final region - just a clue to the simulator to tell it (say) that the device is off and hence to expect it to be off when trying to reach DC convergence).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    If you're using OCEAN, and you've run a DC operating point simulation, then you can use the report() function to do this.

    For example:

    analysis('dc ?saveOppoint t)
    run()
    selectResult('dcOpInfo)
    report(?param "region")

    You'll get the region of each device returned as a number. If you look at "spectre -h modelType" - e.g. "spectre -h bsim4" you get:

     1       region=triode     Estimated operating region. Spectre outputs the number (0-4) in a rawfile.
                              Possible values are off, triode, sat, subth, and breakdown.

    and for "spectre -h bjt" you get:

     3       region=fwd        Estimated operating region. Spectre outputs number (0-4) in a rawfile.
                              Possible values are off, fwd, rev, sat, and breakdown.

    So the numbers correspond to the various regions. So for a MOS, 2 means it is in the saturation region.

    The previous reply talking about CDF parameters is not relevant - that was (presumably) talking about the instance parameter region - which is merely a hint to the simulator as to which region the device is in, to help with DC convergence (an option that is rarely set, because it's not that practical to set it on each transistor, and anyway it's not the final region - just a clue to the simulator to tell it (say) that the device is off and hence to expect it to be off when trying to reach DC convergence).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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