Stats

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

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
Parents

  • 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
Reply

  • 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
Children
No Data

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.