Description

• MP#1

• regstim.v - the example testbench

This machine problem is the first foray into building your very own processor. Please work in the same teams as MP#0, and read the machine problem description carefully -- it's a long one!

MP#1 Demo

Important Information

• All demos will take place in the East Hall first floor team rooms.
• All members of your team should try and show up. If someone cannot make it, we should know ahead of time.

• The test cases we will be testing with are right here --> regfile_test_cases.zip

  • These are the exact stimulus files we will be using during the demo of your machine problem. Please download them and make sure they run through your system. If your register file is not correct, I suggest you and your team investigate the reason for the problem so you may discuss with us what you think the issue is with your design.

• You may not change your code after you turn it in.

• If you are not done with your code and you are taking a late penalty, do not use these stimulus files! You must turn in your machine problem write-up first.

• If your team does not demo the lab, you get zero points.

Grading Rubric

This is a loose rubric, with no points or weighting assigned.

• The goal of the demo is for the team to demonstrate, collectively, that their register file works correctly.
• If the register file does not work correctly, we will shift gears to assess the team's ability to diagnose a problem on the fly. Solving the problem is not paramount, but making intelligent diagnosis and demonstrating the ability to effectively find the source of a problem is important in making up ground lost in functionality.
• Evaluation will be through the use and explanation of the team's test cases and our own test cases (attached below).
• We will also be evaluating team member contributions to the technical effort.
• Finally, we will be looking over the final report for a level of detail and understanding we can't assess in the demo.

Think of it this way. If it goes swimmingly in the demo, you will probably do great, grade-wise. If it breaks, then we will rely more on your write up to find points.

In more detail, we will test:

• register zero does nothing, but returns zero all the time
• read and write every register
• glitching on write-enable signal
• ability to read two registers and write one simultaneously

also:

• teams should walk through the test benches, not the code
• how long did the lab take?
• how did the team break up the work?

The times we have available are the below. If these times do not work for you, please email me and John (together) and we will work out a time for you.

JohnMorgan Hours

MarkChang Hours

---

• [get | view] (2007-10-02 13:38:41, 407.1 KB) [[attachment:mp1.pdf]]
• [get | view] (2007-10-06 23:48:06, 2.0 KB) [[attachment:regstim.v]]