Which brings up an interesting point. If you include an asynchronous reset for your flops, it turns out that the value to which you reset or preset your flops is actually used as the INIT value for the flop.
So, in the following example, FlopA initializes to 0 and FlopB initializes to 1, either because of the GSR assertion during configuration or because you yanked the reset line:

always @(posedge Clk or negedge Rst_l) begin : Flops
    if (~Rst_l) begin
        FlopA <= 1'b0;
        FlopB <= 1'b1;
    end else begin
        FlopA <= da;
        FlopB <= db;
    end
end // Flops