My new logic appears to have solved the issue of cleaning up the unequal
length streams coming from the radios. So, my block is not getting into
this bad state anymore.
However, just to finish up this discussion, I don't think that the warning
is solely related to the output ports (which is how I
I like your first idea. To get rid of the warning, I think your block just
needs to finish the last packet cleanly on each output port (i.e., TLAST
needs to be asserted on the last word written to the NoC shell). The second
idea will probably work too, but it won't necessarily get rid of the
warnin
Thanks Wade,
So, I get what you are saying in general but I'm still not clear on
specifics.
My custom block is a multi-port pulse detector with an equal number of
input and output ports. The idea is that the radios stream Rx samples on
multiple ports to my block in a single continuous burst. My b
I believe RFNoC tries to flush any partially transmitted packets out of
blocks during initialization before resetting them. The idea is to get rid
of any leftover data that might still be in the data pipes. I think a
timeout means the noc_shell never saw the end of the last packet before the
timeou
Hi,
Using RFNOC 4.0 with a few of my custom blocks, I get the following warning
at UHD startup (after having run it at least once before):
[WARNING] [RFNOC::GRAPH] One or more blocks timed out during flush!
I'm confident it is something that I'm doing incorrectly with my block, but
I'm wondering
