Stats

  • Locked Locked
  • Replies 1
  • Subscribers 92
  • Views 8754
  • 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

common end point for hold fixes

vkad747

Hi All,

I am looking for adding delay buf at hold endpoints ,trying to trace out common point,so that i can put a buf at that point to see changes across all violating endpoints,I am stuck at the point ,to get the common point for example 1000 unique endpoints,please share your thoughts on how to approach.

  • Hi,

    typically Innovus would prioritize putting hold fixing buffers at the endpoints.

    What are you trying to achieve exactly ? Do you see Innovus not fixing certain paths for hold?

    If so, there might be some reasons for it that you need to investigate.  E.g. one thing to try could be to allow hold fixing on the cost of setup time violations with the following command:set_db opt_fix_hold_allow_setup_tns_degradation false

    Also please refer to this article for some general guidelines on fixing hold violations: Recommendations for fixing hold violations in EDI System / Innovus

    You can use SDC commands  such as all_fanin, all_fanout to try to track these endpoints. However, at a design of that size where you have thousands of endpoints in the fanout, I have a hard time imagining that manually finding a solution will work.

    -Dimo

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.