CS/ECE 552 Introduction to Computer Architecture Spring 2012 Section 1 Instructor David A. Wood and T. A. Ramkumar Ravikumar URL: http://www.cs.wisc.edu/~david/courses/cs552/S12/

How Do I submit the code

• By 6 PM tomorrow, one member from every team needs to send me an e-mail letting me know which project member's handin directory will contain the code for demo I (NOTE: Only one team member needs to electronically handin code) Format for e-mail: The subject line should be [CS/ECE 552] Demo I handin directory (I will be using filters. Please ensure you have the same subject line)

• Code needs to be submitted into a directory called demo1 that is already created in your respective handin folders For instructions, you can refer to the slides here

What needs to be turned in electronically

• All your verilog files including any primitives you have used in the code (Please do not miss out any files. Do not assume that I will be using files from your HW)

• Vcheck outputs for all your *.v files (other than test-benches)

• Synthesis results (area and other reports).

Do I need to submit anything manually

• Like what we have already discussed, if you have not included the detailed project plan/schematics as part of your design overview, then you will need to manually turn this in. No manual copies will be accepted beyond Friday (03/22)

I have done something additional that I want the TA to know

• If at all this is the case, please include a README.txt and explain the issue briefly

Are there any exceptions to the due date/time

• The answer is NO. However, the final authority on this will be professor Wood. Please talk to him/let him know in case of any major issues

The proc_hier_bench.v needs clkrst.v to have a cycle_count variable. I do not find it

• Remember that you will have to use an updated clkrst.v file and not the ones you have been using for your project You can find that file here

I changed the proc_hier_bench.v logic (i.e., anything before line 118). Is that OK ?

• NO. You are not allowed to change the test bench. However, you are free to modify lines 119 and beyond as the file clearly says