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
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
Parents
  • Thanks  Mickey, Fepcine and Cadence Team for their wonderful support.

    Here is the way it get resolved :

    Till now we are compiling and elaborating "RTL files" in respected Envs independently using "irun" in one and "nc commands" in other. With different commands this creates merging issue in tool even with same arguments and model number file.

    As a solution,now we are not compiling RTL files (design files) again in both Env, instead, we are re-using already compiled worklib of design files of one Env. i.e. `fmr_worklib` located @ .../data/compiled/rtl
    By doing so, we are making sure to have same elaborated data base in use in both Envs and thus merging problem is eliminated in spite of different commands, "irun" and "nc commands".

    Previously, we had also got solution by converting "nc commands" to "irun" too. But, the above change is minor and quickly accepted by Team.

     

    Kind Regards,

    Kinjal Shah
Reply
  • Thanks  Mickey, Fepcine and Cadence Team for their wonderful support.

    Here is the way it get resolved :

    Till now we are compiling and elaborating "RTL files" in respected Envs independently using "irun" in one and "nc commands" in other. With different commands this creates merging issue in tool even with same arguments and model number file.

    As a solution,now we are not compiling RTL files (design files) again in both Env, instead, we are re-using already compiled worklib of design files of one Env. i.e. `fmr_worklib` located @ .../data/compiled/rtl
    By doing so, we are making sure to have same elaborated data base in use in both Envs and thus merging problem is eliminated in spite of different commands, "irun" and "nc commands".

    Previously, we had also got solution by converting "nc commands" to "irun" too. But, the above change is minor and quickly accepted by Team.

     

    Kind Regards,

    Kinjal Shah
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.