Calibre PEX Extraction issue

Discussion created by mugofgold on Nov 28, 2012
Latest reply on Dec 13, 2012 by mugofgold

Like • Show 0 Likes0
Comment • 6

Hi All,

I have had no problems with the DRC and LVS. But when I run PEX, the extraction starts and ends with the following error without producing any output netlist.

********************************************************************************************************************************

XDB created with: Calibre v2012.2_17.11 Thu May 10 12:53:19 PDT 2012

WARNING: XDB Database not available: No comparison was made.

Unable to restore XDB database.

ERROR: Error:: restore of XDB failed

--- CREATING XREF INFORMATION FROM XDB DATABASE

ERROR: Unable to read layout to source cross reference information.

========================================================================

CALIBRE xRC WARNING / ERROR Summary

------------------------------------------------------------------------

xRC Warnings = 0

xRC Errors = 2

========================================================================

--- CALIBRE xRC::FORMATTER COMPLETED - Tue Nov 27 18:37:09 2012

--- TOTAL CPU TIME = 0 REAL TIME = 0 LVHEAP = 166/167/231 MALLOC = 245/245/245 ELAPSED TIME = 8

*** Calibre finished with Exit Code: 4 ***

********************************************************************************************************************************

We have recently moved to v2012.2_17.11 version of Calibre.

Anyone has experienced this problem before?

Thanks,

Outcomes

samantha_lizak Dec 3, 2012 8:36 AM

Hi N-

What does your Mask SVDB Directory statement look like? The XDB information is only generated if you have certain options set. It is not generated by default by LVS.

Best-

Sam.

Actions

mugofgold @ samantha_lizak on Dec 3, 2012 8:26 PM

Hi Sam,

It looks like:

MASK SVDB DIRECTORY "svdb" QUERY XRC CCI IXF NXF SLPH

We have recently moved to 6LM metal option from the original 4LM option. I was able run the PEX in 4LM but not in 6LM.

Any explanation for this?

Thanks,

Actions

Joel @ mugofgold on Dec 4, 2012 10:07 AM

Hello N,

I recommend that your first perform a /bin/rm -rf svdb in the working directory.

Then, make sure your LVS is "CORRECT" and there are no Errors in the PDB step and review all Warnings.

By following these steps, you will ensure that the possibility of corrupting the database is low.

If you still have the Error, I would then recommend the latest release followed by a Service Request on SupportNet.

Thank you.
Joel

Actions

mugofgold @ Joel on Dec 4, 2012 3:59 PM

Here are my settings in PEX:

************************************************************************************

// Rule file generated on Tue Dec 04 15:49:25 PST 2012

// by Calibre Interactive - PEX (v2012.2_17.11)

// *** PLEASE DO NOT MODIFY THIS FILE ***

LAYOUT PATH "file_name.calibre.db"

LAYOUT PRIMARY "file_name"

LAYOUT SYSTEM GDSII

SOURCE PATH "./CalibrePEX/file_name.src.net"

SOURCE PRIMARY "file_name"

SOURCE SYSTEM SPICE

MASK SVDB DIRECTORY "svdb" QUERY XRC CCI IXF NXF SLPH

LVS REPORT "file_name.lvs.report"

PEX NETLIST "file_name.pex.netlist" CALIBREVIEW 1 SOURCENAMES LOCATION

PEX REPORT "file_name.pex.report" SOURCENAMES

PEX REDUCE ANALOG NO

PEX NETLIST UPPERCASE KEYWORDS NO

PEX NETLIST VIRTUAL CONNECT NO

PEX NETLIST NOXREF NET NAMES YES

PEX NETLIST MUTUAL RESISTANCE YES

LVS REPORT OPTION S

LVS FILTER UNUSED OPTION NONE SOURCE

LVS FILTER UNUSED OPTION NONE LAYOUT

LVS RECOGNIZE GATES ALL

VIRTUAL CONNECT COLON YES

VIRTUAL CONNECT REPORT NO

DRC ICSTATION YES

SOURCE CASE YES

LVS FILTER PRCUT OPEN

LVS FILTER R (SH) SHORT

LVS FILTER C (CP) OPEN

************************************************************************************

Actions

Joel @ mugofgold on Dec 5, 2012 6:44 AM

Hi,

This looks like the top level rule file.

The changes I recommend are on the command line execution or Calibre xRC.

If you are using Calibre Interactive from the command line, use the following shell statements(be sure that LVS is correct);

/bin/rm -rf svdb

calibre -gui -pex

If you are running Calibre xRC by command line, use the following shell statements;

/bin/rm -rf svdb

calibre -lvs <options> rule_file >& lvs.log

echo "Verify LVS is CORRECT before continuing"

calibre -pdb <options> rule_file >& pdb.log

echo "Verify Errors and Warnings in pdb.log before continuing"

calibre -fmt <options> rule_file >& fmt.log

echo "Verify Errors and Warnings in fmt.log

There are other ways of running the tools which are documented in the Calibre xRC User's Manual.

Thank you.
joel

Actions

