Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 16357
  • 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

QRC (EXT91) always fails

Zach

Greetings.  First post here.  I can use QRC via EXT71 and EXT81 with no problem.  But when I envoke EXT91, QRC instantly fails to run.  Specifically using IC5.1.41 and qrc -v --> EXT 9.1.2-p009.  The log file gives errors as follows:

 

INFO (EXTQRCXOPT-249) : For Assura inputs, if the "output_setup -directory_name" option was not
specified, it is automatically set to the input directory.
Killed
ERROR (LBRCXM-554): ?capCouplingFactor is an unrecognized rcxParameter in the DFII flow.

ERROR (LBRCXM-554): ?capGround is an unrecognized rcxParameter in the DFII flow.

ERROR (LBRCXM-554): ?arrayViasSpacing is an unrecognized rcxParameter in the DFII flow.

ERROR (LBRCXM-554): ?maxFractureLength is an unrecognized rcxParameter in the DFII flow.

...

 

ERROR (LBRCXM-554): ?capExtractMode is an unrecognized rcxParameter in the DFII flow.

INFO (LBRCXM-699): Errors exist in master control file "<>/assura_lvs/lvs/__qrc.rcx_cmd".

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


INFO (EXTQRCXOPT-249) : For Assura inputs, if the "output_setup -directory_name" option was not
specified, it is automatically set to the input directory.

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

 This has happended to me with multiple PDK's that support EXT91.  So it must be a setup error and unrelated to the PDK files.  I would appreciate if any advice could be offered.  Thanks.

 

Parents

  • Hi everyone,

    I have the same issue with the extraction, i run the command:

    $QRC_HOME/tools/bin/RCXspice -args
    /CAD/Cadence/EXT161/tools/extraction/bin/32bit/RCXspice: error while loading shared libraries: libelf.so.1: cannot open shared object file: No such file or directory

    I found out that the library libelf.so.1 is present in the usr/lib64 but not in the usr/lib.

    On the other hand I dont understand why the RCXspice  is the 32bits and not the 64bits since we add the line "setenv     CDS_AUTO_64BIT       all" in the .cshrc

    The question is: should we intall the libelf.so.1 library 32bits or run the RCXspice 64bits? In case of run the RCXspice 64bits: how can we force cadence to run it instead the 32bits?

    additional info:

    >$ qrc -V
    -----------------------------------------------------------------
    Name           : qrc - Quantus QRC - (64-bit)
    Description    : Quantus QRC Extraction program
    Version        : 16.1.1-s111

    >virtuoso version 6.1.6-64b

    >Red Hat Enterprise Linux Workstation release 6.7

    Thanks and best regards.

    M

Reply

  • Hi everyone,

    I have the same issue with the extraction, i run the command:

    $QRC_HOME/tools/bin/RCXspice -args
    /CAD/Cadence/EXT161/tools/extraction/bin/32bit/RCXspice: error while loading shared libraries: libelf.so.1: cannot open shared object file: No such file or directory

    I found out that the library libelf.so.1 is present in the usr/lib64 but not in the usr/lib.

    On the other hand I dont understand why the RCXspice  is the 32bits and not the 64bits since we add the line "setenv     CDS_AUTO_64BIT       all" in the .cshrc

    The question is: should we intall the libelf.so.1 library 32bits or run the RCXspice 64bits? In case of run the RCXspice 64bits: how can we force cadence to run it instead the 32bits?

    additional info:

    >$ qrc -V
    -----------------------------------------------------------------
    Name           : qrc - Quantus QRC - (64-bit)
    Description    : Quantus QRC Extraction program
    Version        : 16.1.1-s111

    >virtuoso version 6.1.6-64b

    >Red Hat Enterprise Linux Workstation release 6.7

    Thanks and best regards.

    M

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.