• 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. Custom IC SKILL
  3. Find a list of floating gates in schematic

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 145
  • Views 18265
  • 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

Find a list of floating gates in schematic

pham777
pham777 over 11 years ago

Hi,

I wonder if there is a skill code to find hierarchily a list of transistors which have its gate

1) not connected to power/ground

2) and not connected to other devices(transistors, R,L,C)

I am using cadence IC615.

Thanks a lot,

HP

  • Cancel
  • Quek
    Quek over 11 years ago

    Hi HP

    I think it can be done by examining the net info of each transistor hierarchically. But this is an ERC (Electrical Rule Check) problem which should be resolved using an LVS tool. Using SKILL is definitely not the most efficient approach. The problem can be resolved using Assura or PVS as follows:

    === Assura ===
    ercPathCheck(noPwr or noGnd "No pwr/gnd connection")
    ercCheckFloatingDevices(mosSourceOrDrain)

    === PVS ===
    erc_pathcheck -power not -or -ground not
    lvs_filter_option AE
    lvs_report_option -filtered_devices

    Check "design.cfr" file in the PVS LVS run directory for a list of floating mos devices which have been filtered.


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • pham777
    pham777 over 11 years ago

    Hi Quek,

    Thanks for your input. Yes, DRC rule deck (not ERC) can catch these floating gates, but it only happen when you run DRC at the top level ( analog + digital ). At that time, it's probably too late .... The situation is this:

    we work on analog section of the chip and deliver to PnR people who will integrate with digital section. We see a lot of floating gates at our analog section but we don't know if they are real or not at this stage. What happen is there are a lot of gates which connected to output/input pins which inturn will be connected to digital section. Some of them are unused which cause real floating gates when they run drc at top level.

    I'd like to have a skill code to find a list of transistors in schematic (not in layout) which have its gates not connected to anything except pins, then I can determine which one is not used and terminate it properly by connecting to power/ground.

    Thanks a lot,

    HP

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    This is also something that can be done with a FastSPICE simulator, such as XPS or UltraSim. See "spectre -h static_highz" for more details, and also there's the "dyn_floatdcpath" check which is available in APS (so not a FastSPICE engine) as well as XPS which performs a "Dynamic Floating Node Induced DC Leakage Path Check".

    There's a RAK (Rapid Adoption Kit) for "Static and Dynamic Checks" available here.

    Andrew.


     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Dan Geise
    Dan Geise over 9 years ago
    I would like to check for floating nodes in a top level mixed signal design APS simulation. I am interested in setting the "dyn_floatdcpath" check. Could you possibly help me by letting me know how to set that in ADE?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago
    In IC617 there's the checks and asserts assistant. There's a Rapid Adoption Kit (Resources->Rapid Adoption Kits->Custom and Signoff) called "Check & Assertions in Virtuoso ADE XL, Virtuoso ADE Assembler and Virtuoso ADE Explorer" on support.cadence.com which covers this. In IC616 you have to set it up by putting the dyn_floatdcpath statement in an include file.
    • 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