Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 13146
  • 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

one covergroup showing twice in emanager vplan tree

whiteriver
Hi all,

After a regression run, my eManager vPlan tree shows a covergroup more than once at one of my scoreboards. It seems that the cover information from the tests are splitted between the two covergroups. I know that this happens if the tests instanciate them with different parameters, but this is not the case. Since the cover information is divided, I can't use it for my verification plan.

Some information:
- I have a few instances of this scoreboard on my testbench and they all show this covergroup twice in the vPlan;
- the scoreboard is parameterized;
- I have 10s of tests but they all use the same parameters;

the covergroup has these options:
  covergroup reg_cov @(cov_trigger);
    option.per_instance = 1;
    option.goal = 100;
    ....
  endgroup

  • No solution for this problem?

    I could find a similar description in cdnshelp on "ICC known problems and solutions" under the id: CCR 561287

     So, again, what I have is one scoreboard with a covergroup. This scoreboard is instantiated 5 times on my top level testbench class, each instance is connected to a different interface (each through a different monitor). Each of the instances shows the same covergroup more than once when I open the verification tree on eplanner or emanager. I believe it has some issue with merging the data from several simulation runs.

    The covergroup has "option.per_instance = 1;" and if I take this option out, the covergroup doesn't show at all in the tools. The scoreboard is parameterized, but the testbench sets the same parameters (constants) for all test runs.

    This problem annoys me because even if the tests fill all coverpoints, they are spreaded between the duplicate entries, making it not possible to map to a verification statement in the plan.

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.