• 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. MDL Autostop Using cross and freq Functions

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14199
  • 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

MDL Autostop Using cross and freq Functions

baltacican87
baltacican87 over 6 years ago

Hello,

I am using Virtuoso version IC6.1.7.

I would like to termiante a transient simulation on an event using autostop with MDL option. My circuit is a 5-stage static inverter ring oscillator. I provide a ramp on vdd and modulate the output frequency at node vout. The frequency rises from ~1GHz to ~2GHz during the transient simulation and I can observe this using the calculator function freq. In my MDL file, create an event which is triggered when the frequency crosses 1.5GHz:

alias measurement tran_autostop {
export real Tcross
run tran
Tcross = cross( sig=freq(sig=V(vout), thresh=0.5, dir='rise), dir='rise, n=1, thresh=1500000000.0 )
}
run tran_autostop

However, the simulation does not stop. What do I need to do to have the simulation stopped when this event (frequency's crossing a threshold) is triggered?

Many thanks in advance.

Best regards,

Can

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

    Hi Can,

    From the documentation, only a limited number of functions (particularly things like deltax and delay) that identify particular events can trigger auto-stop. The challenge with the approach  you are taking is that normally freq runs at the end of the simulation rather than continuously during the simulation.

    I'm not sure there's an alternative way of doing this using autostop (I wondered about using deltax but that normally triggers auto-stop as soon as the delta has been measured, not when the delta is in a certain range). So this would need an enhancement request via customer support.

    Regards,

    Andrew

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

    Hi Can,

    From the documentation, only a limited number of functions (particularly things like deltax and delay) that identify particular events can trigger auto-stop. The challenge with the approach  you are taking is that normally freq runs at the end of the simulation rather than continuously during the simulation.

    I'm not sure there's an alternative way of doing this using autostop (I wondered about using deltax but that normally triggers auto-stop as soon as the delta has been measured, not when the delta is in a certain range). So this would need an enhancement request via customer support.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • baltacican87
    baltacican87 over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    Many thanks for your explanations. I didn't know that some of the functions are evaluated at the end of the simulation.

    Best regards,

    Can

    • 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