• 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. Psl assertions for checking ECC

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 64
  • Views 16885
  • 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

Psl assertions for checking ECC

archive
archive over 18 years ago

Hi all,

I would like to know if it useful to  write the psl assertions for checking the ECC(error correction code).The ECC is a standard algorithm(Hamming Code).

Thanks,


Originally posted in cdnusers.org by abna
  • Cancel
Parents
  • archive
    archive over 18 years ago

    hi,

    Other than running a reference encoder in parallel and writing an assertion to say that both outputs must always be the same, I am not aware of another way to verify this with assertions.

    I assume that there will be a decoder block somewhere in the larger system, or is the ECC data the final output of the chip?
    If you could get the decoder then the previous method will verify both parts.

    Regards,
    Vince.


    Originally posted in cdnusers.org by vincentr
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    hi,

    Other than running a reference encoder in parallel and writing an assertion to say that both outputs must always be the same, I am not aware of another way to verify this with assertions.

    I assume that there will be a decoder block somewhere in the larger system, or is the ECC data the final output of the chip?
    If you could get the decoder then the previous method will verify both parts.

    Regards,
    Vince.


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