Prerequisites
ECE 4760 and ECE 4750, or permission of instructor. This course may be restricted to MEng students.
At the beginning of the class you need to know:

• Digital design using Verilog
• CPU design at the RTL level
• C programming
• Some electronic construction
• Ablity to find and read complex component data sheets.
  

Reading
Labs will be based on web pages and Altera documentation. We will expect you to become completely familiar with a large amount of detailed FPGA, NiosII, and MicroC/OS information from Altera. You will have to find, read, and apply appropriate information.

The book Rapid prototyping of Digital Systems -- SOPC edition by JO Hamblen, TS Hall and MD Furman is required. Buy online, for instance at Amazon.

Purpose
The purpose of this course is to enable its students to carry out sophisticated designs of digital systems using system-on-programmable-chip (SOPC) techniques, along with a variety of digital and analog interface technologies to build complex devices.

This course is a design course. This means that we will expect you to show considerable creativity, flexibility, and motivation.
In particular you will need to:

• Hit the web and even go to the library to find your own answers to questions you have.
• Read and understand every aspect of manufacturer's data sheets for a variety of devices.
• Use material from many of the courses you have taken. Dig out those old textbooks and stack them on the corner of your desk.
• Find solutions on your own from general, incomplete specifications. The lab assignments will be open-ended. Clever, efficient solutions will be rewarded. Detailed designs must be generated by the student teams before they get to lab. Designs will typically include C language code, digital circuitry designed in Verilog, and use of digital and analog peripherals.

Course Work

There will be lab assignments and a final project.

The course grade will be calculated as follows:

• 50% labratory assignments
  • You could lose up to 25% of the lab grade if you are not ready for lab.Ask lots of questions and read the material before lab. You are expected to be familiar with the assignment before coming to lab. Roughly 25% of your lab grade depends upon being prepared. Another 25% depends on the quality, quantity and character of the work done during the lab period. The remaining 50% will be based on your lab writeup. The same ratios (25, 25, 50%) hare used to evaluate the final project.
  • Lab assignments are due at the beginning of the next lab period.
  • No late assigments will be accepted without prior permission.
    (Except for sickness or family emergency)
  • A late assignment receives a ZERO grade.
  • Laboratory work will be done in groups of two where, of course, collaboration is encouraged between members of the group. You will turn in one report per team. No written collaboration between groups is permitted. You are (of course) encouraged to help anyone in lab.
• 50% for the final project. Final project grades will be assigned by rank-ordering all projects in all sections, thus you will be competing against everyone in the class for this grade. This means that staff will not be able to estimate your grade on this project until all projects are finished and handed in.
• If you feel that you have been unfairly graded, you have one week from the time the assignment is handed back to request a regrade. To request a regrade, you must submit the assignment with a written description of your concern attached to the instructor.

Laboratory Policies

You are expected to attend your assigned lab period every week and to finish the lab assignment in the alloted time. There is no makeup lab time available. You must finish the assignment in the alloted 3 hours, or you will lose up to 25% of your lab grade. All negotiations concerning lab absences due to plant trips or sickness are to be conducted with your lab instructor. For plant trips you must notify your instructor in advance.

Lab work will be in groups of 2. Both members are expected to become proficient with all aspects of the lab. Where each has prepared design work or code assigned as homework, the group design will involve negotiation. The members of a group may be graded differentially if it becomes obvious that one person is doing the bulk of the work.

Each student in this course is expected to abide by the Cornell University Code of Academic Integrity. Any work submitted by a student in this
course for academic credit will be the student's own work. For this course, collaboration is allowed between partners in a group.

In the event of a major campus emergency like an H1N1 flu outbreak, course requirements, deadlines, and grading percentages are subject to changes that may be necessitated by a revised semester calendar or other circumstances.More information about changes in this course will be available on the course web site if necessary.

Laboratory Reports

Each laboratory assignment requires a written report. You will submit a single report for your group. The report must be handed in at your assigned lab section, one week after the lab is finished. The report should be submitted as a collection of pages stapled or bound together.

The report should be a concise documentation of the project assigned. The presentation should be arranged so that any reader with technical competence in the subject can easily understand what was done and how it was done. The following report organization is suggested:

1. Introduction: Give a short explanation of what was done. This will include the homework assignment answers.
2. Design and Testing Methods: Explain the approach you used for both software and hardware aspects of the assignment. Be sure to include the design of tests whose outcome are convincing to the reader (or to the instructor in the lab) that the requirements of the assignment have been met.
3. Documentation: Include here drawings and program listings, together with any explanatory comments needed.
4. Answers to specific questions given in the lab writeups.
5. Comments: This optional section is for any comments the authors may wish to make concerning the assignment, including suggestions for improvement, excuses, and complaints. The purpose of this section is to encourage the writer to make the other sections clear, concise and understandable, and to reserve this section for creative comments.

A couple of example reports are from Idan Beck (1, 2).

Access to computers

You and your partner will have use of a PC, microcontroller evaluation board, and peripheral breadboard in Phillips 238 during your assigned lab period. Students from other lab periods may use setups not needed by students attending their assigned lab.

N.B. Machines and file systems sometimes die. You should always back up all your work. There is no excuse for lost work, even if it is because of a compiler or other system error.