• 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. Clock definition in sdc file

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 15058
  • 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

Clock definition in sdc file

gdellaca
gdellaca over 10 years ago

Hello,

In my design I need to distribute the clock signal to 32 different external blocks with minimun delay and skew respect to the clock input source. So in my vhdl I defined:

clk_out(31)<=clk_in;

clk_out(30)<=clk_in;

...

clk_out(0)<=clk_in;

In the sdc file I declare these clocks as follow (for each port):

create_generated_clock -source [get_ports {clk_in}] -name clk_out_0 -divide_by 1 [get_ports {clk_out[0]}]

then I set the output delay for each group of combinatorial outputs that should be related to this clk_out.

set_output_delay -clock clk_out_0 0.2 {a[0] b[0] c[0]}

and so on...

Since the clk_out signals are not used inside my design (I use clk_in for the internal logic), the synthesis report "No paths found" for these signals, and during PnR with Encounter the clock outputs are not distributed with a clock tree, but it is inserted only one buffer for all the 32 outputs, giving then a huge delay on these nets.

Please, does anybody know how to force Encounter to propagate these clock outputs with a clock tree like the internal clk_in?

Regards

  • 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