Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 15442
  • 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 database not getting merged

sautech

 hi

I tried to merge functional coverage for 2 test. its not getting merged. it always show same figure.

can anybody comment on it. further when I collect coverage for individual test, for both test, it shows 30%. but for second test when I see internal covergroup figures, those are different. strange behaviour. I am using IRUN to dump coverage data.

 I am using following commands to merge it.

set_dut_modules DUT_TOP
merge ./coverage/design/test1 ./coverage/design/test2 -output all_tests
load_test ./coverage/design/all_tests
report_html  * > ./coverage/report.html
view_graphics

Your help will be highly appreciated. thanks in advance.

-saurabh

 

Parents

  • sorry guys. ignore previous solution, that i gave. it doesn't work fully.

    the real issue was "set_dut_modules <top_module>".

    if you have set your dut module while merging, it will try to merge only this module across all tests. in my case i had testbench classes in compilation unit scope and hence was not merging it. by not setting set_dut_modules, it worked fine for me without any more issues.

     

    --saurabh makwana 

Reply

  • sorry guys. ignore previous solution, that i gave. it doesn't work fully.

    the real issue was "set_dut_modules <top_module>".

    if you have set your dut module while merging, it will try to merge only this module across all tests. in my case i had testbench classes in compilation unit scope and hence was not merging it. by not setting set_dut_modules, it worked fine for me without any more issues.

     

    --saurabh makwana 

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.