• 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 Design
  3. Problem with MOS Bulk Routing Parasitic Resistance Extr...

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 126
  • Views 18008
  • 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

Problem with MOS Bulk Routing Parasitic Resistance Extraction

Stepan
Stepan over 10 years ago

Hi,

During the Spectre netlist generation process, I have found out that the Assura QRC extractor includes the parasitic resistances of the MOS transistor bulk routing in the extraction view:

rg58 (vdda \5\:vdda) resistor r=24.5376 c=0

But, it skips connecting this parasitic resistor to the bulk of the transistor:

M10 (\3\:vout \5\:nclk \2\:vin vdda) p_lv_18_mm w=1.92e-06 l=2.4e-07 ad=2.224e-13 as=2.224e-13 pd=2.0u ps=2.0u m=(1)*(1)

From the line above, you can see that it circumvents the parasitic resistor and connects the bulk directly to the polarization net vdda (NOT \5\:vdda)

As a result, the simulation netlist generated from this extracted view is also incorrect.

 

I have tried two different technologies with two different design kits and both have the same issue. Two kits are:

1. Virtuoso Design Environment version IC6.1.3.500.13 with Cadence Extraction QRC - Parasitic Extractor - Version 8.1.4-p002.

2. Virtuoso Design Environment version IC6.1.5-64b.500.132 with Cadence Extraction QRC - Parasitic Extractor - Version 11.1.2-p106.


Is there any way to fix this problem? Can it be done by modifying the configuration script or updating the kit?

Thanks,

Stepan.

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

    Hi Stepan

    The difficulty is, the bulk is under the transistor - and how do you know which substrate tap is the one that is connecting to it? One approach might be to write rules in the LVS to create pseudo islands or wells under the transistors - these don't exist in reality, but you could effectively try to treat each of these regions as unconnected from each other, and only connected via the substrate taps. Of course, you'd need to ensure that these substrate regions are big enough to include a substrate tap near the transistor.

    Then the behaviour would be similar to your n-wells (if a p-substate process) or vice-versa.

    All this would involve changing the LVS extraction rule deck. 

    There's not (as far as I know) any magic switch to do this isolation of the bulks automatically (at least not making sure they are connected up to a suitable tap).

    Regards,

    Andrew.

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

    Hi Stepan

    The difficulty is, the bulk is under the transistor - and how do you know which substrate tap is the one that is connecting to it? One approach might be to write rules in the LVS to create pseudo islands or wells under the transistors - these don't exist in reality, but you could effectively try to treat each of these regions as unconnected from each other, and only connected via the substrate taps. Of course, you'd need to ensure that these substrate regions are big enough to include a substrate tap near the transistor.

    Then the behaviour would be similar to your n-wells (if a p-substate process) or vice-versa.

    All this would involve changing the LVS extraction rule deck. 

    There's not (as far as I know) any magic switch to do this isolation of the bulks automatically (at least not making sure they are connected up to a suitable tap).

    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