Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 13783
  • 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

The clock propagating delay to the capture ff clk pin

archive

When I looked into FE timing report after clock tree build, I am expecting the actual clock propagating delay will be used in the setup timing check report.  I did see the actual clock propagating delay to the launch ff clock pin (from clock root through all the buffers/inverters) is used, but for the capture ff, the data required time is simply calculated by: Phase Shift - setup.  For examle, for the timing arc ff-->ff, if the clock cycle is 10ns, capture ff setup time is 0.1ns, then, FE simply told me the required time = 10 - 0.1 = 9.9ns.  Why is the clock delay to the capture ff clock pin (required time)  not calculated by actual clock path propagating delay while the clock path to the launch ff clock pin  did? Did I do something wrong?

Thanks,

Tongju


Originally posted in cdnusers.org by Tongju
Parents

  • Hi Tongju,

    It sounds like something has malfunctioned in the process of switching the design from ideal clock mode to propagated clock mode, and peculiarly it has affected only the capturing clock in your case. I would first look to check whether different clocks driving the launch and capture- they probably are different. If they are different then I would examine the postCTS SDCs you're using and look at the "set_propagated_clock" SDCs that are present. The way clocks are propagated in Encounter is that for each AutoCTSRootPin in your clock tree spec file, a set_propagated_clock statement is appended to your SDCs. If this has malfunctioned for some reason, you'd see it reflected as a missing set_propagated_clock in your postCTS SDCs. Sometimes, users choose to manage clock propagation themselves and insert "set_propagated_clocks [all_clocks]" either interactively or as part of their postCTS SDCs. You may want to try that to see if you can cause the capture clock to be propagated.

    Hope this helps,
    Bob


    Originally posted in cdnusers.org by BobD
Reply

  • Hi Tongju,

    It sounds like something has malfunctioned in the process of switching the design from ideal clock mode to propagated clock mode, and peculiarly it has affected only the capturing clock in your case. I would first look to check whether different clocks driving the launch and capture- they probably are different. If they are different then I would examine the postCTS SDCs you're using and look at the "set_propagated_clock" SDCs that are present. The way clocks are propagated in Encounter is that for each AutoCTSRootPin in your clock tree spec file, a set_propagated_clock statement is appended to your SDCs. If this has malfunctioned for some reason, you'd see it reflected as a missing set_propagated_clock in your postCTS SDCs. Sometimes, users choose to manage clock propagation themselves and insert "set_propagated_clocks [all_clocks]" either interactively or as part of their postCTS SDCs. You may want to try that to see if you can cause the capture clock to be propagated.

    Hope this helps,
    Bob


    Originally posted in cdnusers.org by BobD
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.