• 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. Getting schematic instances from multiple open schemati...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 144
  • Views 16334
  • 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

Getting schematic instances from multiple open schematics

shajujan
shajujan over 11 years ago

Hi,
 
I want write a skill routine that lets the user interactively select instances from multiple schematics & get those instance names. I tried geAddSelectPoint(), but that will prompt the user to select instances only from the current cellview. I tried dbGetOpenCellViews(), but that will get me all the open cellviews in memory including the ones not open currently.
 
Any ideas on how to get started will be much appreciated.
 
Thanks,
Shaju 
 
 
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    A couple of things. First the callback should be:

                                             ?callback       "asiSelectInst('inst ?form symeval(form))"

    and in fact it might make sense to avoid it needing the "form" global variable, so using:

                                             ?callback       sprintf(nil "asiSelectInst('inst ?form symeval('%s))" form)

    might be better still.

    Secondly it requires the design to be open in a tab. It doesn't do that automatically. I can't see a way of ensuring that happens without using private APIs (and I don't really have time now to debug this fully as I'm travelling at the moment). So I suggest you contact customer support for this.

    Thirdly, your form stores asiSession on the form symbol - you might want to use:

    symeval(form)->asiSession=sevEnvironment(asiGetToolSession(ses testName)) 

    and have this updated based on your cyclic field (as a callback) so that it reflect the "right" session for the test. 

    Not fully debugged, as I said, but I did a little experimentation.

    Regards,

    Andrew.

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

    A couple of things. First the callback should be:

                                             ?callback       "asiSelectInst('inst ?form symeval(form))"

    and in fact it might make sense to avoid it needing the "form" global variable, so using:

                                             ?callback       sprintf(nil "asiSelectInst('inst ?form symeval('%s))" form)

    might be better still.

    Secondly it requires the design to be open in a tab. It doesn't do that automatically. I can't see a way of ensuring that happens without using private APIs (and I don't really have time now to debug this fully as I'm travelling at the moment). So I suggest you contact customer support for this.

    Thirdly, your form stores asiSession on the form symbol - you might want to use:

    symeval(form)->asiSession=sevEnvironment(asiGetToolSession(ses testName)) 

    and have this updated based on your cyclic field (as a callback) so that it reflect the "right" session for the test. 

    Not fully debugged, as I said, but I did a little experimentation.

    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