• 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. InsertRepeater violations

Stats

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

InsertRepeater violations

spach
spach over 15 years ago

hi

I am using insertRepeater command with  500um wire length & maxCap 0.51pf as rules, after using this command at preroute & postroute stages still I have failed nets with wire length violation(nets having lenghts > 500um) & no maxCap violation.

Can any one tell me a method to fix interRepeater failed nets at postRoute stage.

Regards,

spach 

 

  • Cancel
  • PatBoug
    PatBoug over 15 years ago

    Hi spach,

    there is two main raisons why insertRepeater do not fix long nets :

    1. Net has a dontTouch
      typically, clock nets are let untouch by insertRepeater
      To report such nets, please use the "-reportIgnoreNets" option of insertRepeaters
    2. There is no legal standard cell placement area available under long net wiring.
      Imagine that in your floorplan there is a long channel where you have hard placement blockage.
      insertRepeater will not be in a position to insert buffers.
      insertRepeater is not allower to make long detour to fix long nets.
      In such situation you must update your floorplan, you can add available std cell site (transform your hard placement blockage into soft placement blockage), or you add routing blockage to prevent router to use such long channel.

    Regards,

     Pat.

    • 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