• 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. error while using QRC to extract the DSPF file of the c...

Stats

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

error while using QRC to extract the DSPF file of the circuit

yuanshangu
yuanshangu over 2 years ago

I encountered a problem while using QRC to extract the DSPF file of the circuit. However, I couldn't find any relevant solutions. Have others experienced similar issues? Thanks!!!

[guys20@orion QRC]$ qrc -multi_cpu 32 -cmd qrc.test.ccl -logfile qrc.log
/home/tools/eda/cadence/QUANTUS/22.10/tools.lnx86/extraction/bin/64bit/qrc: /home/tools/lib64/libcrypto.so.10: no version information available (required by /lib64/libssh2.so.1)
/home/tools/eda/cadence/QUANTUS/22.10/tools.lnx86/extraction/bin/64bit/qrc: /home/tools/lib64/libcrypto.so.10: no version information available (required by /lib64/libldap-2.4.so.2)
/home/tools/eda/cadence/QUANTUS/22.10/tools.lnx86/extraction/bin/64bit/qrc: /home/tools/lib64/libcrypto.so.10: no version information available (required by /lib64/libldap-2.4.so.2)
/home/tools/eda/cadence/QUANTUS/22.10/tools.lnx86/extraction/bin/64bit/qrc: /home/tools/lib64/libssl.so.10: no version information available (required by /lib64/libldap-2.4.so.2)


Cadence Quantus Extraction - 64-bit Parasitic Extractor - Version
22.1.0-p089 Thu Jan 19 12:18:17 PST 2023
---------------------------------------------------------------------------------------------------------------
Copyright 2023 Cadence Design Systems,
Inc.

INFO (EXTQRCXLOG-128) : Quantus command line:
Started at: 2023-Jul-26 16:00:33 (2023-Jul-26 08:00:33 GMT)
Executable:
/home/tools/eda/cadence/QUANTUS/22.10/tools.lnx86/extraction/bin/64bit/qrc
Options: -multi_cpu 32 -cmd qrc.test.ccl -logfile qrc.log
Current working directory: /home/guys20/asic/qrc_e203/QRC


INFO (EXTQRCXLOG-103) : The Command File Options for the current Quantus run are as follows:

capacitance \
-decoupling_factor 1.0 \
-ground_net "VSS"
distributed_processing \
-multi_cpu 32
extract \
-selection "all" \
-type "rc_decoupled"
extraction_setup \
-analysis "em" \
-array_vias_spacing "auto" \
-max_fracture_length infinite \
-max_fracture_length_unit "MICRONS" \
-max_via_array_size \
"auto" \
-net_name_space "LAYOUT"
filter_res \
-min_res 0.001
input_db -type calibre \
-device_property_value 7 \
-directory_name "/home/guys20/asic/qrc_e203/QRC/./query_output" \
-hierarchy_delimiter "/" \
-instance_property_value 6 \
-layer_map_file "/home/guys20/asic/qrc_e203/QRC/./query_output/Design.gds.map" \
-net_property_value 5 \
-run_name "Design"
output_db -type dspf \
-add_bulk_terminal "false" \
-add_explicit_vias true \
-busbit_delimiter "\[\]" \
-disable_instances false \
-hierarchy_delimiter "/" \
-include_cap_model "false" \
-include_parasitic_cap_model "false" \
-include_parasitic_res_conductor_bounding_box "edge" \
-include_parasitic_res_length true \
-include_parasitic_res_model "comment" \
-include_parasitic_res_via_bounding_box_by_layer \
"ALL" \
-include_parasitic_res_width false \
-include_parasitic_res_width_drawn true \
-include_res_model "false" \
-netlist_coupling_values "single" \
-output_xy \
"CANONICAL_RES" \
"PARASITIC_RES" \
-sub_node_char "#" \
-subtype "EXTENDED"
process_technology \
-technology_corner \
"default" \
-technology_library_file "/home/guys20/asic/qrc_e203/QRC/./qrc/assura_tech.lib" \
-technology_name "assura_lib" \
-temperature \
"25.0"

