UVM Register sequence and register predictor.

[kiranbhaskar]

I have a small problem with my register sequence and register predictor.

I initiate the predefined test sequence provided by UVM for the reset check (uvm_reg_hw_reset_seq)

I am using explicit monitoring to update the register model.

I see that the the comparison b/w the DUT value and the register model value is happening at the start of the register access rather than the after the completion of the register access.

I have set the auto prediction to 1 .

Am i missing out on any configurations and is there a method to pull the register model to your waveform window to check the value reflecting the model

Regards,

kiran bhaskar

[janick]

It looks like the read() method does not block until it can return the readback data. Even with explicit monitoring, read() has a blocking completion model and should return the read-back data -- and thus wait until the the transaction has completed before returning.

[kiranbhaskar]

I did a small debug and i found that the problem is not with the read but it is with the mirror method.

When you use the mirror method with the read and check mode( UVM_CHECK)

The mirror method first does the check and then does the read.This throws me an error as the readback value is still not updated in the DUT.

Is this a bug in the UVM.

The mirror method should first read and then do the check as the read back value will be updated.

[lisakb1963]

I too have encountered this problem and tried all sorts of way to get rid of it. There is a Mantis Fix 3540, but I don't know if this will fix this or it's a separate Mantis Issue.