CS 2734 Computer Organization II

• You should implement the remaining MIPS simulator components: (Refer to Fig. 5.29 on page 372.) Notice that you should already have completed the ALU, the Register File, and the Instruction Register components, so that 4 more components remain. You should finish this lab as soon as possible, so that you can start on the full-blown simulator (Lab 11).
  • ALU: Use header file mipsALU.h. (Already implemented as part of Lab 8.)

  • Register File: Use header file mipsRegFile.h. (Already implemented as part of Lab 8. This register file occurs midway in the simulation, and then a second time in case a register must be written.)

  • Instruction Memory: Use header file mipsInstrMem.h. (Here you also need to load the memory: read instructions from another file, storing 32-bit words in successive locations in and array. Then, given the input instruction address (the PC), divide it by 4 and fetch the instruction at that array index.)

  • Instruction Register: Use header file mipsInstrReg.h. (This is a component not shown in Fig. 5.29. It takes an input instruction and tears it apart into separate fields. Note that some fields overlap.)

  • Control: Use header file mipsControl.h. (This just implements Fig. 5.27 on page 370. Note that I have combined ALUOp0 and ALUOp1 into one 2-bit integer. You need to add a j instruction with op = 2 that will only assert the Jump control line.)

  • ALU Control: Use header file mipsALUControl.h. (This just implements Fig. 5.15 on page 356.)

  • Data Memory: Use header file mipsDataMem.h. (This is the rightmost component in Fig. 5.29.)

• Here are the actual header files as a starting point for creating each simulator component in turn:
  • mipsALU.h
  • mipsRegFile.h
  • mipsInstrMem.h
  • mipsInstrReg.h
  • mipsControl.h
  • mipsALUControl.h
  • mipsDataMem.h

• You may check each component off separately. You must show your source code for the component when you get it checked off.