Tuesday 20 September 2022

Why NAND structures are preferred over NOR ones?


Both NAND and NOR are classified as universal gates, but we see that NAND is preferred over NOR in CMOS logic structures. Let us discuss why it is so:


We know that when output is at logic 1, pull up structure for the output stage is on and it provides a path from VDD to output. Similarly, pull down structure provides a path from GND to output when output is logic 0. Pull up and pull down resistances are one of major factor in determining the speed of cell. The inverse of pull up and pull down resistances are called output high drive and output low drive of the cell respectively. In general, cells are designed to have similar drive strength of pull up and pull down structures to have comparable rise and fall time.



NMOS has half the resistance of an equal sized PMOS. let us say resistance of a given sized NMOS is R then resistance of PMOS of same size will be 2R. In NAND gate, two NMOS are connected in series and two PMOS are connected in parallel. So, pull up and pull down resistances will be:

Pull up resistance = 2R || 2R = R
Pull down resistance = R + R = 2R



On the other hand, in a NOR gate, two NMOS are connected in parallel and two PMOS are connected in series. The pull-up and pull-down resistances, now, will be:
Pull up resistance = 2R + 2R = 4R
Pull down resistance = R || R = R/2



NAND gate has better ratio of output high drive and output low drive as compared to NOR gate. Hence NAND gate is preferred over NOR.



To use NOR gate as universal gate either pull up or pull down structure has to be resized(decrease the length of PMOS cells or increase length of NMOS cells) to have similar resistance as resistance is directly proportional to length (length of channel here).

Sunday 11 September 2022

Context hier signoff

 Context: 

What is it?

Top-level context captures the actual timing information at the block boundary•

What does it contain?

  • Input/output boundary conditions
  • Non-SDC informationsuch as CRPR, AOCV, POCV, cross-block exceptions, SI and noise information, MIM pessimism reduction.
  • Support for bounded context for MIM instances•

  • PrimeTimecan generate context using characterize_context/write_contextset_hier_config/write_hier_data
  • There are 2 user interfaces to generate the context. 
    • One is with characterize_context/write_contextfor blocks in netlists. 
    • The other is set_hier_config/write_hier_datafor blocks in HyperScalemodels. 
    • The context generated from both UI contains the same content.



Ref: solvnet