Assura LVS fail

Hi Stefano

Assura LVS is failing due to unbound devices. You can force LVS to continue uses the following cmd so that you can debug the results:

a. In LVS form, press "avCompareRules" button
b. Select "abortOnUnboundDevices" cmd
c. Enable "Use in Run" optoin
d. Disable "Abort on unbound devices" option
e. Press ok on the form

Best regards
Quek

I read the log file that you provided. It seems that the schematic you are using is not properly matched with the layout, that's why it is saying that the devices on schematic are not matched with the devices on layout and vice versa.

I recommend you to use the following procedure:

Option 1:

Open your schematic, select Launch --> Layout XL --> press OK.

In the new layout window select

1. Connectivity --> Generate --> All from soruce

2. Connectivity --> Nets --> Show/Hide selected incomplete nets

Now make your layout and run the LVS

Option 2:

If you already did this please check following points in the Run LVS window:

1. In the Schematic Design source section- "Library" should contain the name of the library in which your schematic is located

"Cell" Should have the name of the cell (Schematic) in which you have designed the schematic.

"View" Should have the text "Schematic"

2. In the Layout Design source section- "Library" should contain the name of the library where the layout is located

"Cell" Should contain the name of the cell (Layout) in which you have designed your layout.

"View" Should have the text "Layout".

This should solve your problem.

Note: Before running LVS make sure that the options "Technology" should contain the same technology that u have used to design the schematic and the Extracted rule and Design rules have the correct destinations for the LVS to run properly.

Hi

Quek Thanks for the reply, I've tryed to do how you said, but Assura still failed. The problem is that I'm sure about the layout. I have already done the LVS of the same layout on a different PC and it was correct. When Assura LVS fails, it open some windows for the debug of the layout, in my case anything happens. I begin to think that the problem is the installation of the tecnology file. In the log file there is something like this :

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'pnp_s_mis(BJT)' is not found. This binding will be skipped.

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'ndio(DIO)' is not found. This binding will be skipped.

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'ndio_18(DIO)' is not found. This binding will be skipped.

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'ndio_25(DIO)' is not found. This binding will be skipped.

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'ndio_25od33(DIO)' is not found. This binding will be skipped.

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'ndio_25ud18(DIO)' is not found. This binding will be skipped.

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'ndio_33(DIO)' is not found. This binding will be skipped.

WARNING (AVLVSNN-10040) : bindingFile/bind rule - schematic cell 'ndio_esd(DIO)' is not found. This binding will be skipped. 

Could it be the problem ?

Hi Stefano

Would you please try the following?

a. Execute the following in terminal window:
terminal>setenv CDS_Netlisting_Mode Analog

b. Restart Virtuoso
c. Re-run Assura LVS

The above should get rid of the following errors:

Error - Can not evaluate parameter 'm' on inst 'M46' in cell 'FF_DICE schematic DICE_LIB'
*ERROR* Unknown Expression Parser Error Type!

Best regards
Quek

Hi Quek

It works, thanks a lot. What is  CDS_Netlisting_Mode ? Where can I find some information ?

 Best regards

Stefano 

Hi Stefano

There are netlisting modes in Virtuoso, digital and analog. The default mode is digital.The mode that most of us needs is analog. During analog mode, the netlister gets info from CDF (Component Description Section) of the devices. During digital mode, the netlister gets info from the NLP expressions which have been set on the device cellviews.


Best regards
Quek