• 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. pPar not works for intiger CDF parameters

Stats

  • Locked Locked
  • Replies 17
  • Subscribers 145
  • Views 28742
  • 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

pPar not works for intiger CDF parameters

Sarvani
Sarvani over 13 years ago

 Hi all,

        Is pPar works for all CDF parameters? I need to pass intiger numbers (like no. of fingers) from top level to bottem level in schematic. But when I enter pPar(NF) through edit object properties options then it doesn't work's. How can I get this intiger values to bottom level? Let me know if any other set up is needed.

thankyou,

sarvani

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

    Sarvani,

    You can only use pPar() on CDF parameters of type string, which have parseAsCEL set to Yes. You can only use expressions (including operators and math functions) on string fields, and if they are going to be interpreted, it has to know it should be treated as a component expression language (a.k.a. Analog Expression Language) expression. If the CDF parameter is defined as an int or a float, you can only set the value to be an int or a float; an expression would not be an int or a float and so it cannot be used.

    It's quite unusual for foundry PDKs to be using int or float parameters - it sounds as if something is incorrect with the setup and it hasn't been designed with ADE in mind.

    Regards,

    Andrew.

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

    Sarvani,

    You can only use pPar() on CDF parameters of type string, which have parseAsCEL set to Yes. You can only use expressions (including operators and math functions) on string fields, and if they are going to be interpreted, it has to know it should be treated as a component expression language (a.k.a. Analog Expression Language) expression. If the CDF parameter is defined as an int or a float, you can only set the value to be an int or a float; an expression would not be an int or a float and so it cannot be used.

    It's quite unusual for foundry PDKs to be using int or float parameters - it sounds as if something is incorrect with the setup and it hasn't been designed with ADE in mind.

    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