Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 13522
  • 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, prove one assertion

archive

Sometimes I want to prove just one assertion or cover.  I run the steps below filling in the last assertion step with the assertion or cover requested.
 
assertion -delete -cover
assertion -delete -specification
assertion -add assertion [-specification | -cover]
prove
 
Any suggestions on how to automate this?  Ideally, I would like to right-click the assertion and click prove from menu.

Thanks!


Originally posted in cdnusers.org by weberrm

  • I would write a TCL procedure that takes the assertion name as the parameter ( or the type as you asked for):

    proc only_prove { prop_name } {
    assertion -delete -cover
    assertion -delete -specification
    assertion -add $prop_name
    prove
    }

    then you can just do:
    only_prove tb.prop1
    etc

    You can also use this idea to make a new GUI toolbar button.
    Take a look at the following article to see how it's done:
    http://www.cdnusers.org/Forums/tabid/52/forumid/64/postid/3933/view/topic/Default.aspx



    Originally posted in cdnusers.org by stephenh

  • Steve,

    I implemented the button as you suggested. This works well in conjunction with a custom button that runs the following tcl code for this button:

    only_prove %s

    Make sure you click the box for "selection sensitive to selection" and select from the drop down to make this a FormalVerifier script command.

    Consider not delelting all assertions in the proc as you will not be able to get results at the end of the run via the assertion -show command. In otherwords, put the commands:

    ass -del -all

    in the base tcl script and have the proc add the specified assertion and prove. You will then accumulate results in the gui and ass -show tcl command.

    JB


    Originally posted in cdnusers.org by jb

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.