CS/ECE 552 Intro to Computer Architecture Spring 2020 Section 1
Instructor Matthew D. Sinclair
URL: http://www.cs.wisc.edu/~sinclair/courses/cs552/spring2020/

Project

Links to specific parts of webpage:

Due Dates

  • Form Project Team: Due 1159PM Friday, February 14th (1% of project grade)
  • Design Review: Due 1159 PM on Monday, February 24th (4% of project grade)
  • Phase 1: Due 1159 PM on Friday, March 13th (15% of project grade)
  • Phase 2: Due 1159 PM on Friday, April 3rd (30% of project grade)
  • Phase 2.3: Due 1159 PM on Friday, April 17th (10% of project grade)
  • Phase 3: Due 1159 PM on Friday, May 1st (30% of project grade)
  • Final Report: Due 1159 PM on Tuesday, May 5th (10% of project grade)
  • Extra Credit: Due 1159 PM on Tuesday, May 5th

Overall Weight: 30%

Important Documents

Project Goal

The CS/ECE 552 term project is the complete functional design of a microprocessor called the WISC-SP20. All components of your design will be written in Verilog. As with the course homeworks, the CS/ECE 552 Verilog restrictions apply, and all final code is expected to pass the Vcheck program.

The project will be completed in groups of two. Each group must contain at least one person who has not taken ECE 551 already. You can self-signup for your group on Canvas using the "Student Groups" tab under "People".

The specifics of the microarchitecture and WISC-SP20 architecture are posted above under "Important Documents."

The project will progress in several distinct stages. Some of these stages are enforced through grading deadlines; others are not. The key deadlines are listed above.

Unless approved by the instructor in advance, you may turn in each phase of the project up to 48 hours late, with a 10% penalty per day, up to two days max. Any submissions over two days late will receive a zero. I strongly recommend that you do not avail yourself of this option; your hard work deserves full credit. Additionally, your group will also be allowed three "free" late days for the project. If you need these free late days, I strongly advise you to utilize them for the coding phases (Phases 1-3).

Relevant Course Webpages

Important Notes

  • Start early: This project is designed to take a considerable amount of time.
  • Plan ahead: You may find that the instructor, TAs, and/or peer mentors will be very inaccessible the night before a deadline.
  • Ask questions: If you are getting stuck on some problem ask for help. Ask me, the TAs, the peer mentors, or your classmates.
  • Functionality: Getting a working design is of paramount importance. Optimizations, clock-speek and bonus questions come 2nd. First make sure your design works!

Presentation and Writing Resources

 
Computer Sciences | UW Home