Faculty of Engineering, Architecture and Science

Department of Electrical and Computer Engineering

Course Outline (Fall 2015)

BME 538: Microprocessor Systems
Instructor

Prerequisites
Course Type
Program Level
Website
Compulsory
Texts

Reference
Text
Calendar
Description

Learning
Objectives

Dr. Sattar Hussain

Office: TBA
Phone: TBA
Email: sattar.hussain@ryerson.ca
Office hours: TBA
BME 328

Compulsory
BME 05 (5th Semester)
https://ryerson.desire2learn.com/d2l/home/29989

1. Programming 32-Bit Microcontrollers in C: Exploring the PIC32, 1st Edition, by

Lucio Di Jasio (plus support page: http://exploringpic32.com/)
2. Microcontrollers and Microcomputers Principles of Software and Hardware
Engineering, 2nd Edition by Frederick M Cady.
n/a
This course introduces students to small microprocessor-based systems, with an emphasis
on embedded system hardware and software design. Topics will include microprocessor
architecture and structure, with an overview of 8- 16- and 32-bit systems, assembly
language programming and the use of high-level languages. Basic input/output including
parallel communications with and without handshaking and serial protocols. Hardware and
software timing. Using interrupts and exceptions. Overview of single-chip microprocessors
and controllers with an emphasis on the PIC32xxxx microcontrollers. The internal structure
and design of peripheral devices. Memory system design and analysis. The use and
structure of development tools such as (cross) assemblers or compilers, monitor programs,
simulators, emulators, etc.
At the end of this course, the successful student will be able to:
1. Use technical knowledge including microprocessor architecture, microprocessor I/O
interface, microprocessor peripherals, programming and debugging methodology.
Use design tools and related resources including microprocessor, microprocessor
peripherals, assemblers, compilers, and hardware debuggers (4a)
2. Apply the programming principles to define an accurate programming problem
statement. Recognize that good problem definition assists the program design
process. (4b)
3. Describe differences between the various approaches that can be used to solve a
microprocessor programming problem using assembly/C language. Select one
specific approach to solve the problem. When the selected approach fails to solve the
problem satisfactorily, analyze the cause of failure using standard assembly/C

language programming and debugging methodologies. Based on the analysis, come

up with new suggestions to improve the existing approach. Integrate the new
suggestions into the existing design plan. Judge the completeness and quality of the
generated solutions using standard assembly/C language programming and debugging
methodologies. (4d)
4. Describe the iterative process of programming and debugging microprocessor
programs using assembly/C language. Using debugging tools to generate information
on the current state of an assembly/C language program that can be used to modify
and improve the current program solution. Based on the generated information,
examine and critique the current program solution to revise the solution as needed.
Incorporate and integrate feedback from the teaching assistants and others and
generate new knowledge about the programming problem. (4h)
5. Produce lab and project reports using appropriate format, grammar, and citation
styles for technical and non-technical audiences. (7a)
6. Illustrate concepts including the structure of assembly/C language programs and
obtained experimental results. (7d)
Note: Numbers in parentheses (e.g. 10a) refer to the graduate attributes required by the
Canadian Engineering Accreditation Board. For more information, see:
http://www.feas.ryerson.ca/quality_assurance/accreditation.pdf
Course
Organization

Course
Evaluation

3 hours of lecture per week for 13 weeks, in 1 section

2 hours of lab/tutorial every week for 13 weeks in 4 sections
2 Teaching Assistant
Assignments
Midterm Exam
Final Exam
Laboratory
Final Project
Total

0%
25%
45%
20%
10%
100%

(a)

Assignments: Assignments, taken from the text, will not be graded. Answers
are given in the textbook.

(b)

Midterm Exam: A single midterm will be held on week 7, Wed. October 21,
2015.
Final Exam: A single final exam will be held during the final examination period.

(c)
(d)

Laboratory: The hands-on laboratory sessions, conducted over the course of

the semester, using Department-supplied laboratory kits (MikroE boards).

(e)

Final Project: A final project will be conducted by individual students using

student-supplied microcontroller kits (ChipKit boards).

Students are required to pass both (1) the theory and (2) the laboratory components of the
course in order to obtain a passing grade for the course. The theory component is assessed
via the midterm and final exams and Final Exam (70% of final grade), while the laboratory
component is assessed on project development and reporting (Laboratory is 20% of final
grade and Final Project is 10%).

Course Content
The following table lists the lecture and lab material on a weekly basis, with relevant chapters from the two texts
listed.
Week
1
Sept. 8,
2015
2
Sept. 14,
2015

3
Sept. 21,
2015

4
Sept. 28,
2015

5
Oct. 5, 2015

6
Oct. 12,
2015

7
Oct. 19,
2015

8
Oct. 26,
2015

9
Nov. 2, 2015

Theme

Lecture/lab Description
Hour
Introduction
3 hours
Cady book Ch. 1 & 2: Introduction and general principles of
microcontrollers
Di Jasio book Ch. 1 & 2: Preparation-Loops
No labs
General
concepts

C for
embedded
systems

3 hours

2 hours
Lab 1
3 hours

Cady book Ch. 2: General principles of microcontrollers

Di Jasio book Ch. 3: Loops (continued) arrays-LEDs on
ChipKit
Blinking LEDs on MicroE board
Cady book Ch. 3: Structured programming
Ch. 7: C for embedded systems
Di Jasio book Ch. 4: Numbers
Keypad part 1

Interrupts

2 hours
Lab 2
3 hours

Keypad part 2

Interrupts

2 hours
Lab 3
3 hours

Interrupts and exceptions part 1

Memory

2 hours
Lab 4
3 hours

Interrupts and exceptions part 2

Serial I/O

2 hours
Lab 5
1 hours
(lecture)
2 hours
(Midterm)
2 hours
Lab 6
3 hours

Mixing assembler and C

Serial I/O

2 hours
Lab 7
3 hours
2 hours
Lab 8

Serial communication

MidtermAssembler

Cady book Ch. 10: Interrupts and real-time events

Di Jasio book Ch. 5: Interrupts

Cady book Ch. 10: Interrupts and real-time events

Di Jasio book Ch. 5: Interrupts

Cady book Ch. 5 and 11: Memory and addressing modes

Di Jasio book Ch. 6: Memory

Cady book Ch. 11: Assembler and watchdogs

Midterm Test

Memory, arrays, and strings

Cady book Ch. 12: Serial I/O, SPI and peripherals
Di Jasio Ch. 8: Serial communication

Cady book Ch. 12: Serial I/O, SPI and UART

10
Nov. 9, 2015

11
Nov. 16,
2015

Analog
interfacing

Counters

12
Nov. 23,
2015

More
interfacing

13
Nov. 30,
2015

Interrupts to
RTOSs

3 hours
2 hours
Lab 9
3 hours

Cady book Ch. 13 and Di Jasio book Ch. 11: Analog

interfacing
Measuring body joint angles
Cady book Ch. 14: Counters and timers
Preparation for final project

2 hours
Lab 10
3 hours

Final project part 1

2 hours
Lab 11
3 hours

Final project part 2

Cady book Ch. 15: Interfacing

Cady book 16: From interrupts to state machines, Schedulers

and RTOSs
No labs

Laboratory
The hands-on component of the course is made up of formal labs and a final project. The formal labs are to be
done in groups of two. You are expected to find a partner either prior to the first lab or at the beginning of the
first lab. Labs begin in the second week of class. Equipment will be provided by the Department during these
formal labs. Students are expected to attend the lab section for which they are registered. A short quiz will be
conducted in the first ten minutes of every lab. The quiz will count towards each individual students lab grade.
Late students will receive a zero for a missed in-lab quiz.
The other hands-on component of the course involves a student-purchased microcontroller kit. Each student is
to purchase a separate kit, consisting of a ChipKit uC32 processor board, a ChipKit I/O board, a Microchip
PICkit 3 programmer and an enclosure. The kit is available from the ELCE Departments Mr. Jim Koch.
All reports, whether for the lab or the final project, are expected to include a standard FEAS cover sheet. The
reports are expected to adhere to IEEE format, including referencing. Refer to the marking and style guides for
details on what is required in these reports.
Important Notes
1. All of the required course-specific written reports will be assessed not only on their technical/academic
merit, but also on the communication skills exhibited through these reports.
2. All assignment and lab/tutorial reports must have the standard cover page which can be completed and
printed from the Department website (link to be given at a later date) The cover page must be signed by
the student(s) prior to submission of the work. Submissions without the cover pages will not be accepted.
3. Students who miss a final exam for a verifiable reason and who cannot be given a make-up exam prior to
the submission of final course grades, must be given a grade of INC (as outlined in the Grading Promotion
and Academic Standing Policy) and a make-up exam (normally within 2 weeks of the beginning of the
next semester) that carries the same weight and measures the same knowledge, must be scheduled.
4. Medical or Compassionate documents for the missing of an exam must be submitted within 3 working
days of the exam. Students are responsible for notifying the instructor that they will be missing an exam
as soon as possible.
5. Requests for accommodation of specific religious or spiritual observance must be presented to the
instructor no later than two weeks prior to the conflict in question (in the case of final examinations within

6.
7.

8.
9.
10.

11.
12.

two weeks of the release of the examination schedule). In extenuating circumstances this deadline may
be extended. If the dates are not known well in advance because they are linked to other conditions,
requests should be submitted as soon as possible in advance of the required observance. Given that timely
requests will prevent difficulties with arranging constructive accommodations, students are strongly
encouraged to notify the instructor of an observance accommodation issue within the first two weeks of
classes.
The results of the first test or mid-term exam will be returned to students before the deadline to drop an
undergraduate course in good Academic Standing.
Students are required to adhere to all relevant University policies including:
- Undergraduate Grading, Promotion and Academic Standing,
http://www.ryerson.ca/senate/policies/pol46.pdf
- Student Code of Academic Conduct, http://www.ryerson.ca/senate/policies/pol60.pdf
- Student Code of Non-Academic Conduct, http://www.ryerson.ca/senate/policies/pol61.pdf
- Undergraduate Academic Consideration and Appeals,
http://www.ryerson.ca/senate/policies/pol134.pdf
- Examination Policy, http://www.ryerson.ca/senate/policies/pol135.pdf
- Accom.of Student Relig., Abor. and Spir. Observance,
http://www.ryerson.ca/senate/policies/pol150.pdf
- Est.of Stud. Email Accts for Official Univ. Commun.,
http://www.ryerson.ca/senate/policies/pol157.pdf
Students are required to obtain and maintain a Ryerson Matrix e-mail account for timely communications
between the instructor and the students.
Any changes in the course outline, test dates, marking or evaluation will be discussed in class prior to
being implemented.
In-class use of cellular telephones is not permitted. Please turn off your cell phone prior to class. Quiet
use of laptops, text-messengers and similar non-audible devices is permitted only in the rear two rows of
class. This restriction allows use of such devices by their users while limiting audible and visual
distractions to other students. This policy may change without notice.
Assignments, projects and/or quizzes handed in past the due date and time will not be accepted for
marking and will receive a mark of ZERO, unless otherwise stated in the marking guides.
Students found to have plagiarized any portion of their laboratory reports will receive a grade of zero.

Course Developer ______________________

Date ______________________________

Approved by _______________________________

Date ________________________________

Associate Chair, Program Director

or Department Chair