EE444

Embedded Systems Design

Course syllabus

For the current version, and for the material (slides, homework and lab assignment, notes, etc.) please see Blackboard

NEW! STUDENT PROJECTS

Course Information

Course Description (from the catalog)

Issues surrounding the design and implementation of microcontroller-based embedded systems. Topics include hardware architecture and glue logic, embedded programs design, analysis, and optimization, hardware/firmware partitioning, firmware architecture and design. Includes laboratory exercises using evaluation board and a complete embedded system design project. Emphasis on robust designs, energy efficiency, and proper documentation.

IMPORTANT DATES:

  • Last day to drop the class (course does not appear on academic record): Friday, February 2

  • Last day to withdraw (W grade appears on academic record): Friday, March 23

  • Spring break (no classes): Monday-Sunday, March 12-18

  • Last EE444 class: Thursday, May 3

LECTURE SLIDES (links removed - see Blackboard):

HANDOUTS AND DOCUMENTATION (removed)

COURSE POLICIES

Grading:

This course is a design elective. Design projects will be assigned to students based on their interests and background. You are encouraged to start thinking about the topic of your project from the very beginning of the course. The format of the final report will follow the format of a typical conference paper. For the final project presentations, students will have to prepare a PowerPoint presentation and to present their project to the entire class. The instructor will assist the students in preparing the paper and the presentation. Grading of lab reports, final reports, and oral presentations will follow the guidelines set by the University for "O" and "W" designated undergraduate courses: Specific Guidelines for "O" Designated courses emphasizing public communication in small class contexts (Regularly enrolling less than 12 students):

  1. All presentations must involve question and answer interaction. As appropriate for the discipline, it is highly desirable that there be at least one assigned respondent, with questions by other audience members encouraged.

  2. All presentations must have a clear introduction-body-conclusion organization, appropriate to the discipline.

  3. At least one presentation must involve the development and use of appropriate visual aids, and it is desirable that all presentations do so.

  4. All presentations should receive evaluation by the instructor on oral communication competency (including responsiveness to audience questions), as well as on subject mastery.

  5. Students must receive, as part of the course structure, information/instruction on effective speaking, effective responding, organization of material for effective presentation, and on development and use of media and visual aids. If thematic panels are used, students should also receive instruction on panel/symposium and moderator techniques.

To grade a course on written work means to use the student's written work as the basis for his or her grade. Written work is graded mainly on content and organization, with tone, word choice, sentence structure, grammar, punctuation, and spelling accounting for a smaller fraction of the grade.Students are strongly encouraged to attend every class and laboratory and participate in the classroom discussion in a manner that would benefit other students as well. Discussions that would require too much time, especially if not of interest to all the students, will be held during lab periods and/or office hours. Written laboratory reports are due 1 week after each laboratory exercise. Written reports will be graded for both writing style and technical content. No late laboratory reports will be accepted unless previously arranged with the instructor.Attendance is required during your assigned lab period, unless otherwise arranged in advance with the instructor. A lecture/discussion at the start of each lab period will provide useful information for completing the lab and/or final project. The labs will be worked on individually. Each student is required to establish a reliable email address (preferably a uaf.edu address) and to send it to the instructor (d.raskovic@uaf.edu) as soon as possible. This address will be used for class correspondence - announcements, laboratory assignments clarifications, etc. The course web page will contain useful information and will be updated throughout the course. The students will be notified by email when the content of the web site changes. The current version of this syllabus will be available on the course web page.

Tentative Course Topics

  • Embedded systems concepts

  • Microprocessor/microcontroller architectures

  • Embedded systems components

  • Memory selection, memory maps

  • Microcontroller instruction sets

  • Microcontroller peripherals and drivers

  • Interrupts and Interrupt Service Routines

  • Timing requirements

  • MSP430 specifics

  • Processes and Operating Systems

  • Embedded programs design, analysis, and optimization

  • Multiprocessor embedded architectures

  • Energy efficiency

  • Hardware/software co-design

The course content will evolve based on students' progress and interests.

Disabilities Services. The Office of Disability Services implements the Americans with Disabilities Act (ADA), and insures that UAF students have equal access to the campus and course materials. The instructor, the teaching assistant, and the administrative assistant will work with the Office of Disabilities Services (203 WHIT, 474-7043) to provide reasonable accommodation to students with disabilities.

Plagiarism. As a UAF student, you are subject to UAF's Honor Code:"Students will not collaborate on any quizzes, in-class exams, or take-home exams that will contribute to their grade in a course, unless permission is granted by the instructor of the course. Only those materials permitted by the instructor may be used to assist in quizzes and examinations.Students will not represent the work of others as their own. A student will attribute the source of information not original with himself or herself (direct quotes or paraphrases) in compositions, theses and other reports. No work submitted for one course may be submitted for credit in another course without the explicit approval of both instructors. Violations of the Honor Code will result in a failing grade for the assignment and, ordinarily, for the course in which the violation occurred. Moreover, violation of the Honor Code may result in suspension or expulsion."

Plus/Minus grading will be used – see the UAF catalog for numerical values used for GPA calculation

Teaching a class as small as this one allows me to use a more qualitative, subjective grading scale. Final course grade will be determined, in part, based on the final distribution of all grades in the class. I will look at the individual students' achievements and try to find natural breaks in the grade distribution. The following descriptions will be used as guidelines:

A: achievement that is outstanding and well above the level necessary to meet course requirements;

B: achievement that is above the level necessary to meet course requirements;

C: achievement that meets the basic course requirements;

D: achievement that is worthy of credit even though it does not fully meet the basic course requirements;

F: achievement that fails to satisfy the basic course requirements.

The rank ordering of grades will not deviate from the rank ordering of student performance. In any case, the grade cutoffs will never be set higher than these:

A’s: 90+ B’s: 80+ C’s: 70+ D’s: 60+ F: 59 and below