Reply To: AxiStreamReceiver: Multiple Drivers on Transaction Record.
Why OSVVM™? › Forums › OSVVM › AxiStreamReceiver: Multiple Drivers on Transaction Record. › Reply To: AxiStreamReceiver: Multiple Drivers on Transaction Record.
![](https://osvvm.wpenginepowered.com/wp-content/uploads/avatars/11/4f2d90293ce57ed989d616466bef786b-bpfull.jpg)
Hi Gianico,
Each AxiStreamReceiver needs its own transaction record. In the OSVVM testcases, we are using a single record named StreamRxRec. You need separate ones, such as StreamRx1Rec and StreamRx2Rec.
There is an example of this done with the Axi4 interface. See directory OsvvmLibraries/AXI4/Axi4/testbench_MultipleMemory. In there see the test case TbAxi4_Shared1.vhd which uses Manager1Rec and Manager2Rec. The test harness, TbAxi4_MultipleMemory.vhd, also uses the same names.
The whole purpose of the multiple driver error message is that when you cut and paste pieces of code in this environment, it is easy to forget to use the transaction record that corresponds to the process that drives it.
Generally speaking then, a given record only driven by a single process. We have a methodology to allow that to stop driving a record in one process so another process can drive it, but that is not the case you are looking at.
Best Regards,
Jim