8/29/2014 Laboratory Procedures

http://www0.egr.uh.edu/courses/ece/ece4436/support/laboratory/Laboratory_Procedures.html 1/2
Laboratory Procedures
ECE 4436

Laboratory Environment:
The Microprocessor Laboratory hardware and software environment consists of
several stations in S391D, each with:
Servo/Sensor/Motor Interface (SSMI) Board powered by a MCS912C32
microcontroller (MCU). One board is assigned to each lab team for the
semester.
BDM (Background Debug Module) with USB connection to PC and ribbon
cable connection to MCU on the SSMI Board. Used for downloading
program from PC to MCU, and for real-time debugging.
Freescale CodeWarrior Integrated Development Environment (IDE) on the
PC. CodeWarrior provides project management, source file editing, and
assembly of programs, plus debugging services via the BDM.

Obtaining your own Software:
Students should see Dr. Glover regarding obtaining a free student copy of the
CodeWarrior software to use on their own machines

Before you come to Lab:
Read relevant sections of notes and books.
Write the program source file using CodeWarrior or a text editor. Please DO
NOT write the initial source file in the laboratory!
Using your own copy of CodeWarrior, compile/assemble the program until
there are no compilation errors. Inspect the assembled code in the listing to
see if it looks correct.
Analyze your program and create a debugging plan. This plan should include
your planned test procedure, expected results, and debugging steps you will
immediately take if the program does not meet expectations.
Bring to Lab:
Your project directory, with source files (and object files if already assembled)
should simply be in your Windows network home directory, or on a flash
drive, to which you can connect from the laboratory computer. NEVER
leave any files on the local hard disk of the lab computers!
Test and Debugging Plan, written out.
Lab assignment sheet with directions, and Lab Check Sheet, if there is one.
8/29/2014 Laboratory Procedures
http://www0.egr.uh.edu/courses/ece/ece4436/support/laboratory/Laboratory_Procedures.html 2/2
Debug in Lab:
Using CodeWarrior, download your program to the MCU.
Follow your Test and Debugging Plan to test it, and then debug it when it
doesn't work properly. CodeWarrior provides excellent debugging services
through the BDM.
Thoroughly test your program in preparation for turning it in.
Fill out the Lab Check Sheet, if there is one, based on the operation of your
program.
Demo to TA in Lab:
The TAs hours in the lab for demonstrations are posted in the lab and on the
course web site.
Bring your completed Lab Check Sheet, if there is one. You will leave it with
the TA.
Bring to the lab a hard copy printout of your program listing (.LST listing file,
not the .ASM source file). You will leave it with the TA. (When you print
your listing (.LST), your should print in portrait format IF the comments
do not wrap to the next line. If they do, either shorten them or print it in
landscape format. The font should be large enough to read easily! Do NOT
double space your code or the listing!
Demo your program to the TA and answer questions regarding how it was
written and what it is doing.
Turn in:
Upload your compressed Assignment Folder to Blackboard Learn.
Instructions for doing so are in the document, "Turning in Programming
Assignments."
Your Assignment Folder should contain:
CodeWarrior project folder (named Lab1, Lab2, etc.) containing all
relevant files
Any other files called for by the assignment
The assignment folder would then look like, for example, the following:
SmithJonesLab1\ assignment folder
Lab1\ CodeWarrior
project folder
Other files or directories