Why always blocks are needed in Verilog - Visual Breakdown

Concept Flow - Why always blocks are needed

Start Simulation

↓

Evaluate Inputs

↓

Trigger always block on event

↓

Execute sequential logic inside always

↓

Update outputs/registers

↓

Wait for next event

↩Back to Evaluate Inputs

The always block runs whenever specified signals change, allowing Verilog to model hardware behavior that reacts to input changes over time.

Execution Sample

Verilog

always @(posedge clk) begin
  q <= d;
end

This code copies input d to output q on every rising edge of clock clk.

Execution Table

Step	Event	Condition	Action	Output q
1	Initial	No clock edge	No action	x (unknown)
2	clk rises	posedge clk detected	q <= d (q updated)	q = d value
3	clk stable	No edge	No action	q unchanged
4	clk rises	posedge clk detected	q <= d (q updated)	q = new d value
5	Simulation ends	No more events	Stop	Final q value

💡 Simulation stops when no more clock edges occur.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
clk	0	1 (rising)	1	1	1
d	d0	d0	d1	d1	d1
q	x	d0	d0	d1	d1

Key Moments - 2 Insights

Why does the always block run only on clock edges?

Because the sensitivity list @(posedge clk) tells Verilog to run the block only when clk rises, as shown in execution_table rows 2 and 4.

Why can't we just assign q = d outside an always block?

Outside always blocks, assignments are continuous and combinational. To model sequential logic that updates only on clock edges, always blocks are needed, as shown by q updating only on posedge clk.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of q after the first clock rising edge?

A d0

B x (unknown)

C d1

D 0

💡 Hint

Check row 2 in execution_table where q updates to d value on posedge clk.

At which step does the always block NOT execute any action?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at execution_table row 3 where no clock edge means no action.

If we remove @(posedge clk) and write always @(*) instead, how would q update?

A q updates only on clock rising edge

B q updates continuously whenever d changes

C q never updates

D q updates only on clock falling edge

💡 Hint

Sensitivity list controls when always block runs; @(*) means run on any input change.

Concept Snapshot

always @(event) begin
  // sequential or combinational logic
end

- always blocks run when signals in sensitivity list change
- used to model hardware reacting to events (like clock edges)
- essential for sequential logic (flip-flops, registers)
- without always, can't model event-driven updates

Full Transcript

In Verilog, always blocks are needed to model hardware behavior that depends on events like clock edges. The always block runs whenever signals in its sensitivity list change. For example, always @(posedge clk) runs the block on every rising clock edge, updating outputs or registers. This lets us model sequential logic that updates only at specific times, unlike continuous assignments that update anytime inputs change. The execution table shows how q updates only on clock rises, and variable tracking shows clk, d, and q values changing over time. Beginners often wonder why always blocks run only on events and why we can't assign outputs outside them. The answer is that always blocks let us describe event-driven hardware behavior essential for real circuits.