• 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 do I add signal probes to Simvision waveform viewer...

Stats

  • Locked Locked
  • Replies 19
  • Subscribers 66
  • Views 23986
  • 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 do I add signal probes to Simvision waveform viewer?

ianmurph
ianmurph over 2 years ago

I have some packages that live outside the top level testbench that drive some interfaces. I am trying to figure out how to add these signals into the waveform window. In Simvision, I can see all my packages and the signals from them, but they are in italics and say 'not probed':

How does one make these signals probed? Is there a file somewhere that tells the simulator what signals are probed? The simulation is run through a makefile script, here is a snippet from it. I tried adding the line that starts with 'probe' but I dont really know what I'm doing and this did not work:

if [ ! -d $(SIM_OUTPUT_DIR) ]; then mkdir $(SIM_OUTPUT_DIR); fi; \
cd $(SIM_OUTPUT_DIR); \
find . -type f -maxdepth 1 -delete; \
echo "Curent folder: "; pwd; \
irun -v200x -makelib rcf_lib ../../$(XSC_IP_DIR)/xsc_q7_neptec_ddvs_ntsc_ctrl_axi/src/hdl/constants_pkg.vhd -endlib \
-dumpstack -reflib xil_defaultlib $(IRUN_FILES) $(IRUN_SIM_OPT) $(IRUN_SIM_DEFINE_TC) $(IRUN_SIM_DEFINE_OPT) $(IRUN_CODE_COVERAGE_OPTIONS) -top $(TOP_LEVEL) -top glbl -logfile sim_log.log; \
probe -create -database waves::worklib.cpc_tools_pkg::cpc_tools -all -depth all

I may not have provided enough info to answer the quesiton, if so let me know what info is missing and I will try to answer it. Thanks in advance.

  • Cancel
