Yeah but if I change the upper limit of the transmit and receive loops to
be 256, none of the results come back from noc_block_addsub.
On Sat, Feb 8, 2020 at 15:50 Nick Foster <bistrom...@gmail.com> wrote:
> The NOC bus is 64 bits wide. This means each item in the testbench data
> array is 2 samples {16i, 16q, 16i, 16q}. The testbench is failing because
> you're reading past the end of the input data array.
>
> On Sat, Feb 8, 2020 at 5:04 AM Andrew Payne via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> Hello,
>>
>> I'm running and slightly modifying the simulation testbench for the
>> RFNOC addsub module. I've noticed that the for loop in test case 4
>> goes to SPP/2 - that upper limit is what I'm modifying to learn how
>> packets work in the NOC shell. So it passes as a stock testbench, and
>> after modifying it to run to SPP (256), the entire test case 4 fails,
>> with every return from the noc block being "x" (undriven as I
>> understand it). Why does the test fail when I increase the upper
>> limit of tests?
>>
>> Thanks,
>> Andrew
>>
>> _______________________________________________
>> USRP-users mailing list
>> USRP-users@lists.ettus.com
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
