• 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. how to merge the coverage report using IMC?

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 69
  • Views 36271
  • 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

how to merge the coverage report using IMC?

guest4cadence
guest4cadence over 13 years ago

Hi All,

 

I am running the tests using the VIPP OVM using irun. I am able to dump the icc*.ucd. Also, I am able to open the coverage of each test using the IMC gui and not ICCR.

But, when it comes to merge IMC doesn't support the gui mode merge. Can some1 help me how to merge and generate the coverage report.

 

 Thanks

  • Cancel
  • AmitGupta
    AmitGupta over 13 years ago

    Currently IMC does not support merge in GUI. For merge you need to invoke IMC in batch mode, specify the merge config option and the apply merge. For example consider the following runs –

    ./cov_work/scope/test1/
    ./cov_work/scope/test2/
    ./cov_work/scope/test3/

    To merge coverage for the above runs to all, use:
    imc>> merge test1 test2 test3 -out all

    After the merge operation, merged results (both .ucm and .ucd files) will be stored in ./cov_work/scope/all

    Further to generate reports you can load the merged database and generate reports – imc>>load –run all imc>> report –html/detal/summary –metrics -out path

    For details you can refer to IMC UserGuide also please feel free to get in touch with me in case you need further information regarding any IMC operation.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • smubarak
    smubarak over 13 years ago

    Hi,

     I am trying to merge my coverage results from regrssion with imc or iccr , but the tool gives some error even for a simple packet example.

    IMC: getting error : "Data projrction failed "

    ICCR: failed due to mismatch in design checksum with the loaded model file "cov_work/scope/icc70938af1_63e43f52.ucm".

    options used :-

    irun test1.sv -covtest  test1 -coverage all covdut test1 

    irun test1.sv -covtest  test1 -coverage all covdut test1 

    imc -batch imc.cmd

    imc.cmd:-

     merge cov_work/scope/test* -out result  [ ERROR: Data projection failed , when laoding 2nd test]

     

    Can You please help me on this.

    Thanks

    Siraj 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tpylant
    tpylant over 13 years ago
    Are you really executing the same command line two times or did you not paste correctly? Also, you did not specify which version of the tool you are using.

    Tim
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • etng
    etng over 10 years ago

    Hi,

    I'd like to merge a few coverage results using imc batch mode.

    I'm currently using the gui but if I can do it automatically it will be superb.

    [edit]

    Found how it's done:

    my_run_file contains all the .ucd paths

    imc -execcmd "merge -runfile my_run_file -out merge_s -metrics toggle -initial_model union_all;load -run cov_work/scope/merge_s/;report_metrics -out report_s -detail -metrics toggle -inst sim_top"

    Thanks,

    Eitan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • VARUN MARICHI
    VARUN MARICHI over 10 years ago

    I am merging using batch mode as directed above but in the merged report it is not ignoring the weight 0 coverpoints. Every coverpoint is having the default weight of 1. where as when I analyze the coverage of a single test case in GUI mode, I am able to observe the weight 0 coverpoints and it is also not being considered for the overall coverage percentage.

    Can you please tell me why this is happening and how to make the merged coverage ignore the weight 0 coverpoints.

    • 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