design methodology. design methodology specification trade-off’s design domains - abstraction...
TRANSCRIPT
![Page 1: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/1.jpg)
Design methodology
![Page 2: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/2.jpg)
Design Methodology
• Specification• Trade-off’s• Design domains - abstraction level• Top-down - Bottom up• Schematic based• Synthesis based• Getting it right - Simulation• Lower power
![Page 3: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/3.jpg)
Specification
• A specification of what to construct is the first major step.
• 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 levelsSystemBoardHybridIC
• Specifications can be verified by system simulations.• Specification is 1/4 - 1/3 of total IC project !.
![Page 4: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/4.jpg)
Trade offs
Chip size
Power
Technology
Reliability
Packaging
Productioncosts
Speed
Integration
Testing
Tools
Developmentcosts
TimeSchedule
Man power
Flexibility
AvailabilityPartitioning
![Page 5: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/5.jpg)
Design domains
Structural Behavioral
Geometric
Processor, memory
ALU, registersCell
Device, gate
Transistor
Program
State machineModule
Boolean equationTransfer function
IC
Macro
Functional unit
Gate
Masks
Gajski chart
![Page 6: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/6.jpg)
Design domains and synthesis
Architectural level Logic level Circuit level
Beh
avio
ral l
evel
Str
uct
ura
l lev
el
For I=0 to I=15Sum = Sum + array[I]
0
0 0
0
State
Memory
+
Control
Clk
Architecturesynthesis
Logicsynthesis
Circuitsynthesis
![Page 7: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/7.jpg)
Top - down design
• Choice of algorithm (optimization)• Choice of architecture (optimization)• Definition of functional modules• Definition of design hierarchy• Split up in small boxes - split up in small boxes - split up in small boxes • Define required units ( adders, state machine, etc.)• Floor-planning• Map into chosen technology (synthesis, schematic,
layout)(change algorithms or architecture if speed or chip size problems)
• Behavioral simulation tools
![Page 8: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/8.jpg)
CMOS Design Flow
![Page 9: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/9.jpg)
RTL Synthesis Flow
![Page 10: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/10.jpg)
Standard Cell Place and Rout Design Flow
![Page 11: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/11.jpg)
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 tools
Comment by one of the main designers of the Pentium processor
The design was made in a typical top - down , bottom - up , inside - out design methodology
![Page 12: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/12.jpg)
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 gateLogic module
![Page 13: Design methodology. Design Methodology Specification Trade-off’s Design domains - abstraction level Top-down - Bottom up Schematic based Synthesis based](https://reader035.vdocument.in/reader035/viewer/2022072011/56649e185503460f94b03b77/html5/thumbnails/13.jpg)
Synthesis based
• Define modules and their behavior in a proper language(also used for simulation)
• Use synthesis tools to generate schematics and symbols (netlists)
always @(posedge clk)beginif (set) coarse <= #(test.ff_delay) offset;else if (coarse == count_roll_over)
coarse <= #(test.ff_delay) 0;else coarse <= #(test.ff_delay) coarse + 1;end