UCR CS122B
Advance Embedded and Real-Time Systems
Winter 2005
Announcement:
none.
Course
Information
Lecture
Laboratory
Student Presentation Homework
Course
Information
Lecture
Laboratory
Student Presentation Homework
In CS122B, you'll learn how to develop and program embedded systems. We'll cover the a variety of topics including method and technology of design, how to deal with hardware/software/firmware, trouble-shooting embedded systems, real-time programming, synchronization and atomic actions, scheduling, low-power design, and software testing. In the laboratory you will deal hands-on with Real-Time operating systesms like Windriver's Tornado and real-time Linux, advance specification/simulation environment like SystemC, SimpleScalar, and Tensilica. Your grade will be based on lab exercises, homework, in-class presentations, and exams. Graduate students are welcome to take the course.
| Instructor | Harry Hsieh, (harry@cs.ucr.edu),
SURGE 329
Office hours: TuTh 11AM-noon, or by appointment |
|---|---|
| Lecture | HMNSS 1502, TR 9:40AM-11AM |
| Lab | Location SURGE 173, MW 11:10AM-2PM Lab attendance is mandatory. You are expected to stay in the lab for the entire lab session, working on material related to this course. part of your lab grade is based on attendance and participation. |
| Textbooks | REQUIRED: None. Lecture notes and
hand-outs will be available throughout the quarter.
Recommended (NOT required): Embedded System Design: A Unified Hardware/Software Approach, Vahid and Givargis, Wiley & Sons, 2002, Accompanying Web page . Real Time Systems and Programming Languages: Ada 95, Real-Time
Java and Real-Time C/POSIX by Alan Burns, Andrew J. Wellings, 3rd
edition (April 5, 2001) Addison-Wesley Publishing. The Art of Designing
Embedded Systems, J. Ganssle, 1st ed., 1999, Newnes Press,
Butterworth-Heinemann. Building Embedded Linux Systems, K. Yaghmour, 2003, O'Reilly. (On-Line
version through California Digital Library). (You can access
through campus domain or proxy) |
| TA | David Sheldon (dsheldon@cs.ucr.edu)
Office hours: in lab Xi Chen (xichen@cs.ucr.edu) Office hours: in lab |
| Prerequisite | CS012 AND CS122A |
| Exams | Final 03/15/2005 8 to 11 a.m. HMNSS1502 | Midterm TBA |
| Call # and units | 12284, 5 units. |
| Grade | Labs 50%, Homeworks 5%, In-Class Quizzes 15%, Presentations
5%, Final 25%
Letter grades are assigned according to the usual
90/80/70/60 rule: 90% and above correspond to an A, 80% and above
to a B, 70% and above to a C, 60% and above to a D, and less than 60%
to an F. +/- grades will be given. Curving may be done on
individual items only if it helps the class. You are NOT
competing against one another -- you can all earn A's (and that
has happened in the past), so work together and help each other to
succeed. To ensure minimum competency in both the principle and
practice, students must pass each both Quizzes+Final portion and the
Labs+Homework portion to pass the course. |
Lecture Schedule, Slides, and Handouts
No late homework will be accepted. If you have any question about the grading of your homework after it is returned, you have only 1 week to bring it to my attention. After that, the grading is considered final. (Note: you may work in group, but you MUST turn in your own write-up. Obtaining answers from your classmate or any outside source will be considered as academic misconduct).
Labs should be done with one partner.
While lecture and lab material obviously overlap, the two aspects of
the course are quite independent, with lectures dealing with general
theory
and principles, and lab dealing specifically with specific designs and
tools. Exam will cover both the lecture and lab, with slight
emphasis on the lecture material.
You should plan to stay in every lab for the full three hours, starting from the very first lab. If you finish a lab early, then you should start on the next one (each comes with a good description), so that you will have even more time to work on later labs which are more difficult.
An electronic copy of the lab report (i.e. web turn-in's) need to be submitted, at the time of the demo for the lab to be completed.
(Note: While working in group of 2, you still must write your own lab report. You and your partner may jointly write the code and be jointly responsible for it. All aspects of the lab should be done by you and your partner. Obtaining information from outside source, especially if it is without citation, will be considered as academic misconduct.)