• 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. custom the Ade-XL "run" button

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 1475
  • 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

custom the Ade-XL "run" button

Meny Lea
Meny Lea over 12 years ago

 Hi,

 

I'm trying to change the functionality of the run button of ADE XL.

I want it to launce some skill script befor start simulation. I did it on the past for ADE-L on IC61,

but there I add a new pull down menu button. I cant find the exact documentation that explain what to do.

I do understand that I need to defince some kind of user trigger ( deregusertriggers)  that will run the script  once the run button was pressed. where do I find the exact callback that being used by "run" button?

any information will be appriciated.

thx

 

Meny 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Meny,

    The right way to do this is to use the "preRun" trigger. For example:

    procedure(CCFaddPreRunTrigger(sess)
      axlSessionConnect(sess "preRun" 'CCFpreRunTrigger)
    )

    procedure(CCFregPreRunTrigger()
      axlSessionRegisterCreationCallback('CCFaddPreRunTrigger)
    )

    procedure(CCFpreRunTrigger(sess sdb mode testName)
      printf("JUST ABOUT TO RUN TEST %L IN MODE %L\n" testName mode)
      t
    )

    Call CCFregPreRunTrigger() to set it up so that the next ADE XL view you open will call the trigger.

    You can find out the triggers using:

    sess=axlGetWindowSession()
    axlSessionSignalList(sess)  ; outputs the trigger names
    axlSessionSignalSignature(sess "preRun") ; tells you the expected arguments for the named trigger.

    This avoids having to change any buttons and so on.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Meny,

    The right way to do this is to use the "preRun" trigger. For example:

    procedure(CCFaddPreRunTrigger(sess)
      axlSessionConnect(sess "preRun" 'CCFpreRunTrigger)
    )

    procedure(CCFregPreRunTrigger()
      axlSessionRegisterCreationCallback('CCFaddPreRunTrigger)
    )

    procedure(CCFpreRunTrigger(sess sdb mode testName)
      printf("JUST ABOUT TO RUN TEST %L IN MODE %L\n" testName mode)
      t
    )

    Call CCFregPreRunTrigger() to set it up so that the next ADE XL view you open will call the trigger.

    You can find out the triggers using:

    sess=axlGetWindowSession()
    axlSessionSignalList(sess)  ; outputs the trigger names
    axlSessionSignalSignature(sess "preRun") ; tells you the expected arguments for the named trigger.

    This avoids having to change any buttons and so on.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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