here - Kettering University

Electrical and Computer Engineering

Kettering University

Course Syllabus CE-320L: Microcomputers I Lab Winter 2010 Course Website http://www.kettering.edu/~jkwon/teaching/10-t1/ce-320l/

Textbook: The HCS12/9S12: An Introduction to Software and Hardware Interfacing, Huang (1st Edition)

Instructor Dr. Jaerock Kwon Email: [email protected] Office: 2-703 Phone: (810) 762-9500 ext. 5917

Hours  Class: (02L): Tue 10:15am-12:20pm at AB 2817  Class: (03L): Tue 01:20pm-03:25pm at AB 2817  Office Hours: MW 11:15am-12:15pm and Tue 3:25pm-4:25pm or by appointment

General Information  Labs can be done in a group of up to two students if there are not enough seats. However, each student should prepare and submit his/her own lab report. Also you have to answer the questions in the lab report individually. Thus, you are expected to actively participate in all lab sessions.

Grading  You need to see the CE-320 course syllabus for this lab portion in the grade of CE-320.  There are eight labs plus one practical exam.  Grades are composed of the eight lab reports (10% each), a practical (10%), and group contribution (10%).  Each lab report is graded in a scale of 0-100 points.  A day penalty for late reports is 20% of the portion of the lab. If you are one day late on your report submission, you will get 0.8 x your score, and so on.

Lab Reports  A lab report must be submitted for each lab experiment.  Most lab assignments consist of two main parts: questions and programming. Questions are supposed to be completed before the lab session ends. The assignment due in programming part including flow charts is before the next week’s lab session starts. You must bring your printed copy of the assignment.  Your lab report should have a proper cover sheet with your name on it.  You must demonstrate your program at the beginning of the class period it is due. Demonstration involves showing the successful operation of the program to the instructor

1|Page

Electrical and Computer Engineering

Kettering University

and may include changing some data values, setting breakpoints to verify your program is properly written.  If you fail to demonstrate when asked, your lab report score will be 30% off. See 'Portion of grades' section below.  Portion of grades  Programming: 50% Your program must be demonstrated at the beginning of the class  Demonstration: 30% Working programs  Program structure: 10% Organized programs, data  Program comments: 10% Use of comments to explain the purpose of what an instruction is doing or to clarify the function of a few lines of code. Do not use comments to simply reiterate the instruction.  Additional items: 50% Questions, flow charts, test cases as specified by each lab individually.

Lab Practical Exam The lab practical exam will be held during the 6th lab period. The exam is one hour long and is taken individually.

Academic Integrity Kettering Code of Conduct (http://www.kettering.edu/currentstudents/coop/codeofconduct.jsp) will be strictly enforced. Each lab group is expected to complete the assignments on their own. Cheating is not tolerated. It is better to not turn in a lab than to turn in a copy. Students are responsible for collecting printouts of their code created as they compile to keep their code from being used by other groups.

Weekly Schedule and Class Notes Microcomputers 1 Lab (CE-320L) Schedule* Winter 2010 - Last Updated 1/10/2010 Week Week Week Week Week Week Week Week Week Week Week Week

Day 1 2 3 4 5 6 7 8 9 10 11

T T T T T T T T T T T

Topics 2: Review number systems Lab1: MiniIDE Lab2: Comparison Lab3: as12 assembler Lab4: Format Conversion Practical Exam Lab5: Subroutines Lab6: Input and Output Lab7: Interrupt-Driven Clock Lab8: Programming in C Final week (no lab)

Note Lecture

Due**

Lab2 Prog Lab3 Prog Lab 4 Lab 5 Lab 6 Lab 7

Prog Prog Prog Prog

* This schedule may be subject to change without further notice. ** There are two different dues for each lab assignment. 1. The due for all questions is before the lab session ends. 2. The due for programming assignments is before the next lab session starts.

2|Page