Icom5217:Microprocessor Interfacing

University of Puerto Rico at Mayagüez
Department of Electrical and Computer Engineering
Electronics/Hardware and Embedded Systems Area

ICOM-5217
Microprocessor Interfacing

Fall Semester, 2009

“Programming microcontrollers is like riding a bike: once you get the skill you
can switch bicycles and still ride”

Last Updated: November 3, 2009

Page Contents

1. INSTRUCTOR INFORMATION 2. COURSE DESCRIPTION 3. OBJECTIVES & OUTCOMES 4. PREREQUISITES BY TOPIC 5. TEXTBOOK & REFERENCES 6. COURSE OUTLINE	7. INSTRUCTIONAL STRATEGY 8. COURSE SCHEDULE 9. GRADING RULES 10. GENERAL POLICIES 11. CLASS MATERIALS 12. USEFUL LINKS

1. Instructor Information

Instructor:	Dr. Manuel Jiménez
Office:	Stefani 222B
Phone:	(787)832-4040 Ext. 3780
Office Hours:	Please, refer to Current Schedule
E-mail:	mjimenez@ece.uprm.edu
URL:	http://ece.uprm.edu/~mjimenez
Lab. Page	Microprocessors Interfacing Laboratory (MIL)

2. Course Description

ICOM 5217 – Microprocessor Interfacing: Development of micro-controller based systems for embedded applications. Interfacing to peripherals such as liquid-crystal displays (LCD), keypads, digital-to-analog and analog-to-digital converters, etc. Emphasizes hardware and software design. Requires a final project that consists in the development and laboratory demonstration of the working prototype of an embedded application.

3. Objectives and Outcomes

Objectives: At the end of the course the students are expected to know how to specify, design, and prototype a microprocessor-based embedded system. To achieve this objective the students have to develop a semester-long project consisting of specifying, designing, and prototyping an embedded system solution to a real life problem.

Outcomes: Using the ABET-2000 criteria:

Activity	Program Outcome
1. Students conduct laboratory work to implement a working prototype of their project.	(b)
2. Students perform a project of an original idea proposed by their group. Project implementation is a course requirement.	(b)
3. Groups of two to four members work towards completion of the class project. Peer evaluation and individual interviews with the professor are required.	(d)
4. Each group must show originality in their work, the procedure of partitioning a complex problem into parts, and combining peer work into the final solution.	(d)
5. Students identify a problem where microprocessor interfacings kills can be applied.	(e)
6. The project idea, along with a plausible procedure, is submitted by the working group as a proposal.	(e)
7. Groups must offer an oral presentation and a written final report of their work.	(g)
8. Student presentations and demonstrations are open to the public, and therefore should be understandable by interested parties. Mathematical and technical content are expected in a way that attendants at least understand why they were used, although full comprehension is not expected.	(g)
9. Projects proposals should reflect awareness of societal needs.	(h)
10. Students should comment the project impact to society reflected by acceptance of their design. This includes the impact to low-skilled workers being replaced by their solution and the impact to the environment. Benefits to the intended social group.	(h)
11. Students must include references that demonstrate their ability to search for information. This information could be reflected in the theory part of the report or elsewhere.	(i)
12. Students should comment on different alternatives to solve their problem. These alternatives should include emerging technologies and their associated cost, although they might not be been implemented.	(j)
13. Students must be able to program a microcontroller using a development environment that includes debuggers, editing tools, and compilers, among others. The microcontrollers used in class are considered state of the art.	(k)

4. Prerequisites by Topic

Students enrolled in this course are expected to have an undergraduate-level equivalent background in the following topics:

Logic circuit design
Microprocessor fundamentals

Basic microprocessor organization
Assembly language programming

A/D and D/A converters
Fundamental programming skills

5. Textbook and References

Textbook:

F. Vahid & T. Givargis: “EMBEDDED SYSTEM DESIGN: A Unified Hardware Software Introduction” John Wiley & Sons, Inc. 2002

Textbook Web Site:
http://esd.ds.ucr.edu

References:

A. Gaonkar, "Fundamentals of Microcontrollers and Applications In Embedded Systems: With the PIC18 Microcontroller Family", Thomson Delmar Learning, 2007
B. Brey, “The Intel Microprocessors”, 5th Ed., Prentice Hall, 2000
G. Miller, “Microcomputer Engineering”, 2nd. Ed. Prentice Hall, 1999
K. Ayala, “The 8051 Microcontroller”, West Publishing, 1997
Driscoll, Coughlin, & Villanucci, “Data Acquisition and Process Control with the M68HC11”, Merril 1994
M. Slater, “Microprocessor-based Design”, Prentice Hall, 1989

6. Course Outline

The course material is distributed in eleven main topics going from introductory to advanced concepts, as indicated below:

