This material is assembled solely for use by students in ECE 353 at the University of Wisconsin-Madison and is not to be otherwise sold, distributed, or reproduced. Department of Electrical and Computer Engineering University of Wisconsin-Madison ECE 353 INTRODUCTION TO MICROPROCESSOR SYSTEMS Syllabus and Policies Spring 2008 Last updated 1/21/2008 5:51 PM Required Supplement to the Text Michael J. SchulteECE 353 Introduction to Microprocessor Systems Spring 2008 (Schulte) 1 INSTRUCTOR: Michael J. Schulte, 4619 Engineering Hall Ph: 262-0206 email: [email protected] CREDITS: 3 PREREQUISITES: ECE/CS 352, ECE/CS 354 GOALS: This course focuses on the construction of microprocessor based systems from off-the-shelf components. The emphasis is on building microprocessor-based systems through the interfacing of commercially available devices. At the end of the course, it is expected that you will be able to design a microprocessor-based system with confidence. TOPICS: Microprocessor System Design Process Hardware and Software Development Tools Introduction to the ARM Microprocessors ARM7TDMI Organization Instruction Set, Addressing Modes Stack, Branching, Subroutines Microprocessor Support Circuits and Peripherals Parallel Interfacing and Timing Memory Systems Interrupts and Exceptions Switches, Keypads, and Displays Serial Interfacing Analog Signals TEXTBOOK: F.M. Cady, Microcontrollers and Microcomputers, Oxford Press, 1997 Supplementary material from Bob’s Copy Shop Materials posted on the course web page GRADING POLICY: 5% Pre-quizzes and other individual assignments 25% Homework 45% Midterm quizzes (3) 25% Final examECE 353 Introduction to Microprocessor Systems Spring 2008 (Schulte) 2 COURSE CONDUCT TIMETABLE Lecture: 1:20-2:10pm, MWF, 2534 Engineering Hall Discussion: 6:30-8:00pm, Wednesdays, 3534 Engineering Hall INSTRUCTOR Name: Michael J. Schulte Office: 4619 Engineering Hall, 262-0206, [email protected] Office hours: 2:15-3:30pm, MW TEACHING ASSISTANT Name: Ranjith Kumar Office: TBA Office Hours: TBA REQUIRED TEXT / MATERIAL • F.M. Cady, Microcontrollers and Microcomputers, Oxford Press, 1997 • Supplementary material from Bob’s Copy Shop • Supplementary material published online REFERENCE TEXTS • Numerous references are posted in electronic form on the course web page o ARM Architecture Reference Manual (ARM) o ARM7TDMI Technical Reference Manual (ARM) o ADuC7026 Datasheet (Analog Devices) o ARM7 Instruction Set Reference (Morrow) o ARM7 Instruction Set Quick Reference (Morrow) • Steve Furber, ARM System-on-Chip Architecture, Addison-Wesley, 2000 • M.M. Mano & C.R. Kime, Logic and Computer Design Fundamentals, 3rd Edition, Prentice Hall, Inc., 2004 COURSE ORGANIZATION The course is organized into seven modules, each two weeks in length. Each module will have an associated homework assignment, and an exam will be given after every two modules. Each student will be assigned to a 3-person team, and will complete all homework and in-class activities as part of this team. Teams will be assigned at the start of the semester, and will remain in place for the entire semester. Each team will prepare and submit a contract outlining their responsibilities to each other. Details of team organization and responsibilities will be presented on the first day of class. Learn@UW will be used for a number of purposes, including administering pre-quizzes and providing students with online access to their grades. A link to the Learn@UW entry page isECE 353 Introduction to Microprocessor Systems Spring 2008 (Schulte) 3 available on the course web page. Email will be used extensively to communicate with the class. Students should verify that their UW email information is correct, and check their email at least daily during the course. STUDENT RESPONSIBILITY You are responsible for all assigned reading material in the text and notes, and all lecture content unless otherwise specified by the instructor. If you miss class, it is your responsibility to obtain assignments and other information given on the days you missed. Unless otherwise specified, your work in this course is to be your own. In particular, the use of software including script written wholly or partially by other students is specifically prohibited. USE OF COMPUTER-AIDED ENGINEERING CENTER (CAE) There will be extensive homework assignments requiring the use of programs on PCs in the Computer-Aided Engineering Center. Brief introductory sessions to CAE systems are provided by CAE early in the semester. Mandatory tutorial sessions will be held early in the semester to familiarize you with the Keil µVision3 integrated development environment (IDE) that we will be using for software development. HOMEWORK Homework shall be accomplished by students working in 3-person teams. Each assignment will be given a single grade for all team members. Team self-assessment will be used to determine an overall weighting factor for individual members of the team. Seven homework sets will be assigned during the semester. These should be neatly done on 8½ by 11 sheets with all pages stapled together in order. Computer output must be properly formatted and annotated with comments, per the Documentation Standards included in the course notes. All diagrams shall be drawn using Mentor Graphics or other tools capable of generating high quality logic diagrams. Homework assignments tend to build on one another throughout the semester; therefore it is essential to complete each one. If you do not have a fully functional assignment on the day it is due, turn in what you have and continue to work on the assignment. All homework that you submit in this course is expected to be the product of only your team. Evidence indicating copying of work from others outside your team or other inappropriate cooperation will be dealt with as academic misconduct. Acceptable types of assistance you may receive from (or offer to) others outside your team are limited to assisting in problem interpretation, and occasional general hints on ways of attacking a problem. If in doubt, see the instructor or teaching assistant. Homework assignments are due at the beginning of class on the date specified for submission. After this deadline, no credit will be given except under extreme non-academic circumstances. Both the instructor