Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 1660
  • 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

asiGetStimulusGlobals is only valid after calling ADE - Setup->Stimuli...

MLindig

asiGetStimulusGlobals methods only works if you prev. called dialog "ADE - Setup->Stimuli...". Is there any workaround for that? How can I get the global nets of current design?

I am using Virtuose 6.1.5

Michael

Parents

  • Michael,

    I checked what it's doing - as part of the form being launched, it needs to identify the available global signals, and when it finds them it stores them in the data structure but all disabled. So there is no practical difference between it returning a list of disabled global signals and it returning nil.

    So there's nothing wrong here.

    If you want to find out the global signals for the session, effectively it is just doing this:

    setof(sig asiGetTopCellView(asiGetCurrentSession())~>signals sig~>isGlobal)~>name

    Note that it doesn't traverse the hierarchy; it assumes that any global signal will also be defined at the top level (that's what the form population does too).

    Andrew.

Reply

  • Michael,

    I checked what it's doing - as part of the form being launched, it needs to identify the available global signals, and when it finds them it stores them in the data structure but all disabled. So there is no practical difference between it returning a list of disabled global signals and it returning nil.

    So there's nothing wrong here.

    If you want to find out the global signals for the session, effectively it is just doing this:

    setof(sig asiGetTopCellView(asiGetCurrentSession())~>signals sig~>isGlobal)~>name

    Note that it doesn't traverse the hierarchy; it assumes that any global signal will also be defined at the top level (that's what the form population does too).

    Andrew.

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.