Parents
  • Doug Koslow
    Doug Koslow over 2 years ago

    Instead of hardcoding the top level name in your "probe" command, try replacing "waves::worklib.cpc_tools_pkg::cpc_tools" with "[scope -tops]".

    So your probe command becomes:

    probe -create -database [scope -tops] -all -depth all

    "scope -tops" will list out all the top levels of the design - including the packages. See if this addresses your issue.

    Thanks.

    - Doug

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Doug Koslow
    Doug Koslow over 2 years ago

    Instead of hardcoding the top level name in your "probe" command, try replacing "waves::worklib.cpc_tools_pkg::cpc_tools" with "[scope -tops]".

    So your probe command becomes:

    probe -create -database [scope -tops] -all -depth all

    "scope -tops" will list out all the top levels of the design - including the packages. See if this addresses your issue.

    Thanks.

    - Doug

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • ianmurph
    ianmurph over 2 years ago in reply to Doug Koslow

    Thank you for the reply. Unfortunately this didn't resolve my issue, the signals inside my packages still say 'not probed'. For more information, my top level is set to my tb_fpga in the script:

    ifneq ($(TOP_LEVEL), 1)
    TOP_LEVEL = tb_fpga
    endif

    But my packages are outside of my tb_fpga.sv. In order to see my packages in the Design Browser at all, I have to right click and select 'Explore Full Design' (they are not there by default):

    Not sure if packages need to be included in the wave dump or somthing. Not sure if any of this info is relevant or not, this stuff is all pretty new to me. Thanks in advance!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Doug Koslow
    Doug Koslow over 2 years ago in reply to ianmurph

    At this point, I suggest filing a support ticket, and we can take the issue from there. (The command I gave should have probed the packages. We'll need to check why it did not.) 

    Thanks.

    - Doug

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ianmurph
    ianmurph over 2 years ago in reply to Doug Koslow

    Okay, I am going to try opening a ticket. I am stilling trying to figure out what our licence server host ID is so that I can open the ticket. In the meantime, I did find more info on the issue. I am gettting an error message that says "... does not match any database name" Here is the full error message:

    ncsim> probe -create -database [scope -tops] -all -depth all


    ncsim: *E,DBNFND: @STD.STANDARD @SYNOPSYS.ATTRIBUTES @UNIMACRO.VCOMPONENTS @CDS_ASSERTIONS.cds_assertion_stubs @IEEE.std_logic_arith @IEEE.NUMERIC_STD @IEEE.NUMERIC_BIT @IEEE.std_logic_1164 @STD.standard_additions @STD.TEXTIO @UNISIM.VPKG @IEEE.VITAL_Primitives @IEEE.VITAL_Timing @RCF_LIB.constants_pkg @IEEE.std_logic_unsigned @AXI_DMA_V7_1_18.axi_dma_pkg @LIB_PKG_V1_0_2.lib_pkg @IEEE.std_logic_misc @XPM.VCOMPONENTS @AXI_SG_V4_1_10.axi_sg_pkg @AXI_EMC_V3_0_17.emc_pkg @IEEE.std_logic_signed @AXI_ETHERNETLITE_V3_0_15.mac_pkg @AXI_LITE_IPIF_V3_0_4.ipif_pkg @AXI_IIC_V2_0_20.iic_pkg @IEEE.MATH_REAL @WORKLIB.axi3s_gp_pkg @WORKLIB.vivado_pkg buffer_if glbl tb_fpga $unit_0x324b5966 axi4stream_vip_pkg:: $unit_0x1ef055ef axi_vip_pkg:: xil_common_vip_pkg:: testcase_colourbar_lwir_axi_pkg:: testcase_colourmap_lwir_axi_pkg:: $unit_0x06fbb5dc testcase_version_reg_pkg:: testcase_lwir_receiver_pkg:: lwir_video_model_pkg:: crc32_model_pkg:: lwir_receiver_pkg:: testcase_hdcs_axi_pkg:: cpc_tools_pkg:: common_pkg:: header_pkg:: does not match any database name.

    Any idea what this means?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Doug Koslow
    Doug Koslow over 2 years ago in reply to ianmurph

    Please try these 2 commands:

    database -open -default waves.shm

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

    Thanks.

    - Doug

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ianmurph
    ianmurph over 2 years ago in reply to Doug Koslow

    Hi Doug, thanks very much for the reply. This actually did changed some stuff, I can now see more packages in simvision  (just the axi_vip stuff) but it did not probe the package that I want to probe. Sorry I didn't mention this earlier, but I JUST realized some of the probing is happening in the testbench sv file rather than in the simulation scripts? I have these lines in the tb.sv:

    initial begin: waveform_dump
        $display("Waves dump is Enabled");
        $shm_open("waves.shm", 1);
        $shm_probe(tb_fpga, "ACMTF"); // add hierarchy here.
    end

    What does the ACMTF part do? Should I specify the packages I want to probe here? Adding the lines you provided to the tcl script did add some probes, but the log file now shows this error (among others):

    ncsim: *E,PRNONE: No new objects to probe in scope cpc_tools_pkg::.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Doug Koslow
    Doug Koslow over 2 years ago in reply to ianmurph

    You're welcome. 

    I would not recommend mixing the $shm-based probing and the Tcl "probe" commands. Can you try removing that initial block and leave the probe command and see if that helps?

    Thanks.

    - Doug

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ianmurph
    ianmurph over 2 years ago in reply to Doug Koslow

    I have commented out that entire inital block in my testbench and I am using the tcl commands you gave. I dont see much difference. When I open simvision, I can see the "Packages" drop down now, but there is only 3 packages there, not all of them:

    I am still getting the same error in the sim log:

    ncsim: *E,PRNONE: No new objects to probe in scope cpc_tools_pkg::.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Doug Koslow
    Doug Koslow over 2 years ago in reply to ianmurph

    Did you provide read access to the package you want to probe during the compile?

    If you give the command: 

    probe <package_name>::

    ...for the package you want to probe, do you get an error?

    - Doug

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ianmurph
    ianmurph over 2 years ago in reply to Doug Koslow

    Forgive me, not sure I fulyl understand how to check that. I added probe cpc_tools_pkg:: to the tcl and it gave this error:

    ncsim: *E,PBNODB: Cannot determine database for the given probe command.

    I also tried other variations all of which gave errors (*E,PBNODB, *E,PNOOBJ, and *E,PRNONE)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Doug Koslow
    Doug Koslow over 2 years ago in reply to ianmurph

    You need to give the "database -open ..." command above first, so it knows which database to write the data to.

    - Doug

    • 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