• 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. unique and priority in SV

Stats

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

unique and priority in SV

hipooja
hipooja over 15 years ago

I wanted to check if my understanding on the usage of unique and priority keywords is correct or not.Unique i understand is a keyword used to tell the synthesis tool to infer a simple mux.The statements would be evaluated in parallel and which ever becomes true ,is executed.The advantage of using 'unique' keyword is that it gives warning messages when the conditions are not mutually exclusive,and hence would be best suited for applications such as processing a read and write request to memory ,read and write requests must not overlap,incase they do ,it should be reported as an error.

 

Priority keyword is to inform the synthesis tool ,to infer a priority mux.This may be used to implement a priority arbitration mechanism.

Conditions are evaluated in priority.

 

Examples of the usage of these keywords used in TB which you have worked on will be appreciated.

 

Regards,

Pooja

  • Cancel
  • Shalom B
    Shalom B over 15 years ago

    Hi,

     'priority' is a misleading name. Even without 'priority', the conditions will be evaluated in order and the first one to be found true will be taken. 'priority' is just a contrast to 'unique', where the logic can be synthesized without priority logic.

    What 'priority' does give you is a check that at least one of the specified conditions (including 'default') is true. If none of them is true, then the simulator issues a violation message. In synthesis, this is like a full_case directive.

    'unique' also does this check in addition to the mutual exclusivity check. Thus, 'unique' is like specifying both full_case and parallel_case.

    Shalom

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Vinayhonnavara
    Vinayhonnavara over 15 years ago

     To make it simple default is priority (the first true branching element is executed)

    You specify unique when you do not want to have contention between two or more branching case items.

     

    Vinay Honnavara

    vinayh@keyutech.com

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • hipooja
    hipooja over 15 years ago

     Thanks Shalom and Vinay,

     

    I am now pretty certain that priority keyword infers a priority mux (which happens even without the 'priority' keyword)

    and it the advantage of using priority is that it issues a run-time warning if all the cases are not covered

     

    Thanks,

    Pooja

    • 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