• 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. "capgen" error in Assura QRC (RCX)

Stats

  • Locked Locked
  • Replies 24
  • Subscribers 129
  • Views 9957
  • 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

"capgen" error in Assura QRC (RCX)

bjbit
bjbit over 13 years ago

Hi all,

I work with the technology of IBM CMOS7RF on Cadence 5.1 (IC5141). Currently I am trying to extract parameters for a self-customized inductor.  By setting "ind" model in schemetic as a blackbox and ignoring mismatches, I go through LVS. Now an error happens in QRC as below.

========================================================================= 

*WARNING* at "capgen": x-tile size is not floating point number

*ERROR* at "capgen": capgen job quit due to process file errors.

 

quitting.

 -blocking coupled5_shield1:0.02,M1,M2,M3,M4,M5 -blocking coupled5_shield2:0.02,M2,M3,M4,M5 -blocking coupled5_shield3:0.02,M3,M4,M5 -blocking coupled5_shield4:0.02,M4,M5 -blocking coupled4_shield1:0.02,M1,M2,M3,M4 -blocking coupled4_shield2:0.02,M2,M3,M4 -blocking coupled4_shield3:0.02,M3,M4 -blocking coupled3_shield1:0.02,M1,M2,M3 -blocking coupled3_shield2:0.02,M2,M3 -blocking coupled2_shield1:0.02,M1,M2 -blocking singleEndA_shieldT:0.02,MT,ML -blocking singleEndA_shield5:0.02,M5,MT,ML -blocking singleEndA_shield4:0.02,M4,M5,MT,ML -blocking singleEndA_shield3:0.02,M3,M4,M5,MT,ML -blocking singleEndA_shield2:0.02,M2,M3,M4,M5,MT,ML -blocking singleEndA_shield1:0.02,M1,M2,M3,M4,M5,MT,ML -res_blocking singleEndA_shieldT:0.02,ml -res_blocking singleEndA_shield5:0.02,ml -res_blocking singleEndA_shield4:0.02,ml -res_blocking singleEndA_shield3:0.02,ml -res_blocking singleEndA_shield2:0.02,ml -res_blocking singleEndA_shield1:0.02,ml -blocking singleEndT_shield1:0.02,M1,M2,M3,M4,M5,MT -blocking singleEndT_shield2:0.02,M2,M3,M4,M5,MT -blocking singleEndT_shield3:0.02,M3,M4,M5,MT -blocking singleEndT_shield4:0.02,M4,M5,MT -blocking singleEndT_shield5:0.02,M5,MT -blocking singleEnd5_shield1:0.02,M1,M2,M3,M4,M5 -blocking singleEnd5_shield2:0.02,M2,M3,M4,M5 -blocking singleEnd5_shield3:0.02,M3,M4,M5 -blocking singleEnd5_shield4:0.02,M4,M5 -blocking singleEnd4_shield1:0.02,M1,M2,M3,M4 -blocking singleEnd4_shield2:0.02,M2,M3,M4 -blocking singleEnd4_shield3:0.02,M3,M4 -blocking singleEnd3_shield1:0.02,M1,M2,M3 -blocking singleEnd3_shield2:0.02,M2,M3 -blocking singleEnd2_shield1:0.02,M1,M2 -blocking ml_transmission,sti,ML -blocking symind3_mlml_m1,sti,M1,MT,ML -blocking symind2_mlml_m1,sti,M1,MT,ML -blocking ind2_mtml_m1,sti,M1,MT,ML -res_blocking symind3_mlml_m1,mt_resistive,ml -res_blocking symind2_mlml_m1,mt_resistive,ml -res_blocking ind2_mtml_m1,mt_resistive,ml -blocking symind3_mlml_bb,sti,MT,ML -blocking symind2_mlml_bb,sti,MT,ML -blocking ind2_mtml_bb,sti,MT,ML -res_blocking symind3_mlml_bb,mt_resistive,ml -res_blocking symind2_mlml_bb,mt_resistive,ml -res_blocking ind2_mtml_bb,mt_resistive,ml -blocking bondPad_PC:5.28,sti,PC,ML -res_blocking bondPad_PC:5.28,ml -blocking bondPad_BB:5.28,sti,ML -res_blocking bondPad_BB,ml /home/zheng072/zy_senser/inductor_test1

*WARNING* Bad return status from RCX script generator. 0x100

===============================================================================

I cannot figure out what's wrong with "process file". I have installed Assura QRC package exactly as the document states. Any advices are appreciated.

Thanks. 

  • Cancel
  • Jonjohn
    Jonjohn over 13 years ago

     Ok

     Thaks very much everybody.

     Best regards,

     Jonjohn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi Jonjohn

    You can correct the problem as follows:
    a. Check $QRC_HOME/share. Is there a soft link named "oa"? It should point to the OA directory (e.g. oa_v22.1123) in the QRC installation directory.

    b. If the link is not present, please create it using:

    terminal>ln -s ../oa_v22.1123 oa

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ebecheto
    ebecheto over 12 years ago

     I experienced a similar bug.

    Whether EXT9 or EXT10 was not opening properly. The menu ASSURA was refering to RCX and not QRC. And the QRC menu add only one field... not working.

    We fixed the bug by changing ASSURA version :

    sub-version 4.1_USR1, integ signature 2009-12-08-1700           #<= not working with QRC
    sub-version 4.1_USR2_HF17, integ signature 2012-06-06-0926 #<= in working properly with QRC

    And of course, our path where set correctly in any cases

    export QRC_ENABLE_EXTRACTION
    export QRC_HOME=/soft/cadence/EXT10.13.065

    ASSURAHOME=/soft/cadence/ASSURA41-614_0412017

    PATH=$QRCDIR/bin:$QRCDIR/tools/bi:$PATH:$ASSURAHOME/tools/bin:$ASSURAHOME/tools/assura/bin

     

     

    I hope this post will save two working days to other person in the same trouble.

    Regards,

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kabal
    Kabal over 12 years ago

    We have EXT10, the qrc version is: 10.1.1-p095

    The assura is 4.1, 6.13

    In the .cshrc I have:

     

    setenv ASSURAHOME $cadence_install_dir/assura41
    setenv QRC_HOME $cadence_install_dir/ext10

    And the path to internal folders of ext10 and assura41. However I also do get: 

    *WARNING* The RCX UI context file is already loaded.

     

    The Linux which we are using is an updated new version of RHEL.  what else could I be missing?

     

    • 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