• 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. M1 pins not getting extracted

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 14186
  • 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

M1 pins not getting extracted

lavgupta2
lavgupta2 over 9 years ago

Hi everyone

I am doing a simple experiment by placing two parallel metal lines in the  layout view and trying to find the coupling between them like follows:  Since I am doing this in layout, and I don't have schematic to perform lvs, first I created a dummy spice file, used it to perform lvs and generate qrc data as in article 11691566 and then run qrc to extract the layout. 

The problem I am facing is that the extracted layout doesn't have any M1 pins. I created these pins to observe the coupling between signals applied across them. I have also made Vdd and gnd! lines and provided them with tap lines directly from my technology library. I am using virtuoso 6.1.6.101, assura 4.1.USR2 and QRC 14.1.2-s148 with IBM7RF technology. 

Edit: Does anybody know of a better way for simulating coupling across metal lines and then leveraging that coupler for circuit design in virtuoso? I thought of directly using rfTlinelib instead, but that library doesn't seem to have the layouts for devices. Also, I think I can't use coupledwires from cmrf7sf as I want to extend the coupled metal lines.

Thanks

Sincerely

Lav Gupta

  • Cancel
Parents
  • lavgupta2
    lavgupta2 over 9 years ago

    Hi Quek

    Thanks for the reply. Here is the information that you asked for.

    a. Content of Assura .ldb file:

    *.LDD


    .subckt subc SUBCON sub
    *.PININFO
    .ends subc

    .subckt testcoupler
    *.PININFO
    XavD206_1 avC1 avC3 subc a=2.51888e-11 l=7.28e-06 p=2.148e-05 w=3.46e-06
    .ends testcoupler

    b. The distance between the metal lines is 5um.

    c. M1 Space if atleast one M1 line width is greater than 25 um is 1.920 and I am using M1 width of 35um. Otherwise M1 to M1 space is >=0.2um.

    d. Regarding the spice file, I have not done a spice extraction yet and not very sure about it as QRC only works for av_extracted format for my pdk.

    One more thing, I have been thinking to use Sonnet for running the EM simulation and then do the extraction for the above problem as assura doesn't seem to work out for me. Also, Sonnet can be used to extract a spice netlist. What do you think about that?

    Sincerely

    Lav Gupta

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • lavgupta2
    lavgupta2 over 9 years ago

    Hi Quek

    Thanks for the reply. Here is the information that you asked for.

    a. Content of Assura .ldb file:

    *.LDD


    .subckt subc SUBCON sub
    *.PININFO
    .ends subc

    .subckt testcoupler
    *.PININFO
    XavD206_1 avC1 avC3 subc a=2.51888e-11 l=7.28e-06 p=2.148e-05 w=3.46e-06
    .ends testcoupler

    b. The distance between the metal lines is 5um.

    c. M1 Space if atleast one M1 line width is greater than 25 um is 1.920 and I am using M1 width of 35um. Otherwise M1 to M1 space is >=0.2um.

    d. Regarding the spice file, I have not done a spice extraction yet and not very sure about it as QRC only works for av_extracted format for my pdk.

    One more thing, I have been thinking to use Sonnet for running the EM simulation and then do the extraction for the above problem as assura doesn't seem to work out for me. Also, Sonnet can be used to extract a spice netlist. What do you think about that?

    Sincerely

    Lav Gupta

    • 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