RTL design is the craft of describing digital hardware in a hardware description language so tools can simulate it and later implement it. This is your home base for the rest of the course.
Register-Transfer Level — you describe how data moves between registers each clock, and what combo logic sits between them.
Register-Transfer Level = describe how data moves between flops each cycle.
You are both author and first QA. Shipping untested RTL is like publishing a book without spellcheck.
| Activity | Typical time | Output |
|---|---|---|
| Read spec / attend standup | 30–60 min | Clarified requirements, blockers listed |
| Code + local sim | 3–5 hrs | RTL diff + passing unit TB |
| Debug waves | 1–3 hrs | Root cause + fix or bug filed |
| Review (give/receive) | 1–2 hrs | Comments addressed in next commit |
| Lint / CDC / synthesis preview | 30 min | Clean reports or waiver request |
End standups with “open issues” — not just “still coding.” List: lint waivers pending, CDC review needed, TB not updated for M4.
Example of clean, synthesizable style you will practice — a loadable counter:
module load_counter #(
parameter WIDTH = 8
)(
input wire clk,
input wire rst_n,
input wire load,
input wire en,
input wire [WIDTH-1:0] din,
output reg [WIDTH-1:0] count
);
always @(posedge clk or negedge rst_n) begin
if (!rst_n)
count <= {WIDTH{1'b0}};
else if (load)
count <= din;
else if (en)
count <= count + 1'b1;
end
endmodule
// COMBO: always @(*) or assign — no clock, updates when inputs change assign sum = a + b; // SEQ: always @(posedge clk) — state updates only on clock edge always @(posedge clk or negedge rst_n) if (!rst_n) q <= 1'b0; else q <= d;
module fsm_two_process (
input wire clk, rst_n, go,
output reg busy
);
localparam IDLE = 1'b0, RUN = 1'b1;
reg state, next;
always @(posedge clk or negedge rst_n)
if (!rst_n) state <= IDLE;
else state <= next;
always @(*) begin
next = state;
busy = 1'b0;
case (state)
IDLE: if (go) next = RUN;
RUN: begin busy = 1'b1; next = IDLE; end
default: next = IDLE;
endcase
end
endmodule
Teammates understand intent without archaeology.
Maps cleanly to flops and gates.
Avoids accidental mega-combo clouds.
Observable, reset-clean, asserts possible.
<= in sequential blocks; blocking = in combo8'd0 not bare 0)#10) in synthesizable RTL“What makes RTL reviewable?” — Mention separation of combo/seq, FSM structure, reset, and tests included in the PR.
Mindset shift: you describe hardware structure and timed behavior, not algorithms in the software sense alone.
| RTL habit | Who benefits |
|---|---|
| Registered block outputs | PD — timing closure |
| Clean FSM + full case | DFT — scan insertion |
| Observable CSR status bits | DV — self-checking TB |
| Documented reset values | FW — driver init sequence |
“I’ll clean it up after it works” — cleanup rarely happens before tape-out pressure. Write review-ready RTL on the first commit.