• 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. How to get status of variable (enabled/disabled) from checkpoint...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 143
  • Views 3080
  • 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

How to get status of variable (enabled/disabled) from checkpoint using SKILL

Alex Stepanov
Alex Stepanov over 8 years ago

Hi,

Is it any SKILL function that allows to know if variable was enabled in checkpoint (history entry).

I mean I can get list of global variables from checkpoint using axlGetVars(), but then i want to know which variables was disabled.

And second question, is it possible to get list of variables for test in checkpoint?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    sess=axlGetWindowSession()
    sdb=axlGetMainSetupDB(sess)
    hist=axlGetHistoryEntry(sdb "tran.3")
    ckpt=axlGetHistoryCheckpoint(hist)
    var=axlGetVar(ckpt "rx_inpbufwhatever")
    axlGetEnabled(var) ; was it enabled or not.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Stepanov
    Alex Stepanov over 8 years ago
    Andrew, thank you very much. (It is typo in line 5. should be ckpt instead of kept)
    What about my second question? Is it a way to get also list of variables for test in checkpoint?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago
    Sorry - that was auto-corrected by my web browser. I've just boarded a plane so I'll answer the second question later when I've landed... (I didn't notice it earlier)
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Corrected the earlier post. To get the design variables for a test (from a particular history), just do:

    sevSess=axlGetToolSession(sess "TRAN" ?history "tran.3")
    asiGetDesignVarList(sevEnvironment(sevSess))

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Stepanov
    Alex Stepanov over 8 years ago
    Thank you very much!
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Stepanov
    Alex Stepanov over 8 years ago
    Hi Andrew,
    I have a problem with asiGetDesignVarList function.
    In Assembler it is possible now to define sweep for variable in test. So if sweep defined for variable, asiGetDesignVarList function returns zero as value of this variable.
    Is it bug? Is it any other way to get value of variable for a test from a particular history?
    Best regards,
    Alex.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Alex,

    I'd hoped that maeGetVar() could do this, but currently it just shows one value for the variable when called with 

    maeGetVar("AVDD" ?typeName "test" ?typeValue "AMP_SIM")

    for example. I've appended this to a CCR asking for a nice mae function way of doing this.

    For now, you can use:

    axlSess=axlGetWindowSession()
    sdb=axlGetMainSetupDB(axlSess)
    test=axlGetTest(sdb "AMP_SIM")
    var=axlGetVar(test "AVDD")
    varVal=axlGetVarValue(var)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Stepanov
    Alex Stepanov over 8 years ago
    Andrew,
    Actually I need this for history item. But I figured out I can use axlGetHistoryCheckpoint to get database, and then rest of the scripts works fine.
    Thank you.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago
    Good point - sorry, I overlooked the fact that you said you wanted to do this for a history.

    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