Help with Virtuoso XL Probe...

Hi Roi,

This isn't (as far as I know) possible. You can find all the probes with geGetAllProbe(), and then for each probe you can look at probeId~>objectId which will return the net object (if it's a probed net).

You can then do probeId~>objectId~>figs to find all the figures on that net, but this will only be in the cellView containing the net object, so it won't traverse the hierarchy - assuming that's what you want. If you don't need it to traverse hierarchy, maybe this is sufficient for your needs.

Regards,

Andrew.

Hi Andrew ,

The main topic of my skill is to go down hierarchy like the probe doing during highlight.

So i need the Probe tool to help me find fast and based on the probe the items that he found during the probe options.

i tried all the Transform codes options and it will take alonge time to find pathes and vias downlevel .

 do you have a idea how to find all paths and vias by net to find all the property?

 Roi.

Hi Roi,

It's not a trival amount of code to do this. So I don't have an example which illustrates this. If you have connectivity in the database though, you can find all the figures on the nets at the current level, and then look at the instTerms on that net, and follow through to the term attribute (which will give you the terminal within the cellView a level below), and from this you can get the net, and then all the figures. Do the same again recursively...

Something like:

procedure(MYprocessNet(net)
  foreach(fig net~>fig
    ; do whatever you need to do with the figures
  )
  foreach(instTerm net~>instTerms
    MYprocessNet(instTerm~>term~>net)
  )
)

Regards,

Andrew.

Hi Andrew,

 I used this topic because I also have queries with regards to XL probing.

 Can I use XL probing in gds data? What I mean is the layout is imported from gds. I tried this but it did not work.

The forum guidelines specifically say not to do this... (append to an old thread, especially when your request is only very loosely related to the original).

The probing can only be done if you are using layout XL and have managed to extract it and bind the instances across to the source schematic (assuming you have one). This is better in IC61X than IC5141 (you didn't say which version you're using - also requested in the guidelines), but even so you probably would need to define the mapping of devices from your source PDK in Configure Physical Hierarchy.

There is further work we are doing right now to get layouts from stream files to become XL compliant, but that's planned for an upcoming release. 

You may be better off using Mark Net.

I'm having to guess a bit here because you didn't give much information... (particularly versions, whether you have a schematic, and so on).

Regards,

Andrew.

Hi Andrew,

Sorry. I will keep that in mind.You have answered my question. Thanks.

Regards

Jielson

Jielson,

Sorry to be a bit picky - it just helps anyone searching to have clear distinction in the threads - plus there's a mechanism to highlight unanswered threads, which won't work if you continue a very old thread. So you're more likely to get an answer (because your unanswered append to an old thread might get accidentally forgotten).

No problem though - I don't want to get too fussy about this!

Andrew.

I am having problems  with cadence version 6.1.6-64b

When using update components and nets, it is not  working for me.

It I have a pin and pin text on a net, I use to get the net property of the route to update, and will high- light the

whole complete route when using XL probe .  This  no longing is working, or I am missing some cadence set switch.

The Forum Guidelines ask you not to post on old threads.

There's really not enough information here to figure out what your problem is. I suggest you contact customer support.

Kind Regards,

Andrew.