• 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. Auxiliary code:Tick event not synthesiseable

Stats

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

Auxiliary code:Tick event not synthesiseable

archive
archive over 17 years ago

Hi,

why is a tick event without defining rising or falling edge not allowed in auxiliary code (" elsif clock'event then ..."), as it is a legal construct for use in a testbench and doesn't have to be synthesisable?

Thanks.


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

    Hi Thomas666,

    tick event without defining rising or falling edge is not synthesizable and therefore it is not going to work in IFV. What are you trying to model which requires tick event without defining rising/falling edge? Please provide more information so we can address it properly.

    Regards,
    Amir


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

    Hi Thomas666,

    tick event without defining rising or falling edge is not synthesizable and therefore it is not going to work in IFV. What are you trying to model which requires tick event without defining rising/falling edge? Please provide more information so we can address it properly.

    Regards,
    Amir


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