The Multicycle Datapath

Rodolfo Azevedo

Institute of Computing, University of Campinas (UNICAMP), Brazil

rodolfo.azevedo@unicamp.br

http://www.ic.unicamp.br/~rodolfo/mo801

Goal of this class

Module 2, Class 2: building a RV32I datapath one cycle at a time.

Last class was "what an instruction means." Today is "what hardware do we need to execute it, and why does it take more than one cycle." By the end, you'll have the component-level picture your Project 1 datapath needs to instantiate and wire together.

At the end of this class, you should be able to:

• Break any RV32I instruction into its fetch, decode, execute, memory, and writeback steps.
• Identify the hardware components of the multicycle datapath and the control signals that steer them.
• Draw the datapath diagram and trace the data flow for R-type, I-type, load, store, and branch instructions.
• Map datapath components (ALU, register file, memory, PC) to the SystemVerilog modules built in M01.

Why multicycle?

• A single-cycle datapath executes every instruction in one clock cycle - simple to reason about, but the cycle time must be long enough for the slowest instruction (typically a memory access), wasting time on every other instruction.
• A multicycle datapath breaks execution into several shorter steps (cycles), each doing one "unit" of work (a register read, an ALU operation, a memory access, ...). Different instructions take different numbers of cycles - simple instructions finish sooner.
• This matches our SystemVerilog toolkit directly: each cycle is one step of an always_ff-driven control FSM (M01A02's two-process pattern), and the datapath components are the combinational logic and registers it controls.

The five canonical steps

Most RV32I instructions can be executed as a subset of these steps:

1. Fetch: read the instruction word from instruction memory at PC; compute PC + 4.
2. Decode: split the instruction into fields (M02A01's formats); read rs1/rs2 from the register file; reassemble any immediate.
3. Execute: the ALU computes a result - rs1 + rs2, rs1 + imm, a branch comparison, an address, ...
4. Memory: for loads/stores, access data memory at the address computed in step 3.
5. Write-back: write a result into rd (the ALU result, loaded data, or PC+4 for JAL/JALR).

• ADD needs steps 1-3 and 5 (no memory). LW needs all five. BEQ needs 1-3 (compare, then conditionally update PC - no register write-back). Different instructions = different paths through the same steps.

The multicycle datapath — state elements

The datapath components

flowchart LR
    PC[PC register] --> IMEM[Instruction memory]
    IMEM --> IR[Instruction register]
    IR --> RF[Register file]
    RF --> ALU
    IR -->|immediate| ALU
    ALU --> ALUOUT[ALU result register]
    ALUOUT --> DMEM[Data memory]
    DMEM --> MDR[Memory data register]
    ALUOUT --> RF
    MDR --> RF
    ALUOUT --> PC

• PC, IR, ALUOUT, MDR: the "extra" registers a multicycle design needs beyond the architectural register file - they hold intermediate values between cycles, so each cycle's combinational logic only needs to look at the previous cycle's results.
• Register file: from M02A01 - 32 x 32-bit, x0 hardwired to 0. Typically one write port, one or two read ports.
• ALU: the same kind of module as M01A01's alu1, but wider (32-bit) and with more operations (add, subtract, compare, shift, AND/OR/XOR - enough to cover all RV32I ALU ops).
• Instruction memory / data memory: for Project 1, can start as simple synchronous-read logic arrays (BRAM-friendly) - see M01A04 for resource budget.

Complete multicycle datapath

Why the extra registers?

Consider LW rd, imm(rs1): address = rs1 + imm (an ALU operation), then mem[address] (a memory operation), then rd = mem[address] (a register write) - three operations that each take one cycle.

// Cycle 3 (Execute): compute the address
always_ff @(posedge clk)
    if (state == EXECUTE)
        alu_out <= rs1_val + imm;   // ALUOUT register captures the address

// Cycle 4 (Memory): use the captured address
always_ff @(posedge clk)
    if (state == MEMORY)
        mdr <= data_mem[alu_out];   // MDR register captures the loaded word

• Without alu_out and mdr, the address computed in cycle 3 would be lost by cycle 4 - it exists only as a combinational signal during cycle 3.
• This is the register + combinational logic pattern from M01A02, applied at the datapath level: every value that must survive to a later cycle needs its own register.

Control signals: the datapath's "knobs"

The datapath components don't decide anything by themselves - they're driven by control signals that the FSM (M02A03) sets each cycle:

• Each signal is one bit (or a small enum) computed by always_comb in the control FSM, based on the current state and the decoded opcode/funct3/funct7.
• This is the same enum + always_comb + case pattern from M01A02's FSM example - just with many more outputs per state.

Control signals per state — reference table

The FSM sets these signals on every clock cycle. A – means "don't care / unchanged":

• pc_write = cond in EXEC_BRANCH means "write PC only if the branch condition is true."
• This table is the specification for your Project 1 control FSM — each row becomes one case arm in always_comb.
• Signals left as – can keep their default value (set at the top of always_comb) — same discipline as the accidental-latch fix from M01A02.

Putting it together: one ALU input mux

typedef enum logic [1:0] { ALU_SRC_A_RS1, ALU_SRC_A_PC } alu_src_a_t;
typedef enum logic [1:0] { ALU_SRC_B_RS2, ALU_SRC_B_IMM, ALU_SRC_B_4 } alu_src_b_t;

logic [31:0] alu_a, alu_b;

always_comb begin
    case (alu_src_a)
        ALU_SRC_A_RS1: alu_a = rs1_val;
        ALU_SRC_A_PC:  alu_a = pc;
        default:       alu_a = rs1_val;
    endcase
    case (alu_src_b)
        ALU_SRC_B_RS2: alu_b = rs2_val;
        ALU_SRC_B_IMM: alu_b = imm;
        ALU_SRC_B_4:   alu_b = 32'd4;
        default:       alu_b = rs2_val;
    endcase
end

• alu_src_a/alu_src_b are control signals set by the FSM. The same physical ALU computes rs1 + rs2 (for ADD), rs1 + imm (for LW's address), PC + imm (for BEQ's target), and PC + 4 (for the next-PC default) - just by changing what feeds it.
• This is the heart of "multicycle": one ALU, reused across cycles for different purposes, instead of separate adders for each.

Instruction trace: ADD x3, x1, x2

Cycle-by-cycle walk-through (4 cycles total):

Control signals in cycle 3: alu_src_a=RS1, alu_src_b=RS2, alu_op=ADD, reg_write=0 (not yet).
Control signals in cycle 4: reg_write=1, result_src=ALUOUT, reg_dst=rd.

Every R-type and I-type ALU instruction follows this exact 4-cycle template. The FSM reuses the same states — only the alu_op and the source of alu_src_b differ.

Instruction trace: LW x3, 8(x1)

The most complex instruction — 5 cycles:

• MEM_ADDR is shared with SW — both compute rs1 + imm; the next state distinguishes load from store.
• MDR (Memory Data Register) exists precisely so the loaded value survives from cycle 4 to cycle 5.
• Without MDR, data_mem output would need to remain stable for two cycles — which is harder to guarantee and wastes a memory port.

In-class exercise — datapath trace

Exercise (10 min): trace SW x2, 12(x1) (store x2 to address x1 + 12) through the datapath.

Fill in the table:

Questions:

1. Which control signals differ from LW in cycles 3–4?
2. Does reg_write ever go high during SW? Why or why not?
3. Why does SW use only 4 cycles while LW uses 5?

Expected: FETCH → DECODE → MEM_ADDR (x1+12 → ALUOUT) → MEM_WRITE (data_mem[ALUOUT] ← x2). reg_write is never 1 — stores write memory, not registers. No WRITEBACK state needed.

Next class

Designing the Control FSM: the enum of states, the case-based control logic that drives every signal from the table above, and a cycle-by-cycle trace of ADDI, LW, and BEQ through the datapath.