Stats

Locked Locked
Replies 6
Subscribers 126
Views 17555
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

How to ignore FILL cells from Encounter in LVS Assura?

I have imported some design in Virtuoso Layout from Encounter, which has some FILL cells: FILL1, FILL2, NWSX. When I do LVS with Assura, I want those cells to be ignored. This is very small part of the bigger problem desribed in some another thread, but beacuse this issue is kind of specific just to Assura I would like to ask about it separately in this thread so that someone who knows issues with Assura can give me idea.

I am attaching the error log of LVS, and the snapshot of settings how I make Assura ignore those cells using ignoreCell command. The problem is that at the beginning of the log it actually says that its going to ignore those cells, which is fine, but then it again throws error at the end saying that FILL1,FILL2,NWSX are not defined. Why is it doing it? Am I doing something wrong?

Parents

Kabal over 11 years ago

Hi Andrew, thanks for reply.
Here are the things:
1) Those cells *ARE* in Verilog (or in physical Verilog produced by encounter after routing and FILLing is done)
2) Reason I decided to Ignore them is because the LVS was saying something like "FILL1,FILL2,NWSX" *not defined*
My problem starts from that bigger thread nearby, where Alex Soyer was trying to help me. I thought that I am almost done, and just that last step left with those cells, and all I need to do is to figure out the way to make LVS ignore them.
But again, bigger problem is:
I managed to get routing done properly in Encounter, I managed to get Layout import to Virtuoso Layout environment properly, I managed to get the clean DRC, but I *cannot manage* to get LVS working, because of reason stated above. which is what pushed me to start figuring out how to ignore those cells.
also: I do LVS over the Imported clean DRC'ed layout by checking against the Physical Verilog produced by encounter.
I am showing below the commands from Encounter which I used to generate physical verilog final7.v, which was used by LVS against the imported Layout. Maybe you can now get a better feeling of why it doesnt want to do LVS normally and throws those errors at me.
================================================
The following commands:
================================================
saveNetlist -excludeCellInst {FILL1 FILL2 NWSX} -includePowerGround final7.v
saveNetlist -excludeCellInst {FILL1 FILL2 NWSX} -phys final7.v
saveNetlist -includePhysicalInst -excludeCellInst {FILL1 FILL2 NWSX} -includePowerGround final7.v
saveNetlist -includePhysicalInst -includePowerGround -excludeCellInst {FILL1 FILL2 NWSX} final7.v

Result in following errors in Assura LVS log:
================================================
Preprocessing layout network phase 2
*ERROR* Device 'nfet(MOS)' on Layout is unbound to any Schematic device.
*ERROR* Device 'pfet(MOS)' on Layout is unbound to any Schematic device.
*ERROR* Device 'subc(RES)' on Layout is unbound to any Schematic device.
*ERROR* UnBound devices found.
Info: All devices must be bound or filtered for comparision to be run.
================================================
************************************************
================================================
The following commands:
================================================
saveNetlist -phys final7.v

Result in following errors in Assura LVS log:
================================================
Top cell 'refleks_switcher' specified, starting from specified point...
*ERROR* cell 'FILL1' is not defined.
*ERROR* cell 'NWSX' is not defined.
*ERROR* cell 'FILL2' is not defined.
================================================
************************************************
================================================
The following commands:
================================================
saveNetlist -phys -excludeLeafCell final7.v
saveNetlist -excludeLeafCell -includePhysicalInst -excludeCellInst {FILL1 FILL2 NWSX} final7.v

Result in following errors in Assura LVS log:
================================================
Top cell 'refleks_switcher' specified, starting from specified point...
*ERROR* cell 'DFF_E' is not defined.
*ERROR* cell 'NOR2_E' is not defined.
*ERROR* cell 'INVERTBAL_E' is not defined.
*ERROR* cell 'INVERTBAL_H' is not defined.
*ERROR* cell 'MUX21I_D' is not defined.
*ERROR* cell 'OA21_I' is not defined.
*ERROR* cell 'OAI21_C' is not defined.
*ERROR* cell 'AND4_E' is not defined.
*ERROR* cell 'AO22_B' is not defined.
*ERROR* cell 'OR4_E' is not defined.
*ERROR* cell 'AND2_F' is not defined.
*ERROR* cell 'NAND2_F' is not defined.
*ERROR* cell 'INVERT_I' is not defined.
*ERROR* cell 'NOR2_D' is not defined.
*ERROR* cell 'XOR2_C' is not defined.
*ERROR* cell 'INVERT_H' is not defined.
*ERROR* cell 'XNOR2_C' is not defined.
*ERROR* cell 'INVERT_E' is not defined.
*ERROR* cell 'OR2_I' is not defined.
*ERROR* cell 'AOI21_C' is not defined.
*ERROR* cell 'INVERT_F' is not defined.
*ERROR* cell 'FILL1' is not defined.
*ERROR* cell 'NWSX' is not defined.
*ERROR* cell 'FILL2' is not defined.
================================================
So the whole business here is to be able to figure out the right way to do LVS vs my Imported layout from Encounter. And again, the layout from encounter was imported perfectly, has no DRC errors and has all cells and connections in it, and is viewed just great in Virtuoso Layout view. I just cannot get the LVS to work.
Any ideas?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

