• 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. Errors in pad fillers using AMS 0.35u technology (SOCE)

Stats

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

Errors in pad fillers using AMS 0.35u technology (SOCE)

Mooty
Mooty over 16 years ago

Hi,

I'm using SOCE for P&R and I keep getting this spacing error with the pad fillers:

Pin of Cell IN0_5 & Blockage of Cell pfill_W_44

Actual:     0.7     Min:     0.8    bbox = (180.000, 1768.250) (180.700, 1772.550)

 I cannot seem to resolve it.  What could be the problem?

 

  • Cancel
  • archive
    archive over 16 years ago
    Hello Mooty, Would you be able to publish the zoomed snap shot of the violation with blockage and pin highlighted ? Thanks, Vishnu
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mooty
    Mooty over 16 years ago

     Hi,

     Thanks for responding!

    Attached are some of the pics detailing the errors.

     

     

    There are 2 main DRCs, one between the fillers etc. and the other is the special route to the power I/O pads.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 16 years ago

     Hi Mooty,

    The first picture looks like nanoRoute is trying to route some nets that are really connected by abutment of the IO cells. You should place a -skip_routing attribute on these nets:

    setAttribute -net net1 -skip_routing true

    The second picture looks like a violation between the route to the IO pin and the blockages around the IO pin. These may or may not be real violations - you'll have to run your signoff DRC to be sure. 

    I'm not sure about the other two.

    - Kari 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mooty
    Mooty over 16 years ago

    Hi,

    Thanks a lot for your help.

     The first case, however, is actually the connection between the power pads and the power ring.   This connection is necessary right?

    I have another problem now.

     

     

     Apparently, there are some  DRCs between the power stripe and the cells beside it.  The error seems related to the clock as all of the errors have the clock present.


    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 16 years ago

     For the first issue, if you mean that the IO ring is connected by abutment but you are seeing violations, it could be blockages causing verify geometry to think there is an error where there really isn't. You can try turning on/off some of the ver geom settings and see if you get different results. The real test is signoff DRC. Does it show any problems in your IO ring?

    For the second issue, it's hard to tell from this picture (not everything is turned on), but it looks like you have a wide metal (the power) too close to regular routing. Maybe your clock routes are double-width? I'm not sure. Turn on signal routing and see if you can tell what the error marker is flagging. The text description should also shed some light.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mooty
    Mooty over 16 years ago

     Hi,

    with regards to the second issue, 

     

    The error message is of this form:

    SPACING: Regular Via of Net Final/CLK__L7_N231 & Special Wire of Net vdd!  ( M2 )
    Bounds : ( 2746.350, 711.800 ) ( 2747.100, 712.600 )
    Actual:     0.75     Min:     0.8

    I still can't figure out how to solve this problem.  Is this a placement problem?

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 16 years ago

     Mooty,

    You have a spacing violation between the m2 in the via on the C pin and the m2 bus on the left. (I think your nets are not displayed because you are in floorplan view instead of physical view.) Once you get the nets displayed, the error should be clear.

    - Kari 

    • 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