Home
  • Products
  • Solutions
  • Support
  • Company
  • Products
  • Solutions
  • Support
  • Company
Community Forums Functional Verification How to create coverage configuration file

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 67
  • Views 72376
  • 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 to create coverage configuration file

sonam20
sonam20 over 10 years ago

 I want to run    "set_toggle_excludefile"   command . And I pass this command to coverage configuration file . And run that file in elaboration command but it did'nt run.

 

where to create coverage configuaration file?

Elaboration command is directly run on terminal or give this command to run script or else???

 

  • Cancel
  • archive
    archive over 10 years ago

     Using the xbus example as a starting point, you can create a .ccf file with any editor.

     

    irun -f ../filelist.f \
    +OVM_TESTNAME=test_read_modify_write \
    -covfile ./xbus.ccf \
    -covoverwrite   \
    -covworkdir ./cov_work  \
    -covdesign xbus_chip    \
    -covtest test_read_modify_write

    --

    if you are using 3 step (ncvhdl/ncvlog, ncelab, ncsim):

    ncelab -covfile ./xbus.ccf \

     ===

    Below is a *sample* .ccf file.  There are many dozens of options.  You will need to review the ICC User Guide to figure out your coverage requirements.  This is the *most important* step.

    ===Contents of sample .ccf====

    # Wildcard *
    # Single char match ?
    # Matches module/instance and descendents ...
    # b = Block
    # e = expression
    # t = Toggle
    # f = FSM
    # u = functional
    # a = all

    # Since other modules besides the DUT have covergroups and assertions
    # you need to select multiple dut_modules to collect coverage
    # In this design there are modules bind-ed into the design

    # Get rid of constant signals at elab time
    set_com

    #Need this for test in different regression areas
    set_ignore_library_name

    # ------Instrumenting Block, Expression, Toggle Coverage -------------
    # select_coverage [<coverage>] [-module] <list>  | [-instance] <list>
    select_coverage -block -expr -fsm -toggle -module xbus_tb_top.dut...

    # Branch coverage NOT enabled by default
    # If branch coverage desired (branch takes more resources to run, slows sim):
    set_branch_scoring

    # Deselect Verification modules which were binded into the design
    deselect_coverage -bet -module test_driver_bind lowest_verif_bind

    # Deselect unwanted modules

    deselect_coverage -bet -file mysubdut.sv

    # deselect by file list works too!
    deselect_coverage -betf -filelist deselected_filelist

    # ----- Instrumenting for Functional (Assertions and Covergroups) ----
    # Typically Functional coverage is scored for Test + DUT
    select_functional

    • Cancel
    • Up 0 Down
    • Cancel
  • bachu
    bachu over 9 years ago

    Hi,

    How to deselct the coverage for the modules which are instantiated by generate block. I deselct the modules but still i can find the coverage .

    thanks

    shiva

    • Cancel
    • Up 0 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.

© 2023 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information