Write a Verilog traffic light controller FSM using three-process style with state…
- User
Write a Verilog traffic light controller FSM using three-process style with state register, next state logic, and output logic. Include a sensor input that triggers green to yellow transition only if a car is waiting.
- Assistant
Designing three-process traffic light FSM
Planning a Verilog FSM with separate always blocks for state register, next-state logic, and output logic, incorporating a sensor input that triggers green-to-yellow transition only when a car is detected, with parameterized timing counters for yellow and red states and a minimum green time before sensor-triggered transition. One common way to write a finite–state machine in Verilog is to separate it into three always‑blocks:
- a synchronous state register,
- combinational next–state (and any internal counter) logic, and
- combinational output logic.
The example below drives a single three–lamp head. It stays green until a car is detected on
sensor, then goes to yellow for a fixed number of cycles, then to red for a fixed number of cycles, and finally back to green. Minimum dwell times are parameterised:module traffic_light #( parameter integer GREEN_MIN = 20, // minimum green dwell in clock cycles parameter integer YELLOW_TIME = 5, // yellow dwell in clock cycles parameter integer RED_TIME = 10 // red dwell in clock cycles ) ( input wire clk, input wire rst_n, // active–low asynchronous reset input wire sensor, // high when a car is waiting output reg red, output reg yellow, output reg green ); // State encoding localparam [1:0] S_GREEN = 2'b00, S_YELLOW = 2'b01, S_RED = 2'b10; reg [1:0] state, next_state; reg [7:0] count; // counts cycles spent in current state //---------------------------------------------------------------- // 1. State register and dwell counter //---------------------------------------------------------------- always @(posedge clk or negedge rst_n) begin if (!rst_n) begin state <= S_RED; count <= 8'd0; end else begin state <= next_state; // reset the counter on state change, otherwise increment if (next_state != state) count <= 8'd0; else count <= count + 1'b1; end end //---------------------------------------------------------------- // 2. Next–state combinational logic //---------------------------------------------------------------- always @* begin case (state) S_GREEN: begin // Stay green until sensor is asserted and minimum green time elapsed if (sensor && (count >= GREEN_MIN-1)) next_state = S_YELLOW; else next_state = S_GREEN; end S_YELLOW: begin if (count >= YELLOW_TIME-1) next_state = S_RED; else next_state = S_YELLOW; end S_RED: begin if (count >= RED_TIME-1) next_state = S_GREEN; else next_state = S_RED; end default: next_state = S_RED; endcase end //---------------------------------------------------------------- // 3. Output combinational logic //---------------------------------------------------------------- always @* begin // default all lamps off red = 1'b0; yellow = 1'b0; green = 1'b0; case (state) S_GREEN: green = 1'b1; S_YELLOW: yellow = 1'b1; S_RED: red = 1'b1; endcase end endmoduleWith this coding style the
sensorinput is only consulted in theS_GREENstate; if it never goes high the controller will remain green indefinitely. When a car is detected and the minimum green time has elapsed, the FSM transitions to yellow and then red for their programmed durations before returning to green.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.