University of Massachusetts, Amherst
Department of Electrical and Computer Engineering

ECE 353 - Computer Systems Lab I - Fall 2008

Course web site: www.ecs.umass.edu/ece353
ECE 353, Course No: 71976

---

Updates:

10/1/2008

• Course Email Archive has been updated. Updates can be seen here.
• Schedule has been updated. Updates can be seen here.

9/28/2008

• Course Email Archive has been updated. Updates can be seen here.
• Project 1 Lecture slides have been posted. Slides can be seen here.
• The following TA hours will be cancelled for this week:
     Felipe - Tuesday 2:30 - 6:30
     Michael - Wednesday 11:30 - 1:00
     Ivan - Wednesday 3:00 - 6:00

9/25/2008

• Project 1 Description added. Can be seen here.

9/23/2008

• Course Email Archive has been updated. Updates can be seen here.
     If you did not get these emails, please email Michael.

9/19/2008

• Course Email Archive has been updated. Updates can be seen here.
     If you did not get this email, please email Michael.

9/18/2008

• Course Email Archive has been updated. Updates can be seen here.

9/15/2008

• TA Hours changed. Can be seen here.

9/9/2008

• Professor Office Hours Updated.
• Course Email Archive has been updated. Updates can be seen here.
• Lab 0 Demo Presentation Slides posted. Can be viewed in Lab 0.

9/5/2008

•  Schedule has been updated. Changes can be seen here.
     First TA hours starts Tuesday at 2:30 PM.
•  Professor Lab Office Hours and TA Lab Hours posted.
     TA lab hours can be seen here.

9/4/2008

•  Altera ByteBlaster Datasheet added to Lab 0. Can be seen here.
•  Student Kit Inventory Partlist can be seen here.

9/2/2008

•  Lab 0 handout updated to show correct dates.
•  Schedule changed. Schedule can be seen here.
•  Lab 0 & Pre-Lab 0 Posted.
•  TA Schedules have been posted here.
•  Questionaire to be filled out can be downloaded here.
•  Course objectives vs. ABET Outcomes can be downloaded here.

---

Course description:

Design and analysis of digital systems using both hardware (Altera Complex Programmable Logic Device (CPLD) and Verilog) and software (Atmel AVR ATmega32 microcontroller, assembly language and C). The five labs will cover topics such as finite state machines, C programming, models of CPUs and memory in C and Verilog, and asynchronous and synchronous serial data communication. Emphasis will be placed on sound engineering practices, including team-based hw/sw development, debug, demonstration and documentation.

Prerequisite: C or better in ECE 232

Lecture Times: Tue and Thu, 1:00PM - 2:15PM, Room: TBA

Instructors:

•  Wayne Burleson - KEB 309 C, 545-2382, burleson@ecs.umass.edu
  Office hours: Tuesday & Thursday 2:00 PM to 3:00 PM for Labs 0 & 3 or by appointment via email
  
•  C. Mani Krishna - KEB 309 K, 545-0766, krishna@ecs.umass.edu
  Office hours: Tuesday & Thursday 2:00 PM to 3:00 PM for Labs 1 & 2 or by appointment via email
  

Technical Support:

• Keith Shimeld - ECE Trailer, tel: 545-3523, shimeld@ecs.umass.edu
  Shop hours: M-F 8:30-11:30 AM and 1:00-3:30 PM, ECE Trailer, southeast of the ELab I Building, north of the Gunness Lab.
  

Textbook: No official textbook is required for the course. All handouts and course materials will be posted on the course web site

UTAs :

• Michael Haines - mhaines@student.umass.edu
• Doug Frazer - dfrazer@student.umass.edu
• Ivan Bercovich - ibercovich@gmail.com
• Felipe Vilas-Boas - fvilasbo@gmail.com

Course Objectives:

1. Describe, design, and verify digital hardware using the VERILOG language

2. Use the C language to model digital components such as cache and pipelines.

3. Work in a team, learning how to partition tasks and share responsibilities.

4. Implement digital hardware such as synchronous and asynchronous serial interfaces using programmable logic as well as microcontroller peripherals

5. Program a microcontroller (AVR) in both assembly and C language

6. Demonstrate hardware and software-based embedded systems using a logic analyzer.

7. Document designs and the design process with formal written laboratory reports.

Lab Information:

• Lab 0 - Introduction to Altera
  
• Lab 1 - Cache Simulator (C)
  
• Lab 2 - Pipelined Machine (C)
  
