• 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. Using Assertions to test arbiter priority

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 15013
  • 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

Using Assertions to test arbiter priority

archive
archive over 17 years ago

Can anyone share how they use PSL to test arbiter priority? In other words, if I have multiple req inputs, and the priority is hardcoded (reqA higher than reqB, whch is higher than reqC), how can I use ABV to test this?


Originally posted in cdnusers.org by gobuffs
  • Cancel
  • archive
    archive over 17 years ago

    Hi Gobuffs,

    there are 2 excellent places to look at:

    1) the IAL library (part of any IUS installation) contails a item called ial_arbiter. It is qualified for simulation.
    2) in the IFV installation there are 4 vcomps, one of them is the vcomp_arbiter (IFV62-p001/doc/ifvref/example/meth/verif_docs/vcomp_arbiter.zip). It is qualified for formal verification.

    Both of them can serve as starting point or template for your verification task.

    Regards,
    Joerg.


    Originally posted in cdnusers.org by jmueller
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    I can't find anything in ial_arbiter.vlib that answers my question.  Anyone else have any thoughts?


    Originally posted in cdnusers.org by gobuffs
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    If your arbiter is a priority encoded arbiter. You should be able to create the following series of properties to ensure the priority encoding is working. These properties work on the premise that the currently granted channel has its req asserted and no other higher requests asserted. The goal of these properties is to give you a starting point to customize your own properties for your specific design.

    Given:

    4 input priority encoded arbiter with channels a, b, c, and d. Channel a has the highest priority and d the lowest.

    // psl assert_A_should_be_granted: assert always {gnta} |-> {reqa};
    // psl assert_B_should_be_granted: assert always {gntb} |-> {regb & !rega};
    // psl assert_C_should_be_granted: assert always {gntc} |-> {reqc & !reqa & !reqb};
    // psl assert_D_should_be_granted: assert always {gntd} |-> {reqd & !reqa & !reqb & !reqc};

    You will probably have to fine tune these properties to handle other channels arbitrating for service while the current channel is granted but I hope you get the idea. In reality you may have to create aux signals that you can place into these properties to check for grants at the correct points in time in the arbitration.

    In other words, the language behind assert_A_should_be_granted should read: IF channel a is granted I just have to make sure channel A requested service at the appropriate time.

    For the property assert_D_should_be_granted it should read: If channel d is granted, I must have had no other higher priority channels requesting service.

    Hope this helps.

    JB


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