• 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. Digital Implementation
  3. Can Encounter add some delay elements automatically ?!

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 12870
  • 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

Can Encounter add some delay elements automatically ?!

amrzahir
amrzahir over 15 years ago
I want to add some delay in an input path to the design. The problem is a hold violation, the input data changes before registering it. In other words, what is the constraint to be given to Encounter to add a delay (fix the hold violation on the input ports). Thanks
  • Cancel
Parents
  • BobD
    BobD over 15 years ago

    If I follow your situation correctly, this type of violation should be fixed by the tool automatically with "optDesign [-postCTS | -postRoute] -hold".  You shouldn't have to add any special constraints to the design other than create_clock statements for the launching port and capturing register and a set_input_delay constraint on the input port.

    If you can see the violation reported, then optDesign should try to fix it.

    Hope this helps,
    Bob

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • BobD
    BobD over 15 years ago

    If I follow your situation correctly, this type of violation should be fixed by the tool automatically with "optDesign [-postCTS | -postRoute] -hold".  You shouldn't have to add any special constraints to the design other than create_clock statements for the launching port and capturing register and a set_input_delay constraint on the input port.

    If you can see the violation reported, then optDesign should try to fix it.

    Hope this helps,
    Bob

     

    • 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