• 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. how to aggregate tests and results

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 13492
  • 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

how to aggregate tests and results

archive
archive over 17 years ago

Hi,

It is the first time I used formal verification. In my case, I verified an internal bus protocol by writing some PSL assertions. I developped some overconstraints to configure the tool : like never write or never read an so on...
But I am not allowed to change them unless a reset command is done, that I do not want to issue. Is the tool is able to aggreate the results in different configurations?

Do you have another ideas apart from merging scripts ?

Thanks for your answers

Fred


Originally posted in cdnusers.org by e_vangelist
  • Cancel
Parents
  • archive
    archive over 17 years ago

    Hi Fred,

    I still don't fully understand.

    If a property does not trigger in one environment, then it will also not trigger if you add constraints (overconstraint). Only if you remove constraints there is a chance to trigger previously untriggered properties.

    If you want to verify a set of protocol properties I recommend to systematically inject errors in the design and test if they are caught by the properties. Other methods include back to back testing. The IFV Advanced Training has a section dedicated to this type of property development and verification.

    Regards,
    Joerg.


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

    Hi Fred,

    I still don't fully understand.

    If a property does not trigger in one environment, then it will also not trigger if you add constraints (overconstraint). Only if you remove constraints there is a chance to trigger previously untriggered properties.

    If you want to verify a set of protocol properties I recommend to systematically inject errors in the design and test if they are caught by the properties. Other methods include back to back testing. The IFV Advanced Training has a section dedicated to this type of property development and verification.

    Regards,
    Joerg.


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