Stats

  • Locked Locked
  • Replies 14
  • Subscribers 125
  • Views 7339
  • 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: *Error* load: can't access file "[...]/ext_18.12.000/tools/extraction/bin/32bit/etc/context/6.1.0/qrc.ini"

dontpanic

Hi! When I launch the "PVS->Run LVS..." command in a layour editor, I get the following messages in the CIW:

QRC: *Error* load: can't access file "[...]/ext_18.12.000/tools/extraction/bin/32bit/etc/context/6.1.0/qrc.ini"
*WARNING* (DEBASE-102079): A SKILL error occurred in function CCSSetupQRC

In my QRC installation the "[...]/32bit" directory does not exist, but the "[...]/64bit" does. Moreover, I have the environment CDS_AUTO_64BIT variable set to ALL, but it seems CCSSetupQRC is looking for the wrong executable. How can I solve this issue? I am using ICADV12.3-64b.500.17 with PVS 16.12

Thanks and regards, Jorge.


  • Saloni Chhabra

    Hi Jorge,

    It is odd that trying to run PVS LVS gives an error related to QRC. Can you tell me what the below commands return in a terminal:

    pvs -v

    qrc -v

    Regards,
    Saloni

  • dontpanic
    in reply to Saloni Chhabra

    Thanks for your reply, Saloni. Please find below the output of both commands:

    I am trying to follow the PVS-QRC flow as described in "Setting PVS to Quantus QRC av_extracted view Flow with tsmc16 LVS package". In particular, I get the error at Step 5 ("Running PVS LVS", p. 20).

    Moreover, I get a different error at Step 6 ("Running Quantus QRC", p. 22), as shown below:

    ...and in the CIW I get the following message:

    QRC Run: Loading Technology Data. Standby...
    *Error* eval: unbound variable - preRCXQueryUI

    Could you please give me a further hand on these?

    Thanks and regards, Jorge.

  • Saloni Chhabra
    in reply to dontpanic

    Thanks Jorge. The tools appear to be properly setup, so I am not sure where the problem is. When you get the error in CIW while trying to run PVS LVS, does PVS form come up?

  • dontpanic
    in reply to Saloni Chhabra

    Saloni, I just realized that the error in the CIW (the one in my original post) doesn't appear when launching that form: it appears when I open the layout view! So it seems the issue is in the initial QRC setup. Sorry for the confusion! (BTW, the PVS->Run LVS... form does appear, and the LVS does run). The 2nd error I reported subsequently, DOES appear when executing "QRC->Run PVS - Quantus QRC...".

  • Saloni Chhabra
    in reply to dontpanic

    Can you tell me what the below commands return in CIW:

    getShellEnvVar("QRC_HOME")
    getShellEnvVar("QRC_ENABLE_EXTRACTION")

    Also, in your terminal, what does 'echo $path' return?

  • dontpanic
    in reply to Saloni Chhabra

    Please see below the requested outputs:

  • Saloni Chhabra
    in reply to dontpanic

    Sorry I missed asking what does 'which qrc' return?

  • dontpanic
    in reply to Saloni Chhabra

    It returns: /[...]/software/cadence/release2018/ext_18.12.000/tools/bin/qrc

  • Saloni Chhabra
    in reply to Saloni Chhabra

    Things look ok. Going back to the error you mentioned you get when the pop-up asks 'Do you want to ignore this error and continue?' : what happens when you click on Yes? Does any form come up?

  • dontpanic
    in reply to Saloni Chhabra

    The QRC form does come up and I'm able to perform extractions; I however wonder if the error is having some impact in the extraction results I get.

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.