• 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. How to identify dummy mos in layout

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 15452
  • 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 to identify dummy mos in layout

Venu Ch
Venu Ch over 11 years ago

Hi All,

I have lot of layouts which contains dummy mos devices but they are not added in schematics. I have to add them in schematic to get LVS clean. It is not generated with VXL. So connectivity is not defined for them. I need to identify dummy transistors in my layout. Could you share your thoughts on it using skill? I am using ic616.

I saw http://www.cadence.com/forums/p/24988/1319633.aspx#1319633 in previous posts. Can we assign default net names for device terminals? If we can assign net names for device terminals then we can able to find dummy.

Thank you,

Chandaka.

  • Cancel
Parents
  • Venu Ch
    Venu Ch over 11 years ago

    I completed this code by using some combination of dbgetoverlaps,and, andnot, size commands. Now it is identifing Dummy mos in layout if all terminals are shorted with M1 metal(this is ok because all dummys are connected with m1 only in my layouts). And also I can able to back annotate this dummy in schematic. This is sufficeint fo me except one task. I have to assign dummy terminal net to VDD or VSS.

    In my layouts all terminals of dummy are shorted and connected to either VDD or VSS pin at some where through m2 or m3 metals. 

     For this I have two steps. I am strugling with step1.

    1)Now I have m1 metal id on dummy. I want to get all m1,m2,m3 metals connected to that m1 metal id. (Just like net extraction or saveallmarknet feature,). I can able to get m2 layer which is connected to m1 metal id by using

    via1=setof(x cv~>shapes x~>layerName==v1)

    viaOnMetal=dbLayerAnd(m1metal  via1) ;for quick view i am not writing original syntax.

    m2Lay=dbLayerStraddle(m2Layers viaOnMetal)

    After this I can not able to get remaining metals. Please let me know if you know some other solution?

    2)I have all pins layout. I will check which pin is overlapping with that net and then I will assign that net name in schematic.

     Thanks,

    Chandaka

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Venu Ch
    Venu Ch over 11 years ago

    I completed this code by using some combination of dbgetoverlaps,and, andnot, size commands. Now it is identifing Dummy mos in layout if all terminals are shorted with M1 metal(this is ok because all dummys are connected with m1 only in my layouts). And also I can able to back annotate this dummy in schematic. This is sufficeint fo me except one task. I have to assign dummy terminal net to VDD or VSS.

    In my layouts all terminals of dummy are shorted and connected to either VDD or VSS pin at some where through m2 or m3 metals. 

     For this I have two steps. I am strugling with step1.

    1)Now I have m1 metal id on dummy. I want to get all m1,m2,m3 metals connected to that m1 metal id. (Just like net extraction or saveallmarknet feature,). I can able to get m2 layer which is connected to m1 metal id by using

    via1=setof(x cv~>shapes x~>layerName==v1)

    viaOnMetal=dbLayerAnd(m1metal  via1) ;for quick view i am not writing original syntax.

    m2Lay=dbLayerStraddle(m2Layers viaOnMetal)

    After this I can not able to get remaining metals. Please let me know if you know some other solution?

    2)I have all pins layout. I will check which pin is overlapping with that net and then I will assign that net name in schematic.

     Thanks,

    Chandaka

    • 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