• 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. vr_ad reset check

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 66
  • Views 13844
  • 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

vr_ad reset check

Ravisinha
Ravisinha over 14 years ago
Hi all, When we define as vr_ad reg_fld for each reg_file we used to provide the reset value of each field. As i know the application for this is when we call reset() function for that reg_file it will overwritten with a reset value whatever we have assigned. My doubt here is can it be use for doing a reset check.. For example whenever i do a read of some register i need not to provide the extra check method in my code for checking the reset value and it should be done automatically with vr_ad compare_and_update() method w.r.t the reset value of corresponding reg_def. Thanks Ravi
  • Cancel
Parents
  • StephenH
    StephenH over 14 years ago

    Hi Ravi.

    vr_ad doesn't explicitly cover or check for reset values, however if you reset a register and subsequently read it before writing it, then the value you read and check will be the reset value. In this case vr_ad will be checking the reset value implicitly.

    If you look at the vrad/examples/vr_ad_reg_sequence_lib.e you'll find some helpful pre-defined register sequences. For example the CHECK_RESET_VALUES sequence will go through all the registers checking their reset values. You can evenoverride the list of registers so that the sequence checks only a specific subset of the registers, or you can use it to force the order of checking.

    If you need some coverage to tell whether a register's reset value was read, you could easily extend the base vr_ad_reg with a new boolean field that gets set TRUE by the reset() method, and cleared after covering its value in post_access(). Thus when the flag is covered TRUE you know you've checked the reset value for that register.

    Hope this helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 14 years ago

    Hi Ravi.

    vr_ad doesn't explicitly cover or check for reset values, however if you reset a register and subsequently read it before writing it, then the value you read and check will be the reset value. In this case vr_ad will be checking the reset value implicitly.

    If you look at the vrad/examples/vr_ad_reg_sequence_lib.e you'll find some helpful pre-defined register sequences. For example the CHECK_RESET_VALUES sequence will go through all the registers checking their reset values. You can evenoverride the list of registers so that the sequence checks only a specific subset of the registers, or you can use it to force the order of checking.

    If you need some coverage to tell whether a register's reset value was read, you could easily extend the base vr_ad_reg with a new boolean field that gets set TRUE by the reset() method, and cleared after covering its value in post_access(). Thus when the flag is covered TRUE you know you've checked the reset value for that register.

    Hope this helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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