{"id":2575,"date":"2017-07-13T08:20:11","date_gmt":"2017-07-13T08:20:11","guid":{"rendered":"http:\/\/support.plunify.com\/en\/?p=2575"},"modified":"2018-05-05T02:09:54","modified_gmt":"2018-05-05T02:09:54","slug":"closing-timing-is-a-matter-of-fine-clock-margins","status":"publish","type":"post","link":"https:\/\/support.plunify.com\/en\/2017\/07\/13\/closing-timing-is-a-matter-of-fine-clock-margins\/","title":{"rendered":"New InTime Recipe: Timing Closure is a Matter of Fine (Clock) Margins"},"content":{"rendered":"

The difference between passing and failing timing can be tiny, but failing by 500ps is just as frustrating as falling short by 5ns. Clock Margin Exploration is a new recipe in InTime<\/a> version 2.3.0 that over-constrains the user's design, potentially yielding better timing results without modifying the design.<\/p>\n

Use Clock Uncertainty<\/h2>\n

The idea is to apply\u00a0\"Clock Margin\" adjustments at certain implementation stages to focus Vivado's efforts\u00a0at the appropriate stages. As mentioned, this recipe does not modify the design and hence does not affect existing clock edges and relationships. It is a safe and effective recipe.<\/p>\n

InTime will automatically target\u00a0the\u00a0critical clock(s). The user configures the\u00a0amount of margin to be applied, as shown below:<\/p>\n

\"clock_margin_exploration_4\"<\/p>\n