Cadence IC612: Problem in overriding Assura317 by EXT92

Status
Not open for further replies.

shahriar22nd

Member level 2
Joined
Sep 24, 2009
Messages
45
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Location
Dhaka, Bangladesh
Activity points
1,663
Hello all,
I am trying to perform QRC for IBM cmc9flp in Cadence IC612 together with Assura317 and EXT92. I added followings in my .cshrc file:

setenv QRC_HOME /vhome/EDA/EXT92
set path=( $QRC_HOME/tools/bin $PATH )
setenv QRC_ENABLE_EXTRACTION 't'
setenv ASSURAHOME /usr/local/cadence/assura317
set path=( $ASSURAHOME/tools/dfII/bin $ASSURAHOME/tools/bin $ASSURAHOME/tools/assura/bin $PATH )
setenv OA_HOME /vhome/EDA/EXT92/oa_v22.04.050


With all these, I can run DRC and LVS without any problem, but problem occurs when I try: Assura->Run RCX from the Layout L window. The form which appears is named Assura Parasitic Extraction Run Form (not 'QRC Parasitic Extraction Run Form'). At the same time, the CIW reads:

\w *WARNING* QRC_ENABLE_EXTRACTION environmental variable is set but UI can't locate correct QRC installation.
\o In order to run UI in QRC compatibility mode you need to have QRC executables in your $PATH and QRC
\o version should be 6.2.0 or greater. Check your QRC installation and environmental settings.


It seems, my Assura is not overridden properly by the EXT. Anyone please suggest me a right way to override Assura by EXT.
Thank you.
 

setenv ASSURAHOME /usr/local/cadence/assura317
set path=( $ASSURAHOME/tools/dfII/bin $ASSURAHOME/tools/bin $ASSURAHOME/tools/assura/bin $PATH )
setenv QRC_HOME /vhome/EDA/EXT92
set path=( $QRC_HOME/tools/bin $PATH )
setenv QRC_ENABLE_EXTRACTION 't'
setenv OA_HOME /vhome/EDA/EXT92/oa_v22.04.050

Refer to release notes of the PDK, I think IC613 and ASSURA32 should be used.
 
Thank you for your reply.
https://www.mosis.com/ibm/ibm-cmos-kits.html prescribes only Cadence IC6.1, no more specifications ! Even I got no information about the compatible tools in any docs of the pdk.
However, I was concerned about the warning of the CIW, because it seems, my Assura was not properly overridden by the EXT wheres so far I know, EXT overrides Assura when it's path comes before that of Assura in the csh file. I thought this warning has no relation with the pdk.
Would you please mention whether I am missing something here or not?
Thank you ...
 

read the release notes in <path to pdk>/doc/, <path to pdk>/Spectre/doc/, <path to pdk>/cdslib/doc/, <path to pdk>/Assura/doc/ for the versions of the tools you need. it is one of the first things in the document. the website is not up to date.

If you reread my previous reply you will see that I switched the order of the assura and ext definitions, which will achieve what you want.
 
Thank you, oermens. You are right. I checked your paths and found in <path to pdk>/Assura/doc/ that, it needs 'assura version av3.20.018-613.610'. And as assura32 runs with ic613, so it seems must.
I reread your previous reply and realized that I didn't notice the re-arrangement first time. I must try them and shall update the thread after that.
Thanks a lot ...
 

I rearranged the paths, but no change ! I am thinking about the message:

\w *WARNING* QRC_ENABLE_EXTRACTION environmental variable is set but UI can't locate correct QRC installation.
\o In order to run UI in QRC compatibility mode you need to have QRC executables in your $PATH and QRC
\o version should be 6.2.0 or greater. Check your QRC installation and environmental settings.


I doubt about the installation of my EXT, though I had no warning/error during the installation. Is there any way to check the installation? For example, for assura, I can see assura -V or avview -V to check if it exists. Please write me if there is any way to debug.
Thanks ...
 


i know someone who had this problem, it was related to using 32bit tools on a 64bit OS.


source your environment setup script and type qrc -V. also, type echo $PATH and check the output just to be sure it is correct.

best to post on https://www.cadence.com/community/forums/ and make sure to give details of the tools you have installed and your OS.
 
Status
Not open for further replies.
Cookies are required to use this site. You must accept them to continue using the site. Learn more…