• 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. PSL

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 65
  • Views 15695
  • 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

natg9
natg9 over 16 years ago

Can anybody help me understand how to use vunit in PSL

please explain the use with appropriate verilog file

 

i am using IFV tool to verify the design

 

thanks in advance

regards

Girish

  • Cancel
Parents
  • StephenH
    StephenH over 16 years ago

    Hi Girish

    In case you're not aware of it, the Cadence tools like IUS and IFV now come with a really good documentation browser called "cdnshelp". If you run cdnshelp, it opens a GUI where you can search the docs for terms like "vunit".

    I'd recommend to read the IFV docs - look into the "book" called "Assertion Writing Guide" in cdnshelp, then navigate into "Using PSL", followed by "Placing PSL Assertions" and finally the section called "Putting PSL Assertions in Verification Units". This gives a lot of detail, but also a good overview on what to put in the vunit, the syntax and how the vunit binds to the design.

    In summary though, a vunit is a side-file that you compile along with your Verilog / VHDL source code. It effectively gets inserted into the module that it binds to, as though you'd typed the vunit code directly in the same module. This lets you access all the module's internal nets, and even add new Verilog code to assist the assertions (e.g. to decode a signal or count values).

    Note that you don't have to put your PSL inside comments in a vunit, since the compiler already knows to expect PSL keywords in the vunit.

    Hope this helps. Let us know if you need more help.

    Steve.

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

    Hi Girish

    In case you're not aware of it, the Cadence tools like IUS and IFV now come with a really good documentation browser called "cdnshelp". If you run cdnshelp, it opens a GUI where you can search the docs for terms like "vunit".

    I'd recommend to read the IFV docs - look into the "book" called "Assertion Writing Guide" in cdnshelp, then navigate into "Using PSL", followed by "Placing PSL Assertions" and finally the section called "Putting PSL Assertions in Verification Units". This gives a lot of detail, but also a good overview on what to put in the vunit, the syntax and how the vunit binds to the design.

    In summary though, a vunit is a side-file that you compile along with your Verilog / VHDL source code. It effectively gets inserted into the module that it binds to, as though you'd typed the vunit code directly in the same module. This lets you access all the module's internal nets, and even add new Verilog code to assist the assertions (e.g. to decode a signal or count values).

    Note that you don't have to put your PSL inside comments in a vunit, since the compiler already knows to expect PSL keywords in the vunit.

    Hope this helps. Let us know if you need more help.

    Steve.

    • 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