• 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. XRUN: Dump all internal signals

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 67
  • Views 23619
  • 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

XRUN: Dump all internal signals

bimartin
bimartin over 2 years ago

Hello everyone. I'm using XRUN to compile/elab and simulate a design with a single command:

xrun <opts>

This is a basic SystemVerilog design, I've also added the following statements to the top module

$recordfile("output.trn");
$recordvars();

This, as far as I know, should dump the database to be later viewed with SimVision.

I'm able to see most of the signals, but there are some signals that are not probed and I don't know how to force dumping/probing of all available signals.
If I dump a .VCD it shows all signals but then I lose abilities like proper Enumerate printing, which I need.

Can anyone please help me out? Thanks


 

  • Cancel
Parents
  • StephenH
    StephenH over 2 years ago

    Generally we prefer the Tcl "probe" command rather than embedding probe commands via system tasks like $recordvars, as you get more control with Tcl and it's easier to turn the probing on/off.

    I don't think the system tasks have any way to control the inclusion of signals that are excluded by default, again Tcl is the preferred route as it has options to control the size of arrays and vectors that get probed.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 2 years ago

    Generally we prefer the Tcl "probe" command rather than embedding probe commands via system tasks like $recordvars, as you get more control with Tcl and it's easier to turn the probing on/off.

    I don't think the system tasks have any way to control the inclusion of signals that are excluded by default, again Tcl is the preferred route as it has options to control the size of arrays and vectors that get probed.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Children
  • bimartin
    bimartin over 2 years ago in reply to StephenH

    Thanks a lot for your feedback Stephen! How should I include these TCL commands in the xrun commandline? I think I can execute these probe commands if I use interactive/GUI mode, but my idea is to compile/elaborate/simulate/generate waves in a single command. I think -input is the option that allows to include a TCL script, but I don't know what database should I specify etc...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tpylant
    tpylant over 2 years ago in reply to bimartin

    Yes, use the "-input" argument to xrun to run the TCL code. Here is a simple example:

    % cat probes.tcl
    database -open waves -into waves.shm -event -default
    probe -create test -depth all -tasks -functions -all -database waves
    run

    % xrun -input probes.tcl

    Tim

    • 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