• 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. Nor Gate

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 15804
  • 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

Nor Gate

CHECKMATE
CHECKMATE over 14 years ago

I am designing a simple two input NOR gate in cadence.

But the problem is when I do LVS of my NOR gate it gives me an error.

Since the NOR gate is designed with two PMOS in series and two NMOS in parallel.

I used Number of fingers equal to 2 for both pmos and nmos properties and set Number of fingers equal to 1 as well for both

I have attached my schematic and layout screenshots.

In the Assura LVS report:

======================================= 

Under the Matched Instances with Bad Net Connections

=========================================

Schematic Instance: MN1_enm

Layout Instance: avD62_1 n

Pin                     SchNet                  LayNet

S                          GND                     Out

D                           Out                      GND

 

Looking at this it seems my Nmos in parallel for a NOR gate are not merging.Is there a way I can solve this problem.

 Thanks for your help....but this is a weird error.

 

  • Screenshot-1.png
  • View
  • Hide
  • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    It looks from the error as if the S and D pins have not been set to be permutable. There are several places this would be done - one in the extract rules themselves (e.g. on the extractMOS or extractDevice statements). That takes care of the extraction side. On the schematic side, it can be done in the auLvs part of the CDF. Also there's various functions (e.g pinSwap) in the avCompareRules which can used to do this kind of thing.

    I think in practice to debug it, you'd be best to contact customer support (sorry if I keep advising this, but it is there for a reason) so somebody can work through with you what could be wrong. It's hard to diagnose without more of the data.

    Best Regards,

    Andrew.

    • 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