yes...
even though u werent intended to do tat....
check the TB regs if u have initialized them
and it may cause a multiple driver.
this is one common mistake i usually do.....
if this is not the thing check the wire which is connected as an input to the output reg.
if tats X this is not a multiple driver case....
it may be synthesis issue also...
Hi,
1. what is post-simulaiton? do you mean post synthesis.
The most common cause of X in netlist(post synth) sims is uninitialized registers in your design.
The second most common cause of X in netlist is a register, which in RTL was reset, wont reset in netlsit.
You need to first see, if all the registers in your design, to which you have applied reset in RTL are actually being reset in netlist.
Due to the way synthesis is done, if you dont use 'set_sync_reset' attribute to your reset signal, then the register which are meant to be reset can go to X in netlist sims.
Kr,
Avi http://www.vlsiip.com
Hi,Avi!
post-simulation I mean refers to netlist+SDF+testcase-->run
I just replaced the RTL module with corresponding Netlist module one by one today. and find one module has problem.
I will try the ur suggestion
thx!
regards
Arthur
if u have sdf u shouldn't have a mix of netlist and RTL as netlist has delays(cell and path) and ur RTL doesn't. if u still need to have a mix of both use no timing checks option...
Here is some suggestions I can think of
1. check if it is multi-driven net
2. check if the driving flop don't have a reset in start up
3. check if there is timing violations occur if you are doing post-sim with annotated timing information
4. if there is unconnect interface signal