• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Coverage customization for multiple eVC instances

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 13866
  • 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

Coverage customization for multiple eVC instances

archive
archive over 17 years ago

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.


Originally posted in cdnusers.org by angelo.diblasi
  • Cancel
  • archive
    archive over 17 years ago

    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


    Originally posted in cdnusers.org by jhzhang
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    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


    Originally posted in cdnusers.org by angelo.diblasi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Which version of Specman are you using?


    Originally posted in cdnusers.org by pjigar
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    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.


    Originally posted in cdnusers.org by stelix
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    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.


    Originally posted in cdnusers.org by angelo.diblasi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information