Lecture 5 Design Representation

22
ETU 08108:Introduction to VLSI Design Representation

Transcript of Lecture 5 Design Representation

Page 1: Lecture 5 Design Representation

ETU 08108:Introduction to VLSI

Design Representation

Page 2: Lecture 5 Design Representation

Overview of lecture• What is design• Managing complexity• Abstraction• Hierarchical approach to design

Page 3: Lecture 5 Design Representation

What is design?• The design process involves taking an

idea and implementing it in some manner.– We can think of design as a top down

refinement of a specification.– Design is a complex process and can be a bit

of an art.• Design is a continual refinement in the

representation of something.

Page 4: Lecture 5 Design Representation

Implementation choices

Page 5: Lecture 5 Design Representation

Design constraints

Page 6: Lecture 5 Design Representation

Managing complexity• The design complexity of logic devices

increases almost exponentially with the number of transistors to be integrated - translates to an increase in design time.

• How do we manage complex designs?– Using suitable design methodologies– Abstraction– Using EDA tools

Page 7: Lecture 5 Design Representation

Top down approach to design

Page 8: Lecture 5 Design Representation

Domains and levels of abstraction - example

For example, a half adder

Page 9: Lecture 5 Design Representation

Hierarchical approach to design

• Divide and conquer approach• Split the design into smaller more manageable chunks• Can be applied at different levels of abstraction

Page 10: Lecture 5 Design Representation

General Design Process

Page 11: Lecture 5 Design Representation

How to put together millions of transistors and make it work ?

• Well chosen design methodologies• Well chosen architectures• Extensive use of powerful EDA tools• Strict design management• Well chosen testing methodologies• Design re-use.

Page 12: Lecture 5 Design Representation

Specification• A specification of what to construct is the first major step.• Compromise between what is wanted and what can be

made– Requires extensive experience to define best compromise

• A detailed specification must be agreed upon with the system people. Major changes during design will result in significant delays.

• Requirements must be considered at many levelsSystem, sub-system, Board, Hybrid, IC

• Specifications can (must) be verified by system simulations.

• Specification is 1/4 - 1/3 of total IC project !

Page 13: Lecture 5 Design Representation

Bottom - up• Build gates in given technology• Build basic units using gates• Build generic modules of use• Put modules together• Hope that you arrived at some reasonable

architecture• Gate level simulation toolsOld fashioned design methodology a la discrete logic

Comment by one of the main designers of a Pentium processor

The design was made in a typical top - down, bottom - up, inside - out design methodology

Page 14: Lecture 5 Design Representation

Schematic based• Symbol of module defines interface• Schematic of module defines function• Top - down: Make first symbol and then schematic• Bottom - up: Make first Schematic and then symbol

Symbol

Schematic

Basic gate Logic module

Long and tedious

Page 15: Lecture 5 Design Representation

Getting it right - Simulation• Simulate the design at all levels (transistor, gate, system)• Analog simulator (SPICE) for transistor level• Digital gate level simulator for gate based design• Mixed mode simulation of mixed analog-digital design• Behavioural simulation at system/module level (Verilog, VHDL)• All functions must be simulated and verified.• Worst case data must be used to verify timing• Worst - Typical - Best case conditions must be verified

Process variations, Temperature range, Power supply voltageFactor two variation to both sides ( speed: ½ : 1 : 2)

• Use programming approach to verify large set of functions(not looking at waveform displays)

Page 16: Lecture 5 Design Representation

Low power design• Low power design gets increasingly important:

Gate count increasing > increasing power.Clock frequency increasing > increasing power.Packaging problems for high power devices.Portable equipment working on battery.

• Where does power go:1: Charging and dis-charging of capacitance: Switching nodes2: Short circuit current: Both N and P MOS conducting during transition3: Leakage currents: MOS transistors (switch) does not turn completely off

• The power density of modern ICs are at the same level as the hot plate on your stove and is approaching the power density seen in a nuclear reactor !

Vdd

Gnd

P = Nswitch* f * C * Vdd2 2 + N + Nswitch switch * f * E* f * Eshortshort + N *I + N *I lea klea k* V* Vdddd

C

K*Vdd2

Page 17: Lecture 5 Design Representation

Power in a CMOS GateVVDDDD

iiDDDD(t)(t)

GroundGround

Page 18: Lecture 5 Design Representation

Power Dissipation in CMOS Logic (0.25µ)

%75 %5%20

Ptotal (0→1) = CL VDD2 + tscVDD Ipeak + VDDIleakage

CL

Page 19: Lecture 5 Design Representation

Components of Power• Dynamic

– Signal transitions• Logic activity• Glitches

– Short-circuit• Static

– Leakage

Page 20: Lecture 5 Design Representation

Decrease power• Lower Vdd:

5v > 2.5v gives a factor 4 !New technologies use lower Vdd

because of risk of gate-oxide break-down and hot electron effect.

• Lower Vdd and duplicate hardware

• Lower number of switching nodes The clock signal often consumes 50% of total power

Functionalunit

One functional unit:frequency = 1Vdd = 1

Functionalunit 1

Two functional units:frequency = 1/2Vdd = 1/2 (optimistic)

Functionalunit 2

P= 1 * 12 = 1P = 2 * 1/2 * (1/2)2 = 1/4

Clock

Unit 1

Ena

Unit 2

Ena

Unit 3

Ena

Clock gating

Page 21: Lecture 5 Design Representation

Design partitioning• Good partitioning in the design provides several

advantages including:– Easy handling of design requires sensible hierarchy– Several designers/locations– Easier to keep version control– Design management is easier

• Better synthesis results– Synthesis tools work better if design is partitioned well

• Reusability– Verification is easier to do if partitioning is correct– Verification/Synthesis/Layout all has an effect on

partitioning

Page 22: Lecture 5 Design Representation

Design partitioning• Locate related combinational logic in a single module

and single process if possible.• The synthesis tool has more flexibility in optimising a

design when related combinational logic is located in the same module. This is because synthesis tools cannot move logic across hierarchical boundaries during compile operation.