• 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. Mixed-Signal Design
  3. SPICE file of layout showing ground and gate interchang...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 15135
  • 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

SPICE file of layout showing ground and gate interchanged

Charanraj Mohan
Charanraj Mohan over 9 years ago

Hi,

  I am beginner to Cadence. I am designing a simple CMOS inverter using UMC 130nm technology.

 I have a specific doubt in one of the flow of the design. After I do Calibre-LVS check and it passes successfully, I get a file in .sp format. Basically it is the SPICE netlist of the layout. I notice something strange in it. I found that in pMOS the drain and source got interchanged. But everything is rightly connected and the DRC, LVS and even PEX is also done. I really could't understand this, why the .sp file shows a wrong pin configuration for pMOS, but everything is fine.


 I can see that the layout is upside down, when I compare it with schematic in RVE, but it is correctly connected. Is there a top down approach for getting .sp file after LVC or something, that is still not clear. Or is it a bug, that needs to be fixed in Cadence for this particular design kit or something. Can someone give me an explanation for this ?

Thanks in advance.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    I already explained this. The extraction rules have no means of knowing which of the two device pins is the source and which is the drain - they have the same geometries. So which way around it's connected is somewhat arbitrary, and generally the LVS rules would allow the source and drain to be permuted because of this reason which allows LVS to pass.

    It makes no difference to simulation.

    If the devices were non-symmetrical, then the extraction rules would be written to be able to identify which is specifically the source and which is specifically the drain - and if it was wrong in that situation, then it would be a problem with the rules (which are part of the PDK) rather than the extraction tool (most likely, at least, although it might be a tool bug).

    However, I suspect (as I said before) that this is just because the devices are symmetrical and so the source is indistinguishable from the drain, and is nothing to worry about.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    I already explained this. The extraction rules have no means of knowing which of the two device pins is the source and which is the drain - they have the same geometries. So which way around it's connected is somewhat arbitrary, and generally the LVS rules would allow the source and drain to be permuted because of this reason which allows LVS to pass.

    It makes no difference to simulation.

    If the devices were non-symmetrical, then the extraction rules would be written to be able to identify which is specifically the source and which is specifically the drain - and if it was wrong in that situation, then it would be a problem with the rules (which are part of the PDK) rather than the extraction tool (most likely, at least, although it might be a tool bug).

    However, I suspect (as I said before) that this is just because the devices are symmetrical and so the source is indistinguishable from the drain, and is nothing to worry about.

    Regards,

    Andrew.

    • 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