• 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. Merging code coverage from two different test benches

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 66
  • Views 31697
  • 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 two different test benches

Nilesh Goswami
Nilesh Goswami over 16 years ago
Hi

I am facing issue while merging code coverage from two different test benches.

Here is my testbench and tools :

One test bench(A) is written in SV and other test bench(B) is written in Verilog.

I am using IUS62 to run test cases and ICCR to merge coverage and generate report.

Both testbenches are pointing to same RTL core but the hierarchy is different.

I ran test case in both the environment and tried to merge code coverage report.

Here, ICCR is not loading the test because different model file (<checksum>.model) are generated.

I would like to know which are the points I should take care while running the test case and while merging coverage.

Please let me know your inputs.

Thanks & Regards,

Nilesh Goswami
  • Cancel
Parents
  • Kinjal
    Kinjal over 16 years ago

    Hi Mickey,

     Thanks for quick reply.

     We tried with your inputs. To be honest, we are not able to merge yet.

     I would like to have one more input here. For irun based testbench we have used " -covdut <module_name>"  and for ncsim testbench we have used "-input <file_name>" and that file contains "coverage -dut x.y.z" .

    Clearly, irun command uses module base and ncsim uses instance based. Does that matter at merge ? If yes, then how to solve?  

    Both Testbeches shows the same model name (489eaa3b_00000000.model), I believe that indicates same coverage database generated.

     As Nilesh has mentioned, we are able to load both successfully at ICCR and while merge command it shows warning. 

     

    With your inputs, I am able to generate the individual testbench reports and that shows the intended module/instance at top. But while merge it shows "0 %" 

     

    Thanks & Regards,

    Kinjal Shah

    kinjal.shah@einfochips.com 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kinjal
    Kinjal over 16 years ago

    Hi Mickey,

     Thanks for quick reply.

     We tried with your inputs. To be honest, we are not able to merge yet.

     I would like to have one more input here. For irun based testbench we have used " -covdut <module_name>"  and for ncsim testbench we have used "-input <file_name>" and that file contains "coverage -dut x.y.z" .

    Clearly, irun command uses module base and ncsim uses instance based. Does that matter at merge ? If yes, then how to solve?  

    Both Testbeches shows the same model name (489eaa3b_00000000.model), I believe that indicates same coverage database generated.

     As Nilesh has mentioned, we are able to load both successfully at ICCR and while merge command it shows warning. 

     

    With your inputs, I am able to generate the individual testbench reports and that shows the intended module/instance at top. But while merge it shows "0 %" 

     

    Thanks & Regards,

    Kinjal Shah

    kinjal.shah@einfochips.com 

    • 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