-------------------------------------------------------------------------------------
Wed Jul 26 16:00:34 2023: BEGIN INPUT stage
-------------------------------------------------------------------------------------
|==================================================| 100%
-------------------------------------------------------------------------------------
Wed Jul 26 16:00:35 2023: DONE INPUT stage
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
INPUT stage summary:
-------------------------------------------------------------------------------------
Number of CPUs requested: 32
Techfile(s):
/home/guys20/asic/qrc_e203/QRC/rcx//qrcTechFile; process name:

License(s) used: QTS300 (x16)

Techgen compilation option(s):
-techdir /home/guys20/asic/qrc_e203/QRC/rcx -inc /home/guys20/asic/qrc_e203/QRC/Design.ilf -lvs /home/guys20/asic/qrc_e203/QRC/Design.xcn -p2lvs /home/guys20/asic/qrc_e203/QRC/rcx/qrcTechFile -reseqn -sw3d -length_units meters /home/guys20/asic/qrc_e203/QRC

Input files:
/home/guys20/asic/qrc_e203/QRC/./query_output/Design.gds.map
/home/guys20/asic/qrc_e203/QRC/query_output/Design.agf
/home/guys20/asic/qrc_e203/QRC/query_output/Design.devtab
/home/guys20/asic/qrc_e203/QRC/query_output/Design.ixf
/home/guys20/asic/qrc_e203/QRC/query_output/Design.lph
/home/guys20/asic/qrc_e203/QRC/query_output/Design.nxf
/home/guys20/asic/qrc_e203/QRC/query_output/Design.ports
/home/guys20/asic/qrc_e203/QRC/query_output/Design.sph
/home/guys20/asic/qrc_e203/QRC/query_output/Design_pin_xy.spi
/home/guys20/asic/qrc_e203/QRC/rcx/lvsfile

Design data:
global nets: 0

Peak memory: 87 MB

Messages:
INFO (CAPGEN-41199):


Techgen -trans results will be written to directory: /home/guys20/asic/qrc_e203/QRC

WARNING (CAPGEN-41466): process layer 'ALRDL_C' maps to one or more extraction
layers that do not appear in the lvsfile.

WARNING (CAPGEN-41466): process layer 'PLY_C' maps to one or more extraction
layers that do not appear in the lvsfile.

WARNING (CAPGEN-41466): process layer 'DIFF_diel' maps to one or more extraction
layers that do not appear in the lvsfile.

WARNING (CAPGEN-41446): Substrate layer 'DIFF_diel' will be automatically generated
during extraction due to incomplete p2lvs mapping. This may lead to
unintended results.

WARNING (CAPGEN-41474): Contact layer 'PLYCONT' specified in the p2lvsfile is not found in the lvsfile.

WARNING (CAPGEN-41474): Contact layer 'DIFFCONT' specified in the p2lvsfile is not found in the lvsfile.

WARNING (CAPGEN-41474): Contact layer 'DIFFCONT' specified in the p2lvsfile is not found in the lvsfile.

WARNING (CAPGEN-41474): Contact layer 'ALVIA' specified in the p2lvsfile is not found in the lvsfile.

