• 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. How to get the correct hierachy path by using API geGetAllProbe...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 142
  • Views 1291
  • 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

How to get the correct hierachy path by using API geGetAllProbe()

Zest
Zest over 6 years ago

Hi

Issue:  

If a net is high light probed, geGetAllProbe()  returns the current edit schemaitc hierachy instead of the actual net hierarchy.

example:

netX is in hierarchy L0.L1.netX,  if I high light netX in L0.L1.L2.netX,

geGetAllProbe() will return path ''L0.L1.L2" for netX,

but ''L0.L1" is the ONLY correct path for netX

How can get the correct probe net path by SKILL?

THX!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Not sure if I've entirely understood what you're saying, but it sounds as if you're after the "adjusted path" to provide the highest level that the signal exists at? I wouldn't say the probe net path is wrong, with what you're seeing (so it's not incorrect), but maybe you want the highest probe point?

    If so, this would provide the list of the adjusted paths for all probes:

    adjustedProbePaths=foreach(mapcar probe geGetAllProbe()
      geGetAdjustedPath(hiGetCurrentWindow() strcat(probe~>pathList "/" probe~>pathObjectName))
    )

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Zest
    Zest over 6 years ago in reply to Andrew Beckett

    Thank you Andrew!

    This is exactly what I want, problem solved!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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