| ECE153A Introductory Information
|
Index
Course Goals
Time and Place
Course Personnel
Prerequisites
Course Texts
Course Project
Homework
Exams
Grading Policy
Honor Code Policy
Course Goals
This course, the first in the sequence of Hardware Software Interface, is
intended to teach the technology from which modern embedded
systems are built.
We will first review the major software and hardware components,
which you should have learned from the O.S. and architecture
courses. We then focus on the mechanisms and
policies that are employed to interface between hardware
and software components.
Topics include traps and interrupts, process management, memory
management, device drivers, DMA, real-time systems, and hardware/software
co-design.
A Course outline is available.
It is an evolving document, to be filled out in more detail as the
course progresses.
Time and Place
Lectures: Tue/Thur, 9:30AM - 10:45AM, Building 387 Room #104.
Lab Session #1: Wed 2:00 - 2:50pm
Lab Session #2: Wed 3:00 - 3:50pm
Lab Session #3: Fri 3:00 - 3:50pm
Course Personnel
| Person | Role | Office | Phone | Office Hours | Email |
|---|
| Edward
Chang | Instructor | 3163,
Engineering-1 | (805)893-2971 | 11:00am - noon Thur.
| echang@ece.ucsb.edu |
| Anshuman Kanwar
| TA | 2152C,
Engineering-1 | (805)893-4316 | 12:30 - 1:30pm Wed
| akanwar@umail.ucsb.edu |
| TBD
| TA | 2152C,
Engineering-1 | (805)893-4316 | 4:00 - 5:00pm Tue |
tbd@engineering.ucsb.edu |
Prerequisites
Students should have the background on Operating Systems
and Computer Architectures. Knowledge of C, Assembly
and Compilers will be helpful.
Textbook
Operating System Concepts, Sixth Edition,
John Wiley & Sons, Inc., ISBN 0-471-41743-2,
Abraham Silberschatz, Peter Baer Galvin, and Greg Gagne
Course Requirements
Project
There will be two projects, each covering several weeks, involving
some aspect of system implementation.
Homework
Some conventional homework questions will be assigned each week.
Homeworks will generally be due on Thursdays.
On some weeks, both a project and written homework will be due, so you
should pace yourself regarding the projects.
No late homeworks will be accepted.
Exams
Midterm: In class, Tue, Nov. 6th.
Final: Dec. 10th, 8am to 11am.
Grading Policy
The approximate weights of the four components are:
| Component | Weight |
|---|
| Project | 20% |
| Homework | 20% |
| Midterm | 20% |
| Final | 40% |
Honor-Code Policy
The basic presumption is that the work you do is your own.
Occasionally, especially when working problem sets or
writing programs (but never on exams!), it may be
necessary to ask someone for help.
You are permitted to do so, provided you meet the following two
conditions.
-
You acknowledge the help on the work you hand in.
-
You understand the work that you hand in, so that you could explain
the reasoning behind the parts of the work done for you by another.
Any other assistance by another person constitutes a violation
of the honor code and will be treated as such.
We shall not deduct credit for small amounts of acknowledged assistance.
Even working as a team on one of several problems in a problem set may
not hurt your grade, as long as all members of the group acknowledge
their collaboration.
Such shared interest can be beneficial to all concerned.
We do reserve the right to give less than full credit in circumstances
where it appears that there has been large-scale division of labor, and
you are not getting as much learning out of the assignment as you should.
However, as long as you acknowledge your sources, you cannot get into
Honor-Code trouble.
If you have any questions about what this policy means, please discuss
the matter with the instructor now.