Stats

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

 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

Parents

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

Reply

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

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.