Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13794
  • 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

Procedural interface for Virtuoso schematic navigator

PSOORYA

I am trying to get the hierarchical list of instances that a net is connected to. I found two flows and both have issues:

 

  1. Schematic Navigator --> Select Net --> Right-Mouse-click on the net in navigator --> Probe --> Add net and connected instance
    • This works great and it probes all the instances the net is connected to.
    • However the geGetAllProbe() returns the probeId of the net. I can't get the dbId of instances connected to the net procedurally. Is there a better way to get these instance dbIds?
  2. auProbeAddDevsForNet()
    • This auLvs() functionality is broken. Works on certain schematics but fails on many.
    • I also tried setting the graphic env variable probeNetDisplayCheckInstance and this did not work
    • windowId~>probeNetDisplayCheckInstance = t did not work either
    • Is this function supported at all?

 

I heard probing has been enhanced in IC616 and I am yet to try this.

Any help or insight into this is greatly appreicated.

-- PSoorya 

Parents
  • Andrew Beckett

     Probe objects do not provide such information.

    The auProbeAddDevsForNet() is not really "broken", but was never intended for certain operations. For example, it was never intended to be used down in the hierarchy. It only looks down, and not up. You can use the Right Mouse->Probe->Net and connected instances in the navigator to do this properly. But that won't help you because it's a probe too.

    You should look at the probes assistant in IC616, since this provides lots of information about everything connected to the probe. You can export this to a CSV file. That said, it doesn't provide a SKILL API to do this - if you want that, please contact customer support.

    The alternative is to write your own code to trace through the hierarchy and find all connected nets. This is not entirely trivial, particularly if you need to cope with iterated instances, busses, inherited connections, and connections that go up and down the hierarchy. Not impossible, but a reasonable amount of work to write and get right.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

     Probe objects do not provide such information.

    The auProbeAddDevsForNet() is not really "broken", but was never intended for certain operations. For example, it was never intended to be used down in the hierarchy. It only looks down, and not up. You can use the Right Mouse->Probe->Net and connected instances in the navigator to do this properly. But that won't help you because it's a probe too.

    You should look at the probes assistant in IC616, since this provides lots of information about everything connected to the probe. You can export this to a CSV file. That said, it doesn't provide a SKILL API to do this - if you want that, please contact customer support.

    The alternative is to write your own code to trace through the hierarchy and find all connected nets. This is not entirely trivial, particularly if you need to cope with iterated instances, busses, inherited connections, and connections that go up and down the hierarchy. Not impossible, but a reasonable amount of work to write and get right.

    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.