• 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

    Well, I would worry about it. :-)

    When you  wrote the assertion you obviously thought that the trigger was possible and that you needed to check for certain behavior when it occurred. If IFV reports that the trigger is impossible you need to figure out what that means. Why can't the trigger occur? Did you write it correctly? Is there a bug in the DUT that makes behavior you expected to be legal impossible? Why did someone give you a specification describing behavior for conditions that can never be seen?

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

    Well, I would worry about it. :-)

    When you  wrote the assertion you obviously thought that the trigger was possible and that you needed to check for certain behavior when it occurred. If IFV reports that the trigger is impossible you need to figure out what that means. Why can't the trigger occur? Did you write it correctly? Is there a bug in the DUT that makes behavior you expected to be legal impossible? Why did someone give you a specification describing behavior for conditions that can never be seen?

    • 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