• 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. Waveform of task in class?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 14128
  • 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

Waveform of task in class?

archive
archive over 18 years ago

Hi all,

We all know that tasks in module can be viewed in simvision by add a "probe -tasks".
But how to see waveform of task in class?

BTW, I use IUS583.

Best regards,
Davy


Originally posted in cdnusers.org by davyzhu
  • Cancel
  • archive
    archive over 18 years ago

    I saw the same/similar post in comp.lang.verilog, here is my reply to that post>>

    Ajeetha, CVC
    www.noveldv.com

    I don't use IUS, but going by other simulators, SV class dumping to
    waveform is not something as easy as that of modules, hence this may
    be not yet implemented feature. IMHO in many cases one can do without
    it. As we speak I'm writing a paper on Advanced Debugging for SV
    testbenches for SNUG India 2007. That talks about special approaches
    for testbenches. Some key points:

    1. It really helps if the environment is layered - be it VMM or AVM
    etc. I don't know much about uRM except its name, hope it has similar
    layered approach.
    2. If #1 is true, then the "task in waveform" is required only for
    "command transactor" or BFM layer. And there we do have a virtual
    interface, simply add few extra debug signals to that interface and
    update the class members to that interface. This approach is detailed
    in our 2006 SJ SNUG paper as well.

    3. Even for any class this approach #2 works as a workaround.
    4. For higher level models, breakpoints, transaction tracking etc. is
    important. We are looking at Verdi, command line debugger etc. for
    this.

    Regards
    Ajeetha, CVC
    www.noveldv.com


    Originally posted in cdnusers.org by ajeetha
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 9 years ago

    Hi Davy.

    Firstly, you should really use a newer version of Incisive, the version you mention is so old I doubt it has much support for classes at all!

    Secondly, because most of the activity inside class methods happens in zero time, putting the class variables into the waveform doesn't generally help you to understand the execution of the testbench. It's better to either single-step the simulation in the SimVision debug GUI and watch the code execute on the fly, or the best is to use the Indago Debug Analyzer tool which probes all your testbench activity and allows you to post-process debug the classes with reverse stepping back from the point of failure. It is a massive time-saver. Indago is only available in relatively recent version of Incisive, you'd want to be using 14.2 or later, and ideally 15.2.

    Your local Cadence AE should be able to help you with that. If you're not sure who your local contact is, drop me a private message with your corporate email and location, and I'll get someone to get in touch.

    Regards,

    Steve

    • 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