|Assignment||Prelab?||Supporting Files||Due Dates|
Lab 0 template
Signoff due: Thu, 25 May by 7pm
Report due: Friday, 26 May by 11:59pm
|Lab 1||See assignment||
Lab 1 template
Signoff due: Tue, 6 Jun by 7pm
Report due: Wed, 7 Jun by 11:59pm
|Lab 2||See assignment||
Signoff due: Thursday, 16 Jun by 7pm
Report due: Friday, 17 Jun by 11:59pm
|Lab 3||See assignment||
Lab 3 template
String building examples
Signoff due: Wed, 28 June by 5pm
Report due: Friday, 30 June by 11:59pm
|"Lab 4"||None!||Submissions due: Fri, 30 Jun by 11:59pm|
Working on the labs
You will work on the labs during your scheduled lab section and on your own time. At the start of the lab section, the course staff will introduce the lab and discuss some important points about how to implement it. It is highly recommended that you attend your lab section to receive this information and so you have the chance to ask questions.
Our labs utilize the MSP430 development environment provided by Code Composer Studio (CCS). A fully-licensed copy of CCS is available on all of the lab computers in AK113 and the other ECE labs (AK227 and AK317), which have all the necessary resources for working on your labs.
If you want, you can also run CCS on your own computer, though this is not required. If you are interested, please see the appropriate section of the Resources page.
All labs have two separate deadlines: one for the completion of all signoff components, and one for completion of the report.
- Signoff deadlines
You may acquire signoffs for portions of the lab during your schedule lab time or during office hours. If you need a signoff outside these times, please contact the course staff to set up an appointment and we will do our best to accomodate you. After the signoff deadline, you may not receive signoffs for other portions of the lab–the goal of this is so that you can focus on writing a good lab report.
- Report deadlines
Lab reports are submitted electronically using Canvas. Your submission will include a copy of your report, and an archive of your code for the lab. Instructions on how to package your code for submission are included in the lab 0 assignment.
Lab report guidelines
See each assignment for details on what you should include in each report. Also, make sure you answer all of the questions asked in the assignment!
You can view an example lab report here. Note that this report provides an example of the general structure and content you should include–you do NOT need to copy its exact formatting!