• 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. Temporal expression in e

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 65
  • Views 13894
  • 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

Temporal expression in e

spark
spark over 16 years ago

Hi All,

When I use "expect" to do the timing check, "=>" operator is used in "expect", but "=>"will have one cycle delay, for example

@a => {[1];  @b}; then event b has two cycles delay than event a, if event b can be the same time as event a how to check it?

expect  @a => {[..]; @b;} only indicates event b is later than event a, can not include event b can occur same time as event a.

  • Cancel
Parents
  • spark
    spark over 16 years ago

    Thanks for your reply.

    In another case, if I want to check event b is delay N cycles after event a, N is a signal in HDL code and range of N is >=0. Can I use this kind check, I wonder whether I can use "if else" here.

    if ("N" == 0)  {

        expect (@a and @b);

    };

    else {

       expect @a => {["N"-1]; @b};

    };

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • spark
    spark over 16 years ago

    Thanks for your reply.

    In another case, if I want to check event b is delay N cycles after event a, N is a signal in HDL code and range of N is >=0. Can I use this kind check, I wonder whether I can use "if else" here.

    if ("N" == 0)  {

        expect (@a and @b);

    };

    else {

       expect @a => {["N"-1]; @b};

    };

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information