• 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. Passing a string as a design variable in ADEXL

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 17025
  • 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

Passing a string as a design variable in ADEXL

apskohli
apskohli over 7 years ago

Hello All,

I have a simulation setup where I'm writing output to a file, for post-processing; the file is created using a Verilog-A module and I have parameterized the

file name, and this all works fine in ADEL. However, when I try to run a corner sweep in ADEXL, I want to pass the output filename thru the corner setup,

in this case the input.scs contains "netlist" as an include, and the method fails.

Is there a way in ADEXL to avoid to creating a hierarchical netlist, and instead have the flat netlist as created in ADEL, i.e. not .include the netlist? or a better work around.

I would really appreciate your inputs on this issue.

Thanks,

AS

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    I don't see why having the "netlist" included would make any difference here. Why does that cause a problem? I don't see why that would impact the ability to make the filename a variable through corner setup - the variables are not defined in the included netlist. I also don't think what you're asking about flat versus hierarchical makes sense either - ADE L doesn't create a flat netlist - it's hierarchical just as it is in ADE XL.

    Most likely the include mechanism is as a consequence of having ignoreDesignChangesDuringRun set somewhere in your environment:

    envSetVal("adexl.simulation" "ignoreDesignChangesDuringRun" 'boolean t)

    This in turn forces this variable to t:

    envSetVal( "adexl.simulation" "includeStatementForNetlistInSimInputFile" 'boolean nil )

    (note that this variable has no effect if ignoreDesignChangesDuringRun is set to t).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • apskohli
    apskohli over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your reply. I guess I need to rethink my approach.

    I'm trying to save the output thru a verilog-A measurement block to a file. I need to

    do this for multiple runs of transient-noise analysis, so each file needs to be separate

    entity. Any suggestion on how to accomplish this?

    Best Regards,

    AS

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to apskohli
    Andrew Beckett said:
    I don't see why having the "netlist" included would make any difference here. Why does that cause a problem? I don't see why that would impact the ability to make the filename a variable through corner setup - the variables are not defined in the included netlist. I also don't think what you're asking about flat versus hierarchical makes sense either - ADE L doesn't create a flat netlist - it's hierarchical just as it is in ADE XL.

    As I said 2 months ago, I don't know what your problem actually is - this ought to work, and I didn't think then that it had any thing to do with the netlist being included the way it is in ADE XL.

    Perhaps you should contact customer support so an application engineer can look at your set up and find out what is wrong?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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