Activity

Hi Jim,

We have resolved the issue. We checked our other components and found out that the one causing the error is in the test.

We are truly grateful for your help.

Thank you very much.

Regards,
Cols

Hi Jim,

Thank you very much for responding. We are currently debugging and we are doing the method you suggested when our simulator does not support interactive debugging. Please check our reply.

Thank you.

Regards,
Cols

Hi Cols and Nico,
This brings up a bigger question, “how do we debug our simulations when something like this happens?”

First observe the time at which something happens. Look at what transactions were running before that time.

If our simulator supports interactive debugging such as single step and/or breakpoint, then the following may help…[Read more]

Hi Cols and Nico,
Did you look at TbAxi4_Shared1.vhd? Each instance of the VC needs to have its own record. See TestCtrl_e.vhd in the same directory.

Send me an email with your TestCtrl in it. It would probably be good to see your test harness also.

Best Regards,
Jim

Hi Jim, we have done your suggestion but still encounter the Failure error.

It can still read multiple drivers per process even if we declared it separately.
Do you think it is advisable to finish all transactions first on the first instance of axi stream receiver before proceeding to the transactions of the 2nd axi stream receiver?

Thank you…[Read more]

Hello Jim!

Thank you very much for the very informative response.

We will apply what we have learned.

Best regards,
Nico

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…[Read more]