mugofgold @ Joel on Dec 13, 2012 12:19 PM

Hi Joel,

I was finally able to complete the PEX run by including "LVS INJECT LOGIC YES" in PEX options.

Now I do not get the XDB issue any more but the LVS didn't pass this time and giving me these errors:

****************************************************

Error: Different numbers of ports.

Error: Different numbers of nets.

Error: Different numbers of instances.

Error: Connectivity errors.

Warning: Ambiguity points were found and resolved arbitrarily.

****************************************************

Any suggestions?

Thanks,

Actions

6 Replies

samantha_lizak Dec 3, 2012 8:36 AM
Hi N-

What does your Mask SVDB Directory statement look like? The XDB information is only generated if you have certain options set. It is not generated by default by LVS.

Best-

Sam.
Like • Show 0 Likes0
Actions
mugofgold @ samantha_lizak on Dec 3, 2012 8:26 PM
Hi Sam,

It looks like:
MASK SVDB DIRECTORY "svdb" QUERY XRC CCI IXF NXF SLPH

We have recently moved to 6LM metal option from the original 4LM option. I was able run the PEX in 4LM but not in 6LM.

Any explanation for this?

Thanks,
N
Like • Show 0 Likes0
Actions
Joel @ mugofgold on Dec 4, 2012 10:07 AM
Hello N,

I recommend that your first perform a /bin/rm -rf svdb in the working directory.

Then, make sure your LVS is "CORRECT" and there are no Errors in the PDB step and review all Warnings.

By following these steps, you will ensure that the possibility of corrupting the database is low.

If you still have the Error, I would then recommend the latest release followed by a Service Request on SupportNet.

Thank you.
Joel
Like • Show 0 Likes0
Actions
mugofgold @ Joel on Dec 4, 2012 3:59 PM
Here are my settings in PEX:

************************************************************************************
// Rule file generated on Tue Dec 04 15:49:25 PST 2012
// by Calibre Interactive - PEX (v2012.2_17.11)
//
// *** PLEASE DO NOT MODIFY THIS FILE ***
//
//
LAYOUT PATH "file_name.calibre.db"
LAYOUT PRIMARY "file_name"
LAYOUT SYSTEM GDSII
SOURCE PATH "./CalibrePEX/file_name.src.net"
SOURCE PRIMARY "file_name"
SOURCE SYSTEM SPICE
MASK SVDB DIRECTORY "svdb" QUERY XRC CCI IXF NXF SLPH
LVS REPORT "file_name.lvs.report"
PEX NETLIST "file_name.pex.netlist" CALIBREVIEW 1 SOURCENAMES LOCATION
PEX REPORT "file_name.pex.report" SOURCENAMES
PEX REDUCE ANALOG NO
PEX NETLIST UPPERCASE KEYWORDS NO
PEX NETLIST VIRTUAL CONNECT NO
PEX NETLIST NOXREF NET NAMES YES
PEX NETLIST MUTUAL RESISTANCE YES
LVS REPORT OPTION S
LVS FILTER UNUSED OPTION NONE SOURCE
LVS FILTER UNUSED OPTION NONE LAYOUT
LVS RECOGNIZE GATES ALL
VIRTUAL CONNECT COLON YES
VIRTUAL CONNECT REPORT NO
DRC ICSTATION YES

SOURCE CASE YES
LVS FILTER PRCUT OPEN
LVS FILTER R (SH) SHORT
LVS FILTER C (CP) OPEN
************************************************************************************
Like • Show 0 Likes0
Actions
Joel @ mugofgold on Dec 5, 2012 6:44 AM
Hi,

This looks like the top level rule file.

The changes I recommend are on the command line execution or Calibre xRC.

If you are using Calibre Interactive from the command line, use the following shell statements(be sure that LVS is correct);

/bin/rm -rf svdb
calibre -gui -pex

If you are running Calibre xRC by command line, use the following shell statements;

/bin/rm -rf svdb
calibre -lvs <options> rule_file >& lvs.log
echo "Verify LVS is CORRECT before continuing"
calibre -pdb <options> rule_file >& pdb.log
echo "Verify Errors and Warnings in pdb.log before continuing"
calibre -fmt <options> rule_file >& fmt.log
echo "Verify Errors and Warnings in fmt.log

There are other ways of running the tools which are documented in the Calibre xRC User's Manual.

Thank you.
joel
Like • Show 0 Likes0
Actions
mugofgold @ Joel on Dec 13, 2012 12:19 PM
Hi Joel,

I was finally able to complete the PEX run by including "LVS INJECT LOGIC YES" in PEX options.

Now I do not get the XDB issue any more but the LVS didn't pass this time and giving me these errors:
****************************************************
Error:    Different numbers of ports.
Error:    Different numbers of nets.
Error:    Different numbers of instances.
Error:    Connectivity errors.
Warning: Ambiguity points were found and resolved arbitrarily.
****************************************************
Any suggestions?

Thanks,
N
Like • Show 0 Likes0
Actions

Calibre PEX Extraction issue

Outcomes

Related Content

Recommended Content