Lecture #1: Embedded Computing Systems - An OverviewWelcome to EEM202A/CSM213A!Course Logistics: Instructor InfoAbout This CourseCourse Logistics: PrerequisitesCourse Logistics: EnrollmentCourse Logistics: GradingCourse Logistics: ProjectMore Project GuidelinesCourse Logistics: On the WebCourse Logistics: Reader & TextbooksCourse Logistics: Some More Books (for your interest only…)Embedded Systems on the WebEmbedded Systems Courses on the WebCourse Logistics: Some Conferences and JournalsCourse Logistics: Impact of Travel on Class ScheduleCheating & PlagiarismPowerPoint PresentationReading List for This LectureCourse GoalsSecondary GoalsWhat are Embedded Systems?More Examples...Why do we care? Some Market Tidbits...Where are the CPUs?Profusion of Embedded SystemsExample: BMW 745iHistory of ComputingTypical Characteristics of Embedded SystemsKey Recent Trends“Traditional” Software Embedded Systems = CPU + RTOS“Traditional” Hardware Embedded Systems = ASICModern Embedded Systems?Complexity and HeterogeneityHandling HeterogeneityIncreasingly on the Same Chip System-on-Chip (SoC)More SoCsSoCs with Mechanics: Berkeley’s Smart DustIndustrial Structure Shift (from Sony)Tied to Trends in MicroelectronicsMany Implementation ChoicesHardware vs. Software ModulesMultiplexing Software ModulesMany Types of Programmable ProcessorsExample: Network ProcessorApplication-Specific Instruction Processors (ASIPs)Reconfigurable SoCH/W-S/W ArchitectureEmbedded System DesignProductivity Gap in Hardware DesignSituation Worse in S/WEmbedded System Design from a Design Technology PerspectiveSlide 53On-going Paradigm Shift in Embedded System DesignIP-based DesignMap from Behavior to ArchitectureThis CourseCourse PlanHW #1 - Due Monday October 10 @ 10AMCopyright © 2005EEM202A/CSM213A - Fall 2005Mani SrivastavaUCLA - [email protected]://nesl.ee.ucla.eduLecture #1: Embedded Computing Systems - An Overview2Welcome to EEM202A/CSM213A!•Course logistics and administrivia•Overview–what are embedded computing systems?–why are they important?–what are their characteristics & requirements?–what are the interesting trends?–what will the course cover?3Course Logistics: Instructor Info•Email: [email protected]•Phone: 310-267-2098•Office: 6731-H BH•Office hours–Mon 10:30-11:30 AM, We 2:00-3:00 PM–or by appointment–I’m very responsive with email–Please put “EE202A” or “CS213A” in mail subject line–Do not send emails from hotmail, yahoo etc. as my spam filter will likely discard them unless you put EE202A or CS213A in the subject field•Assistant: Marilyn Saunders, 6731 BH [email protected] This Course•Part of embedded systems course suite in EE and CS–Potkonjak/Srivastava’s EEM202A/CS213A (Fall): Core–Kaiser/Pottie’s EE180D (Fall): Undergrad Design–Estrin’s CS113 (Winter): Undergrad–Kaiser’s EE209S (Winter): Design–Estrin/Srivastava’s EEM202B/CSM213B (Spring): Distributed•Required course for EE’s ECS Major Field Students as well as those with ECS minor–Plus, question in M.S. comprehensive exam / PhD prelims5Course Logistics: Prerequisites•No official prerequisite graduate courses as the course covers a wide range of topics, but I’ll assume that you have–Background equivalent to UCLA’s BS in CSE or EE/CE option•Requirement #1: knowledge–Digital systems, Operating systems•Requirement #2: skills–Using simulation and analysis tools–Advanced ability to program & use simulation/analysis tools–Strong ability to communicate your ideas (talks, reports) •Requirement #3: initiative–Definitely not a spoon-fed undergrad or basic grad course–Open-ended problems with no single answer, requiring thinking and research•Requirement #4: interest–Have strong interest in research in embedded systems or related fields–Don’t take this course if you’re here for a quickie MS and are overloaded with courses6Course Logistics: Enrollment•If you want to enroll–Limit of 39 across the two courses–I’ll hand out some PTEs if needed, based on my discretion•wait till end of week 2 as many students drop out•Priority order for PTEs–ECS students who have been at UCLA for > 1 year–Students of one of my close research collaborators–ECS students in their first year•Auditors okay (space permitting)•If you decide to drop the course–Be considerate and drop by week 2 or 3 as after that you only hurt your fellow project partners–Please drop the course officially on URSA as well–Unsubscribe from the class mailing list7Course Logistics: Grading•Homeworks: 20% total–Analysis, simulation, programming, library/web research, paper reviews•Topic presentations : 15% total–Teams of 2-4 for each presentation as a function of topic (decided by me)–Survey a set of papers or an area (topic & resources specified by me on a continual basis)–Prepare slides and do a (12*TeamSize)-minute presentation•slides prepared jointly, all students share the presentation•slides must include a bibliography•One project: 25% quality of accomplishments normalized to difficulty of the project, 10% final report, 5% weekly reports and regular interactions, 15% presentation & demo = 55% total–Software/hardware design, tools, analysis, simulation–Implementation projects strongly encouraged–Literature surveys unacceptable, bogus hand-wavy stuff won’t get you far–Groups of 1-3 students–Up to 30 minute presentation during the finals week to me, like a conference talk with a demo–Up to 12 page report in the style of a technical conference paper•use ACM’s template at http://www.acm.org/sigs/pubs/proceed/template.html•Class participation and interaction: 10%–E.g. questions that you ask during lectures and student presentations–E.g. how much you interact with me regarding the project8Course Logistics: Project•Dig deep into a focus area on your own–lectures would provide a “broad” coverage•Should have some new idea/result, even if minor–one or more of simulation, analysis, implementation–no paper reviews and surveys•Project topics–some suggested project topics on class web page by early Week 2•I encourage you to think of your own topic–may relate to your own research•but you may not “reuse” work already done or being done for some other purpose–come and discuss possible project ideas with me!•What should be your goal?–something useful–similar style/quality as a conference paper and