EECS150 Components and Design Techniques for Digital SystemsOutlineEnrollmentCourse MaterialsCourse ContentSlide 6Significant Changes from Fall 2001Course Structure & GradingSlide 9CheatingQuestionnaireExample Digital SystemsSlide 13Basic Design TradeoffsDesign RepresentationHierarchy in DesignsDigital DesignSpring 2002 EECS150 lec01-introPage 1EECS150 Components and Design Techniques for Digital SystemsJohn Wawrzynek(Warznek)Professor of [email protected] Soda HallOffice hours: Tu, Th 1-2Teaching Assistants:Gabriel EireaMark FengYury MarkovskiyYatish PatelJack SampsonNorm ZhouSpring 2002 EECS150 lec01-introPage 2Outline•Enrollment•Course Content•Course Structure & Grading•Cheating•Questionnaire•A Few Basic Principles of Digital DesignSpring 2002 EECS150 lec01-introPage 3Enrollment•If you are enrolled and plan to take the course you must attend your lab section next week, if not you will be dropped from the class roster. No exceptions! •Please note: Thursday morning lab section will not be held. If you are enrolled in that lab section, please change (using Telebears) to a different lab before next week. •If you are on the wait list and would like to get into the class you must: 1Turn in an appeal for on third floor Soda.2 Attend lectures and do the homework, the first two weeks. 3 In the second week of classes, go to the lab section in which you wish to enroll. Give the TA your name and student ID. 4 Later, we will process the waitlist based on these requests, and lab section openings. The final class roster will be posted at noon on Friday Feb 1.Spring 2002 EECS150 lec01-introPage 4Course Materials•Class notes, homework & lab assignments, and other documentation will be available on the CS150 homepage: http://www-inst.eecs.berkeley.edu/~cs152/index.html–Check the class homepage and newsgroup often! –You are responsible for checking the class web page at least once every 24 hours. •Textbook: Digital Design, Third EditionM. Morris ManoPrentice Hall, 2002•Laboratory Materials: –Xilinx tools and design libraries available online.–Verilog reference online.Spring 2002 EECS150 lec01-introPage 5Course ContentComponents and Design Techniques for Digital SystemsSynchronous Digital Hardware Systems–Example: sound waveform–A series of numbers is used to represent the waveform, rather than a voltage or current, as in analog systems.•Synchronous: “Clocked” - all changes in the system are controlled by a global clock (not asynchronous)•Digital: All inputs/outputs and internal values (signals) take on discrete values (not analog).Spring 2002 EECS150 lec01-introPage 6Course Content•Not a course on transistor physics and transistor circuits. Although, we will look at these to better understand the primitive elements for digital circuits. •Not a course on computer architecture or the architecture of other systems. Although we will look at these as examples. •Digital Architectures•Arithmetic units, controllers•Memory elements, logic gates, busses•Transistor-level circuits•Transistors, wiresSpring 2002 EECS150 lec01-introPage 7Significant Changes from Fall 2001•Lower enrollment•Verilog replaces schematics•New laboratory facility, 125 Cory. Thanks to National Semiconductor!•New project board, virtex based. Thanks to Xilinx, Inc.•Mano book replaces Katz.•Changes in order and emphasis in course content (you will probably not notice.)•Not Changed:–large project–lots of work–lots of fun!Spring 2002 EECS150 lec01-introPage 8Course Structure & GradingSpring 2002 EECS150 lec01-introPage 9Course Structure & GradingMonday (for example):Discussion section 1Tuesday:Lecture 2-3:30 1.5Wednesday (for example):Lab section 3Thursday:Lecture 2-3:30 1.5Friday:Lab Lecture 1Reading book, reviewing notes 3Homework 4TOTAL 15 hours/weekA week in the life of a EECS150 studentSpring 2002 EECS150 lec01-introPage 10Cheating•Any act that gives you unfair advantage at the expense of another classmate.•Examples:–copying on exams, homework,–copying design data,–modifying class CAD software,–modifying or intentionally damaging lab equipment.•If you ever have a question about what will be considered cheating, please ask me.•We will use software to automatically compare your submitted work to others.•If we detect you are involved in cheating you will be:–turned over to the Office of Student Judicial Affairs, for investigation and sanctions, additionally,–if you are found to have cheated, you will receive an F in the course.Spring 2002 EECS150 lec01-introPage 11QuestionnaireSpring 2002 EECS150 lec01-introPage 12Example Digital Systems•Digital Computer–Usually design to maximize performance. "Optimized for speed" - Usually designed to minimize cost. “Optimized for low cost”- Of course, low cost comes at the expense of speed.•Handheld CalculatorSpring 2002 EECS150 lec01-introPage 13Example Digital Systems•Digital Watch–Low power operation comes at the expense of:•lower speed•higher costDesigned to minimize power.Single battery must last for years.Spring 2002 EECS150 lec01-introPage 14Basic Design Tradeoffs•You can improve on one at the expense of worsening one or both of the others. •These tradeoffs exist at every level in the system design - every sub-piece and component. •Design Specification - –Functional Description. –Performance, cost, power constraints. •As a designer you must make the tradeoffs necessary to achieve the function within the constraints.Spring 2002 EECS150 lec01-introPage 15Design RepresentationSpring 2002 EECS150 lec01-introPage 16Hierarchy in Designs•Helps control complexity - –by hiding details and reducing the total number of things to handle at any time. •Modulalizes the design - –divide and conquer –simplifies implementation and debugging •Top-Down Design –Starts at the top (root) and works down by successive refinement. •Bottom-up Design –Starts at the leaves & puts pieces together to build up the design. •Which is better?–In practice both are needed & used.•Need top-down divide and conquer to handle the complexity. •Need bottom-up because in a well designed system, the structure is influence by what primitves are available.Spring 2002 EECS150 lec01-introPage 17Digital DesignGiven a functional description and performance, cost, & power constraints, come up with an implementation using a set of primitives.
View Full Document
Unlocking...