• 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. MOS Bulk Routing Parasitic Resistance Extracted by Assura...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 12914
  • 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

MOS Bulk Routing Parasitic Resistance Extracted by Assura, But Not Used by ADE Spectre Netlister

Stepan
Stepan over 10 years ago

Hi,

During the Spectre netlist generation process, I have found out that the netlister includes the parasitic resistances of the MOS transistor bulk routing in the resulting netlist like:

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 that I have been expecting from my av_extracted view).

Is there any way to fix this problem?


I'm using Virtuoso Design Environment version IC6.1.3.500.13 with Assura 3.2OA lnx86 (Cadence Extraction QRC - Parasitic Extractor - Version 8.1.4-p002).


Thanks,

Stepan.

  • Cancel
  • Stepan
    Stepan over 10 years ago

    Finally, inspecting closely the extracted view, I realized that the root of the problem resides not in the Spectre netlister, but in the Assura QRC extraction tool. I tried out 2 different design kits and obtained the the same problem.

    Please, follow this updated thread to help me to solve this issue:

    http://community.cadence.com/cadence_technology_forums/f/38/t/31556

    Thanks,

    Stepan.

    • 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