Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 16497
  • 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

Warnings for Breakdowns, not suppressing.

MarkGr15

Is there a way to make it so that in my spectre.out files (for Analog Simulation) does not suppress the warnings? 

If so, what do I need to do?

In the ADE->Simulation->Options Analog->Annotation->  I changed the maxwarns to a large number, and have the "warn" box checked.  When I do this, I do not see a change.

Here is an example output:

Warning from spectre at time = 6.84728 s during transient analysis `tran'.
WARNING (CMI-2756): ILDO1.I50.M152: Vbs(=6.13091 V) has exceeded vbs_max (=6 V).

tran: time = 6.847 s (34.2 %), step = 400 ms (2 %)

Warning from spectre at time = 7.24728 s during transient analysis `tran'.
WARNING (CMI-2756): ILDO1.I50.M152: Vbs(=6.24858 V) has exceeded vbs_max (=6 V).
Warning from spectre at time = 7.64728 s during transient analysis `tran'.
WARNING (CMI-2756): ILDO1.I50.M152: Vbs(=6.36624 V) has exceeded vbs_max (=6 V).

tran: time = 7.647 s (38.2 %), step = 400 ms (2 %)

Warning from spectre at time = 8.04728 s during transient analysis `tran'.
WARNING (CMI-2756): ILDO1.I50.M152: Vbs(=6.48391 V) has exceeded vbs_max (=6 V).
Further occurrences of this warning will be suppressed.

tran: time = 8.847 s (44.2 %), step = 400 ms (2 %)
tran: time = 9.647 s (48.2 %), step = 400 ms (2 %)

If there are any setting in the ADE that I can play with and adjust, that would be helpful.

thanks

Mark

Parents

  • HI Mark,

    > Is there a way to make it so that in my spectre.out files (for Analog Simulation) does not suppress the warnings? 

    I can only speak for the PDK I have used  - but it appears you are trying to observe all the warnings related to device parameters exceeding their respective voltage thresholds associated with a specific reliability target. If so, these warnings, I believe, are not generated by "spectre" - but rather by some code particular to a specific PDK. Hence, as is the case in the PDK I have used, the warnings (and supressions) are enabled by the use of the SKILL code that adds the voltage monitoring function.

    For example, I just ran a simulation using a 20V supply in a circuit where the maximum allowable MOS device voltage is about 1 V. No warnings were generated. However, when I invoked an feature that adds a reliability audit, the log file contains numerous warnings related to the obvious overvoltage conditions.

    Is there any chance you know anyone who supplies your PDK whom you might ask?

    Sorry I can't be more specific!

    Shawn

    I believe the clause you are refering to "Further occurrences of this warning with be supressed." only refers to the the

Reply

  • HI Mark,

    > Is there a way to make it so that in my spectre.out files (for Analog Simulation) does not suppress the warnings? 

    I can only speak for the PDK I have used  - but it appears you are trying to observe all the warnings related to device parameters exceeding their respective voltage thresholds associated with a specific reliability target. If so, these warnings, I believe, are not generated by "spectre" - but rather by some code particular to a specific PDK. Hence, as is the case in the PDK I have used, the warnings (and supressions) are enabled by the use of the SKILL code that adds the voltage monitoring function.

    For example, I just ran a simulation using a 20V supply in a circuit where the maximum allowable MOS device voltage is about 1 V. No warnings were generated. However, when I invoked an feature that adds a reliability audit, the log file contains numerous warnings related to the obvious overvoltage conditions.

    Is there any chance you know anyone who supplies your PDK whom you might ask?

    Sorry I can't be more specific!

    Shawn

    I believe the clause you are refering to "Further occurrences of this warning with be supressed." only refers to the the

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.