Reply To: Dissecting the OSVVM AXI Master BFM
Why OSVVM™? › Forums › OSVVM › Dissecting the OSVVM AXI Master BFM › Reply To: Dissecting the OSVVM AXI Master BFM
HassanThe AXI4Manager source code contains these lines in the architecture declaration part:
signal WriteAddressFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal WriteDataFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal ReadAddressFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal ReadAddressTransactionFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal ReadDataFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal WriteResponseScoreboard : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal ReadResponseScoreboard : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
It is clear that these are being used as FIFO to accomodate latency in the system.
Then there is this:
signal WriteAddressDelayCov, WriteDataDelayCov, WriteResponseDelayCov : DelayCoverageIDType ;
signal ReadAddressDelayCov, ReadDataDelayCov : DelayCoverageIDType ;
What is the reason for the coverage being gathered inside this BFM rather than inside a monitor BFM?