Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 4884
  • 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

ADE - Copy Design Variables From Cellview - CDF parameters

Adrian Nistor

Hello,

I have a schematic with one instance. That instance has 3 parameters defind in CDF:
Param1 (float) = 1.23
Param2 (string) = "1.23"
Param3 (string + parseAsNumber) = "1.23"
I open Analog Design Environment and I select Variables - Copy From CellView and no design variable is found (this is normal);

 BUT

If I set:
Param1 (float) = 1.23
Param2 (string) = "abc def"
Param3 (string + parseAsNumber) = "ghi jkl
then in Analog Design Environment and I select Variables - Copy From CellView and the result is that I get 2 variables:
"ghi" and "jkl" ! I don't understand why?

The question: How does ADE find the Design Variables in a Cell View ? (on what rules? Why are both strings taken ? Why only the strings from the parameters with parseAsNumber? )

Thank you,

Best Regards,

Adrian

 

 

  • Andrew Beckett

    Hi Adrian,

    Initially I would have expected the criteria should be string+parseAsCEL (since that is really what indicates that the string is an expression, and hence could contain variables). However, it also supports simple (non-expression) references even on string fields which are numbers (i.e. string+parseAsNumber). The variables are extracted by using the AEL functions to determine the variables which appear in the "expression". It doesn't check to see whether the syntax is valid (that will get caught later). So it is reasonable that it detects non-numerical values in the field as design variables (assuming they're also not valid AEL functions). The fact that it returns two variables is reasonable too, isn't it? What would you expect it to do otherwise? Ultimately both will end up in the netlist (it would cause a syntax error in this case) - if it was "ghi+jkl" you'd expect both to be found and the netlist would then be correct. 

    The "abc def" wouldn't be extracted as variables because these are just simple strings - they won't appear in any netlist (or at least shouldn't, unless there's a custom netlist procedure) as variable references (probably they'd appear in quotation marks).

    Hope that clarifies things.

    Regards,

    Andrew.

  • Adrian Nistor

     Thanks Andrew for the explination, 

    so, for a string CDF parameter which may have non numerical string values, if I want:

    - to be detected by ADE (for design variables) I should have: parseAsNumber,  (and also would be nice to have parseAsCEL)

    - NOT to be detected by ADE (for design variables) I should: remove parseAsNumber

    Is this a correct conclusion ?

     

    Thank you,

    Best Regards,

    Adrian

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.