• 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. Regarding : PVS - QRC RUN FAILURE

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 3840
  • 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

Regarding : PVS - QRC RUN FAILURE

narendra046
narendra046 over 11 years ago

 HI All,

 Newly I made PVS drc & lvs and QRC setup for new technology(gf28nm).

 PVS version - Version        : 12.1.1-p076

 QRC Version        : 10.1.0-s231

 

When I'm running PVS - QRC through QRC menu, It was failed and showing error like..,


------------------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------------------

--------------

--------------

All device symbols for the extracted view are present.

INFO (LBRCXU-114): Finished /chicago/tools/cadence/IC6150/bin/qrcToDfII

INFO (LBRCXM-642): Constructing the RCX run script

INFO (RCXSPIC-28057): RCXspice: unrecognized variable 'CFITABLE' in file '/remote2/test_proj/analog_project/gf28hp/release/qrc/5U1x_1T8x_LB/nominal/RCXspiceINIT'

ERROR (LBRCXM-644): Bad return status from RCX script generator. 0x100

INFO (LBRCXM-709): *****  QRC terminated abnormally  *****

 ------------------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------------------

  Please let me know any suggestions to resolve this issue. 

 Thanks in Advance.

 

Regards,

Narendra

  • Cancel
  • Quek
    Quek over 11 years ago

    Hi Narendra

    It means that your current version of QRC is older compared to the version which Globalfoundries had used to prepared the QRC package. The problem can be easily resolved by switching to a newer version of QRC (e.g. QRC14.1).

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • narendra046
    narendra046 over 11 years ago

     Thanks Quek for your valuble suggestions.

    Now QRC was almost run after installed qrc newer version(EXT13.2).  But, At the end of qrc run it was failed and showing error like..,

     

     

    ENDCAT
    cat \
            /remote2/test_proj/analog_project/GF/VIRTUOSO/LVS_QRC/svdb/test/hccisavefile \
            >> _save_layers

    INFO (LBRCXM-610): Extraction finished.

    INFO (LBRCXU-108): Starting

     /chicago/tools/cadence/IC6150/bin/qrcToDfII -extract both -run_name test -cdlout_run_dir /remote2/test_proj/analog_project/GF/VIRTUOSO/LVS_QRC -check_cell_view FALSE -device_finger_delimiter @ -extracted_view av_extracted -lvs_source agds -cap_models no -capacitor pcapacitor -res_models no -resistor presistor -cap_prop_name c -res_prop_name r -extview_tmp /remote2/test_proj/analog_project/GF/VIRTUOSO/LVS_QRC/svdb/test/extview.tmp -run_dir /remote2/test_proj/analog_project/GF/VIRTUOSO/LVS_QRC/svdb/test -lib_name narendra -cell_name test -view_name layout -extview_rul /remote2/test_proj/analog_project/GF/release/qrc/extview.rul -server /remote2/tools/cadence/EXT13.2/tools.lnx86/extraction/bin/32bit//../shapeServer
    Virtuoso Framework License (111) was checked out successfully. Total checkout time was 0.16s.
    exec: /remote2/tools/cadence/EXT13.2/tools.lnx86/extraction/bin/64bit/shapeServer: cannot execute [Exec format error]
    Failed to start QRC module 'shapeServer'. Please check QRC installation or contact Cadence Customer Support.
    INFO (LBRCXU-111): Warning /chicago/tools/cadence/IC6150/bin/qrcToDfII exit with bad status

    INFO (LBRCXU-112): Warning Status 256

    INFO (LBRCXU-113): Warning QRC execution terminated



    *****  aveng fork terminated abnormally  *****

     

     

     

    Please help me to resolve this issue. Thanks in advance.

     

    Regards Narendra

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    What OS distribution are you using? And what does "uname -a" report?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • narendra046
    narendra046 over 11 years ago

    Hi Andrew,

    Sorry for late reply.

    "uname -a" report on my side is -

    Linux blue 2.6.32-431.el6.i686 #1 SMP Fri Nov 22 00:26:36 UTC 2013 i686 i686 i386 GNU/Linux
     

    Thank you

    Narendra

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Narendra,

    It looks as if you're using a 32-bit OS (although probably a RHEL6 flavour - you didn't say - given the kernel subversion). Generally speaking we don't support 32-bit OS for recent releases of the software, so the best thing to do is to update to a 64-bit OS.

    I took a quick look, and initially thought by setting $CDS_AUTO_64BIT to "none" or "NONE" you could force QRC to run in 32-bit mode (the default for QRC is 64-bit. However, it appears that on RHEL6.1 and RHEL6.3 (i.e. the same region of kernel versions that you're using - RHEL6.3 is kernel  2.6.32-279.el6.x86_64) it always seems to run shapeServer in 64-bit mode even when CDS_AUTO_64BIT is set (the "qrc" executable is OK, but not shapeServer). On RHEL5.8 setting this successfully runs shapeServer in 32-bit mode.

    So you really should run on a 64-bit OS. This can be seen in our platform support matrix.

    Regards,

    Andrew.

    • 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