I'm facing some issues while doing Extraction including inductances,like
ERROR: Failed to find a cellview for (pinductor)ERROR: Failed to find a cellview for (pmind)ERROR: Failed to find a cellview for (vsource)ERROR: Failed to find a cellview for (ccvs)
But its working properly for R,C,RC extractions.Can you help me to avoid these errors?
Also please suggest some good referece for Extraction .
Do you have analogLib in your cds.lib? Adding this:
to your cds.lib should solve that (assuming you're using IC6.1.X; if using IC5141, replace virtuoso with icfb in the above line).
In reply to Andrew Beckett:
And for "reference" - why not read the documentation that comes with the software?
There's documentation for QRC included. I'm assuming you're using QRC from the PVE stream, but if using the older EXT stream, the same path would work - essentially pick up the cdnshelp from the same path that "qrc" is found.
Thanks for your advice,Still I have some doubts...
Tool version: cadence IC614,ASSURA410,MMSIM 101
I am using two scripts to invoke tool,in that certain variables are used to set lib paths.After invoking tool,Library viewer shows paths are valid and in that analogLib mapped into IC614.But while executing RCX,its shows 'analogLib in Assura410 installation doesn't exist'.
1)For this issue I edited the the script file (direct path is assigned instead of variale).then RCX works properly.
2) Also i found there is no such lib in my assura installation file.RCX
works properly when i copied the lib file manually into the assura
folder without editing script file.
My doubt is while doing RCX which 'analogLib' we need to use? Or Whether it happens due to mistakes in the script fil?
In reply to hsps:
Can you show what was in your cds.lib for analogLib? That will help understand the issue.
DEFINE analogLib $CDS_INST_DIR/tools.lnx86/dfII/etc/cdslib/artist/analogLib
setenv CDS_INST_DIR /cad/cadence/IC615ISR_lnx86
I thought that might be the case. $CDS_INST_DIR in a cds.lib is not actually the value of the environment variable, but a special sequence which means something to the tools. In the dim and distant past (I think prior to IC443, so something like 13 or 14 years ago), $CDS_INST_DIR was interpreted as an environment variable. This was fine until Cadence split their tools into separate "streams" (in the early days all Cadence products were released together in a single hierarchy, but this stopped being sustainable as the range of the portfolio increased). Since a single environment variable couldn't point to more than one stream, the interpretation of $CDS_INST_DIR in a cds.lib was changed to mean "the installation that the tool reading the cds.lib is coming from". So that means that virtuoso/icfb will interpret as meaning the IC hierarchy, whereas Assura would intepret as being the ASSURA hierarchy and so on.
The incantation that I gave you:
is an additional construct that says "find the hierarchy using your UNIX path that contains tools/dfII/bin/virtuoso under the root".
Alternatively, if you'd set your environment variable to something other that $CDS_INST_DIR, for example $CDSHOME, and then referenced $CDSHOME in the cds.lib, that would have worked too. Other environment variables in cds.lib are interpreted strictly as environment variables - you've just hit a problem because $CDS_INST_DIR is a special case.
Thank you so much for your support.Now things are working fine.
I will expect your sincere help next time too....