Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 14706
  • 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 extraction problem

Adam86

I'm at QRC stage now where I have encountered this extraction problem:

I even enabled the qrc extraction on icfb

setShellEnvVar("QRC_ENABLE_EXTRACTION=t")

Cadence Extraction QRC - 64-bit Parasitic Extractor - Version 8.1.5-p004
Mon Sep 14 18:19:56 PDT 2009
----------------------------------------------------------------------------------------------------------
                               Copyright 2009 Cadence Design Systems, Inc.

INFO (LBRCXU-108): Starting

 /CMC/tools/cadence/ASSURA-5141.3.20.022/tools/assura/bin/rcxToDfII /home/aalsaafi/practice/rcx.Working1110.rsf -t -f /home/aalsaafi/practice/Working1110/extview.tmp -w /home/aalsaafi/practice/Working1110 -cdslib /home/aalsaafi/practice/cds.lib
@(#)$CDS: rcxToDfII_64 version av3.2:Production:dfII5.1.41-64b:5.10.41-64b.500.6.130 06/30/2009 00:57 (dfm325opt04) $
sub-version 3.2_USR2_HF11, integ signature 2009-06-29-0444

run on oslo.doe.carleton.ca from /CMC/tools/cadence/ASSURA-5141.3.20.022/tools.lnx86/assura/bin/64bit/rcxToDfII on Mon Oct 15 13:59:05 2012

Loading IBM PDK cmrf8sf Procedures for Cadence Version "av3.2:Production:dfII5.1.41-64b:5.10.41-64b.500.6.130"
*ERROR* Terminal sub on cellview (cmrf8sf devicepad auLvs) is not defined on device (devicepad#20auLvs#20cmrf8sf) in the extraction rules

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 /CMC/tools/cadence/ASSURA-5141.3.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  *****

 

This is on 0.13um process (cmrf8sf) on Cadence 5.41

 
if anyone has fixed such an error or knows how please help

  • Hi Adam

    This is the cause of the error:

    *ERROR* Terminal sub on cellview (cmrf8sf devicepad auLvs) is not defined
    on device (devicepad#20auLvs#20cmrf8sf) in the extraction rules

    In your extract.rul file, the "devicepad" cell has been defined with terminals "A B C". E.g.

    extractDevice("devicepad" _recLayer layer1("A") layer2("B") layer3("C") ... cellView("devicepad" "auLvs" "cmrf8sf") ... )

    But in auLvs view of the cell, the terminals are "A B sub". This is a common problem due to mismatch pdk/rule deck info. You can either contact the foundry and get a more updated rule deck (or pdk) or correct rule deck yourself.


    Best regards
    Quek

  •  Hi Quek

     Could you please eleobrate more on what needs to be updated in the extract.rul file

     I'm using extract32.rul and see this:

     extractDevice( "devicepad" padOverDev padOverDev_top( "pad" ) flagMalformed namePrefix( "X" ) termOrder( " pad     " ) spiceModel("devicepad") cellView("devicepad auLvs cmrf8sf") )
        saveProperty( padOverDev "c" 1e-15 )

     I'm sure that has nothing to do with  extractDevice("devicepad" _recLayer layer1("A") layer2("B") layer3("C") 

  • Hi Adam

    You can modify the rule as:

    extractDevice( "devicepad" padOverDev padOverDev_top( "pad" ) yourSubLayer("sub") flagMalformed namePrefix( "X" ) termOrder( "pad sub" ) spiceModel("devicepad") cellView("devicepad auLvs cmrf8sf") ) saveProperty( padOverDev "c" 1e-15 )

    Please substitute "yourSubLayer" with the actual name of the substrate layer meant for devicepad cell. E.g. "psub", "bulk", etc. Just check the "B" pins of mos devices to know the layer name.

    In my example, "_recLayer" would correspond to your actual layer name "padOverDev". "layer1(A)" would correspond to "padOverDev_top(pad)".


    Best regards
    Quek

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.