• 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. Functional Coverage using IMC

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 66
  • Views 26325
  • 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

Functional Coverage using IMC

sriganeshd
sriganeshd over 4 years ago

Hello All

        I have three test cases, say test_1, test_2, and test_3. I have generated functional coverage for each test case individually. when I try to merge the coverage of test_1, test_2, and test_3, the functional coverage was 45%. Then I changed order during merging i.e:- test_3, test_1, and test_2, functional coverage was 65 %. 

      By changing the order of test cases, during merging the functional coverage got increased.!  Could someone explain to me, How functional coverage increased by changing the order of test cases during merging?

  • Cancel
Parents
  • StephenH
    StephenH over 4 years ago

    Check the log messages carefully, the information there should tell you. Often it's because you're picking one of the tests to provide the resultant model (structure) of the coverage, and the other tests have different models so any non-overlapping items will get dropped from the merge. For example if you have bins 1,2,3,4,5 in your 1st test, and bins 3,4,5,6,7 in your 2nd test, only 3,4,5 from the 2nd test would merge to the resulting merge file.

    This does depend on your merge command and any preceding merge_config commands that control how the merge is done; you can do a union, pick a primary run (as described above) or even take an empty model and merge only selected items. Please read the docs, there is a very details guide on coverage merging that explains all of this.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sriganeshd
    sriganeshd over 4 years ago in reply to StephenH

    Thanks for your response. I want to take all the non-overlapping bins also. It should not be dropped. For that what I should do.?   

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • sriganeshd
    sriganeshd over 4 years ago in reply to StephenH

    Thanks for your response. I want to take all the non-overlapping bins also. It should not be dropped. For that what I should do.?   

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • StephenH
    StephenH over 4 years ago in reply to sriganeshd

    Then you need "union" merging. There's a great coverage tutorial here: Merging Coverage using IMC - Rapid Adoption Kit (RAK) and i strongly recommend that you study it. You haven't provided any detail of your current flow / scripts, and there are many factors that would need to be considered before anyone could give you a definitive answer for what command suits your need.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sriganeshd
    sriganeshd over 4 years ago in reply to StephenH

    All I did is, I have created a "merge.cmd"  file, then I execute  "imc -exec merge.cmd".  that's it.  

                    

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sriganeshd
    sriganeshd over 4 years ago in reply to StephenH

    Hi, 

      I have used "union" in the merge_config command. but I getting the same result. non-overlapping bins are dropping. 

      I have used is following commands,

             1)imc -batch 

             2) merge_config test_2 test_1 -resolution union 

             3) merge test_1 test_2 -out all

       I want both functional and code coverage of each test should be merged together without any dropping

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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