In reply to Po:
Anytime you send a TRX from the RAL to the DUT the bus2reg is called after monitoring the bus activity (now I’m now aware of your ENV structure).
Anyway
// You have something like this:
/*
REG_WRITE/READ -> REG_MAP -> ADAPTER_REG_2_BUS -> SEQUENCER -> DRIVER -> DUT
BUS_MONITOR -> PREDICTOR (if explicit and hooked up) -> ADAPTER_BUS_2_REG -> REG_ITEM -> REG in map
*/
-- according to this diagram you will be spotting 1 call only of bu2reg unless another TRX is coming or someone else is stimulating your BUS. This depends on your environment basically since there could be 2 or more clients trying to create some BUS activity or basically your BUS monitor is not properly handling the bus activity.
-- AHB for instance detects bus activity based on the HTRANS hence is unique per TRX
Regards