- Project
Phase III (Due 04/09/10)
- Run
your vbsme.s assembly program over a test data using your single
cycle datapath.
- You
must use MIPS ISA. No other instructions are allowed.
- Testing
Procedure
- Hardcode
the machine code of your program into the instruction memory or
read it into the instruction memory from a file
- Initialize
your data memory with test data.
- Read
the frame size, window size, frame data and window data from
a file named "test_data.txt" into the data memory.
Input file must have the exact name "test_data.txt"
with the following format:
- first
line is number of rows for frame data (i)
- second
line is number of columns for frame data (j)
- third
line is number of rows for window data (k)
- fourth
line is number of columns for window data (l)
- followed
by i*j number of pixel values for frame data
- followed
by k*l number of pixel values for window data
- Sample
data
memory module and test
file (NEW)
- You
will need to test your code with 7 block sizes and various
image sizes sama as Phase2-PartA.
- You
will demonstrate the functionality of your code to the TA
for one image size and one window size. This will be 20%
of your phase 3 grade.
- TA
then will test your code offline for various test cases. This
will be 80% of your phase3 score.
- the
frame and window size are defined by the first 4 values in
the data memory file. therefore you will need to modify your
original assembly code so that you read those 4 values with
lw instruction. also, you may assume that for sure frame data
will start at address line 4 and you need to compute the starting
address of the window data based on frame size. (address =
i*j+4) this also requires new instructions to be added to
your assembly code. if you run out of registers, you may use
a0-a3. if
you hard code the address into the register file, your program
may not run when we change the frame size.
- Demonstration
must be done by April 9. After that 10pts
will be taken off each late day.
- TA
will test your projects offline. You will return your project
to the TA after the demo. He will then replace your test_data.txt
with our own test files.
- Make
sure to use the same naming convention
|