• 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. IFV connectivity Check failure debug

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 14234
  • 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

IFV connectivity Check failure debug

rajuchavan1
rajuchavan1 over 10 years ago

Hi, 

I am new to IFV and need your assistance in debugging one of the assertion failure.

Scenario : 

assertion -add -interactive { (<path1>:top_scanb == 0) |-> ((<path2>:out_clk) === (<path3>:in_clk)) } -name test

When the above assertion is RUN, we get Trigger - Pass, Status - Fail (5).

FormalVerifier> debug :test  //opens up Waveform and we observe that top_scanb is 'x'.  

Q1: What is that the tool is checking by making top_scanb = 'x'?

Formal Verifier> assertion -show :test -verbose -list // shows that there are around 85 signals that are uninitialized.

Q2: How to debug this further?

Thanks,

Rajratna

  • Cancel
  • StephenH
    StephenH over 10 years ago
    If a signal is shown as X then its value isn't important for the proof result, so I assume that something else is gating the signal and allowing the property to fail regardless of the value of top_scanb. Fail (5) suggests that there is some sequential logic involved since for a combinational connection you should get a 1 cycle result. You haven't provided enough information to understand the root cause of the issue, and unless you want to share more details of your design on this forum, it might be better to open a support case at support.cadence.com so that you can connect with a formal expert who can guide you through debugging the issue.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rajuchavan1
    rajuchavan1 over 10 years ago

    Hi Stephen,

    Thanks for the reply.

    This is what I intend to do.

    prove that <path1>:clk_out === <path2>:clk_in only when  (<path0>:top_scanb) == 0.

    The assertion I wrote is as follows.

    assertion -add -interactive { (<path1>:top_scanb == 0) -> ((<path2>:out_clk) === (<path3>:in_clk)) } -name test

    Is this assertion correct as per intention?

    Kindly help.

    Thanks and Regards,

    Rajratna

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • TAM1
    TAM1 over 10 years ago

    As  Stephen said, you may need to file a ticket with Cadence Customer Support as debugging a problem in these forums can be difficult.

    What version of the software are you using? Try adding the "define word_level_reduction off" command to your TCL script before the prove command. It has resolved several problems with counter-examples recently in certain versions of the tool.

    Tom

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rajuchavan1
    rajuchavan1 over 10 years ago

    Hi, 

    Thanks, I would raise a support ticket.

    Thanks and Regards,

    Rajratna

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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