Home > Community > Forums > Functional Verification > what do you mean by assertion block


* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 what do you mean by assertion block 

Last post Wed, Jul 3 2013 11:28 PM by maheshs. 1 replies.
Started by BharathECE 03 Jul 2013 11:19 PM. Topic has 1 replies and 558 views
Page 1 of 1 (2 items)
Sort Posts:
  • Wed, Jul 3 2013 11:19 PM

    • BharathECE
    • Not Ranked
    • Joined on Fri, Mar 22 2013
    • Hyderabad, Andhra Pradesh
    • Posts 12
    • Points 210
    what do you mean by assertion block Reply


    Iam having some of the assertions result as block.What do you mean by block and how to make those assertions passing or failing. 




    Filed under: , ,
    • Post Points: 20
  • Wed, Jul 3 2013 11:28 PM

    • maheshs
    • Not Ranked
    • Joined on Fri, Aug 7 2009
    • Posts 3
    • Points 15
    Re: what do you mean by assertion block Reply

    IFV can display the status of an assertion as ‘blocked’ if it detects any combinational loop in the signals involved in the assertion's cone-of-influence. The status ‘blocked’ indicates that the assertion could not be verified, because combinational loops exist in the design. Please follow below steps to identify and resolve the combinational loops.

    Step - 1:

    If you get a blocked status, first of all, please run the following command for the blocked assertion. It will let you know if indeed the assertion was blocked because of combinational loops.

    formalVerifier> assertion –show <blocked_assertion_name > -verbose

    For example

    formalVerifier> assertion –show my_assertion –verbose
    my_assertion: Block (0)
    Combinational loop(s) found in the design. Use the debug command to view the nets involved in the combinational loop(s).

    Step 2:

    Now you would be interested in knowing which module has combinational loops and what signals are involved? In order to get this information, please run the "debug" command as suggested below.

    formalverifier> debug my_assertion

    Counter-example launched.
    Number of combinational loop : 1
    1) Net(s) in combinational loop : 2
    combinational_loop.Y (File: ./test.sv)
    combinational_loop.W (File: ./test.sv)

    So now we know that Y, W are the signals involved. It also points out the file name where those signals are declared. We can now easily check the indicated code and remodel the HDL to remove the combinational loop.


    -Mahesh Soni


    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by BharathECE at 03 Jul 2013 11:19 PM. Topic has 1 replies.