Bilkent University - Department of Computer Engineering

CS431 - Embedded Systems
Laboratory Experiments

	Out	Points	Lab Details	Lab Date	Solutions

1	Feb 10, 2011	100	F340 Tutorial - attendance required	Feb 10, 2011	Lab Tutorial
2	Feb 11, 2011	100	Timers, Interrupts and Digital I/O	Feb 17, 2011
3	Feb 17, 2011	100	Interrupts, Timers and Analog I/O	Feb 24, 2011
4	Feb 25, 2011	100	Generating PWM outputs	Mar 03, 2011
5	Mar 4, 2011	150	Frequency measurement and serial communications	Mar 10, 2011, Mar 17, 2011
6	Mar 25, 2011	100	Interfacing with incremental encoders	Mar 31, 2011
7	Mar 31, 2011	100	H-bridge motor driver circuit and firmware	Apr 7, 2011
8	Apr 14, 2011	100	Connecting a DC motor to the PC	Apr 21, 2011
9	Apr 26, 2011	150	Feedback Control of a DC motor	April 28, 2011 and May 5, 2011

Lab Groups

All laboratory experiments will be conducted by groups of two students unless otherwise specified. There will be no restrictions on who may be in your group so you are free to team up with the person of your choice

Some labs may require two groups to work together (i.e. 4 people total) since they will involve communication protocols and require two instances of the development boards to work together.

Logistics

All laboratory experiments will use the C8051F340-DK development kit and possibly additional external components. Since the experiments will involve significant embedded programming, you will probably need to work in the laboratory BB10 throughout the corresponding week. You will be expected to demonstrate your work at the end of the lab session on Friday.

Each development kit we have in the lab is marked with a serial number. Your group will be assigned one of these kits and you will need to check it out in exchange for your ID whenever you want to work on the experiment throughout the week. Each of these kits costs $70 (relatively cheap, actually, as far as embedded development boards go), so you should be careful in following appropriate procedures in handling them and interfacing them with external circuitry. The kits will be tested by the laboratory attendant once you return them to claim your ID and your group will be responsible from any damage caused to the board while it was checked out under your name.

Unfortunately, we will not be able to let the development kits be used outside the laboratory for the lab experiments.

Attendance

Failure to attend the laboratory session will only be tolerated under special circumstances such as a medical condition or family emergency. Furthermore, you are expected to show up in the beginning of the laboratory session on Friday. Once you demonstrate your work, you may leave, but it is unacceptable to come towards the end of the lab session and expect your work to be considered for grading.

Collaboration and Academic Integrity

You are expected to only work with your own labmate for the lab report and the implementation associated with each experiments. Do not copy any parts of any of these components from any other group. You can discuss your ideas and discoveries with your classmates, but you must provide your own answers and solutions to all the problems you are presented. The university policies on academic integrity will be applied rigorously.

Grading

Your lab grade depends on three components:

Your lab report, collected in the beginning of the lab session on Friday
Your demonstration, evaluated by the teaching assistant
Your source code, to be emailed to the teaching assistant at the end of the lab session.

Late submissions will not be accepted except under very special circumstances (affecting both partners, an unlikely occurence). Your source code submissions should be ZIP file containing everything necessary to compile and run the solution on whatever is the hardware setup that was available for the corresponding lab session.

Most of the lab assignment will rely on your own independent research, thinking and/or design efforts. Consequently, do not expect to find questions and problems where there is a single answer that you have to seek out, especially for design problems. Lab will take into account both your combined group effort in coming up with an answer, their appropriateness with respect to the questions as well as your individual contribution and familiarity with your group's solution.

saranli@cs, Uluç Saranlı
The overall design of this web page was inspired by similar pages by Frank Pfenning.

CS431 - Embedded Systems Laboratory Experiments