INFO (CAPGEN-41737): Lvs connect layers AL_RDL_C AL_RDL_I CONT1 DIFF_C DNWELL Diff_Short_Check Lterm1 Lterm2 M1_MOM_MESH M2_MOM_MESH M3_MOM_MESH M4_MOM_MESH M5_MOM_MESH ME1_C_VP3_MMVCL ME1_I ME1_I_RFMOM ME1_SHIELD_SY ME2_C_VP3_MMVCL ME2_I ME2_I_RFMOM ME2_I_term_m ME2_I_term_p ME2_SHIELD_SY ME3_C_VP3_MMVCL ME3_I ME3_I_RFMOM ME3_I_term_m ME3_I_term_p ME3_SHIELD_SY ME4_C_VP3_MMVCL ME4_I ME4_I_RFMOM ME4_I_term_m ME4_I_term_p ME4_SHIELD_SY ME5_C_VP3_MMVCL ME5_I ME5_I_RFMOM ME6_I ME6_I_RFMOM ME6_OTF_S1 ME6_OTF_S2 ME7_CTS ME7_I ME7_IN_P1 ME7_IN_P2 ME7_I_RFMOM ME7_OTF_P1 ME7_OTF_P2 ME7_OUT_S1 ME7_OUT_S2 MOM1_MESH_SY_P1_A_term MOM1_MESH_SY_P2_A_term MOM2_MESH_ASY_M1_term MOM2_MESH_ASY_M2_term MOM2_MESH_SY_M1_A_term MOM2_MESH_SY_M2_A_term MOM2_MESH_SY_P1_A_term MOM2_MESH_SY_P1_term MOM2_MESH_SY_P2_A_term MOM2_MESH_SY_P2_term MOM3_MESH_ASY_M1_term MOM3_MESH_ASY_M2_term MOM3_MESH_ASY_P1_term MOM3_MESH_ASY_P2_term MOM3_MESH_SY_M1_A_term MOM3_MESH_SY_M1_term MOM3_MESH_SY_M2_A_term MOM3_MESH_SY_M2_term MOM3_MESH_SY_P1_A_term MOM3_MESH_SY_P1_term MOM3_MESH_SY_P2_A_term MOM3_MESH_SY_P2_term MOM4_MESH_ASY_M1_term MOM4_MESH_ASY_M2_term MOM4_MESH_ASY_P1_term MOM4_MESH_ASY_P2_term MOM4_MESH_SY_M1_A_term MOM4_MESH_SY_M1_term MOM4_MESH_SY_M2_A_term MOM4_MESH_SY_M2_term MOM4_MESH_SY_P1_A_term MOM4_MESH_SY_P1_term MOM4_MESH_SY_P2_A_term MOM4_MESH_SY_P2_term MOM5_MESH_ASY_P1_term MOM5_MESH_ASY_P2_term MOM5_MESH_SY_M1_A_term MOM5_MESH_SY_M1_term MOM5_MESH_SY_M2_A_term MOM5_MESH_SY_M2_term NPBDIF NPLY_C NSD_CELL NSD_I NSD_I_B NSD_I_S NSD_LD_D NSD_LD_S N_WELL PLY_I PLY_I_NMISVAR PLY_I_PMISVAR PLY_I_RF PLY_NOSD PLY_SHIELD_SY PPLY_C PSD_CELL PSD_I PSD_I_S PSD_LD_D PSD_LD_S PSUB PSUB_ALL PTUB PWELL PWELL_RF SCONT VP3MM_M2_TERM_M VP3MM_M2_TERM_P VP3MM_M3_TERM_M VP3MM_M3_TERM_P VP3MM_M4_TERM_M VP3MM_M4_TERM_P VP3MM_M5_TERM_M VP3MM_M5_TERM_P VP3_M2_TERM_M VP3_M2_TERM_P VP3_M3_TERM_M VP3_M3_TERM_P VP3_M4_TERM_M VP3_M4_TERM_P VP3_M5_TERM_M VP3_M5_TERM_P VP4_M2_TERM_M VP4_M2_TERM_P VP4_M3_TERM_M VP4_M3_TERM_P VP4_M4_TERM_M VP4_M4_TERM_P VP4_M5_TERM_M VP4_M5_TERM_P VP5_M2_TERM_M VP5_M2_TERM_P VP5_M3_TERM_M VP5_M3_TERM_P VP5_M4_TERM_M VP5_M4_TERM_P VP5_M5_TERM_M VP5_M5_TERM_P VP5_SH1_PO_TERM VP5_SH2_M1_TERM VP5_SH2_PO_TERM VP5_SH3_M1_TERM VP5_SH3_M2_TERM VP5_SH3_PO_TERM VP5_SH4_M1_TERM VP5_SH4_M2_TERM VP5_SH4_M3_TERM VP5_SH4_PO_TERM WEL lay1a lay1b lay2a lay2b lay3a lay3b lay4a lay4b lay5a lay5b lay6a lay6b are not mapped in layer_setup file

