Stats

Locked Locked
Replies 9
Subscribers 128
Views 16312
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

ASSURA RCX fails with MOSIS cmrf8sf

like0904 over 15 years ago

HI, to whom it can help,

I got some problem with the ASSURA RCX with MOSIS cmrf8sf/V1.7.0.0DM.

I m using Cadence IC 6.13.500. Assura3.20.022, EXT 8.14..

WIthin the enviroment setting, I aleady have the EXT come before ASSURA, and set the set QRC_ENABLE_EXTRACTION

The DRC and LVS with ASSURA is fine .. and the ASSURA--Run QRC andRC menu are actived.

Normally setting with the QRC:

e.g. :

setup dir : ...../IBM_PDK/cmrf8sf/V1.7.0.0DM/Assura/QRC/32

RSF included : /IBM_PDK/cmrf8sf/V1.7.0.0DM/Assura/QRC/32/LVSincluded.rsf

ref Node : gnd!

The problem is it fail withQRC with following error messge:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

   Cadence Extraction QRC - Parasitic Extractor - Version 8.1.4-p002 Thu Aug
6 21:21:02 PDT 2009
---------------------------------------------------------------------------------------------------
                            Copyright 2009 Cadence Design Systems, Inc.

INFO (LBRCXU-108): Starting

/opt/esdcad/software/cadence/linux/assura3.20.022/tools/assura/bin/rcxToDfII /home/kl05r/design/IBMtest/test/test2/rcx.test2.rsf -t -f /home/kl05r/design/IBMtest/test/test2/test2/extview.tmp -w /home/kl05r/design/IBMtest/test/test2/test2 -cdslib /home/kl05r/design/IBMtest/lib.defs
@(#)$CDS: rcxToDfII version av3.2:Production:dfII6.1.3:IC6.1.3.500.7 06/29/2009 06:01 (sjlin84) $
sub-version 3.2_USR2_HF11, integ signature 2009-06-29-0444

run on esdcad7.ecs.soton.ac.uk from /opt/esdcad/software/cadence/linux/assura3.20.022/tools.lnx86/assura/bin/32bit/rcxToDfII on Wed Jul 7 14:51:48 2010

Loading IBM PDK cmrf8sf Procedures
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33tw_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33tw_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
*ERROR* No library model for device "hvtnfet33_rf auLvs cmrf8sf".
*WARNING* dbOpenCellViewByType: Failed to open cellview (hvtnfet33_rf auLvs) from lib (cmrf8sf) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.

ERROR: Assura is terminating because some library models do not exist.
        Your rules and your dfII model libraries are inconsistent.
        Assura requires all library models in the rule file be present
        in the database when running rcx with the "extracted_view"
        option.

INFO (LBRCXU-111): Warning /opt/esdcad/software/cadence/linux/assura3.20.022/tools/assura/bin/rcxToDfII exit with bad status

INFO (LBRCXU-112): Warning Status 256

INFO (LBRCXU-113): Warning QRC execution terminated

***** aveng fork terminated abnormally *****

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Don't know what's wrong with the setting, can anyone give me some hint...

aplumb over 15 years ago

Check if you have a lib.defs file in the same location as your cds.lib. I've found that if they both exist and are out of sync, problems crop up in the Assura/QRC flow. We only use cds.lib so the solution for us is simply to delete the lib.defs that some tools insist on creating.

Andrew.
Cancel
Vote Up 0 Vote Down

Cancel
like0904 over 15 years ago

Thanks for the reply...
only 'lib.defs' exist over there.. no 'cds.lib'..
and, just now, I have renamed the 'lib.defs' to the 'cad.lib'
Got same error messege as above...
Cancel
Vote Up 0 Vote Down

Cancel
tkhan over 15 years ago

like0904 said:
and, just now, I have renamed the 'lib.defs' to the 'cad.lib'

I'm guessing that was a typo, but anyways in library path editor save new copies of cds.lib and lib.defs.
Cancel
Vote Up 0 Vote Down

Cancel
like0904 over 15 years ago

Hi,, sorry,,, it was a typo....it should be cds.lib
But, anyway,, i still have the same problem either with the cds.lib or with the lib.defs

The issus I just realize is that with in the error log messege,, it point out the transistor 'hctnfet33tw_rf'......indeed. it was not exist with the library of the cmrf8sf...
I want to know is it because i am using Assura 3.20.... is it has to be Assura 4.1 for this new version design kits.....
If I can not get the new Assura 4.1 immediately , is there any solution to this????
Cancel
Vote Up 0 Vote Down

Cancel
Quek over 15 years ago

Would you please confirm if the cell "hvtnfet33tw_rf" from library "cmrf8sf" really has a view named "auLvs"? If not, then we can ignore the missing cells as follows:

In the QRC form, please go to "Setup" tab. Set output to "Extracted view" and disable "Cellview check".

Best regards
Quek
Cancel
Vote Up 0 Vote Down

Cancel
MKanoun over 15 years ago

Hi, I have the same problem as you, Did you find a solution to this? Thanks
Cancel
Vote Up 0 Vote Down

Cancel
tkhan over 15 years ago

No issues extracting with V1700 8RF-DM IBM_PDK,IC06.14.505, ASSURA04.10.015-614, EXT09.13.000...
Cancel
Vote Up 0 Vote Down

Cancel
Quek over 15 years ago

Would this help? : )

>> In the QRC form, please go to "Setup" tab. Set output to "Extracted view" and disable "Cellview check".

Best regards
Quek
- Noname.gif
- View
- Hide
Cancel
Vote Up 0 Vote Down

Cancel
MKanoun over 15 years ago

thanks, it works ;)
Cancel
Vote Up 0 Vote Down

Cancel

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.