• 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. Regarding Clock Spec file

Stats

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

Regarding Clock Spec file

Ganga111AtFPS
Ganga111AtFPS over 13 years ago

 Hi I have some doubts in spec file declaration.

MaxDelay =?

MinDelay =?

MaxSkew =?

SinkMaxTran =?

BufMaxTran =?

RootInputTran =?

How can we decide and on what basis we decide those values ? Are those values design dependent ?

AFTER CTS::

1) How can we get know that all flops are getting clock?

I mean the flops in netlist and the clocked flops after CTS should be equal inorder to ensure that all flops are getting clock.

2) What is the procedure to decide the no. of  clocked flops in a design aftet CTS ? Is there any command to perform this operaton ?

3) can the encounter tool creates through pin for generated clocks inorder to supply the clock for the flops which are triggered by generated clock ? 

4) How can we know the max skew in our design from clock.report file ? 

  • Cancel
  • archive
    archive over 13 years ago

    Hi,

    All the clock tree spec file entries are documented in the EDI User Guide, "Synthesizing Clock Trees" chapter.

    Here's a summary of those you mentioned above:

    MaxDelay = maximum phase delay constraint (default 10 ns)

    MinDelay = minimum phase delay constraint (default 0 ns)

    MaxSkew = maximum skew between sinks (default 300ps)

    SinkMaxTran = maximum input transition time constraint for sinks (default 400ps)

    BufMaxTran = maximum input transition time constraint for buffers (default 400ps)

    RootInputTran = input transition time for input pins/ports (overrides SDC set_input_transition)

    Cheers,

    Chris

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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