Stats

  • Locked Locked
  • Replies 1
  • Subscribers 66
  • Views 19530
  • 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

merging code coverage from different design databases

perezi

Hello,

 I searched for similar posts but did not find an answer to what I'm looking for, so I'm asking for some info on code coverage.

 

I would like to merge test results from different simulation runs, each from it's own testbench environment.   I ran different regression tests, two for subsystem and one for the chip level.  I was able to merge all the test results for each subsystem and chip level tests, but now I want to merge the subsystem results into the chip level results to see the overall code coverage?  This is needed since subsystem tests were not replicated at the chip level.  Only a subset and some new tests were used.

 Regression runs

1. Testbench hierarchy tb.subsystemA (chip level hieararchy i_chip.i_subsystemA)

    The coverage results for module subsystemA were merged to tb1/cov_work/i_subsystemA/all

2. Testbench hierarchy tb.subsystemB (chip level hieararchy i_chip.i_subsystemB)

    The coverage results for module subsystemB were merged to tb2/cov_work/i_subsystemB/all

3. tb.i_chip 

    The coverage results for chip were merged to tb3/cov_work/i_chip/all

Now I need to merge these 3 merged results into one merged database?  Is that possible?  Or do I need start from the source tests files?  The problem I get is with the model file being different.

Even merging different subsystem tests into the chip level gives me a model error.

failed due to mismatch in design checksum with the loaded model file "cov_work/i_chip/all/70938af1_63e43f52.ucm".


Thanks in advance. 

  •  Hi,

     In order to merge the coverage databases, you'll need to set the DUT to merge and use the merge iccr command.  

     i.e.

    set_dut_modules subSystemA subSystemB

    This is if subSystemA and subSystemB are the actual module names of the blocks instantiated inside the chip  which you want to merge

    Then use the merge command to merge all the tests

     merge tb3/cov_work/i_chip/all tb1/cov_work/i_subsystemA/all tb2/cov_work/i_subsystemB/all -output combined

     The merged output will be dumped in the directory tb3/cov_work/i_chip/combined

      You can reference either the quick reference manual

     http://sourcelink.cadence.com/docs/files/Release_Info/Docs/iccquick/iccquick8.2/examples/iccqrg.pdf

    or the full user guide

     http://sourcelink.cadence.com/docs/files/Release_Info/Docs/iccug/iccug8.2/iccugTOC.html;jsessionidsl=CAFMRW2DZ2MKTLA0BEBCFEQ

     for the detail description of these commands.

     If you are still seeing problems, just reply to the thread, and I will respond to you.

     BTW, in the future, if you run into any issues with Cadence tools, you can file a ticket to Cadence Support from http://sourcelink.cadence.com

    Regards,

    Nancy

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.