• Lab 3 - IR Music Box (C & Assembly)
  

Each team will demonstrate the project to the instructor at a specified due time and will submit a report for each lab.

Lab Demo, Report Schedule and Grading:

• Lab 0 Due: Week of Sept. 22
• Lab 1 Due: Week of Oct. 13
• Lab 2 Due: Week of Nov. 3
• Lab 3 Due: Week of Dec. 1

The grades for demonstrations or reports received up to one week late will be reduced by 40%.

NO ASSIGNMENTS WILL BE ACCEPTED LATER THAN ONE WEEK AFTER THE DEADLINE.

Course Format
-------------------------
The course is composed of the Lecture section and the Lab section. The lectures will provide a detailed introduction for each lab project, will introduce Quartus software, and present tutorials for Verilog HDL, AVR, and WinAVR.

Software
-------------------------
We will issue software licenses of the Altera Quartus II and other tools for use on your personal computers at home so that you can perform most of the design and simulation work outside of the lab. The extended lab hours will be announced later.

Lab Organization
-------------------------
Each group will be assigned a workbench drawer and a key for their kits, including breadboard and parts. Logic analyzers and additional parts that you may need will be signed out with the TA. You should not leave your breadboard or parts unlocked in the lab; you will not receive a grade for this course if the kits are not returned by the end of the semester. You may take your breadboard and components out of the lab, but essential lab equipment (oscilloscopes, logic analyzer probes, etc.) and manuals are NOT to leave the lab.

Reporting Problems
-------------------------
Please report any problems you encounter with lab equipment, components, and breadboards to the TAs or the technician. Don't try to fix the hardware, or just move to a different logic analyzer or stuff the bad component back into your kit and have other groups encounter the same problems as you. Please take the extra time to make sure that the equipment gets fixed or the bad component gets identified.

Returning Equipment
-------------------------
Students take full financial responsibility for lab equipment signed out to them and understand that failure to return that equipment by the due date will result in a grade of Incomplete and possible administrative withdrawal.

Simulations
-------------------------
It is absolutely required that you simulate your design before wiring it up, using Altera's Quartus II simulator and other software. It is much easier to debug problems in your design through simulation than to try to find them in the prototype. This way you will spend less time in the lab, in front of a logic analyzer or oscilloscope, and more in front of a simulator on a PC at home or in the PC lab. You are required to submit a logic, block or circuit diagram (whichever appropriate) of your design with the report.

Project Demonstrations
-------------------------
When a group demonstrates a working design, we expect all partners to fully understand the design. Every member of a group is ``jointly and severally'' responsible for their group's entire report and demonstration, and is expected to have detailed knowledge of the entire lab, including those parts implemented by other members of the group. All partners may not necessarily receive the same grade if it becomes clear that one has done significantly more/less work than the other(s). You should work as a team. If you are the more experienced designer/debugger in the group, we expect you to provide some patience and help to your partner(s). If you are the less experienced designer/debugger, we expect you to work extra hard to learn.

Project Reports
-------------------------
Your report should include a thorough explanation of your design approach, with printed logic schematics, simulation results, and logic analyzer printouts. Reports should be typed using word processor, and include figures and schematics to illustrate your points. In addition, you should include a description of any problems you encountered during the debugging and how you resolved them. The intention of the latter requirement is not to inform us how bad your original design was or how hard you had to work to fix it, but rather to get you into the habit of keeping track of debugging problems. Finally, we expect all members to contribute equally to the project report, even though only one project report is required from each group.

Keep the Lab Clean
-------------------------
Please keep your workplace clean and shut off all equipment (logic analyzers, printers, PCs, etc.) when you are done working on it. Please clean up wire strips, paper, etc., from your work area; nobody else will do it for you. Computer paper must be recycled, so please place it in the designated bins outside the lab.

No Eating or Drinking in the Lab
-------------------------
Eating or Drinking in the lab is strictly prohibited. Eating or drinking in the lab is not only inappropriate, but may also cause contamination of the sensitive and expensive equipment, eventually leading to its malfunctioning. Any student caught violating this requirement will have the grade for the respective project reduced to 0 (zero).

Academic Honesty
-------------------------
We encourage students to discuss the design and debugging problems among the groups. However, there is a fine line between discussion of the problem and discussion of the solution. Each group must independently arrive at its own solution to each project. Exchange of software code, truth tables, state or gate diagrams scribbled on paper, partial or full schematics, parts of lab reports and the like is strictly forbidden and may result in your failing the course.

28Aug2008