Problem when switching from Assura RCX 3.1.7OA to 3.2OA with "unrecognizedrcxParameters"

Hi,

I just tried to switch Assura RCX (64-bit, OA) from 317_USR2_HF7 to
3.2_USR2_HF11. Assura is working on a dfII-database (actually OA I
assume) but tool was started from the command line. The technology and
assura rules are from austriamicrosystems (HitKit 4.00, technology C35B4).

With 3.1.7, the following RSF causes no troubles:

================= BEGIN 1
avParameters(
?workingDirectory "ASSURA_PEX/amba_multiplier"
?runName "amba_multiplier"
?inputLayout ("df2" "amba_multiplier")
?cellName "amba_multiplier"
?viewName "layout"
?technology "c35b4c0"
?techRuleSet "Typical"
?techLib "./assura_tech.lib"
)
rcxParameters(
?outputFormat "dfII"
?extractedView "av_extracted"
?extractMosDiffusionRes t
?checkCellView nil
?resistor "presistor auLvs PRIMLIB"
?resPropName "r"
?capacitor "pcapacitor auLvs PRIMLIB"
?capPropName "c"
?extract "both"
?netNameSpace "schematic"
?maxFractureLength "infinite"
?fractureLengthUnits "microns"
?temperature 25.0
?capExtractMode "coupled"
?capGround "gnd!"
?capCouplingFactor 1.0
?type "full"
?rcxfsType "none"
?excludeSelfCaps t
; ?minR 0.001
; ?minC 0.01e-15
; ?minCByPercentage 0.1
?maxMergedViaSize "auto"
?arrayViasSpacing "auto"
?capModels "no"
?parasiticCapModels "no"
?resModels "no"
?parasiticResModels "comment"
?parasiticResWidth nil
?parasiticResWidthDrawn nil
?substrateStampingOff t
?runName "amba_multiplier"
)
setShellEnvVar("CDS_AUTO_CKOUT=all")
avRCX()
================ END 1

However, when switching to 3.2, assura rcx immediately terminates with
the following messages about various unrecognized rcxParameters (I'm
sorry for the ugly line wrapping):

================= BEGIN 2
Assura (tm) Physical Verification Version
av3.2roduction:dfII6.1.3-64b:IC6.1.3-64b.500.7
Release 3.2_USR2_HF11

Copyright (c) Cadence Design Systems. All rights reserved.
@(#)$CDS: assura_64 version
av3.2roduction:dfII6.1.3-64b:IC6.1.3-64b.500.7 06/29/2009 05:50
(icrop007) $
sub-version 3.2_USR2_HF11, integ signature 2009-06-29-0444

run on redheat.iaik.tugraz.at from
/raid/vlsi_soft/cds2009/assura3.2oa/tools.lnx86/assura/bin/64bit/assura
on Fri Apr 9 14:25:33 2010

Error: ?extractMosDiffusionRes is an unrecognized rcxParameter in the
DFII flow.
Error: ?netNameSpace is an unrecognized rcxParameter in the DFII flow.
Error: ?maxFractureLength is an unrecognized rcxParameter in the DFII flow.
Error: ?fractureLengthUnits is an unrecognized rcxParameter in the DFII
flow.
Error: ?temperature is an unrecognized rcxParameter in the DFII flow.
Error: ?capExtractMode is an unrecognized rcxParameter in the DFII flow.
Error: ?capGround is an unrecognized rcxParameter in the DFII flow.
Error: ?capCouplingFactor is an unrecognized rcxParameter in the DFII flow.
Error: ?type is an unrecognized rcxParameter in the DFII flow.
Error: ?rcxfsType is an unrecognized rcxParameter in the DFII flow.
Error: ?excludeSelfCaps is an unrecognized rcxParameter in the DFII flow.
Error: ?maxMergedViaSize is an unrecognized rcxParameter in the DFII flow.
Error: ?arrayViasSpacing is an unrecognized rcxParameter in the DFII flow.
Error: ?capModels is an unrecognized rcxParameter in the DFII flow.
Error: ?parasiticCapModels is an unrecognized rcxParameter in the DFII flow.
Error: ?resModels is an unrecognized rcxParameter in the DFII flow.
Error: ?parasiticResModels is an unrecognized rcxParameter in the DFII flow.
Error: ?parasiticResWidth is an unrecognized rcxParameter in the DFII flow.
Error: ?parasiticResWidthDrawn is an unrecognized rcxParameter in the
DFII flow.
Error: ?substrateStampingOff is an unrecognized rcxParameter in the DFII
flow.

Loading tech rule set file :
/vlsi_tech/ams_hk4.00/assura/c35b4/c35b4c0/techRuleSets


***** Assura terminated abnormally *****
================= END 2

I've no idea why these parameters are suddenly unrecognized. They are
still listed in the 3.2OA documentation and I got no indication that
they have been removed from the "DFII flow".

Searching the Internet and support.cadence.com didn't yield any
utilizable hints. Maybe someone here can help me...

Thanks,
-Thomas

 

Am 09.04.2010 15:18, schrieb Thomas Popp:

Hi Thomas,

please check if you have all the necessary libs available:

I found some reports that missing libelf packages causing such errors.

Hope that helps,
Marc

 

Am 09.04.2010 16:07, schrieb Marc Heise:

Hi Marc,

Thanks for the hint, but everything seems to be ok in this regard. Is
anything looking suspicious to you?

ldd /vlsi_soft/cds2009/assura3.2oa/tools.lnx86/assura/bin/64bit/assura
linux-vdso.so.1 => (0x00007fffcbde2000)
libm.so.6 => /lib64/libm.so.6 (0x00000033efe00000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00000033fa000000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000033f0200000)
libelf.so.1 => /usr/lib64/libelf.so.1 (0x000000366e200000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000033f0600000)
libgfortran.so.1 =>
/vlsi_soft/cds2009/ius8.2/tools/lib/64bit/libgfortran.so.1
(0x00007fc4dd515000)
libstdc++.so.6 =>
/vlsi_soft/cds2009/ius8.2/tools/lib/64bit/libstdc++.so.6
(0x00007fc4dd317000)
libgcc_s.so.1 =>
/vlsi_soft/cds2009/ius8.2/tools/lib/64bit/libgcc_s.so.1 (0x00007fc4dd109000)
libc.so.6 => /lib64/libc.so.6 (0x00000033efa00000)
/lib64/ld-linux-x86-64.so.2 (0x00000033ef600000)



I also tried to run Assura RCX in 32-bit mode -> same errors (ldd-result
also look fine for the 32-bit executable).

Many thanks so far!

-Thomas