Monday, October 06, 2008     Register | Login | Search | Contact Us
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Subject: ICC data in eManager
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
artmaj1
Posts: 3
Online: User is Offline
1/04/2008 9:30 AM  
    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?
pjigar
Posts: 22
Online: User is Offline
1/04/2008 10:42 AM  
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.

Jigar Patel
Lead Consulting Engineer
Cadence Design Systems
jigar@cadence.com
efratk
Posts: 1
Online: User is Offline
1/07/2008 6:12 AM  
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!
Posting to forums is available to community members only.
Login or Register



ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.