Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 7971
  • 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

Finding view name used by current ADE Explorer session

raduionescu

Hello,

I am starting a ADE explorer session and would like to know which view it is using via skill e.g it can be maestro or maestro_2 and I am unsure of the best way to do this. Most information we get from the object returned by asiGetCurrentSession(). Our tool can be called from either ADE-L or ADE Explorer. I can identify the explorer by asiGetCurrentSession() ->data->fenixMode, but I cannot figure out which maestro view the active session is using. Does anyone have a hint on this? Thank you.

Regards,

Radu

Parents
  • Andrew Beckett

    Radu,

    sess=axlGetWindowSession()
    axlGetSessionLibName(sess) ; returns the library name
    axlGetSessionCellName(sess) ; returns the cell name
    axlGetSessionViewName(sess) ; you've guessed it, returns the view name (e.g. "maestro")

    Using the asi APIs isn't the right approach, because in Assembler there could be multiple tests and each has a separate asi session id, whereas they all share the same "axl" session (be it ADE XL, Explorer or Assembler).

    Andrew

Reply
  • Andrew Beckett

    Radu,

    sess=axlGetWindowSession()
    axlGetSessionLibName(sess) ; returns the library name
    axlGetSessionCellName(sess) ; returns the cell name
    axlGetSessionViewName(sess) ; you've guessed it, returns the view name (e.g. "maestro")

    Using the asi APIs isn't the right approach, because in Assembler there could be multiple tests and each has a separate asi session id, whereas they all share the same "axl" session (be it ADE XL, Explorer or Assembler).

    Andrew

Children
  • raduionescu
    in reply to Andrew Beckett

    Thank you, that is what I was looking for I did not think to look to those axl procs.

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.