55:036

Embedded Systems and Systems Software

Spring, 2006

 

Guidelines for Pre-labs and Lab Reports

 

PRE-LAB:

 

Points

5          A. The problem statement

15        B. The (hardware) circuit schematic with the components labeled.  You don’t need to show the entire QwikFlash schematic.  Just show the portions directly relevant to the objectives of this lab and any additional circuitry that you will need to supply.

15        C. All component values should be calculated and shown on the schematics (This applies only to additional components that you will add to the QwikFlash.)  You should also identify all relevant configuration and device settings required for the PIC processor.

15       D. Procedures to be undertaken in lab should be outlined, and blank data collection tables for use in performing the laboratory should be included, as needed.

20        E. Appropriately-commented source code should be included

70        Total Points

 

Pre-labs are due in class on the Tuesday of the first week of the two-week lab period  (Note: Lab 2 is a one-week lab).

 

 

LAB REPORT

 

Points

5          A. Introduction

15        B. The (hardware) circuit schematic with final component values should be

included  (See comments in the Pre-lab section above.)

35        C. Discussion of lab procedures undertaken; data tabulated as shown in the

prelab should be included

5         D. Conclusions, including discussion of any issues specifically identified in the lab assignment

20        E. Appropriately-commented source code should be included

20        F. Successfully meeting the laboratory specification (did it work?)*

100      Total Points

 

A copy of the pre-lab should be retained for your use during work in the laboratory and attached to the final report. Any deviation from, or changes to, the pre-lab specification should be noted. The discussion of lab procedure is the most important section of the lab report.  It should include a well-organized outline of the steps taken in lab along with sources of difficulties encountered and the solutions to these problems.

 

Lab reports are due in class on Thursday of the week following the lab.

 

*  IMPORTANT:  MAKE SURE THAT YOU DEMONSTRATE YOUR WORKING DESIGN FOR THE TA AND HAVE HIM/HER SIGN YOUR PRE-LAB COPY.  YOU WILL NOT RECIEVE CREDIT FOR A WORKING SOLUTION WITHOUT THIS SIGNATURE.


Due Dates for Pre-labs and Lab Reports

Spring, 2006

 

 

Lab 2 Pre-lab:              February  7

Lab 2 Report:              February 16

Lab 3 Pre-lab:              February 14

Lab 3 Report:              March 2

Lab 4 Pre-lab:              February 28

Lab 4 Report               March 23

Lab 5 Pre-lab:              March 21

Lab 5 Report:              April 6

Lab 6 Pre-lab               April 4

Lab 6 Report               April 20

Project Proposal:         April 13

Project Report:            May 4