Topic	Contact Hours
1. Introduction to embedded systems design	3
2. Embedded microcontroller architecture	4
3. Bus Systems & Input/Output Interfaces	5
4. Displays and Keypads	3
5. Interrupts	4
6. Timers and Applications	4
7. Analog to digital converters	2
8. Serial communication	4
9. Memories and error correction	4
10. DMA Controllers	3
11. Design Technology in Embedded Systems	3
12. Student Presentations	2
13. Exams	4
Total hours: (equivalent to contact period)	45

7. Instructional Strategy

The course consists mainly of lectures and laboratory sessions. Students work in teams of two to four members on a project established at the beginning of the semester. Handouts or electronically accessible documents are provided for selected topics. Although the professor guides the discussion of major topics, students are encouraged to expand beyond the classroom discussion for the richness of their project and overall learning experience.

8. Course Schedule

The scheduled activities for the current offering of the course are outlined below. Important events are highlighted.

Event	Date	Description	Links
Intro	Aug. 12	First day of classes	Syllabus Instructor Info
PR#1	Aug. 24	Progress Report #1: Project proposal and Team composition (See guidelines)	Guidelines
PR#2	Sep. 9	Progress Report #2: Block diagram Version 2 (BDv2), MCU selection, Operating chart, and One-page poster	Program Design Sample Poster
HW	Sep. 25	Homework Due	Instructions Evaluation
MT	Oct. 7 Oct. 26	Midterm Exam	Sample Exam
PR#3	Oct. 14 Oct. 30	Progress Report #3: Schematics, Part list, Timing & Power analysis, BDv3, Software plan	Schematic Guide OrCad Tutorial
PR#4	Nov. 4 Nov. 16	Progress Report #4: Assembled prototype and System software Beta 0.5	Prototyping Guidelines
PR#5	Nov. 13 Nov. 25	Progress Report #5: System software Beta 1.0 and Working prototype demonstration	-
RPT	Nov. 18 Dec. 2	Comprehensive Final Project Report	Guidelines Evaluation Guide Sample Report
H/H	Nov. 24/25 Dec. 7/8	Happy Hours	-
PP	Dec. 2 Dec. 11	Final Project Presentations (Announcement)	Guidelines Evaluation Guide
Final	TBD	Final Exam	–

9. Grading Rule

Evaluations will be based on one midterm exam, one homework assignment, the class project, and a final exam. The tables below provide the weight distribution of each category with details on the project evaluation, and the scale for final grade assignment.

Grading Categories
Category	Weight
Midterm Exam	20%
Homework	10%
Project	50%
Final Exam	20%
Total Points	100%

Project Categories
Category	Points
Progress Reports	10.0
WrittenReport	20.0
Happy Hour	12.5
Presentation	7.5
Total Points	50

Grade Scale
Points	Grade
0.0 – 59.9	F
60.0 – 69.9	D
70.0 – 79.9	C
80.0 – 89.9	B
90.0 – 100	A

10. General Policies

Attendance:

Attendance will be monitored in the classroom at the beginning of each lecture. It is the student responsibility to sign the attendance list to be circulated by the professor at the beginning of each class. Attendance lists cannot be used as alibi in a court of law.
Approximately, every 10 lectures an attendance report will be generated.
A student with more than 3 (three) missed lectures in a reporting period will be considered not to be regularly attending class and will be reported as so in the registrar's attendance report.

Exams:

Make-up for exams will be furnished only to students with a written, valid excuse. The professor reserves the right to determine which excuses are valid.
Under no circumstance will a late take-home exam be accepted. If an exam is not turned-in by the date and time specified, the student will receive zero in that exam.

Homework and Progress Reports:

Homework and reports are due in class on the dates specified in the course schedule.
Late homework and reports will be accepted with an scalating penalty of 10%, 25%, and 50% for each late day up to the third day.
Lateness beyond the third day would make your work worthless (100% penalty).
Students are responsible for verifying the integrity of electronically submitted materials. Unreadable formatting will not be considered a valid submission, and therefore might lead to late penalties.

General Behavior:

Students are responsible for the acquisition of those parts not available in the laboratory stock of components.
All components loaned from the lab are to be returned to the lab at the end of the semester. Failure to do so will carry an Incomplete with F as final grade for the entire group and a report to the finance office to be placed as "debtors".
Students are responsible for the good care of the lab. equipment. Negligence will carry penalties on your grades.
Dishonesty of any kind will be dealt at the professor jurisdiction and reported to the pertinent authorities for the appropriate disciplinary sanctions.
Cellular phones and pagers must be in quiet mode during lectures and meetings and off in exams and other in-class evaluations. No answering of calls will be allowed in the classroom.
Audio or video recording equipment of any kind is not allowed in lectures.
Smoking is not permitted in the classroom or laboratory.

11. Class Materials (TBD)

This section contains materials specific to the class. Access to this area is restricted. Only students officially enrolled in the course will be granted access. Here you will find: