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

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


 

Parents
  • amnldm

    could you please provide a piece of the TCL code, which includes the mentioned probes with on/off controls?

Reply
  • amnldm

    could you please provide a piece of the TCL code, which includes the mentioned probes with on/off controls?

Children
  • StephenH
    in reply to amnldm

    You could start with:

    probe -create -shm [scope -tops] -all -depth to_cells

    if you have large arrays that you need to probe, you might need to add the options to allow larger-than-default arrays:

    probe -create -shm [scope -tops] -all -depth to_cells -packed 20000 -unpacked 20000

    The numbers after the -packed and -unpacked refer to the max size of array that will be probed.
    The -all means probe all signal types (ports, internal signals) and the "[scope -tops]" is a short-cut to specify all top-level modules, you can replace this with the exact name of the module that you want to probe if probing everything isn't what you wanted.

  • amnldm
    in reply to StephenH

    Let's say the H1 is the top hierarchy, H2 hierarchy is nested to the H1, H3 is nested to H2,  and so on...

    So, what TCL command should be used for probing the signals in the H1 and H3 hierarchy? Should it be as following?

    probe -create -shm [scope H1] -all -depth to_cells

    probe -create -shm [scope H1.H2.H3] -all -depth to_cells

    How can I manage a depth of the dumped signals (etc two hierarchies depth)?

    Should I do something special for the signals in the testbench tasks? functions?

  • StephenH
    in reply to amnldm

    The "to_cells" means probe every level until you reach a cell (`celldefine or a module compiled with -y or -v).

    So to only probe H1, use "-depth 1".

    Have a look at the documentation for the probe command (support.cadence.com) to see all the options for probing including probing classes, dynamic arrays, tasks and functions.

    https://support.cadence.com/apex/techpubDocViewerPage?xmlName=tclcmdref.xml&title=Xcelium%20Simulator%20Tcl%20Command%20Reference%20--%20Table%20of%20Contents%20-%20&hash=&c_version=21.09&path=tclcmdref/tclcmdref21.09/tclcmdrefTOC.html

  • amnldm
    in reply to amnldm

    what does the -shm switch in the XRUN command mean?

    what does the .shm extension in the database name means (e.g. waves.shm)?

    Is the shm related to the Shared memory?

  • tpylant
    in reply to amnldm

    The -shm is for the probe command, not xrun. It stands for Simulation History Manager, which is a binary format in contrast to VCD or EVCD format.

    Tim

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.