• 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. code coverage

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 24746
  • 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

code coverage

archive
archive over 18 years ago

Hi
We are using IUS 6.1 and URM for  VIP development.
Can i go for code coverage of the complete environment that i have developed?
HOw do i do that?

Regards

Rishi


Originally posted in cdnusers.org by Tel1234
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Hi Vivek.

    Have a look in the ICC User's Guide (`ncroot`/doc/iccug/iccug.pdf) at the chapter "Generating Coverage Data".
    Specifically the -covfile option to ncelab. You start to need to use a coverage control file, which would contain something like:
    // cov_options.ccf
    select_coverage -be -module *
    deselect_coverage -be -module fred
    deselect_coverage -be -instance top.jim.dummy
    // end of file

    This example would enable block and expression coverage in every module except "fred", and instance "top.jim.dummy".
    You can get quite creative with this is you need to, and you really should read the user guide to get an understanding of what you're doing with these commands :-)

    If you're using 3-step compilation (ncvlog;ncelab;ncsim) then this .ccf file is used like "ncelab -cov58 -covfile cov_options.ccf".
    If you're using single step (ncverilog or irun) then use "irun -cov58 -covfile cov_options.ccf".
    In fact, use irun, it's brilliant because it can sort out all your C, VHDL, Verilog etc files from one command line!

    Steve.


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Hi Vivek.

    Have a look in the ICC User's Guide (`ncroot`/doc/iccug/iccug.pdf) at the chapter "Generating Coverage Data".
    Specifically the -covfile option to ncelab. You start to need to use a coverage control file, which would contain something like:
    // cov_options.ccf
    select_coverage -be -module *
    deselect_coverage -be -module fred
    deselect_coverage -be -instance top.jim.dummy
    // end of file

    This example would enable block and expression coverage in every module except "fred", and instance "top.jim.dummy".
    You can get quite creative with this is you need to, and you really should read the user guide to get an understanding of what you're doing with these commands :-)

    If you're using 3-step compilation (ncvlog;ncelab;ncsim) then this .ccf file is used like "ncelab -cov58 -covfile cov_options.ccf".
    If you're using single step (ncverilog or irun) then use "irun -cov58 -covfile cov_options.ccf".
    In fact, use irun, it's brilliant because it can sort out all your C, VHDL, Verilog etc files from one command line!

    Steve.


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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