• 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 9946
  • 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

    My guess is that you are using redhat enterprise 4.x. You will need redhat enterprise 5.5 and above in order to use PVE package. : )  If it is not possible to find a machine with RHEL5.5 and above, you can also also use the slightly older EXT10.1.2 package. It should also resolve your problem. The history of QRC is as follows:

    a. Named as "rcx" and comes from Assura package
    b. Combined with cell level extractor and renamed as "QRC". Comes from EXT package.
    c. Packaged together with PVS in PVE package.

    Best regards
    Quek

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

    Hi Quek,

    Thanks for the advices. I will ask the manager to have a check.

    Regards,

    bjbit 

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

    bjbit said:
    QRC menu, "Loading QRC menu..." is shown under it, and a warning of "RCX UI is already loaded" is given in CIW

     

     Hello,

    Sorry for my English.

    I have the same problem. I Upgrade EXT91 to EXT101 and now The QRC menu only give me  "Loading QRC menu..." and I ha ve the same warning about RCX UI.

    Does anyone has an idea?

    Thanks in advance

     

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

    Hi Johjohn,

    As Quek advised, I have fixed this problem on PVE11 by using the newer version of Linux system. I am not sure about the compatibility of EXT10, but did EXT9 work for you? If so, probably you are having the same Linux issue. I guess you may try on another machine with newer version OS, and see what's going on. Anyway, I believe Quek can provide further advices.

    Regards,

    bjbit 

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

     Hi bjbit.

    I'm working on Fedora 15. With EXT9, it works. But not with EXT10. The two install have the same configuration...

    I don't know why.

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

    Hi bjbit

    Thanks. : )


    Hi Jon

    Would you please try upgrading to the latest version of Assura (41USR2_HF14) and latest version of EXT10.1 (10.1.3)? I think the earlier versions of EXT10.1 has this problem.

    Best regards
    Quek

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

    Hi Quek,

    Thanks for your reply.

    I already made all the update. I'm well running Assura  41USR2_HF14 and the latest version of EXT10.1.3. But the problem still exist.

    If I running virtuoso layout whithout ASSURAHOME environmental variable configured, and if I click the qrc menu I have this message:

      *WARNING* QRC_HOME environmental variable is set but UI can't locate correct QRC installation. p, li { white-space: pre-wra

    In order to run UI in QRC compatibility mode you need to have QRC executables in your $PATH and QRC version should be 8.1 or greater.

    Check your QRC installation and environmental settings.

     

    And my environmental is configure like this:

     

    setenv QRC_HOME /softs/cadence/EXT101
    setenv PATH $QRC_HOME/bin:$PATH
    setenv PATH $QRC_HOME/tools/bin:$QRC_HOME/tools/extraction/bin:$PATH

     

    If I run  $QRC_HOME/tools/bin/qrc , it return nothing. But whith EXT9 it works with the same configuration.

     

     Best regards

     

    Jonjohn

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

    Hi Jonjohn

    Would you get the path to the qrc executable if you enter the following in a terminal window?

    terminal>which qrc

    How about this?

    terminal>qrc -version

    Best regards
    Quek

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

    Hi Quek,

     which qrc return: /softs/cadence/EXT101/tools/bin/qrc

    In fact I solved a part of the problem if I set OA_HOME to "/softs/cadence/IC614/share/oa", qrc don't work : the command "qrc -version" return nothing.

    But if I don't set the OA_HOME variable, it works...

    If I set OA_HOME to  "$QRC_HOME/share/oa, I can't run virtuoso. I have this error:

     /softs/cadence/IC614/tools/dfII/bin/64bit/virtuoso: /softs/cadence/IC614/tools/lib/64bit/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /softs/cadence/EXT101/share/oa/lib/linux_rhel40_gcc44x_64/opt/liboaPlugIn.so)
    /softs/cadence/IC614/tools/dfII/bin/64bit/virtuoso: /softs/cadence/IC614/tools/lib/64bit/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /softs/cadence/EXT101/share/oa/lib/linux_rhel40_gcc44x_64/opt/liboaCommon.so)

    Any idea?

     Best regards

     

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

    Don't set OA_HOME. You should not have to - and if you do, you end up with these kind of potential compatibility headaches.

    If you don't set OA_HOME, each build can use the OA version it was shipped with, which is the right thing to do since that's what has been tested...

    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