• 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. Metal routing not getting extracted

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15582
  • 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

Metal routing not getting extracted

praveenmv
praveenmv over 7 years ago

Hi!

Some of the metal routings are not getting extracted during QRC extraction. I have a screenshot of av_extracted view to explain my problem. As can be seen in the image, some part of metal is not getting divided into rectangles i.e. not getting extracted into resistors and capacitors.
I am doing RC extraction with max fracture length as 5 squares, full chip all nets and resistance mesh disabled. In filtering tab, I have chosen the option to merge parallel R and set Min R to 0.001 Ohm. How to solve this? If I copy that particular metal routing in another layout window without rest of the blocks, it does get extracted.
https://drive.google.com/file/d/1rWelJKhneXaUqtdh6Morx3MTG9Q0MSOx/view?usp=sharing
Thank You.
  • Cancel
Parents
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago

    Hi Praveen,

    Can you share your QRC command-file as well? The Metal1 shapes that are extracted and not extracetd - are they at the same level of hierarchy in the layout? I noticed you are looking at Metal1 pin in the layout layer palette. Typically, in extracted view, the extracted shapes are written into purpose 'net', so can you check what you see in Metal1 net?

    Regards,

    Saloni

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • praveenmv
    praveenmv over 7 years ago in reply to Saloni Chhabra

    This is the command file (also added in answer). The shapes that are getting and not getting extracted are in the same heirarchy. I am sorry, but I did not understand the last point. In the extracted view I just have pins for every layer in the palette. I didn't understand how to check what I see in Metal1 net (or drw - drawing?)

    https://drive.google.com/file/d/1g_yEiW0dg6qJb6pssnVpHlYfNkOKcQkj/view?usp=sharing


    #--------------------------------------------------------------------------------------
    # OPTION COMMAND FILE created by Cadence Extraction Quantus QRC UI Version 15.22-s247
    #--------------------------------------------------------------------------------------

    capacitance \
         -decoupling_factor 1.0 \
         -ground_net "/gnd!"
    extract \
         -selection "all" \
         -type "rc_coupled"
    extraction_setup \
         -array_vias_spacing auto \
         -max_fracture_length 5 \
         -max_fracture_length_unit "SQUARES" \
         -macro_cells_type "default"  \
         -max_via_array_size "auto" \
         -net_name_space "SCHEMATIC"
    filter_cap \
         -exclude_self_cap true
    filter_coupling_cap \
         -coupling_cap_threshold_absolute 0.01 \
         -coupling_cap_threshold_relative 0.001
    filter_res \
         -merge_parallel_res true \
         -min_res 0.001
    input_db -type assura \
         -design_cell_name "cc_r3sw_metres_3 layout sgb25_schem_lay" \
         -run_name "lvsrec" \
         -directory_name "/data/ee15s015/userP/cds/LVS" \
         -format "DFII"
    output_db -type extracted_view \
         -cap_component "pcapacitor ivpcell SGB25_dev" \
         -cap_property_name "c" \
         -enable_cellview_check true \
         -include_cap_model "false" \
         -include_parasitic_cap_model "false" \
         -include_res_model "false" \
         -include_parasitic_res_model "false" \
         -res_component "presistor ivpcell SGB25_dev" \
         -res_property_name "r" \
         -view_name "av_extractedrc5"
    output_setup \
         -temporary_directory_name "lvsrec"
    process_technology \
         -technology_corner \
            "default" \
         -technology_library_file "/data/ee15s015/userP/cds/assura_tech.lib" \
         -technology_name "SGB25_dev" \
         -temperature \
            27

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago in reply to praveenmv

    Hi Praveen,

    Okay I just noticed that you are already displaying all used layers, and everything in extracted view is in pin layer. Even if you don't see the shape divided into rectangles, its parasitics should still have been computed. If you query the big shape you think has not been extracted, you should see a net name in the 'Connectivity' tab, can you confirm? Also, what is the length of this big rectangle?

    Is there any reason why you want to set the fracture length to 5 squares (the default is microns). This will increase the size of your extracted view and netlist. We typically leave the fracture length to its default of 'inifinite' and let Quantus QRC decide how it needs to fracture the shapes, unless of course there is a reason for changing the default.

    Thanks,

    Saloni

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • praveenmv
    praveenmv over 7 years ago in reply to Saloni Chhabra

    Hey!

    I used the fracture length of 5 squares to show the difference between extracted and non-extracted part. Initially, I was using infinite microns fracture length but then I wouldn't be able to show you the difference. Both give the same results though. The parasitic resistance should be around 600 Ohms but it is just 400 Ohms. To see why this was happening I reduced the fracture length and realized that, that space is not getting extracted in a way similar to other routing.

    Length is 240.843u and width is 1.26u. Parasitic resistance should be in order of 17 Ohms for that rectangle (the one not being extracted). Total should be around 20 Ohms but since only a part of it is extracted it shows 3 Ohms as parasitic resistance. Including all rectangles I should get 600 Ohms of parasitic R.

    If I query the big shape in layout view of the design, then in connectivity tab I don't see any net name. I didn't add any net name. Here is the screenshot for this.https://drive.google.com/file/d/1Lv35hjv9YxQvDTE-pChJA0SopYUt45ub/view?usp=sharing

    Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • praveenmv
    praveenmv over 7 years ago in reply to Saloni Chhabra

    Hey!

    I used the fracture length of 5 squares to show the difference between extracted and non-extracted part. Initially, I was using infinite microns fracture length but then I wouldn't be able to show you the difference. Both give the same results though. The parasitic resistance should be around 600 Ohms but it is just 400 Ohms. To see why this was happening I reduced the fracture length and realized that, that space is not getting extracted in a way similar to other routing.

    Length is 240.843u and width is 1.26u. Parasitic resistance should be in order of 17 Ohms for that rectangle (the one not being extracted). Total should be around 20 Ohms but since only a part of it is extracted it shows 3 Ohms as parasitic resistance. Including all rectangles I should get 600 Ohms of parasitic R.

    If I query the big shape in layout view of the design, then in connectivity tab I don't see any net name. I didn't add any net name. Here is the screenshot for this.https://drive.google.com/file/d/1Lv35hjv9YxQvDTE-pChJA0SopYUt45ub/view?usp=sharing

    Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago in reply to praveenmv

    Hi Praveen,

    It will be difficult to debug this issue further without looking at the data, so I suggest you contact customer support.

    Regards,
    Saloni

    • 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