• 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. Functional Verification
  3. probe tcl syntax to save variables inside automatic tasks...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 67
  • Views 14048
  • 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

probe tcl syntax to save variables inside automatic tasks in systemverilog

dtodorov
dtodorov over 4 years ago

Greetings,

I am running a testbench via xcellium, where the signals to be probed are defined via probe.tcl file, containing :

probe -create -tasks -functions -all -depth 4 -dynamic -variables testbench

However, inside the testbench I have an automatic SystemVerilog task, which internal variables I need to save. In Simvision, I see the task listed as a hierarchy member, but the internal variables are not saved. 

Variables in all other tasks (not automatic tasks) are saved as expected.

I searched through xcellium documentation for tcl commands, specifically in the probe definition, but could not figure out what is missing in the arguments I use. 

Has anybody encountered such hiccup so far?

Thanks,

Dimitar

  • Cancel
Parents
  • Pedro P
    Pedro P over 4 years ago

    Hi Dimitar, I have the same issue , cant probe variables inside a automatic task.

    Anyone can help us with this?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Pedro P
    Pedro P over 4 years ago

    Hi Dimitar, I have the same issue , cant probe variables inside a automatic task.

    Anyone can help us with this?

    • 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