• 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 Design
  3. Recommended delimiter in DSPF for deep probing

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 2874
  • 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

Recommended delimiter in DSPF for deep probing

unSkilled
unSkilled 10 months ago

Virtuoso IC Studio IC23.1-64b.ISR8.40

I'm having issues probing signals from an extracted view and the guides in the support.cadence.com are wrong as well.From the results browser I probe the voltage of interest and get this expression:

v("u_lfxo.u_gp_lfxo_top\\/u_agc\\/in_cmp_p" ?result "tran")

So one would think that using u_lfxo.u_gp_lfxo_top\\/u_agc\\/in_cmp_p as signal path in the deep probe does the job. However, nothing gets probed.

I found this in the forum:

deepprobe not working for extracted cellview in ADE-XL run.

But the suggested underscore would also be a problem because we use underscores in the instance names. What other character could be used as delimiter that does not require escaping in the deep probe syntax? Honestly this is a task that should be very straightforward to but the tool behavior is buggy.

  • Cancel
Parents
  • unSkilled
    unSkilled 10 months ago

    It seems that using $ as dspf divider works without having to escape it.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • unSkilled
    unSkilled 10 months ago

    It seems that using $ as dspf divider works without having to escape it.

    • 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