• 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. Overriding specifications with VAR("...") expressions

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 1090
  • 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

Overriding specifications with VAR("...") expressions

rod1
rod1 over 3 years ago

Hello,

I have an AGC amplifier whose noise specifications depends on the gain step I'm at, temperature and corners.

I initially tackled this with some global variables that computes for me my noise spec depending on the gain step and temperature.
At the moment my specs look like this (I set it up using ADE Assembler):

For the corner-dependent spec, I have another variable called spec_noise_max_153kHz, which is the number I have to use for corners other than TT. I was planning to use this variable when overriding the spec for the other corners.

Unfortunately, I just found that, even though I'm allowed to use global variables in my specifications, I'm not allowed to use them when overriding them.

I could replace the spec_noise_... variable by a number, but the other variable I can't easily replace, as it comprises a bunch of nested ternary expressions which save me having to hardcode specs according to gain step, as well as a not having to create a new test for every new gain step whose noise I want to test.

The Virtuoso version I'm using is the following:

Being able to use VAR("...") expressions in the specs but not being able to when overriding them seems inconsistent to me. At first sight at least. I was wondering if this has been tackled in later versions of Virtuoso.

Thanks in advance for your help

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

    There's an old CCR (from when this was implemented in ADE XL) for this - CCR 1351018. It's not planned, and the issue is still there in the latest versions.

    I guess one workaround might be to define a common variable, and have that variable be set in the corners so that the spec can vary by corner that way?

    Regards,

    Andrew

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

    There's an old CCR (from when this was implemented in ADE XL) for this - CCR 1351018. It's not planned, and the issue is still there in the latest versions.

    I guess one workaround might be to define a common variable, and have that variable be set in the corners so that the spec can vary by corner that way?

    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