INFO (CAPGEN-41804): Lvs stamped by PSUB layers QRC_NCAP_BLOCKING QRC_RF_BLOCKING QRC_RF_MOM_BLOCKING are not mapped in layer_setup file

INFO (CAPGEN-41804): Lvs stamped by WEL layers DNW are not mapped in layer_setup file

INFO (CAPGEN-41809): Lvs connect via TMV_0RDLA VIA6 VIA5 VIA4 VIA3 VIA2 VIA1 PO_0CONT DIF_0CONT PTAP_0RF NTAP TTAP PTAP NNBDIF_0C PPBDIF_0C NNBDIF_0I PPBDIF_0I DIFF_0TAP are not mapped in layer_setup file.

WARNING (AGDSEXT-30124): The <design>.props file is not available. The CCL option "input_db calibre/pvs/pegasus -device_properties_file <filename>" can be used to specify the .props file.

INFO (AGDSEXT-30016):
setting dbunit 1e-09 1 1e-09

-------------------------------------------------------------------------------------
Wed Jul 26 16:00:35 2023: BEGIN EXTRACTION stage
-------------------------------------------------------------------------------------
|=================================================.| 99%
****** For command L717:
pax16 -V -lee_off -gnd 47 -via PLYCONT,DIFFCONT,VIA1,VIA2,VIA3,VIA4,VIA5,VIA6,ALVIA -ignore_cf_table -scf sip.cmd -cgnd 47,1.0 -rcxlvs rcxtolvsmapfile -M_perim_off -c /home/guys20/asic/qrc_e203/QRC/rcx/qrcTechFile -f DIFF_diel PSD_C PLY_C ME1_C:ME1_C_cut ME2_C:ME2_C_cut ME3_C:ME3_C_cut ME4_C:ME4_C_cut ME5_C:ME5_C_cut ME6_C:ME6_C_cut ME7_C ALRDL_C - /home/guys20/asic/qrc_e203/QRC/rcx/qrcTechFile - - NET - capfile
ERROR (LBMISC-215513): Socket: connection with sd 18 closed

ERROR (PAXSXTN-142164): pax16 subtask with resource id 4 failed, terminating main pax16

ERROR (LBMISC-215523): Socket: Resource 7: server closed
ERROR (LBMISC-215523): Socket: Resource 6: server closed


ERROR (LBMISC-215522): Socket: Resource 8 - Can not connect to server

ERROR (LBMISC-215523): Socket: Resource 19: server closed

ERROR (LBMISC-215523): Socket: Resource 18: server closed

ERROR (LBMISC-215523): Socket: Resource 28: server closed
ERROR (LBMISC-215523): Socket: Resource 24: server closed

ERROR (LBMISC-215523): Socket: Resource 32: server closed

ERROR (LBMISC-215523): Socket: Resource 26: server closed
ERROR (LBMISC-215523): Socket: Resource 25: server closed


ERROR (LBMISC-215523): Socket: Resource 31: server closed

ERROR (LBMISC-215523): Socket: Resource 30: server closed


ERROR (LBMISC-215603): Error: pax16 command at line 717 failed with status 255

ERROR (EXTQRCX-609): Bad return status from QUANTUS run. 0xf

