Stats

  • Locked Locked
  • Replies 5
  • Subscribers 49
  • Views 19765
  • 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 deselect_coverage for an instance?

sharangdhar

Hi

Need to deselect coverage for memory instance and any logic hierarchy below  from top module.

Using " deselect_coverage -instance dut.mem_i... -be "  option to deselect coverage during elaboration stage. The final coverage report still shows coverage for dut.mem_i and below.

Is there any other option in iccr or irun for deselecting coverage from getting reported?

regards

Sharangdhar

Parents

  • Hi Sharangdhar.

    What coverage types are you seeing under the dut.mem instance? I would not expect to see block or expression, based on your command above, but you might still have FSM and toggle enabled, depending on the preceding select_coverage commands. Are you accidentally using the "-coverage all" option on the run / ncelab command in addition to -covfile? This is a common mistake, and I would recommend always to use a covfile and never the -coverage option (unless you want all the default coverage options, which is pretty rare).

    Can you share your entire coverage control file, so that we can see what else might be impacting this?

    You might also need to "deselect_coverage -all -module <memory_module_name>..." if you had selected module based coverage as well.

    As a post-processing step you can use IMC to exclude complete levels of hierarchy, just select the dut.mem instance in the GUI and click the exclude button in the toolbar. Just remember to save the refinement file (*.vRefine) for future use! I would however recommend fixing the elaboration coverage settings because that will improve simulation speed as well.

    Regards,Steve.

Reply

  • Hi Sharangdhar.

    What coverage types are you seeing under the dut.mem instance? I would not expect to see block or expression, based on your command above, but you might still have FSM and toggle enabled, depending on the preceding select_coverage commands. Are you accidentally using the "-coverage all" option on the run / ncelab command in addition to -covfile? This is a common mistake, and I would recommend always to use a covfile and never the -coverage option (unless you want all the default coverage options, which is pretty rare).

    Can you share your entire coverage control file, so that we can see what else might be impacting this?

    You might also need to "deselect_coverage -all -module <memory_module_name>..." if you had selected module based coverage as well.

    As a post-processing step you can use IMC to exclude complete levels of hierarchy, just select the dut.mem instance in the GUI and click the exclude button in the toolbar. Just remember to save the refinement file (*.vRefine) for future use! I would however recommend fixing the elaboration coverage settings because that will improve simulation speed as well.

    Regards,Steve.

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.