Friday, November 21, 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
Forums > Functional Verification > e

Subject: Coverage customization for multiple eVC instances
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
angelo.diblasi
Posts: 3
Online: User is Offline
10/04/2007 4:55 AM  
Dear all,

I have the following issue. In my environment I have more instances
of an eRM compliant eVC and each instance has different settings,
then it supports only a subset of the available features. This means
that my coverage will always contain holes (for those items of no
ineterest for a given instance). Does anybody know how to get a
coverage "customized" on the current eVC instance? I mean, is there
a way to tell to Specman that for instance A I want the coverage of
item my_Item limited to values 1, 2 and 3, while for instance B the
values for my_Item can be 2 and 4?

Thanks in advance for your help.

Best regards,
Angelo.
jhzhang
Moderator
Posts: 7
Online: User is Offline
10/04/2007 5:09 AM  
Hi Angelo, just like the rest of Specman, coverage groups (and the items contained within) are extensible. So you can add new coverage items to a coverage group as well as place filtering conditions on existing items. You should consult the Coverage Constructs section (chapter 16) of the e Language Reference manual for details.

Joseph
angelo.diblasi
Posts: 3
Online: User is Offline
10/04/2007 6:03 AM  
Hi Joseph,

thanks for you response, I have already gone through that chapter. I also read chapter 8 of the Verification
Advisor book (honestly it is the manual for Specman 4.3.3, but I suppose it is still valid). Here, in section 8.10.1,
I found some tips about how to properly collect coverage in structs that have a multiple number of instances
and it is quite interesting for me the Note 60 and 61, but there I couldn't find any example. Can you help me?

Angelo
pjigar
Posts: 22
Online: User is Offline
10/04/2007 10:45 AM  
Which version of Specman are you using?
Jigar Patel
Lead Consulting Engineer
Cadence Design Systems
jigar@cadence.com
stelix
Moderator
Posts: 14
Online: User is Offline
10/04/2007 2:40 PM  
Hi Angelo,

Here is a simple filtering example:

type my_values_t: [A, B, C, D, E, F]
cover my_values_e is {
item my_value: my_values_t = ...;
};

To filter on a per instance basis, you can:

cover my_values_e(agent == AG3) is also {
-- Ignore values D, E, F for this instance
item my_value using also ignore = (my_value in [D, E, F]);
};

Note that this will ignore values D, E and F but [b]only[/b] in the context of cover group my_values_e of agent instance AG3. If my_value is used in other cover groups, you would have to extend them separately.

Hope this helps,

-Stelix.
Stylianos Diamantidis
Verification Zone Moderator
CDNusers.org
angelo.diblasi
Posts: 3
Online: User is Offline
10/05/2007 12:39 AM  
Hello Stelix,

thanks for your reply, this really helps me. I know that some of the
limitations in coverage modelling have been removed with newer
Specman versions (starting from 6.0 the per_unit_instance is available).

Thanks again for your help.

Kindest regards,
Angelo.
Posting to forums is available to community members only.
Login or Register
Forums > Functional Verification > e > Coverage customization for multiple eVC instances


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.