• 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. samenet spacing violations

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 93
  • Views 14587
  • 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

samenet spacing violations

Priyatham
Priyatham over 15 years ago
After routing using the NanoRoute - when I run a verifyGeometry I get some samenet spacing violations - all on VIAs. When I run verifyGeometry with -allowDiffCellViols, all these violations are cleared. So someone advised that its probably not the routing that's causing the violations but the cell design. But those are the standard cells for First Encounter and I have no clue why they might be causing the problem. Any advise on this and how to resolve this issue would be a great help.

Thanks,

Priyatham.
  • Cancel
Parents
  • Priyatham
    Priyatham over 15 years ago

     Thanks RajaK for your suggestion, I have resolved that problem. Your guess is right, the standard cells I was using were laid out in a way that they couldn't be abutted without DRC violations. So the DRCs were actually not because of the Routing, but because of the Placement itself. To Resolve that issue I set the following parameter to true before doing the placement:

    setPlaceMode -padForPinNearBorder {true | false}

    Adds padding to a cell if any signal pin is near enough to the border to cause DRC violations with any metal geometry.
    Default: false

    That solved the issue. Thankyou for the reply though.

    Priyatham.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Priyatham
    Priyatham over 15 years ago

     Thanks RajaK for your suggestion, I have resolved that problem. Your guess is right, the standard cells I was using were laid out in a way that they couldn't be abutted without DRC violations. So the DRCs were actually not because of the Routing, but because of the Placement itself. To Resolve that issue I set the following parameter to true before doing the placement:

    setPlaceMode -padForPinNearBorder {true | false}

    Adds padding to a cell if any signal pin is near enough to the border to cause DRC violations with any metal geometry.
    Default: false

    That solved the issue. Thankyou for the reply though.

    Priyatham.

    • 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