• 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. SDC file-HOLD and Setup Time

Stats

  • Locked Locked
  • Replies 14
  • Subscribers 90
  • Views 23017
  • 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

SDC file-HOLD and Setup Time

archive
archive over 18 years ago

Hi,
I am just starting using the nano encounter tool. I just wonder if the sdc file we give to the encounter tool should be the same as SDC file we give to the RTL compiler?
I want to connect my synthesized block to a memory with specific setup hold time. Does anyone has an idea how to give the encounter tool the specific setup time and hold time? how to put a constrain on its output and input port for setup and hold time?

Thanks,

Houman
 


Originally posted in cdnusers.org by houmanh
  • Cancel
Parents
  • archive
    archive over 18 years ago

    The semantics to  set_output_delay -min   are   (IMHO) inverse from what
    one might expect .

    If you were to picture the set_output_delay -min contraint as as the hold check on
    a flip-flop in the fanout of the output port, you would assume that a positive value
    would make the check more conservative - this is  not the case.

    The value specified for set_output_delay -min is subtracted from the clock
    edge. If the value is positive, then the required time is earlier, and
    hence the slack is increased.

    A negative set_output_delay min means that the data is required to stick
    around past the reference clock - which decreases the slack.

    The polarity of hold check values in .lib and those specified in set_output_delay -min
    are not the same.



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

    The semantics to  set_output_delay -min   are   (IMHO) inverse from what
    one might expect .

    If you were to picture the set_output_delay -min contraint as as the hold check on
    a flip-flop in the fanout of the output port, you would assume that a positive value
    would make the check more conservative - this is  not the case.

    The value specified for set_output_delay -min is subtracted from the clock
    edge. If the value is positive, then the required time is earlier, and
    hence the slack is increased.

    A negative set_output_delay min means that the data is required to stick
    around past the reference clock - which decreases the slack.

    The polarity of hold check values in .lib and those specified in set_output_delay -min
    are not the same.



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