In reply to tejastv:
I just wanted to thank you all for the discussion and the good ideas!
I want to contribute with my two cents.
I find that this option discussed here is of big importance in the scenario of vertical reusability. I want to make it clear for those who haven´t seen it. It is a little bit different to the case exposed here.
Now, think about a scenario where you have verified a sub-module A which has e.g. protocol VC AHB to access its registers. You have written your scoreboard and your custom/quirky register classes for that AHB protocol and HDL level.
Then, you have at top module which is a wrapper of this sub-module A which has the same registers (and maybe more for other subblocks), but it uses a different VC protocol e.g. AXI. to access those registers. In other words, internally it will be converted from AXI to AHB.
In that scenario and for vertical reusability, you would like to just reuse your scoreboard and quirky register predictions.
You would like to just write/read your registers using AXI VC in your master sequence and use the predictions you already coded for AHB.
You know that inside the DUT you have the AHB interface for your subblock and you can reuse your scoreboard and the predictions of your registers.
Well, what you can do is to bind a module and interface (spy/backdoor the interface) inside the DUT and get the intern AHB monitor interface in the configdatabase.
Then, in your environment you can connect an AHB VC to that spied interface and use the scoreboard or the AHB adapter to predict correctly the AXI access to the registers. You can do this by following the indications of tejastv on the previous post.
In this case, your use one map and one AXI adapter for the master sequence (this AXI VC should not update the registermodel but just use the adapter to do reg2bus conversions-explicit prediction conf), and the second map and the second AHB adapter to connect the register predictor (which will do the real update and prediction of the register values from the AHB bus using explicit prediction).
Therefore, i think this post has touched a good point and it makes sense to do this.
