• 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. Coverage using "iccr"

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 6925
  • 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

Coverage using "iccr"

archive
archive over 17 years ago

Hi Friends,
  I am doing Coverage  in the Master Monitor for my uVC. I have created a Covergroup which contains 3 coverpoints for Covering Address,Data and Direction. I am using "iccr" for viewing Functional Coverage results but WHen i look in to the DATA-ORIENTED coverage  I am getting two Instances of of single Coverpoints,say for ex: trans_addr is the coverpoint
    1) top.urm_test_top.sve.env.master_agent.monitor.cov_trans.trans_addr   
     2)top.xyz_master_monitor::cov_trans.trans_addr

I Cant understand why the 2nd instance is being Created though there is No Instance or Handle from top to Master monitor !!

And also I can see a Message as "Displaying 13 coverage points". Here I cant Understand y 13 coverpoints are created though i have specified 3 coverpoints in the covergroup !!
 
Regards,
Ramesh Pal


Originally posted in cdnusers.org by ramesh_pal_yadav
  • Cancel
Parents
  • archive
    archive over 17 years ago

    In the data-oriented functional coverage reports you will see more than one report for your covergroup. One reports the combined coverage for every instance of the covergroup. There will also be additional reports for each instance of the covergroup.

    covergroup grp; ... endgroup

    grp seq1 = new();
    grp seq2 = new();

    Here you'll see 3 examples in the iccr report. One will be the combined coverage for all instances of grp created in the test. Then there will be 2 additional reports showing the coverage in seq1 and the coverage in seq2.

    I don't know where you see the message "13 coverage points", I think that you'll need to give us more information. But remember that each coverpoint will often have more than one bin, so typically there will be more "coverage points" that you need to hit than there will be SystemVerilog "coverpoints" in the source.


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

    In the data-oriented functional coverage reports you will see more than one report for your covergroup. One reports the combined coverage for every instance of the covergroup. There will also be additional reports for each instance of the covergroup.

    covergroup grp; ... endgroup

    grp seq1 = new();
    grp seq2 = new();

    Here you'll see 3 examples in the iccr report. One will be the combined coverage for all instances of grp created in the test. Then there will be 2 additional reports showing the coverage in seq1 and the coverage in seq2.

    I don't know where you see the message "13 coverage points", I think that you'll need to give us more information. But remember that each coverpoint will often have more than one bin, so typically there will be more "coverage points" that you need to hit than there will be SystemVerilog "coverpoints" in the source.


    Originally posted in cdnusers.org by TAM
    • 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