Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Cailbre PEX error with UMC65nm

Status
Not open for further replies.

nisha gupta

Member level 4
Joined
May 22, 2012
Messages
71
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Location
Hyderabad, Andhra Pradesh, India
Activity points
1,755
I am encountering the following error when I run extraction using Calibre v2011.4_14.13.

Error while compiling rules file /Application/Cadence/CadencePDK/UMC65LLRF1P8M1T0F1U/RuleDecks/Calibre/G-DF-LOGIC/G-DF-LOGIC_MIXED_MODE65N-LL_LOW_K_CALIBRE-LVS-1.7-P1.txt:
Error PEX5 on line 2302 of $PDK_BASE_DIR/RuleDecks/Calibre/G-DF-LOGIC-LOW-K-XRC/Cmax/G-DF-LOGIC_MIXED_MODE65N_1P9M1T1F1U_LL_LOW_K_TOP_METAL32.5K-XRC-LPE-Cmax_1.0_P1.tec - capacitance or resistance extraction layer not properly configured in CONNECT operation: ME9_C.


line 2302 is
CAPACITANCE NEARBODY VIA2VIA ME9_C AL_RDL_C ME9_C AL_RDL_C MASK
[
PROPERTY C
max_caldistance = 8 // For reference
profile = field_profileid
max_distance = 8
C = length() * (0.0054892 * exp(-1.70187 * distance()) + 0.00548924 * exp(-1.71482 * distance()))
]


kindly help me
 

Hi Nisha-

That error message actually points to the CONNECT statement -- it is saying that layer ME9_C is not "properly configured" there. That could mean the layer is not included in any CONNECT statement (be sure to also check the LAYER MAP, PEX MAP, and PEX ALIAS statements to see if ME9_C is part of a group with another name that is in a CONNECT statement), or that ME9C doesn't actually connect to any of the other layers after it, and thus according to the rules doesn't have vias.

Buried deep in the message is "Error PEX5". You can find an explanation in the SVRF manual that gives more details on exactly how that CONNECT statement might be improperly configured.

If you believe the layer is properly mapped in the connectivity, try contacting the PDK provider. With the 2011 version, chances are that if they made a mistake in their rules you are not the first to encounter it.

Hope that helps-

Sam.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top