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.

layout versus schematic verification

Status
Not open for further replies.

atlaakreddy

Junior Member level 2
Joined
Mar 27, 2017
Messages
23
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
155
what is the difference between the spice netlist,lvs.v,schematic netlist?please expalin withe detail?

what is the formate of spicenetlist, normal netlist, schematicnetlist, lvs.v?
 
Last edited:

what is the difference between the spice netlist,lvs.v,schematic netlist?please expalin withe detail?

what is the formate of spicenetlist, normal netlist, schematicnetlist, lvs.v?


LVS means layout versus schematic. there are many ways to represent schematic in different tools and in different formats. unless you can clarify your question, there is nothing more to be said.

whatever these terms are, they are not standard. I don't know what YOUR lvs.v file is.
 

give one example of schematic netlist and normal netlist
 

give one example of schematic netlist and normal netlist

I can't. I have no idea what you are calling a schematic netlist and a normal netlist because those terms make no sense.
 

As a simple example:
1. after place'n'route you have gate-level netlist (.v verilog), which contains std. cells and wires between them).
2. also, you should have spice (transistor-level) netlist (.sp, .cdl or other extensions), which contains transistors and wires for each of you std. cells.
3. you should convert gate-level netlist into spice-like netlist and merge it with std. cell transistor-netlist.
4. the LVS tool extracts transistor netlist from layout (GDSII) and writes it into spice-like netlist .
5. the LVS tool compares your merged tran-level netlist with extracted tran-level netlist.

The extensions of netlist files may vary and depend on LVS tools.
 

As a simple example:
1. after place'n'route you have gate-level netlist (.v verilog), which contains std. cells and wires between them).
2. also, you should have spice (transistor-level) netlist (.sp, .cdl or other extensions), which contains transistors and wires for each of you std. cells.
3. you should convert gate-level netlist into spice-like netlist and merge it with std. cell transistor-netlist.
4. the LVS tool extracts transistor netlist from layout (GDSII) and writes it into spice-like netlist .
5. the LVS tool compares your merged tran-level netlist with extracted tran-level netlist.

The extensions of netlist files may vary and depend on LVS tools.

you can make LVS pass using gate-level netlist, no need to do spice vs spice

- - - Updated - - -

normal netlist means .v

no it does not. I believe you are referring to a gate-level netlist.
 

you can make LVS pass using gate-level netlist, no need to do spice vs spice

Only in case the hirearchy fully match in schematic and layout. Still, standard signoff (foundry recommended) LVS is transistor-level comparison.
 

Only in case the hirearchy fully match in schematic and layout. Still, standard signoff (foundry recommended) LVS is transistor-level comparison.

Hierarchy is usually not an issue. And spice vs spice is not needed. You can do verilog vs spice.
 

You can do verilog vs spice.
In such case - yes, you can. But, tool still converts verilog into spice-like transistor netlist. Transistor-level is the must for signoff LVS.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top