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: per_instance coverage
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
bug_hunter
Posts: 2
Online: User is Offline
10/31/2007 6:17 AM  
Hello,
My eVC has a configurable list of agents. Every agent in the list may be of kind SLAVE or MASTER.
Of course, every agent kind has some configuration fields in common and other fields are idividual to
SLAVE and MASTER agent kinds.  Hence,  the configuration struct looks like this:


struct my_config_s {
   agent_name : agent_name_t;    
   agent_type : agent_type_t;

   a : uint(bits:5);
   
   event my_cov_ev;
   cover my_cov_ev is {
     item agent_type using per_instance;
     item a;
   };

   when MASTER config_s {
      master_b : bool;

      cover my_cov_ev is also {
         item master_b;
      };
   };

   when SLAVE config_s {
      slave_b : bool;

      cover my_cov_ev is also {
         item slave_b;
      };
   };
};


I can see in the coverage browser that every cover group instance for every agent has all possible cover items no matter of the agent kind. The strange thing is, that I see e.g. the master_b cover item incremented inside the cover group for the agent of kind SLAVE!. What I would expect is that every cover item added by e.g the MASTER "when" inheritance is left empty ( = 0) and is never incremented inside a SLAVE agent kind.

Has somebody made the same experiance and an explanation for this behaviour? Do I miss something?

Thanks in advance,
bug_hunter
hannes
Posts: 30
Online: User is Offline
12/03/2007 9:21 AM  
Hello bug_hunter,

when you write:
     . . .
     cover my_cov_ev is also {
         item master_b;
      };
      . . .
you will extend the base coverage definition.

What you are looking for is to do a conditional extension of the coverage
definition, which would look like this:
      . . .
      cover my_cov_ev(agent_type==MASTER) is also {
         item master_b;
      };
      . . .

Regards,
-hannes 
bug_hunter
Posts: 2
Online: User is Offline
12/04/2007 10:54 PM  
Thanks, hannes.
I'll try this....

Regards,
bug_hunter
Posting to forums is available to community members only.
Login or Register
Forums > Functional Verification > e > per_instance coverage


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.