• 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. Creating cross-coveraghe within vr_ad

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 13090
  • 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
archive over 17 years ago

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
  • Cancel
  • archive
    archive over 17 years ago

    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
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stelix
    stelix over 17 years ago

    Hi Maurizio,

    If the registers are part of the same register file (group, map), then you should probably add the cross between XX_a and YY_b at the group level (I would not add it inside XX or YY though). The sampling event for the register file would be the same for XX and YY, but I would still define it as:

    event reg_file_access is @XX.reg_access or @YY.reg_access;

    If the registers are NOT part of the same register file, then they could be updated at different times and hence you need to

    a) Select an appropriate container/observer (the agent would probably be best)

    b) Define a sampling event:
        event reg_file_access is @my_reg_file1.XX.reg_access or @my_reg_file2.YY.reg_access;

    The good thing about defining these events is that they make it easy to do coverage per unit instance.

    You can also take a look at ${IPCM}/util_lib/vr_ad/examples/vr_ad_reg_cover.e for some other interesting examples. 

    Hope this helps,

     -Stelix.

    • 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