• 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. Questions about IFV - PLS Help! - New to IFV

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 67
  • Views 5416
  • 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

Questions about IFV - PLS Help! - New to IFV

alexlop
alexlop over 16 years ago

 Hi,

I am new to IFV (Formal Verifier), I've just started examining this tool a few days ago.

In our company I am the first one to lern it so I have nobody to ask for help but you guys!

 

Let's say I want to check some feature in the design.

I have a state machine and  INPUT1 is "1" for one clock cycle then another clock cycle (on which I don't care about the inputs) followed by third clock cycle on which  INPUT2 is "1, now I want to check if after this sequence can the state machine be at (let's say) "state_7".

First of all how can I  formulate the assumption for that kind of input sequence? I tried :

    sop_one_cycle : assume always {INPUT1} |-> {!INPUT1};
    short_packet : assume always {INPUT1} |-> {!INPUT2; INPUT2};

    coverS7 : cover {current_state == 7} @ (posedge clk);

but as I understood from "ifvuser.pdf", {!INPUT2; INPUT2} will couse to contradiction as the IFV checks for INPUT2 and !INPUT2 at the same cycle of clock. (However it showed no error message)

Anyway, how can I tell IFV that I want to check sequence of :INPUT1="1":nevermind:INPUT2="1":

Thanks!!!

P.S.

   If this is not the correct place to ask such a question please point me to the right forum.

 

  • Cancel
  • archive
    archive over 16 years ago

     Hi Alexlop,

     You might want to get in touch with your Cadence support person for some IFV help. IFV has good support and they should help you get started on your formal verfication adventure.

    As far as your question goes - it looks like you are trying to shape a specific input stimulus through assumptions. This is a common mistake made by beginners who are familiar with simulation environments (I should know, I was one). Assumptions are used to inform the tool of the DUT's external environment - it is typically not a good idea to use assumptions to specify a directed input sequence like you are trying to do.

    Now, I think your intent is to do some design exploration. This is good and a cool application of IFV. To do this sort of thing - setup assumptions on your design inputs that capture the protocols for those inputs. For instance, if your design uses an AHB interface, then write a set of AHB assumptions so that the tool considers only valid AHB input sequences.

    Next, if you want to see if a specific sequence of events can occur, you write a cover statement like so -

    coverS7: cover {INPUT1 ; !INPUT1 ; INPUT2 ; current_state = 7} @(posedge clk);

    If this sequence is possible, within the set of assumptions on the design, then the tool will show you a trace demonstrating how this can happen. The nice thing about the trace is that if your inputs are not behaving as you (and the design) expect them to, then you can add more input assumptions. If it is not possible for the sequence to occur, then the tool will say that the cover Failed.

    Finally, this is the right forum for this type of question and you should find an adequate level of support here. Let me know if this helped.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 16 years ago

     Further, if you wanted the second term of the cover to be"nevermind" then you can write it like so -

    s7: cover  {INPUT1; true; INPUT2; current_state= 7} @(posedge clk);

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • alexlop
    alexlop over 16 years ago

    Thank you FormalGuy.

    I haven't tried it yet because I am out of my office for a few days, but I try it as soon as I get back.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • alexlop
    alexlop over 16 years ago

     Thanks FormalGuy! Everything worked just like I ment.

     

    Anyway for those who have no idea what is PSL and how to use it, I've found a nice tutorial: http://www.project-veripage.com/psl_tutorial_1.php

    (I find PSL easeir to lern than OVL)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • alexlop
    alexlop over 16 years ago

     HELLO GUYS!

    I have another question.

    I am trying to tell IFV to assume that a packet starts with 'sop' and ends with 'eop' so that it will not look through options like 'eop' without 'sop' and 'sop' followed by 'sop'.

     I tried the following :

    assume_packet_length : assume always ({sop} => {(!sop && !eop)[*4:100];eop}) @ (posedge clk_l);

    but IFV doesn't like this, it shows vacuity problem.

    What is the reason for this and how can I solve this problem.

     Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ckomar
    ckomar over 16 years ago

    Hi,

     I would strongly encourage you to contact your local AE.  We have a training that will answer your questions. In addition, our training labs include an example that has an sop/eop protocol.  My guess is you'll be able to take those assertions from the lab, learn how/why they work and drop them into your design at the same time as learning all the other goodness about IFV.

     My guess is that this will be the fastest route to getting you going.

     Thanks,

    Chris

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • alexlop
    alexlop over 16 years ago

     Thanks ckomar.

     

    I have another question (to all of you).

    How can I check (if it is possible at all) that specific signal has or has not 'z' or 'x' values?

    Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JoergM
    JoergM over 16 years ago

    Hi Alex,

    there is a built-in function in PSL and SVA: isunknown(<bit_vector>). It performs the check you are asking for. In IFV it will return false unless you configure IFV to evaluate Z on tristate signals.

    Joerg.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • srinisv
    srinisv over 16 years ago

    Hi Guys,

           I  have one question. How can i check a combo module with the IFV. IFV ask for the clock.

    let say there 2 input signals and 2 o/p's

    IN1, IN2 , OUT1, OUT2

    the o/p depends on the both inputs as shown below.

    when ever (IN1 == x) && (IN2 == y) then (OUT1 == m) && (OUT == n)

     i had tried the following assertions.

    Lable_1: assert propery

    (

    (IN1 == x) && (IN2 == y))  |-> ((OUT1 == m) && (OUT == n))

    );

    the above assertion gives the error that clock is not spsified

    then i tried that

    assert always

    {

    (IN1 == x) && (IN2 == y))  |-> ((OUT1 == m) && (OUT == n))

    };

     the above assertion is not behaving in the intended way. please help me out

     Thanks

    Sri

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JoergM
    JoergM over 16 years ago

    Hi Sri

    I assume you want to describe the following property:

    // psl p1: assert always ((IN1 == x) && (IN2 == y))  -> ((OUT1 == m) && (OUT == n));

    Note the difference in the brackets ("()" for boolean and "{}" for sequences) and the implication operater "->" for booleans (rather than "|->" for sequences). The above syntax works without a clock. In SVA this is more difficult...

     Joerg.

    • 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