• 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

    Hi TAM,
    From your explanation I understood that for an 'n' covergroups there will n+1 coverage reports => n for each covergroup and 1 for combined coverage.Am i right?? 
    In my case i have defined 3 covergroups and Still i am getting the same result as above mentioned i.e I am getting two Instance s of each covergroups.
      1) representing all the Hierarchy
      2) using scope Resolution Operator. 

    MASTER side
    ------------------
    covergroup cov_trans @cov_transaction;
               trans_addr : coverpoint master_transaction_collected.addr_p;/* {
                                            option.auto_bin_max = 64; } */

               trans_data : coverpoint master_transaction_collected.wdata_p  {
                                            option.auto_bin_max = 64; }
    endgroup : cov_trans

     
    covergroup cov_trans_ctrl @ cov_tran_ctrl;
              trans_dir  : coverpoint master_transaction_collected.direction_p;
     endgroup : cov_trans_ctrl

         cov_trans = new();
          cov_trans.set_inst_name({get_full_name(), ".cov_trans"});

          cov_trans_ctrl = new();
          cov_trans_ctrl.set_inst_name({get_full_name(), ".cov_trans_ctrl"});     // Constructors

    SLAVE side
    -----------------
    covergroup cov_trans @cov_transaction;
         trans_rdata : coverpoint slave_transaction_collected.rdata_p;
    endgroup : cov_trans                    //  SLAVE side Coverage
        

    cov_trans = new();
          cov_trans.set_inst_name({get_full_name(), ".cov_trans"

              
    This is how the coverage is implemented.
    addr_p , data_p , rdata_p are 32 bit and direction_p is Enum type of 3 values.

    I am still unsure of
    a) Creation of Instance using scope resolution operator
    b) What the " 13 coverage points" mean....this message is shown beside the "filter" dropdown option  in the iccr 6.2 version.

    When coming to No.of Bins Creation i am getting Minimum 64 bins for my 32 bit  addr,data.But i cant understand Why " On;y 13 coverage points are created!!


    Thanks and Regards,
    Ramesh







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

    Hi TAM,
    From your explanation I understood that for an 'n' covergroups there will n+1 coverage reports => n for each covergroup and 1 for combined coverage.Am i right?? 
    In my case i have defined 3 covergroups and Still i am getting the same result as above mentioned i.e I am getting two Instance s of each covergroups.
      1) representing all the Hierarchy
      2) using scope Resolution Operator. 

    MASTER side
    ------------------
    covergroup cov_trans @cov_transaction;
               trans_addr : coverpoint master_transaction_collected.addr_p;/* {
                                            option.auto_bin_max = 64; } */

               trans_data : coverpoint master_transaction_collected.wdata_p  {
                                            option.auto_bin_max = 64; }
    endgroup : cov_trans

     
    covergroup cov_trans_ctrl @ cov_tran_ctrl;
              trans_dir  : coverpoint master_transaction_collected.direction_p;
     endgroup : cov_trans_ctrl

         cov_trans = new();
          cov_trans.set_inst_name({get_full_name(), ".cov_trans"});

          cov_trans_ctrl = new();
          cov_trans_ctrl.set_inst_name({get_full_name(), ".cov_trans_ctrl"});     // Constructors

    SLAVE side
    -----------------
    covergroup cov_trans @cov_transaction;
         trans_rdata : coverpoint slave_transaction_collected.rdata_p;
    endgroup : cov_trans                    //  SLAVE side Coverage
        

    cov_trans = new();
          cov_trans.set_inst_name({get_full_name(), ".cov_trans"

              
    This is how the coverage is implemented.
    addr_p , data_p , rdata_p are 32 bit and direction_p is Enum type of 3 values.

    I am still unsure of
    a) Creation of Instance using scope resolution operator
    b) What the " 13 coverage points" mean....this message is shown beside the "filter" dropdown option  in the iccr 6.2 version.

    When coming to No.of Bins Creation i am getting Minimum 64 bins for my 32 bit  addr,data.But i cant understand Why " On;y 13 coverage points are created!!


    Thanks and Regards,
    Ramesh







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