• 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 9945
  • 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
  • Quek
    Quek over 13 years ago

    Hi bjbit

    Would you please provide the specific version of QRC which you are using? This might be an old bug which has already been fixed.

    Best regards
    Quek

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

    Hi Quek,

    Thanks for the quick response.  Here is what I found from the document.

    PDK version: V1.9.0.0

    Assura version: 4.1USR2_HF3

    QRC version: 10.1.2-s078

    Regards,

    bjbit 

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

    Hi bjbit

    Thanks for the info. I meant the actual QRC version which you are using. You can check it in a terminal window using:

    terminal>qrc -version

    Best regards
    Quek

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

    Hi Quek,

    Sorry I cannot find this "qrc" command in any directory from linux console. There is no "bin" folder in the installed PDK. I am confused. Could you please help out? Thanks.

    Regards,

    bjbit 

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

    Hi bjbit

    "qrc" is the executable file for running the extraction. If it is not present in your path, it most probably means that you are not using QRC. You might have used the old Assura RCX for the extraction. Please request your IT to download and install PVE package and it should resolve the problem. 

    Please note that Assura and QRC comes in separate packages. Assura comes from "Assura" package. QRC comes from "PVE" package.


    Best regards
    Quek

    • pve.gif
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • bjbit
    bjbit over 13 years ago

    Hi Quek,

    Thanks a lot for the info. It seems you are right, since I used "run RCX" under "Assura" manu in Cadence virtuoso. By checking the assura installed in the server, I found the version is  4.1_USR1_HF11, while the version tested in document is 4.1_USR2_HF3. Is RCX default integrated with assura, and QRC is seperated tool? Does the assura version matter for installing and using QRC? So I need to install QRC tool for the availability of the QRC package in my PDK, right?

    Sincerely,

    bjbit 

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

    Hi bjbit

    Yes, RCX is integrated with Assura. QRC is a separate tool. You will need to use the latest version of Assura (41USR2_HF12) together with QRC. Please install PVE and add the following to your .cshrc file:

    setenv QRC_HOME /your-path/PVE11
    set qrcPath=($QRC_HOME/bin $path)

    Yes, you need to install QRC for your PDK.

     
    Best regards
    Quek

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

    Hi Quek,

    I appreciate all of your helps. Thanks a ton.

    Regards,

    bjbit 

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

    Hi bjbit

    You are welcome

    Best regards
    Quek

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

    Hi Quek,

    Finally I asked my server manager to get PVE11 package installed. Now my working environment is Assura41 _USR2_HF10 under IC614. Here is a question regarding to setup QRC. When I type "qrc -version" to check version (actually also other commands), no any information poped, even command errors. When I open a layout view and click the QRC menu, "Loading QRC menu..." is shown under it, and a warning of "RCX UI is already loaded" is given in CIW. I guess it maybe a conflict issue between QRC and the integrated old RCX? Any advices to solve it? Thanks in advance.

    Sincerely,

    bjbit 

    • 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