• 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. calcVal and corner groups

Stats

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

calcVal and corner groups

TempViator
TempViator over 3 years ago

Hi,

In performing a set of calibration trim tests, I found a reason I'd like to use corner groups with calcVal.  It appears this is not allowed (per tool manual, in my version, which is IC6.1.8-64b.500.7). 

Here is why I'd like that capability:

At this time I have incomplete specs for a bias current and a reference voltage, which are inputs to my circuit, but I do know their min/mean/max values.  I would like to perform calibration over all 9 combinations of bias and reference, resulting in 9 trim codes. Ultimately this will feed Monte Carlo runs. Later, when the bias and reference blocks are designed, I can simply run calibration tests on them ahead of my block to get actual values for each MC run.

It would be very convenient if subsequent tests could find the matching corner group value to choose the right trim code from the set.

As I read the calcVal documentation, it seems the ?matchParams might do this across multiple non-group corners ("This argument considers the corners and sweep parameters in the same way."), but the ?cornerName will not accept corner groups.

When it is a true single corner, everything works.  When I make a corner group with >1 values to a parameter, I get an error about not finding a corner with the right name (because it is now really a corner group, not a corner, I assume).

Functionally, I'd like this to behave as if a corner group would be matched  correctly and the right trim code gets used when a subsequent test matches the parameters.

I suspect there may be a solution using ?matchParams, but avoiding specifying a ?cornerName,  but I don't see it. Is there a compact way to get this working?

Thanks!

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

    Could you please contact customer support? That would be the best way of working through this.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • TempViator
    TempViator over 3 years ago in reply to Andrew Beckett

    Ok, will do.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • TempViator
    TempViator over 3 years ago in reply to Andrew Beckett

    Ok, will do.

    • 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