Stats

  • Locked Locked
  • Replies 12
  • Subscribers 64
  • Views 18483
  • 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

PSL endpoints and ended()

archive

I need to write a property that states if conditon A occurs then SeqA or SeqB must have occured.

The PSL built-in ended() is not supported in IFV 5.7-s5.  So, I can't do either of these:
always {A} |-> {ended(SeqA) | ended(SeqB)}
 
never (A & ~(ended(SeqA) | ended(SeqB))

Also, I get this error when calling SeqA and SeqB endpoints.
endpoint SeqA ...
endpoint SeqB ...

always {A} |-> {SeqA | SeqB}
                   |
"Endpoints and sequences are illegal as verilog operands."

Does anyone have another idea how this can be done?

Thanks,

Ross


Originally posted in cdnusers.org by weberrm
Parents

  • Thanks,

    This works:
    //psl assert always( {a} |-> {{SeqA} | {SeqB}} )@(posedge clk);

    This still gets the error:
    //psl assert never( {a} & ~({SeqA} | {SeqB}) )@(posedge clk);
                                    |
    ncvlog: *E,PSVERO (test.v,9|32): Endpoints and sequences are illegal as verilog operands.  Check sequence composition syntax.

    I guess I'll go with the always...


    Originally posted in cdnusers.org by weberrm
Reply

  • Thanks,

    This works:
    //psl assert always( {a} |-> {{SeqA} | {SeqB}} )@(posedge clk);

    This still gets the error:
    //psl assert never( {a} & ~({SeqA} | {SeqB}) )@(posedge clk);
                                    |
    ncvlog: *E,PSVERO (test.v,9|32): Endpoints and sequences are illegal as verilog operands.  Check sequence composition syntax.

    I guess I'll go with the always...


    Originally posted in cdnusers.org by weberrm
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.