Kabal over 11 years ago

Hi Andrew, thanks for reply.
Here are the things:
1) Those cells *ARE* in Verilog (or in physical Verilog produced by encounter after routing and FILLing is done)
2) Reason I decided to Ignore them is because the LVS was saying something like "FILL1,FILL2,NWSX" *not defined*
My problem starts from that bigger thread nearby, where Alex Soyer was trying to help me. I thought that I am almost done, and just that last step left with those cells, and all I need to do is to figure out the way to make LVS ignore them.
But again, bigger problem is:
I managed to get routing done properly in Encounter, I managed to get Layout import to Virtuoso Layout environment properly, I managed to get the clean DRC, but I *cannot manage* to get LVS working, because of reason stated above. which is what pushed me to start figuring out how to ignore those cells.
also: I do LVS over the Imported clean DRC'ed layout by checking against the Physical Verilog produced by encounter.
I am showing below the commands from Encounter which I used to generate physical verilog final7.v, which was used by LVS against the imported Layout. Maybe you can now get a better feeling of why it doesnt want to do LVS normally and throws those errors at me.
================================================
The following commands:
================================================
saveNetlist -excludeCellInst {FILL1 FILL2 NWSX} -includePowerGround final7.v
saveNetlist -excludeCellInst {FILL1 FILL2 NWSX} -phys final7.v
saveNetlist -includePhysicalInst -excludeCellInst {FILL1 FILL2 NWSX} -includePowerGround final7.v
saveNetlist -includePhysicalInst -includePowerGround -excludeCellInst {FILL1 FILL2 NWSX} final7.v

Result in following errors in Assura LVS log:
================================================
Preprocessing layout network phase 2
*ERROR* Device 'nfet(MOS)' on Layout is unbound to any Schematic device.
*ERROR* Device 'pfet(MOS)' on Layout is unbound to any Schematic device.
*ERROR* Device 'subc(RES)' on Layout is unbound to any Schematic device.
*ERROR* UnBound devices found.
Info: All devices must be bound or filtered for comparision to be run.
================================================
************************************************
================================================
The following commands:
================================================
saveNetlist -phys final7.v

Result in following errors in Assura LVS log:
================================================
Top cell 'refleks_switcher' specified, starting from specified point...
*ERROR* cell 'FILL1' is not defined.
*ERROR* cell 'NWSX' is not defined.
*ERROR* cell 'FILL2' is not defined.
================================================
************************************************
================================================
The following commands:
================================================
saveNetlist -phys -excludeLeafCell final7.v
saveNetlist -excludeLeafCell -includePhysicalInst -excludeCellInst {FILL1 FILL2 NWSX} final7.v

Result in following errors in Assura LVS log:
================================================
Top cell 'refleks_switcher' specified, starting from specified point...
*ERROR* cell 'DFF_E' is not defined.
*ERROR* cell 'NOR2_E' is not defined.
*ERROR* cell 'INVERTBAL_E' is not defined.
*ERROR* cell 'INVERTBAL_H' is not defined.
*ERROR* cell 'MUX21I_D' is not defined.
*ERROR* cell 'OA21_I' is not defined.
*ERROR* cell 'OAI21_C' is not defined.
*ERROR* cell 'AND4_E' is not defined.
*ERROR* cell 'AO22_B' is not defined.
*ERROR* cell 'OR4_E' is not defined.
*ERROR* cell 'AND2_F' is not defined.
*ERROR* cell 'NAND2_F' is not defined.
*ERROR* cell 'INVERT_I' is not defined.
*ERROR* cell 'NOR2_D' is not defined.
*ERROR* cell 'XOR2_C' is not defined.
*ERROR* cell 'INVERT_H' is not defined.
*ERROR* cell 'XNOR2_C' is not defined.
*ERROR* cell 'INVERT_E' is not defined.
*ERROR* cell 'OR2_I' is not defined.
*ERROR* cell 'AOI21_C' is not defined.
*ERROR* cell 'INVERT_F' is not defined.
*ERROR* cell 'FILL1' is not defined.
*ERROR* cell 'NWSX' is not defined.
*ERROR* cell 'FILL2' is not defined.
================================================
So the whole business here is to be able to figure out the right way to do LVS vs my Imported layout from Encounter. And again, the layout from encounter was imported perfectly, has no DRC errors and has all cells and connections in it, and is viewed just great in Virtuoso Layout view. I just cannot get the LVS to work.
Any ideas?
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

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.