• 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. timingSelfLoopsNoSkew

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 90
  • Views 12960
  • 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

timingSelfLoopsNoSkew

Scrivner
Scrivner over 13 years ago

Has anyone tried using the  "-timingSelfLoopsNoSkew true" option with setAnalysisMode?

I have a handfull of flops that are showing hold time violations but the timing path on each is between it's own input and output. In the timing report, the clock paths are reported as exactly the same, but the timing on each path is different for some reason.

Encounter documentation for "-timingSelfLoopsNoSkew true" in setAnalysisMode say the option:

"Eliminates clock skew due to clock uncertainty for a path starting and ending at the same register."

But my timing report is exactly the same regardless of whether I set this option to true or false. The hold violation gets flagged either way.

  • Cancel
  • Kari
    Kari over 13 years ago

    Is the clock uncertainty the source of the difference in the path? You could also try:

    set_global timing_cppr_self_loop_mode true


     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Scrivner
    Scrivner over 13 years ago

     Hi Kari - sorry for not responding sooner but we've been working on getting a tapeout completed.

    Both clock paths shown by the report are exactly the same physically. They have slightly different timings that is not related to the clock uncertainty. For example, element clk_L1_I1 in the launch path has a slightly different prop delay from the same element clk_L1_I1 in the capture path (I don't know why this is the case, but I see this happen all the time). Cppr is set to both so it shouldn't be that either. I tried your suggestion of setting the global mentioned but it had no effect. Thanks for the suggestion though.

    • 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