• 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. SV: Coverage of assertions (only count hits??)

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 13773
  • 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

SV: Coverage of assertions (only count hits??)

rossbthompson
rossbthompson over 15 years ago

I was under the impression that assertions would be included in functional coverage. It seems that I am only get the evaluated assertions, not ones that have not fired. Is it possible to include the un-evaluated assertions as coverage holes?

 I have multiple instances of the same checker (sv module), but I see different totals under the assertion column. I am new to SV, so it could be something basic. 

Below is an example of what I see, all of the lines are instances of the same checker. The issue is that the assertion total is different

 Coverage of immediate sub-instances:
Total     Assertion     CoverGroup Weighted     CoverGroup Bins     Name
80%     100% (5/5)     60% (1)     47% (8/17)     dbxxt_dgl
73%     100% (6/6)     46% (1)     29% (5/17)     dbxxxd_det
73%     100% (6/6)     46% (1)     29% (5/17)     dbxxxt_det
73%     100% (5/5)     46% (1)     29% (5/17)     dixxrm_det
73%     100% (6/6)     46% (1)     29% (5/17)     dbxxc_det
73%     100% (4/4)     46% (1)     29% (5/17)     dxxxxxp_det
80%     100% (4/4)     60% (1)     47% (8/17)     dxxxxg_det
73%     100% (4/4)     46% (1)     29% (5/17)     dxxxxx_det
73%     100% (5/5)     46% (1)     29% (5/17)     dxxxxin_det
73%     100% (5/5)     46% (1)     29% (5/17)     dxxxxxwv_det
73%     100% (6/6)     46% (1)     29% (5/17)     dxxxxg_det
73%     100% (4/4)     46% (1)     29% (5/17)     dxxxv_det
73%     100% (4/4)     46% (1)     29% (5/17)     dxxxxx_det
73%     100% (4/4)     46% (1)     29% (5/17)     dxxxxt_det
73%     100% (6/6)     46% (1)     29% (5/17)     dixxxctive_det
63%     100% (2/2)     26% (1)     18% (3/17)     dxxxtive_det
78%     100% (6/6)     56% (1)     41% (7/17)     dxxxtive_det
78%     100% (6/6)     56% (1)     41% (7/17)     dxxxxxactive_det

 

 

Command: 

report_html -output cov_web -all fd -inst  xxx.xxxx.*

 

 version 08.20-s015

 

 

  • Cancel
Parents
  • rossbthompson
    rossbthompson over 15 years ago

     It seems my question is fairly basic:

     If you have an assertion, how do you cover if the assertion was evaluated. 

    I have tried to create a cover statement for each assert statement, but that still did not result in a coverage impact.

     I could create a covergroup for each assertion, but that seems to be overkill. Plus I am not sure how to activate the coverpoint. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • rossbthompson
    rossbthompson over 15 years ago

     It seems my question is fairly basic:

     If you have an assertion, how do you cover if the assertion was evaluated. 

    I have tried to create a cover statement for each assert statement, but that still did not result in a coverage impact.

     I could create a covergroup for each assertion, but that seems to be overkill. Plus I am not sure how to activate the coverpoint. 

    • 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