• 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. Viewing task values in Simvision

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 65
  • Views 22100
  • 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

Viewing task values in Simvision

DylanC
DylanC over 6 years ago

Hello,

I'm working on creating a robust simulation environment for a project and I'm not super familiar with Simvision/Incisive.  In modelsim you can view the values inside task calls the same way you view signals in modules.  Is there a way to do this in Simvision?  I'm thinking maybe it has to do with the $shm_probe command.  I'm doing $shm_probe(name, "ACM").

Is this possible with the Cadence tools?

Thank you,

Dylan

  • Cancel
Parents
  • StephenH
    StephenH over 6 years ago

    Hi Dylan.

    In general we recommend not embedding waveform probing in the SV code, as it's less flexible than using the Tcl interface. With Tcl, there is a "probe" command which allows you to specify the hierarchy to send to the waveform file, and at the same time you specify the types of design objects that are included, e.g. just i/o ports, internal nets, assertions etc. This can optionally include tasks and functions as well as memories.

    For example: "probe -create -shm top.dut -all -depth all -tasks -functions".

    Full documentation here: https://support.cadence.com/apex/techpubDocViewerPage?xmlName=tclcmdref.xml&title=Xcelium%20Simulator%20Tcl%20Command%20Reference%20--%20probe%20-%202.35.4%20probe%20Command%20Syntax&hash=probe-probecommand:syntaxprobeCommandSyntax&c_version=18.09&path=tclcmdref/tclcmdref18.09/probe.html#probe-probecommand:syntaxprobeCommandSyntax

    If you really want to stick with $shm_probe, add "T" to the mode string. See https://support.cadence.com/apex/techpubDocViewerPage?xmlName=svsim.xml&title=Debugging%20SystemVerilog%20--%20Accessing%20Design%20Objects%20with%20Tcl%20-%20Probing%20Compilation%20Units%20with%20Tcl%20and%20System%20Tasks&hash=AccessingDesignObjectswithTcl-1057261ProbingCompilationUnitswithTclandSystemTasks&c_version=18.09&path=svsim/svsim18.09/Accessing_Design_Objects_with_Tcl.html#AccessingDesignObjectswithTcl-1057261ProbingCompilationUnitswithTclandSystemTasks for all the options.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DylanC
    DylanC over 6 years ago in reply to StephenH

    Hi Steve,

    Thanks for the very fast reply.  That worked perfectly!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • DylanC
    DylanC over 6 years ago in reply to StephenH

    Hi Steve,

    Thanks for the very fast reply.  That worked perfectly!

    • 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