• 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. How to write sdc for pre/post CTS ?

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 94
  • Views 10553
  • 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

How to write sdc for pre/post CTS ?

yamakazu
yamakazu over 10 years ago

I want to set different clock uncertainity values in the same sdc file for both pre and post CTS modes. Can I do that ? The following sdc didn't work. How to do that ?

if {[getAnalysisMode -clockPropagation -quiet] == "forcedIdeal"} {
    set jit_add 0.2
} else {
    set jit_add 0
}
set_clock_uncertainty [expr 0.200+${jit_add}] \
  -from [get_clocks {my_clk}] -to [get_clocks {my_clk}]

  • Cancel
Parents
  • fitz
    fitz over 10 years ago
    You missed the point completely ... one source to rule them all. ( or as few as possible )
    Let the tools take care of the preCTS and postCTS variations for you.
    You modify your optimization stage margins within the run script not the constraints.

    In the real MMMC world there is rarely just one clock , never one mode and you are guaranteed more than one corner.
    You cannot possibly keep track of all the combinations and permutations manually ... Let the tools do the work for you!!

    My current very old school 65nm SOC eco has 5 separate clocks, two functional modes and three DFT modes across four corners.
    That’s 5 ideal mode constraint source files across 4 corners ... and do the math ... 20 postCTS variants.
    Wait till you see the 14nm corners!

    As always the K.I.S.S. principal rules supreme ... Let the tools do their job.

    Shawn
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • fitz
    fitz over 10 years ago
    You missed the point completely ... one source to rule them all. ( or as few as possible )
    Let the tools take care of the preCTS and postCTS variations for you.
    You modify your optimization stage margins within the run script not the constraints.

    In the real MMMC world there is rarely just one clock , never one mode and you are guaranteed more than one corner.
    You cannot possibly keep track of all the combinations and permutations manually ... Let the tools do the work for you!!

    My current very old school 65nm SOC eco has 5 separate clocks, two functional modes and three DFT modes across four corners.
    That’s 5 ideal mode constraint source files across 4 corners ... and do the math ... 20 postCTS variants.
    Wait till you see the 14nm corners!

    As always the K.I.S.S. principal rules supreme ... Let the tools do their job.

    Shawn
    • 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