• 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. Logic Design
  3. Specifying timing path for synchronous circuits

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 62
  • Views 15487
  • 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

Specifying timing path for synchronous circuits

gchalive
gchalive over 15 years ago

 Hi..

 How do I specify a timing path of a synchronous circuit in Cadence RTL Compielr. What I want is to synthesize the circuit considering the path I specified as the critical path. 

Suppose I have two seqential elements and a combinational logic in between that generates the clock of the second flip flop, I want my critical path delay to be (clk_q)FF1+Comb_delay+(clk_q)FF2. Is there a command in RC that does this.

 

Thanks

 

  • Cancel
Parents
  • grasshopper
    grasshopper over 15 years ago

     I guess we will now have to compound your understanding of my comment with my understanding of yours :)

    Your understanding seems correct. However, I can think of some caveats to your comments:

    In (4) it does not necessarily imply async circuits since input and output can have a clock reference and, in fact, it could even be the same reference. 

    In the case of your question you have to be careful when you say the synthesis tool will not see the path as valid since there are a variety of circuit that synthesis tools will see as combinational clouds (pulse generators, clock doublers, etc.) and will analyze & optimize. What the tools will not do is infer how such clouds would modify the behavior of the clock. For example, a clock doubling circuit would not automatically end up with a clock of double the frequency on the output. Instead, the synthesis tool would propagate the original clock waveform on all loads. Also bear in mind that for STA, tools do not allow combinational timing loops (since they would analyze forever) so the tools will break the timing loop for analysis purposes only.

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • grasshopper
    grasshopper over 15 years ago

     I guess we will now have to compound your understanding of my comment with my understanding of yours :)

    Your understanding seems correct. However, I can think of some caveats to your comments:

    In (4) it does not necessarily imply async circuits since input and output can have a clock reference and, in fact, it could even be the same reference. 

    In the case of your question you have to be careful when you say the synthesis tool will not see the path as valid since there are a variety of circuit that synthesis tools will see as combinational clouds (pulse generators, clock doublers, etc.) and will analyze & optimize. What the tools will not do is infer how such clouds would modify the behavior of the clock. For example, a clock doubling circuit would not automatically end up with a clock of double the frequency on the output. Instead, the synthesis tool would propagate the original clock waveform on all loads. Also bear in mind that for STA, tools do not allow combinational timing loops (since they would analyze forever) so the tools will break the timing loop for analysis purposes only.

    gh-

    • 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