Stats

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

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
Parents

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


    Originally posted in cdnusers.org by TAM
Reply

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


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