Coverage using "iccr"

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.

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

I think we may be talking about different things due to my unclear language. When we speak of "a covergroup", we could be talking about a covergroup type or a covergroup instance (of a covergroup type). There is also a difference in the way things are handled between covergroup instances declared inside a class and covergroup instances declared in a module.

In a class-based methodology, you should have 1 report for every class::covergroup type. You should then have n reports for every covergroup instance of that class/covergroup type.

In a module-based methodology (which I'm not too familiar with) things will be different. I think there you get one report for each instance::covergroup type.

Finally, you are right, the number of coverage points isn't based on the number of bins. So I really don't know where the tool gets your number 13 coverage points. In my reports it is the sum of the number of coverage reports (1 for covergroup type + n for covergroup instances) plus the number of assertion/cover instances in my source code.