DOC PREVIEW
Berkeley COMPSCI 150 - Lecture 30 - Course Wrapup

This preview shows page 1-2-3 out of 9 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 9 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 9 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 9 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 9 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Spring 2009EECS150 - Lec30-wrapupPage EECS150 - Digital DesignLecture 30 - Course WrapupMay 7, 2009John Wawrzynek1Spring 2009 EECS150 – Lec30-wrapupPage Why Study and Learn Digital Design?• We expect that many of our graduates will eventually be employed as designers. – Digital design is not a spectator sport. The only way to learn it and to appreciate the issues is to do it. – To a large extent, it comes with practice/experience (this course is just the beginning).– Another way to get better is to study other designs. Not time to do this during the semester, but a good practice for later.• However, a significant percentage of our graduates will not be digital designers. What’s in it for them?– Better manager of designers, marketers, field engineers, etc.– Better researcher/scientist/designer in related areas• Software engineers, fabrication process development, etc.– To become a better user of electronic systems.2Spring 2009 EECS150 – Lec30-wrapupPage In What Context Will You be Designing?• Electronic design is a critical tool for most areas of pure science:– Astrophysics – special electronics used for processing radio antenna signals.– Genomics – special processing architecture for DNA string matching.– In general - sensor processing, control, and number crunching. In some fields, computation has replaced experimentation – particle physics, world weather prediction (fluid dynamics).• In computer engineering, prototypes often designed, implemented, and studied to “prove out” an idea. Common within Universities and industrial research labs. Lessons learned and proven ideas often transferred to industry through licensing, technical communications, or startup companies.– RISC processors where first proved out at Berkeley and IBM ResearchEngineers learn so that they can build. Scientist build so that they can learn.3Spring 2009 EECS150 – Lec30-wrapupPage Designs in Industry• Of course, companies are the primary employer of designers. Provide some useful products to society or government and make a profit for the shareholders.4Spring 2009 EECS150 – Lec30-wrapupPage The Big Ideas from EECS1501. Modularity and Hierarchy is an important way to describe and think about digital systems.2. Parallelism is a key property of hardware systems and distinguishes them from software.3. Clocking and the use of state elements (latches, flip-flops, and memories) control the flow of data.4. Cost/Performance/Power tradeoffs are possible at all levels of the system design.5. Hardware Description Languages (HDLs) and Logic Synthesis are a central tool for digital design.6. Finite State Machines abstraction gives us a way to model any digital system – however, usually only used for controllers.7. Arithmetic circuits are often based on “long-hand” arithmetic techniques.8. FPGAs give us a convenient and flexible implementation technology.5Spring 2009 EECS150 – Lec30-wrapupPage The Useful Skill from ClassGiven an English language description for the function of a digital system covering any of a wide variety of domains*:You can organize and describe a digital system, and using Verilog and logic synthesis, generate a detailed circuit at the “logic gate level”, and map to an FPGA, and debug it, and optimize for cost or performance or both.We hope that after have taken this class that …6* Well, at least for processors.Spring 2009 EECS150 – Lec30-wrapupPage What We Didn’t Cover• Design Verification and Testing– Industrial designers spend more than half their time testing and verifying correctness of their designs.• Some of this covered in the lab. Didn’t cover rigorous testing procedures and “formal verification”.– Most industrial products are designed from the start for testability. Important for design verification and later for manufacturing test.– Built in self test (BIST), Automatic Test Vector Generation, Scan-chain techniques.• Other High-level Optimization Techniques– Automatic Retiming (although FPGA do it)• Other High-level Architectures: video processing, network routers, ...• Power Aware Design Techniques and Tools• DRAM design and interfacing7Spring 2009 EECS150 – Lec30-wrapupPage Most Closely Related Courses• CS152 Computer Architecture and Engineering– Design and Analysis of Microprocessors– Applies basic design concepts from EECS150• EE141 Digital Integrated Circuits– Transistor-level design of ICs– Understand our EECS150 circuits are mapped to silicon• CS194-6 Digital Systems Project Laboratory– More intensive design experience in the EECS150 style– Not regularly offered (someday will be a regular course) • CS250 VLSI Systems Design– Learn how to design cell-based ASICs– Advanced-undergrad/grad course– “New” format, now design-based8Spring 2009 EECS150 – Lec30-wrapupPage Future Design Issues• Automatic High-level synthesis and optimization (with micro-architecture synthesis) and hardware/software co-design.• Current trend is towards “system on a chip” (SOC) design methodology:– Pre-designed subsystems (processor cores, bus controllers, memory systems, network interfaces, etc. ) connected with standard on-chip interconnect or bus.• Increasing NREs will favor post-fabrication customization.• A number of alternatives to silicon VLSI have been proposed, including techniques based on: – molecular electronics, quantum mechanics, and biological processes. “Nano-devices”– How will these change the way we design systems?9Spring 2009 EECS150 lec01-introPage Course Grading & Final ExamFinal25%project35%HW/quiz15%labs10%• Exam held in scheduled final exam slot: Thursday May 14, 12:30-3:30. • Room: 159 Mulford• “Comprehensive” Final Exam: covers material from the entire semester with emphasis on second half• ~2/3 of final will cover new material since Midterm exam - 7.5, Boolean Algebra, and on, including guest lectures.• ~1/3 of final will cover semester-long topics.10Midterm15%Review session:• Tuesday May 12th• 6-9pm, 306 SodaSpring 2009 EECS150 – Lec30-wrapupPage Important Topics from Second Half• Definitions of the three representations for combinational logic:– truth tables, logic gate networks, algebraic equations• Strengths, weaknesses, and uses for each CL representation.• Conversion of simple logic functions among all CL representations.• Definition and axioms of Boolean algebra• Laws (theorems) of


View Full Document

Berkeley COMPSCI 150 - Lecture 30 - Course Wrapup

Documents in this Course
Lab 2

Lab 2

9 pages

Debugging

Debugging

28 pages

Lab 1

Lab 1

15 pages

Memory

Memory

13 pages

Lecture 7

Lecture 7

11 pages

SPDIF

SPDIF

18 pages

Memory

Memory

27 pages

Exam III

Exam III

15 pages

Quiz

Quiz

6 pages

Problem

Problem

3 pages

Memory

Memory

26 pages

Lab 1

Lab 1

9 pages

Memory

Memory

5 pages

Load more
Download Lecture 30 - Course Wrapup
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Lecture 30 - Course Wrapup and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture 30 - Course Wrapup 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?