Layout Blog: Standard Cells

Multiple Architectures

Standard-cell library offers multiple architecture for best optimisation in performance, power, and area requirements of Digital designs. High Performance Architecture, a High-Density Architecture for varied customer application requirements. In each requirement (power/performance/area), layout approaches will be different to meet the design specifications. Here, we will covering in more common guidelines.

Standard Cell Templates:

Based on specified architecture e.g. 9T, 12T etc. Here, layer specification pre specified and need to calculate height using given data, for reference please check on below link:

Standard Cell Library – SignOff Semiconductors

Custom Architecture based on Area, Power and Performance.

These are the factors which needs to be considered while calculating standard cell height

E.g. let say for metal 1 layer minimum width is 10 units than we need to keep 5 unit space from the PR boundary, So that when that logic cell abut with another logic cell not get any DRC violation. 

Requirements for Standard Cell Calculation

Let the width is A=100 units for PMOS and NMOS

Let the distance is B=40 units

Let the poly extension is C= 10 units 

Let half DRC distance is D= 5 units

Also, other criterion to decide based on number of tracks, so the height of standard cell is to be multiple of metal pitch. (Here metal referred to be used at next level for the connections between standard cells pins)

Placement of transistors, digital Block

How to plan power signal and track width 

Checkout these below blog links to explore more insights on Standard Cells

Disclaimer:

The purpose of this blog is to spread knowledge and facilitate open discussions. The content shared is based on our research from diverse sources including the internet, books, and conversations with others. We strive for accuracy; however, we acknowledge the possibility of errors or omissions. We value your input and encourage you to share your comments, questions, and suggestions. We are open to clarifying or correcting any inaccuracies found within the blog. 

Please note that while we appreciate your contributions, we may not be able to implement all suggestions. The blog should not be considered a substitute for professional advice.