• 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. How can I dump waveform using irun uder UVM environment

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 17261
  • 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

How can I dump waveform using irun uder UVM environment

bbpfancy
bbpfancy over 11 years ago

 
 
I downloaded an example (uvm_phases.tar )   from this website
www.testbench.in/UT_02_UVM_TESTBENCH.html
 
I try to download the waveform with a tcl file
database -open waves -shm
probe -create -database top -all -depth all
uvm_phase -stop_at -end connect
run 
exit
 
but  I get no signal from the waveform 
 
the top module is as follows
 
 

`include "uvm_macros.svh"
 import uvm_pkg::*;

`include "driver.sv"  
`include "monitor.sv"  
`include "agent.sv"  
`include "env.sv"  
`include "test.sv"

module top;

  initial
    run_test();

endmodule
 
and my makefile is as follows
 ius: ${FILES} ${IFILES}
@if [ ! -e ${UVM_HOME}/src/uvm_pkg.sv ];then \
echo "*******************************************************";\
echo "Environemnt varible UVM_HOME is not set or points to incorrect path"; \
echo "*******************************************************";\
fi 
irun ${UVM_FLAGS} +incdir+. ${FILES} +UVM_TESTNAME=test1 -access +rwc -input input.tcl 
 
 
 
 
 
  • Cancel
  • StephenH
    StephenH over 11 years ago

    You almost had it right, but this command "uvm_phase -stop_at -end connect" tells the simulation to stop after the UVM connect phase has finished. This is still at time zero so there will be nothing to see in the waves.

    Try removing that breakpoint.

    Alternatively if you're using that bkpt to help you probe the class hierarchy, move the probe command after the first "run" command, and add a 2nd "run" after the probe command.

     

    • 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