Home > Community > Forums > Functional Verification > How to create coverage configuration file

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 How to create coverage configuration file  

Last post Wed, Feb 26 2014 1:11 AM by bachu. 2 replies.
Started by sonam20 08 May 2012 10:17 PM. Topic has 2 replies and 5581 views
Page 1 of 1 (3 items)
Sort Posts:
  • Tue, May 8 2012 10:17 PM

    • sonam20
    • Not Ranked
    • Joined on Wed, Apr 25 2012
    • Posts 9
    • Points 135
    How to create coverage configuration file Reply

     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???

     

    • Post Points: 20
  • Mon, May 14 2012 11:10 AM

    • tmackett
    • Not Ranked
    • Joined on Thu, Jan 8 2009
    • Irvine, CA
    • Posts 7
    • Points 80
    Re: How to create coverage configuration file Reply

     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

    • Post Points: 20
  • Wed, Feb 26 2014 1:11 AM

    • bachu
    • Not Ranked
    • Joined on Mon, May 13 2013
    • Posts 1
    • Points 5
    Re: How to create coverage configuration file Reply

    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

    • Post Points: 5
Page 1 of 1 (3 items)
Sort Posts:
Started by sonam20 at 08 May 2012 10:17 PM. Topic has 2 replies.