cascade
cascade copied to clipboard
Passing clock.val to modules in a generate statement causes unexpected shutdown
Bug report
When clock.val is passed to a module in a generate statement, Cascade throws the error CASCADE SHUTDOWN UNEXPECTEDLY. Expected behavior is for the clock to be propagated normally to each module. In the below example, excluding the clk input to the EX module works fine (no problem with the foo input); only when clock.val is passed in does the shutdown occur.
Using version with commit ID f14c2de0b50e33a9df97d76a9a522f4bc267f63b.
module EX(
input clk,
input foo
);
endmodule
wire [1:0] somefoo;
genvar i;
generate
for (i = 0; i < 2; i = i + 1) begin
EX ex(
.clk(clock.val),
.foo(somefoo[i]),
end
endgenerate