Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14152
  • 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 L Design variables from include files

itos

Hi,


I define lots of design variables. When I use "Copy from Cellview" in ADE L, all the undefined design variables are detected and I can fill them. I used this extensively.


Now I would like to generate them from a MATLAB script and created an scs file with "parameters Wn = 500u" statements (for example) and include it as library file.


But whatever I do, ADE L still thinks they are undefined, creates empty variables in the workspace. When netlisting, it either complains that they have been defined already or that they are undefined.

How to do this?

  • Tom Volden

    You can prevent ADE from automatically copying the design variables from the cellview by setting the following in your .cdsenv file:

    asimenv.startup   copyDesignVarsFromCellview   boolean   nil

    Or equivalently in the .cdsinit file:

    envSetVal("asimenv.startup"  "copyDesignVarsFromCellview"  'boolean nil)

     

  • itos
    Hi Tom,

    Thank you! However, for some reason this seems to be ignored. Are you sure this is true for ADE L too? I tried the .cdsinit and .cdsenv variant. If I enter the envSetVal in the CIW I get "t" (meaning success).

    I also want to emphasize that I generally like this copying feature. But for larger systems this gets somehow out of control.

    So I would like not only use this for MATLAB scripting but also to keep config for different blocks in a certain "state". For example, if I have an amplifier I do not want to set all the design variables in ADE L. Also, I do not want to statically fill the values in the array. Having include a "amplifier_config_v1764.scs" would it make easier to reference the config later in results for example.

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.