• 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 SKILL
  3. Parameters and pcells in ADE XL

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 14761
  • 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

Parameters and pcells in ADE XL

kvntien
kvntien over 12 years ago

Hi all,

 I have a schematic pcell that generates an n-stage chain of (non-pcell) instances, each with different instance parameters.  To do this, I have a pcell string parameter 'numStages' (also defined in the CDF for the cell), and something in the pcDefinePCell let block like

n = atoi( numStages )
for( inst 1 n ....

I'd like to be able to sweep this parameter for optimisation in ADE by assigning it a design variable. First problem I ran into is, of course, when pcell evaluation happens, numStages is a text string representing a design variable, so atoi( numStages ) is nil. To get around that, I have

if( n == nil then n=round( VAR( numStages ) ) ) 

Not the most foolproof, but at least it seems to work in ADE L. When I try to move it to ADE XL for global optimisation, it fails: all instances of the pcell at every design point are instantiated as if numStages were set equal to the value it takes on in the first design point.

Is this due to the pcell evaluation only happening once, then ADE XL just changing the parameter declaration line in subsequent netlists? Either way, does anyone have any insight into how I can make this work? Or is this a fool's errand... 

Thanks,
Kevin 

  • Cancel
Parents
  • kvntien
    kvntien over 12 years ago

    Got it! Thanks for confirming that my intuition about what was going on was correct. At the very least, this info will get filed away and hopefully solve an issue for me in the future =]

    Thanks,
    Kevin 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • kvntien
    kvntien over 12 years ago

    Got it! Thanks for confirming that my intuition about what was going on was correct. At the very least, this info will get filed away and hopefully solve an issue for me in the future =]

    Thanks,
    Kevin 

    • 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