• 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. Two sdc files and one design

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 92
  • Views 16794
  • 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

Two sdc files and one design

tsahi
tsahi over 16 years ago
Hi friends,

My name is Tsahi, I am electronics student and beginner in place and route field.

One of the inputs of place and route is the timing constraints (sdc file).

In our mini project there are two sdc files:

1)  Pre cts  SDC file

2) Post cts SDC file

Can someone explain me why is the reason to make to two files and not use just single constraint file.

I attached the files to one zip file in comparing to each other (the left is pre cts, on the right hand post cts) and changes are marked.

Thanks,


Tsahi.
sdc.zip
  • Cancel
Parents
  • BobD
    BobD over 16 years ago

    You're welcome!

    The first 2 items are minor (or perhaps meaningless depending on the caveats I mentioned in italics above). The 3rd item (set_clock_latency) is actually quite important and if not included it would invalidate your IO timing.

    Thanks,
    Bob

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

    You're welcome!

    The first 2 items are minor (or perhaps meaningless depending on the caveats I mentioned in italics above). The 3rd item (set_clock_latency) is actually quite important and if not included it would invalidate your IO timing.

    Thanks,
    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