• 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. Trace fail

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 13561
  • 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

Trace fail

Buvna
Buvna over 12 years ago

Hello,

Im running assertions on IFV with witness check defined as trace. The trace fails and the assertion passes. What does this mean?

Thanks. 

  • Cancel
Parents
  • TAM1
    TAM1 over 12 years ago

    There are a couple of ways this can happen. They are based on the principle that an assertion "passes" if IFV cannot find a sequence in which the assertion reaches an error state.

     So, if you have an assertion that looks like "trigger_sequence |-> suffix_sequence", then the assertion will "pass" if the trigger_sequence can never occur. Since the trigger can't occur, the suffix doesn't need to be checked. This is by far the most common way to get the results you have described. 

     You can check to see if the trigger is possible, given your constraints, by issuing the TCL command "define witness_check trigger".

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • TAM1
    TAM1 over 12 years ago

    There are a couple of ways this can happen. They are based on the principle that an assertion "passes" if IFV cannot find a sequence in which the assertion reaches an error state.

     So, if you have an assertion that looks like "trigger_sequence |-> suffix_sequence", then the assertion will "pass" if the trigger_sequence can never occur. Since the trigger can't occur, the suffix doesn't need to be checked. This is by far the most common way to get the results you have described. 

     You can check to see if the trigger is possible, given your constraints, by issuing the TCL command "define witness_check trigger".

    • 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