• 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. Floating gates !

Stats

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

Floating gates !

Amr Zahir
Amr Zahir over 15 years ago
I'm using SoC Encounter 8.1, with IBM 130nm std cell library. When I submit my layout to foundry it reports (floating gates)...exactly twice the number of std cells used ! So my questions are; do I have to tie the substrate & wells to power pins by hand or it's tied internally in the cell ? And what about ENDCAP cells...can they report such violations if they don't exist ? Note that Encounter reports no errors (there's no Unconnected pins in the design) Thank you
  • Cancel
  • Kari
    Kari over 15 years ago

     Some std cell libraries have the well ties as part of the cell, and with others, you have to use well tap cells. These are cells that are included in the library that you have to array out in the design at a specific spacing to satisfy the well tie rules for your process. Endcap cells may or may not also be required. Chances are, if welltaps and endcaps are in your std cell library, they are there for a reason. :-) Check your design process manual or std cell library documentation for more info.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Amr Zahir
    Amr Zahir over 15 years ago
    Thanks Kari Actually I don't have (ENDCAP) or (well tap) cells in my library. I want to know if floating substrate & NWELL can make this (floating gate) violation ?!
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 15 years ago

    Without being familiar with your design's process and DRC/LVS decks, I can't really say. The foundry should be able to give you some more detail about why this error is occurring.

    • 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