nccovdut option : Can it have more than 1 option?

Hi Pooja,

The nccovdut option only takes one module name as an argument.  If the Rx and Tx are defined as two different modules, you can have more than one nccovdut command line options, eg. +nccovdut+tx_module +nccovdut+rx_module.  If the rxtop and txtop are two instantiations of the same module and you want instance level coverage for each instantiation, you need to specify coverage with a coverage configuration file.  Take a look at the ICC documentation for specific information on how to specify coverage in a coverage configuration file.

Please let me know if this helps.

Best regards,

Mickey

Hi Mickey, 

The workaround that you  mentioned works great and thanks a million for that!!!!!!!! I have another question in the same context.

If I want to generate the html report for this what would be the best way would it be

1.report_html * > output.html

or

2.report_html xyz_tx xyz_rx > output.html

 If i have a testbench top that instantiates bith these modules is it fine if I use +nccovdut+test_tx_rx

and use report_html xyz_tx xyz_rx > output.html

Which of the above 3 mehods sounds apt?

Thanks in advance,

Pooja

Hi Pooja,

I would recommend leaving your current covdut option as is (+nccovdut+tx_mod +nccovdut+rx_mod).  When you pass the wildcarp key (*) to the report_html command the report will include the coverage for all modules hierarchically below and including the tx_mod and rx_mod module.  Although you could pass the test as the covdut, that could lead to confusing results when reporting the results because the user would have to remember that the cov database includes stats from the test.

Be aware that since there is no specification on whether the report should be a module or instance report, the default will be a module report.  This means that the coverage numbers for all instantiations of a given module will be combined to provide the total coverage for that module.  So your report currently does include coverage data from both the tx and rx instance trees.  However the report is being done on a module basis, so common modules found under both of those trees are combined to provide the total coverage results for any module.

Perhaps your intent is to capture the coverage results on an instance basis.  In an instance report the tool will report the specific coverage for each instance as well as the cumulative overage stats for all instantiations found hierarchically below a given instance.  To output an instance html report add -instance to the output command as will as *...  The "*" is a wild card to specify all modules at the top level and the "..." means to also include all instantiaions below those top instances.  So your command for an html instance report will be : 

iccr> report_html -instance *... > myreport.out

By the way if you would like more information on any command within iccr you can simply type in help along with the command name within iccr.  For example the help for the report_html command details the defaults for the command as well as other options that can be included.  The help for that command can be brought up as follows:

  iccr> help report_html

Please let me know if that helps.

Best regards,

Mickey

Hi Mickey ,

       Thanks a lot for the valuable inputs that you give me time and again,I must confess it helps me a lot!!!!!!!

            My aim is to get the coverage for TX and Rx modules and if I used a * option to generate the report it gives me the coverage of nested modules which makes it difficult to discern the actual coverage of TX and RX so I agree with you and hence now I generate the coverage report using report_html tx rx > output.html ,It certainly gives a better idea.Also could you give me a pointer to a document which would help me analyze my code coverage? I want to understand the coverage report so that I can fill up the holes.

Thanks,

Pooja

 Hi Pooja,

Take a look at the ICC User Guide.  The pdf version of the guide can be found within the IUS installation as follows:  <install_location>/doc/iccug/iccug.pdf.  Or you can also pull it up using the cdnshelp binary and searching for the ICC User Guide within cdnshelp.  Chapter 10 (Analyzing Coverage Data) within that manual may be what you are seeking.

Best regards,
Mickey