[vc_row][vc_column][vc_column_text]

SignOff checks

 

Author : Aglow A George, Physical Design Engineer, SignOff Semiconductors

Author: Batchu Sri Sai Chaitanya, Physical Design Engineer, Signoff Semiconductors

Author: Ashish Kumar Sharma, Physical Design Engineer, Signoff Semiconductors[/vc_column_text][vc_column_text]

Design Rule Check (DRC)

Design Rule Check (DRC) determines whether the layout of a chip satisfies a series of recommended parameters called design rules. Design rules are set of parameters provided by semiconductor manufacturers to the designers, in order to verify the correctness of a mask set. It varies based on semiconductor manufacturing process. These rule set describes certain restrictions in geometry and connectivity to ensure that the design has sufficient margin to take care of any variability in manufacturing process.

Design rule checks are nothing but physical checks of metal width, pitch and spacing requirement for the different layers with respect to different manufacturing process. If we give physical connection to the components without considering the DRC rules, then it will lead to failure of functionality of chip, so all DRC violations has to be cleaned up.

After the completion of physical connection, we check each and every polygon in the design, based on the design rules and reports all the violations. This whole process is called Design Rule Check.

[/vc_column_text][vc_column_text]

Typical DRC rules are:

  1. Interior
  2. Exterior
  3. Enclosure
  4. Extension

[/vc_column_text][vc_column_text]

Interior:

Fig1: Distance of interior facing edge for a single layer.

Fig2: Distance of interior facing edge of two layer.

[/vc_column_text][vc_column_text]

Exterior:

Fig3: Distance of exterior facing edge of two layer

[/vc_column_text][vc_column_text]

Enclosure:

Fig4: Distance between inside edge to outside edge.

[/vc_column_text][vc_column_text]

Extension:

Fig4: Distance between inside edge to outside edge.

To understand the basic design rules, let’s take CMOS inverter as an examples:

Fig5: CMOS Inverter layout

[/vc_column_text][vc_column_text]

Layout versus Schematic (LVS)

DRC only verifies that the given layout satisfies the design rules provided by the fabrication unit. It does not ensure the functionality of layout. Because of this, idea of LVS is orginated. This blog focuses on how LVS works and what all are the common issues faced in LVS.[/vc_column_text][vc_column_text]

How LVS works

Inputs needed to perform LVS are:

[/vc_column_text][vc_column_text]

.v and GDS should be of same stage.

LVS rule deck is a set of code written in Standard Verification Rule Format (SVRF) or TCL Verification Format (TVF). It guides the tool to extract the devices and the connectivity of IC’s. It contains the layer definition to identify the layers used in layout file and to match it with the location of layer in GDS. It also contains device structure definitions.[/vc_column_text][vc_column_text]

LVS check involves three steps:

  1. Extraction: The tool takes GDSII file containing all the layers and uses polygon based approach to determine the components like transistors, diodes, capacitors and resistors and also connectivity information between devices presented in the layout by their layers of construction. All the device layers, terminals of the devices, size of devices, nets, vias and the locations of pins are defined and given an unique identification.
  2. Reduction: All the defined information is extracted in the form of netlist.
  3. Comparison: The extracted layout netlist is then compared to the netlist of the same stage using the LVS rule deck. In this stage the number of instances, nets and ports are compared. All the mismatches such as shorts and opens, pin mismatch etc.. are reported. The tools also checks topology and size mismatch.

Fig6: LVS Flow

[/vc_column_text][vc_column_text]

Commonly faced LVS issues:

LVS check includes following comparisons:

Typical errors which can occur during LVS checks are:

  1. Shorts: Shorts are formed, if two or more wires which should not be connected together are connected.
  2. Opens: Opens are formed, if the wires or components which should be connected together are left floating or partially connected.
  3. Component mismatch: Component mismatch can happen, if components of different types are used (e.g, LVT cells instead of HVT cells).
  4. Missing components: Component missing can happen, if an expected component is left out from the layout.
  5. Parameter mismatch: All components has it’s own properties, LVS tool is configured to compare these properties with some tolerance. If this tolerance is not met, then it will give parameter mismatch.

[/vc_column_text][vc_column_text]

IR Drop Analysis:

IR Drop can be defined as the voltage drop in metal wires constituting power grids before it reaches the vdd pins of the cells. IR drop occurs when there are cells with high current requirement or high switching regions. IR drop causes voltage drop which in-turn causes the delaying of the cells causing setup and hold violations. Hold violations cannot be fixed once the chip is fabricated.

There are two types of IR drop analysis namely:

Static IR drop analysis:

Dynamic IR drop analysis:

[/vc_column_text][vc_column_text]

Methods to reduce IR drop:

Fig7: Custom power rail added to make it robust

Note:

[/vc_column_text][vc_column_text]

ELECTRO MIGRATION (EM):

Electro migration (EM) refers to the unwanted movement of materials in a semiconductor. If the current density is high enough, there can be a momentum transfer from moving electrons to the metal ions making the ions to drift in the direction of the electron flow. This results in the gradual displacement of metal atoms in a semiconductor, potentially causing open and short circuits. Due to high current density and resistance of metal in the recent technologies EM has become dominating.

[/vc_column_text][vc_column_text]

Methods to fix EM

  1. Widen the wire to reduce current density
  2. Keep the wire length short
  3. Reduce buffer size in clock line

Not in PD point of view

  1. Reduce the frequency
  2. Lower the supply voltage

[/vc_column_text][vc_column_text]

SCAN Tracing:

Files (Scan DEF and .V)

In scan tracing we are checking the connection of flip flops, there should not be any floating connections. The reason why we are doing scan tracing is because, in formality check we disable the Scan(so it doesn’t check the scan chain), and we are assuring that there is no issue with scan chains.[/vc_column_text][vc_column_text]

DFM:

Files (GDS and Rule deck file)

As the technology scales down, manufacturing process is becoming more complex. DFM (design for manufacturing) is the stage in which we modify or add extra things (like redundant via insertion, wire spreading). These techniques will increase the yield and reliability in the design.

Few DFM steps:

  1.  Redundant Via insertion.
  2. Wire spreading.
  3. Wire slotting.
  4. Metal filling.

[/vc_column_text][vc_column_text]

Formality Check:

Files (Reference netlist, Implemented Netlist, .V and .Lib)

The basic idea behind FM check is to compare implemented netlist with reference netlist (Synthesis stage netlist / golden netlist). We check whether the logic output value given in both stages are same.

Example 1: If we check the FM in the Scan mode (i.e, in ON state) we will get the formality issues, because during the scan chain reordering the position of Flip Flops will be changed with respect to SCAN def file. To overcome this issue, we have to disable the scan port (by assigning it’s value to “0”).

Example 2: Undriven port Issue: In golden netlist for the floating pins binary values are assigned like “0” or ”1”, but when it gets implemented floating pin is assigned as “X ” which leads to mismatch. To resolve this issue, we set both pins in implemented and reference netlist either “0” or “1”.

[/vc_column_text][vc_column_text]

Power Analysis:

Files (SPEF, SAIF,.V, Lib, UPF and SDF)

In Power analysis we calculate the power dissipation. Two types of power dissipation, (i) Leakage Power (ii) Dynamic power. Leakage power is basically static power which is dissipate during the Off state or non-toggling (when the input data is fixed) state of device, and for the dynamic power the activity factor is required, which is present in the SAIF (switching activity interchange format) file. We also check for hot spot in the design, the hot spot is basically the small region where the higher power dissipation is present.[/vc_column_text][/vc_column][/vc_row]