C
Charles.Zhao
Guest
hi everyone,
My design is a complex IP written by verilog. Recently, I run
simulation on Questa 6.5b. But a wired situation occured, one of my
sub module's inner signal is always 'x' state from start of
simulation. I think it had been always 'x' state in every simulation
since we began our verification work, because our verification had not
reached this part of logic. Now I noticed this situation. The most
wired is that in source code, it just a normal always block. For an
example,
always @(*)
A = 1'b0;
While in waveform of Questa, It's a x state.
I am totally puzzled by this issue. How can become like this? Bugs for
Questa? Or a verilog gotchas? Hope for somebody's opinion.
Charles
My design is a complex IP written by verilog. Recently, I run
simulation on Questa 6.5b. But a wired situation occured, one of my
sub module's inner signal is always 'x' state from start of
simulation. I think it had been always 'x' state in every simulation
since we began our verification work, because our verification had not
reached this part of logic. Now I noticed this situation. The most
wired is that in source code, it just a normal always block. For an
example,
always @(*)
A = 1'b0;
While in waveform of Questa, It's a x state.
I am totally puzzled by this issue. How can become like this? Bugs for
Questa? Or a verilog gotchas? Hope for somebody's opinion.
Charles