Stats

  • Locked Locked
  • Replies 2
  • Subscribers 66
  • Views 5515
  • 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

Using Xcelium, xrun -nogui option, where are the simulation results

Stephen491

I'm completely new to Cadence. I've been able to run a very simple simulation with the -gui option. Simvision opens, I add the variables to the waveform viewer, and press run. All is good.

I don't understand the flow when using the -nogui option. It appears that the simulation runs and returns control to the OS. When I launch Simvision, is there a database or file that I can open to display the already-simulated data?

My command is of the form:

xrun -gui -64bit -sv -access +rwc -top tb_top.sv <src files>

Parents
  • StephenH

    The default in batch mode is to run till the end of the test and exit. Unless you ask it to, the simulator won't probe waveforms to a file.

    You have various choices including:

    • Run with Tcl interactive mode by adding -tcl to your xrun command
    • Run in batch mode with a Tcl script to control the simulation (-input your_script.tcl)

    If you create a Tcl file and add the relevant probing commands then you can use the GUI in post-processing mode after the simulation ends.

    The simplest probing command would be something like:

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

    But I would advise you to read the documentation for the probe command to fully understand what the options are, to get what you need for your actual debugging requirements.

Reply
  • StephenH

    The default in batch mode is to run till the end of the test and exit. Unless you ask it to, the simulator won't probe waveforms to a file.

    You have various choices including:

    • Run with Tcl interactive mode by adding -tcl to your xrun command
    • Run in batch mode with a Tcl script to control the simulation (-input your_script.tcl)

    If you create a Tcl file and add the relevant probing commands then you can use the GUI in post-processing mode after the simulation ends.

    The simplest probing command would be something like:

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

    But I would advise you to read the documentation for the probe command to fully understand what the options are, to get what you need for your actual debugging requirements.

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.