• 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 is only

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 66
  • Views 12792
  • 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 is only

Specman baby
Specman baby over 16 years ago

Hi, 

 

Is there any way in which I can disable an already defined coverage.

My scenario is this:

I am using an eVc in which coverage is already defined. Now I want to override that coverage defintion for the same struct-events using

cover this_covr_group_defindin_evc is only {

 

};

However is only construct doesn't seem to work for coverage definitions.

Alternatively; is there any way in which I can exclude the coverage items from the coverage browser gui? 

  • Cancel
Parents
  • pjigar
    pjigar over 16 years ago

    Cover groups are "declarative" struct members like fields so you can not "remove" them. But you can extend them to add options and one of the option of cover group is "no_collect". THis option will stop the coverage collection for this group.

     

    extend come_evc_u {

      cover this_covr_group_defindin_evc using also no_collect;

    };

     

    Jigar

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • pjigar
    pjigar over 16 years ago

    Cover groups are "declarative" struct members like fields so you can not "remove" them. But you can extend them to add options and one of the option of cover group is "no_collect". THis option will stop the coverage collection for this group.

     

    extend come_evc_u {

      cover this_covr_group_defindin_evc using also no_collect;

    };

     

    Jigar

    • 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