Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 13095
  • 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

Creating cross-coveraghe within vr_ad

archive

Hi,
does anyone knows a quick method to create a cross coverage between 2 fields belonging to different registers; i.e. I have

reg XX which contains field a

reg YY which contains field b

I would like to create a cross-coverage item (either in reg X or in YY) between fields a and b

Thanks
Maurizio


Originally posted in cdnusers.org by maurizios
Parents

  • Hi Maurizio,

    Normally what I would do is grab the field value from its enclosing reference model by method or by pointing to it.
    This way I can cross reg values with other reg values or with any info I need in the data path. The advantage here is that the sampling event is already taken care of.
    I believe you could also extend the reg_file struct and define the cross items there, but then you'll have to take care of the sampling event, and make sure coverage is only recorded when relevant.

    I hope that helps...

    Yaron


    Originally posted in cdnusers.org by thinkverification
Reply

  • Hi Maurizio,

    Normally what I would do is grab the field value from its enclosing reference model by method or by pointing to it.
    This way I can cross reg values with other reg values or with any info I need in the data path. The advantage here is that the sampling event is already taken care of.
    I believe you could also extend the reg_file struct and define the cross items there, but then you'll have to take care of the sampling event, and make sure coverage is only recorded when relevant.

    I hope that helps...

    Yaron


    Originally posted in cdnusers.org by thinkverification
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.