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,

    It is not a bug or a feature. The function is supposed to return any stimulus globals that have been set up - it is not intended to be a means of finding the global signals in your design - it doesn't say anywhere that this is what the function is for.

    The fact that it returns something after the first time the form has been used (even if cancelled) is really an implementation side effect - even that behaviour I wouldn't rely on because the form wasn't OK'd.

    If you want to find the globals in the design, the correct way to do it is to use code similar to that which I posted before. Most of the time any global signals will appear in the top level testbench, because you'll want to apply a signal to them, so generally the code I gave is sufficient. There are quite a few threads in these forums which show how to do recursive hierarchical traversal - you can use the Search facility to find them - I suspect you don't really need to do that here though - looking at the globals in the top level will probably be sufficient (that's all the global stimulus setup does).

    Regards,

    Andrew

Reply

  •  Michael,

    It is not a bug or a feature. The function is supposed to return any stimulus globals that have been set up - it is not intended to be a means of finding the global signals in your design - it doesn't say anywhere that this is what the function is for.

    The fact that it returns something after the first time the form has been used (even if cancelled) is really an implementation side effect - even that behaviour I wouldn't rely on because the form wasn't OK'd.

    If you want to find the globals in the design, the correct way to do it is to use code similar to that which I posted before. Most of the time any global signals will appear in the top level testbench, because you'll want to apply a signal to them, so generally the code I gave is sufficient. There are quite a few threads in these forums which show how to do recursive hierarchical traversal - you can use the Search facility to find them - I suspect you don't really need to do that here though - looking at the globals in the top level will probably be sufficient (that's all the global stimulus setup does).

    Regards,

    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.