ERROR (EXTQRCX-709): ***** Quantus terminated abnormally *****

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

    I cleaned up the formatting as it was impossible to read as you'd posted it.

    Anyway, this looks like Quantus extraction terminated abnormally with ERROR (LBMISC-215251): Error: command failed with status 255 - the suggestion there is that you have exceeded your disk quota. I found some other reports of similar messages with similar reasons. 

    If that's not it, please contact customer support (submit a case after logging in).

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • yuanshangu
    yuanshangu over 2 years ago in reply to Andrew Beckett

    Hi,Andrew. First of all, thank you very much for formatting my question. Unfortunately, I don't have the permission to access my license server, so I cannot open the link you provided :(  Could you please briefly summarize the problem and the solution for me?

    sincerely,

    Yaunshan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to yuanshangu

    Hi Yaunshan,

    As I said, the key suggestion for this failure was to check whether you had exceeded your disk quota (or filled the disk up). If that's not the case, you'll need to contact customer support.

    Regards,

    Andrew 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • yuanshangu
    yuanshangu over 2 years ago in reply to Andrew Beckett

    Hi Andrew,

    I checked my disk quota, and I can confirm that there is enough space to operate.And I have set the temporary directory for the program to ensure that there is enough space to run it.However, the program still encounters errors during execution :(

    Filesystem               1K-blocks      Used  Available Use% Mounted on

    devtmpfs                  65621188         0   65621188   0% /dev

    tmpfs                     65638120         0   65638120   0% /dev/shm

    tmpfs                     65638120    252336   65385784   1% /run

    tmpfs                     65638120         0   65638120   0% /sys/fs/cgroup

    /dev/mapper/centos-root  125767680  16949536  108818144  14% /

    /dev/sda5                   508580    218124     290456  43% /boot

    /dev/sda4                   204580     11632     192948   6% /boot/efi

    /dev/mapper/centos-var   104806400   2792476  102013924   3% /var

    /dev/mapper/centos-home 1760747520 427171020 1333576500  25% /home

    tmpfs                     13127624       140   13127484   1% /run/user/1003

    tmpfs                     13127624        72   13127552   1% /run/user/1004

    tmpfs                     13127624        48   13127576   1% /run/user/0

    I found a stack trace in the crash report. Could you please help me take a look at this crash to determine what caused it?

    Crashed Executable Name: pax16

    crash_log.c: === Backtrace Information ==

    #0 0x00007faee293560c in waitpid () from /lib64/libc.so.6

    #1 0x00007faee28b2f62 in do_system () from /lib64/libc.so.6

    #2 0x0000000000dbd37f in crash_log_writer ()

    #3 <signal handler called>

    #4 0x00000000009b7460 in Cti_Tech::gConductor(unsigned int) ()

    #5 0x000000000097c4a9 in gCtiConductorWeeTableType ()

    #6 0x0000000000fbf105 in Pax16CapModel::get_regular_wee_bias(int, int, float, float, float*) ()

    #7 0x000000000113b095 in Pax16CapModel::apply_toplayer_bias_G10(_Vsip_input*, int) ()

    #8 0x000000000114a239 in Pax16CapModel::pax16_MDsip_G10(_Vsip_input*, _Vsip_output*, _Sip_D*, _Sw3d_Via*, int, int, int, int, int) ()

    #9 0x0000000001150c0e in Pax16CapModel::pax16_MDsip_SG10_914(_Vsip_input*, _Vsip_output*, _Sip_D*, _Sip_D*, _Sw3d_Via*, int, int, int) ()

    #10 0x00000000011522b2 in Pax16CapModel::pax16_viafunc(_Vsip_input*, _Vsip_output*, int, int, int, Via_Pattern) ()

    #11 0x00000000011269f0 in ccmi_pax16_viafunc ()

    #12 0x00000000007fb91e in do_halfvia_pax16 ()

    #13 0x00000000008d1eb5 in out_vhalf ()

    #14 0x00000000008d359d in proc_vhalf ()

    #15 0x00000000008d4615 in overlap_scan ()

    #16 0x0000000000859d1c in generate_via_3dhalf ()

    #17 0x000000000086c88d in sip_3d_g ()

    #18 0x0000000000854ac1 in sip_main ()

    #19 0x0000000000749d40 in pax16_main ()

    #20 0x00000000006a0700 in main ()

    Thank you so much for your helping!!!

    Regards,

    Yuanshan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to yuanshangu

    Yuanshan,

    Please contact customer support. I've been on vacation, so have not been able to look at this (and customer support is the best avenue anyway for crashes).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to yuanshangu

    Yuanshan,

    Please contact customer support. I've been on vacation, so have not been able to look at this (and customer support is the best avenue anyway for crashes).

    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