Placement

4) Placement:

There are two types in placement 
1) congestion driven and 2)timing driven
1   
    1)congestion driven : the congestion driven placement places the cells freely by Placing  the nets far away .so that the  congestion will be  reduced.
     
    2)Timing driven :The timing driven reduces the net length try to place the cells nearer ,so by placing the cells near by ,due to density the congestion may increase .

We will be adding global nets(tie hi and tie lo) to avoid the floating pins .

Fence, Guide and Region are the techniques to reduce the congestion of cells .


Optimization is done for drv.

Comments

Post a Comment

Popular posts from this blog

Sanity checks

Physical Design 1. Sanity Checks : The inputs to the Physical design are checked here for {The Sanity Checks to be done before floorplan like  Check Netlist for verifying the floating pins ,multidriven nets,tri state buffers,total std cells area,floating nets, fanout nets, ReportConstarints -verbose checks for Max transition,max fanout,max capacitance,setup, checkDesign -timing library in this total cells used ,missing timing for cells,don'tuse cells checkDesign -physical library in this we check for cells pins missing lef,cells missing geometry ,cells pins missing dimension, }}}} a) CheckNetlist: floating input, multidriven nets, black box, undriven Io’s, floating outputs, combinational loops b) Check Timing checks like No_ideal_waveform, no drive, unconstraint_endpooints, no_input_drive. Checks for timing cells are also present in the physical lib. c) CheckDesign –all: timing and netlist checks, and also check for tie hi and ...
Read more

Floorplan Guidelines

2. Floorplan There will be certain guidelines to follow ,to get a good floorplan without congestion and timing issues later in the design a)place the macros at core area b)place the io’s to core area c)use fly lines or flight lines d)if macros to io connections are there ,then place the macro near the io ports e)macros to macros connections ,place near by f) avoid criss cross placement g) place the macros with minimum spacing between macros h) add blockages where to avoid the congestion i) add halos to to every macros ,to avoid cells placing near by(congestion) j) avoid placing macros in the middle(routing issues or ir drop may occur (buffers)due to blockages of macros) k) don’t place the macros at the Io’s ,which may block them l) place macros the macros by allowing some place to the io ‘s routing. m) avoid notches n) place with hierarchical analysis o) provide uniform std cell area. p) add preplace cells(end cap cells ,tap cells,decap cells) ...
Read more

Checks done Before CTS

The checks to be done after placement 1)report_constraint -hotspot This command shows the top 5 highlighted area which are congested with representing the vertical and horizontal congestion.(local congestion) eg : V(31/28)  indicates three more vertical tracks are required in that area . 2)report_constraint -overflow This command indicates the total tracks vertical and  horizontal overflow e.g -1    0   0.00%   2 0.00% which indicates two tracks are less than the required 3)WNS,TNS 4)SLACK :If the slack is below - 200 ps ,The design can be routable ,make sure that the design is having less -ve slack. 5)Density : try to maintain at 75%(after placement) 6)max_transition : This can be reduced by adding clk_buffers  . max_capacitance : This can be balanced by using up-sizing of cells max_fanout :by doing clonning we can divide the fanout ,and can reduce the load. 7)checkPlace : this will do placement legalization of cells...
Read more