ECE 341 - Microcontrollers Lab (Spring 2014)
The laboratory exercises are closely coordinated with the lectures presented
in ECE 340. Successive assignments build on previous lab experiences. Most
labs have a pre-lab assignment that must be submitted at the
start of the lab period. The pre-lab assignments are
designed to motivate you to have a development plan or strategy thought out
before you commence coding the program. This allows the most efficient use
of the time spent with the instructors in the lab. Attendance is
mandatory for the entire lab period or until a fully
functional program is demonstrated to the instructor or Lab TA. Labs must
be completed in sequence and no lab can be started until all previous labs
have been completed. Students must work
A completed lab consists of the following:
Pre-lab report (if specified)
Demonstration of a fully functional program that meets the requirements of
the assignment. Must obtain instructor or TA signature.
A written report addressing the issues and / or questions identified in the
lab assignment, including any supporing material (screenshots, graphs, etc.)
Any other deliverables specifically requested (e.g., source code).
Lab grades are assigned based upon the following scale: A = 90-100%, B =
80-89%, C= 70-79%, D=60-69%, F= below 60%
Lab periods start at the time published in the UI time schedule. Students
who arrive late will lose 5% for that lab.
Pre-lab reports are collected at the start of the lab.
Labs reports are due at the start of the next meeting of your lab section,
unless otherwise specified on the lab web page.
Assignments submitted are to be the work of each individual student. All
Students who participate in plagiarism will receive a zero for the entire
lab assignment. Acts of plagiarism will be promptly report to the dean of
Lab 0 - Introduction to MPLAB and the Cerebot
MX7ck (required files). Lab report due in lab the
week of Jan 27.
Lab 1 - Digital Input and Output with
the Cerebot MX7ck (required files). Lab report due
in lab the week of Feb 3.
Lab 2 - Software Time Delay. Draft
of code collected at the start of lab. Demo both methods by Feb
7, 4 pm. Project Report file.
Report due in lab the week of Feb 10.
Lab 3 - Software-based Finite State
Machines. DFD of project software and CFD of Tasks 4-5 collected at the
start of lab. Demo by Feb 14, 4 pm. Report due in lab the week
of Feb 17.
Lab 4 - Multi-rate processing using
Timer 1. DFD of project software and CFDs of system_init(), main(), and
Timer1_delay() collected at the start of lab. Demo by Feb
21, 4 pm. Report due in lab the week of Feb 24.
Project report file.
Lab 5 - Process control using interrupts.
Demo by Feb 28, 4pm. Report due in lab the week of March 3.
Lab 6 - Handshaking and the LCD. Demo
and report due by Mar 14, 4pm.
Lab 7 - Asynchronous Serial
Communications. (Alert! Looks like a long one - yowza.)
- Lab 8 - I2C Serial Communications. I2C Triggering and Decode.
Demo single byte write/read/verify by 4 pm on Fri, Apr 4. Bring two
screen captures to class on Mon, Apr 7. Demo block write/read/verify by
4 pm on Fri, Apr 11. Bring report to class on Mon, Apr 14.
- Lab 9 - Pulse Width Modulation using Output Compare. Demo by 4 pm on Fri, Apr 25. Bring report to class on Mon, Apr 28.
- Lab 10 - Frequency Measurement using Input Capture. Demo by 4 pm on Wed, May 7. Bring report to class on Fri, May 9.
MPLAB and PIC32 Resources
(single zip archive)