Announcements | Acknowledgments | Teams | Problem Specifications | Time and Location | Teaching Staff | Resources | Grading Policy | Course Policy

Announcements

• 181 Evaluation
• (6/4) Projects are due Tue 6/9. Oral presentations will take place Wed 6/10 10:30-1pm. Final reports are due Friday 6/12.
• (5/11) Final designs are due by the end of day on Friday 6/5.
• (5/11) Demos are due Friday 5/22 during lab hours (9am-12pm). Please contact your TA to reserve a 30 min slot.
• (4/7) Download a brief description of what you need to include in your design plan.
• (4/7) Design Review meeting: Tuesday April 21 10:30-11:50am. Each team will have 10 minutes to present their plan. Please prepare slides.
• (4/7) Design Plans are due Friday April 17 by 5pm.

Acknowledgments

• Our gratitude goes to Altera University Program for donating the boards, and supporting the course.
• We are greatly thankful to FPT Design Contest and Professor Hayden So for providing the problem specifications.

Teams

• Pleas refer to 181 Teams page for information on teams composition and TA assignments.

Problem Specifications

• Download the problem specifications. Note that the scoring scheme and the maximum puzzle size are slightly different than the FPT Design Contest.

Time and location

• Lectures: Tu 11-11:50am @GIEDT 1006
• Labs: MWF 9-11:50am @Kemper 2107

Teaching Staff

• Instructor:
  • Soheil Ghiasi
  • Office Hours: MWF 11am-12pm
  • Office Location: 3171 Kemper Hall
• Teaching Assistants
  • Faisal Khan (fnkhan AT ucdavis) Office Hours: T:1-2:30pm, F 2:30-4:00pm @Kemper 2107
  • Matin Hashemi () Office Hours: MF 9-10:30am @Kemper 2107
  • Naci Mete (anmete AT ucdavis)

Resources

• Sample Hardware Software Co-Design Involving Masters/Slave Avalon Integration and SRAM Read/Write operations: download Readme.pdf
• SOPC Modules download
• Sample UART code download
• Sample Puzzles: download 11_1p.txt 11_1s.txt
• Installing Quartus
• Baseline Implementation
• Using the SRAM: Doc, Project Directory
• Modelsim/Quartus II Tutorial and Lab Exercise
• NIOS II System Development and HW acceleration Example
• NIOS II Memory and Serial Port Interface
• DE2 board tutorials
• Educational IP Cores
• Nios II literature
• SOPC Builder literature
• Teams are allowed (and encouraged) to consult any other appropriate resource including relevant books, datasheets, webpages and knowledgeable individuals to enhance their understanding of the subject, and to excel in the project.

Grading Policy

• Design Plan %15
  • Algorithm %3
  • HW/SW partitioning and Implementation Plan %6
  • Performance Estimations and Expected Speedup %6
• Design Correctness and Performance %65
  • Correctness %40
  • Performance %25
• Presentation %20
  • Oral Report %10
  • Written Report %10

The grades for all items will be based on the performance of the entire team, however the grade of team members will be weighted based on individual contributions to the team effort.

Course Policy

• Prerequisites: EEC180B, and either EEC 170 or ECS 122A.
• Each team can check out an Altera DE2 board for the quarter, and can download development software from Altera webpage to work on the project (see installation notes).
• There will be minimal 'structured' lectures and lab assignments. Lectures are called only when needed. Labs are going to be open labs, in the sense that there will be no written description of the tasks for each lab period. Teams are responsible for formulating their plan, discussing with the teaching staff, and meeting the milestones.
• Team work and Dishonesty: All work must be done by the team, meaning done entirely by the team members whose name is on the work. However, asking other students (and anyother resource for that matter) conceptual questions and discussing high-level concepts are important steps in the learning process and are strongly encouraged. This is very different from giving or receiving aid related to a specific part of the design, which is not permitted. Copying someone else's work or allowing your work to be copied in any setting does not promote learning, is unfair to honest students, and WILL BE immediately reported to Student Judicial Affairs. Students that observe inappropriate activity should report what they see (anonymously if desired) to a TA or the instructor. Please consult the UC-Davis code of academic conduct or the instructor, if you have questions about the subject.