• 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. Exporting ADE-L Variables

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 14566
  • 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

Exporting ADE-L Variables

netbug
netbug over 8 years ago

Dear all,

I have an ADE-L session which has some variables defined and I would like to export them so they could be used in a script (tcl script). Is there a simple way of  doing it ?

Best regards,

José

PS: Not sure if this is the right forum to ask this....

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    José,

    The design variables for the current session can be found using:

    asiGetDesignVarList(asiGetCurrentSession())

    With that you could write something to export them to wherever you want.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • netbug
    netbug over 8 years ago
    Hi Andrew,
    Thanks for your answer.
    So, without writing a skill script, how can I export the variable in Cadence so it can be used by a TCL script ?

    My application:
    I have an ADE-L session which calls a tcl script and opens SimVision. That script will run a piece of code everytime SimVision starts. As this may not be what all the users want, I would like to have a variable built in to ADE-L which could allow the script being run automatically or not.

    Many thanks.

    Best regards,
    José
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Unknown said:
    So, without writing a skill script, how can I export the variable in Cadence so it can be used by a TCL script ?

    You can't. Not sure why you would expect to be able to export an ADE variable to a Tcl script - this seems very specific to your particular needs - and precisely the kind of thing that SKILL is there for!

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • netbug
    netbug over 8 years ago
    Hi Andrew,
    I've solved it, but maybe in a way that is not the most correct.
    From the cds_globals, using the describe command, I could get the value for the ADE-L variable, an then use it.

    set aVar [describe cds_globals.AUTORUN]
    set aList [split $aVar "="]
    set ade_l_var [lindex $aList 1]

    if {$ade_l_var==1} {
    # If AUTORUN was set to 1 run tcl script
    source myFile.tcl
    mainFunction

    } else {
    # If any other character other than 1 do nothing
    }

    Best regards,
    Pedro
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Hi Pedro,

    OK, you didn't mention that you were using AMS Designer as the simulator. That's rather important information!

    You could do it even more simply - use:

    value cds_globals.AUTORUN

    No need to parse the output of the describe command then; the value command directly returns the value of the variable AUTORUN within the cds_globals module.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • netbug
    netbug over 8 years ago
    Hi Andrew,
    Thanks you for your help.
    Yes, I didn't mention the simulator ... sorry
    Best regards,
    Pedro
    • 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