• 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. How can I cut a routing blockage in FE?

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 91
  • Views 17408
  • 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

How can I cut a routing blockage in FE?

archive
archive over 18 years ago

Dear ALL:

I want to cut a routing blockage in one floorplan to make routing guides. For example, I dont have M5 cell routing blockage in a LEF hard block, I add this routing blockage at the top level, I have to cut some notches according to the pin shapes (if pins are on M5), then router can make M5 connections to these pins without DRC. How can I cut these notches on the added M5 routing blockage, this is more like a polygon operation, do Encounter have such db commands? I dont want to modify the LEF file (to add the M5 obstruction).

Thanks in advance!


Originally posted in cdnusers.org by eminemshow
  • Cancel
Parents
  • patrice06
    patrice06 over 14 years ago

    Hi Bob,

    I will move to 10.1 after completing this design.

    In this design, I prefer not incorporate the blockage inside the LEF as I still allow power routing over the macro in the floorplan. So, it is nice to be able to generate those blockage on the fly and delete before checking for violation.

    I am currently using this : foreach inst [dbGet [dbGet -p2 top.insts.cell.baseClass block].name] {createRouteBlk -cover -exceptpgnet -layer 5  -inst $inst}

    layer 5 is my top metal.    That covers the macro.  That is already doing a good job. The sizing would have also allow access in the top metal to the pins. But not an issue for this design.

    Thanks a lot for your answer.

    Patrice

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • patrice06
    patrice06 over 14 years ago

    Hi Bob,

    I will move to 10.1 after completing this design.

    In this design, I prefer not incorporate the blockage inside the LEF as I still allow power routing over the macro in the floorplan. So, it is nice to be able to generate those blockage on the fly and delete before checking for violation.

    I am currently using this : foreach inst [dbGet [dbGet -p2 top.insts.cell.baseClass block].name] {createRouteBlk -cover -exceptpgnet -layer 5  -inst $inst}

    layer 5 is my top metal.    That covers the macro.  That is already doing a good job. The sizing would have also allow access in the top metal to the pins. But not an issue for this design.

    Thanks a lot for your answer.

    Patrice

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information