Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 14324
  • 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

ICC data in eManager

archive

    Has anybody tried to load ICC data from multiple DUTs that have automatically generated coverage models for each in the same eManager session?

Scenario is that, as an integrator, I want to be able to analyze coverage for all blocks that make up the next level of integration.  The blocks have block level environments that I can easily run together in one session(vsif) (or multiple sessions, one for each but  the problem exists with either method).  Each run in the session creates the coverage models, vplans and coverage data.  I can load the session and do test run analysis on the session with no issues. However, when I go into the vplan view to analyze coverage in eManager, the "merge" fails and no coverage information is calculated.  This was tried with a pre-6.2 version of eManager, so I am using the icc adapter.  Maybe 6.2 helps with this problem.

Anybody try something similar? Solutions?


Originally posted in cdnusers.org by artmaj1
  • archive

    We have introduced unified coverage format in 6.2 so all the simulation engines (specman, ncsim) are capable of writing coverage in common format that enterprise manager can understand. So you would not need to use ICC adapter anymore. You will be able to perform exact same operations (ranking, hole analysis, etc) for code coverage in enterprise manager. Please contact your local AE for migration steps.


    Originally posted in cdnusers.org by pjigar
  • archive

    There is a new configuration flag in EMGR 6.2: ‘rule_for_model_selection’ to control merging of multiple coverage models.
    Options: UNION, DONT_READ, TAKE_LAST
    Default value: UNION

    What each option means:
    1. UNION
    User loads the sessions he wants to analyze, when opening vPlan analysis, EMGR merges all models from all sessions (and all runs) and creates the analysis model.

    2. DONT_READ
    User loads the sessions he wants to analyze. When opening vPlan analysis, EMGR uses the currently loaded model and ignores any session related model.

    3. TAKE_LAST
    User loads the sessions he wants to analyze, when opening vPlan analysis, EMGR uses latest model of each tool as its coverage analysis model

    It seems that the UNION option might satisfy your needs.
    Please note that I'm saying "might" since the merge algorithm in 6.2 can't handle conflicts in case you have more than 1 coverage model. However, as you describe your problem, it seems that you have several different blocks that you are trying to see on one vPlan.
    In this case, where the top nodes are strangers, the merge will work fine.
    Good luck!


    Originally posted in cdnusers.org by efratk

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.