mmit/d08203f60d3460a170ad8b3550b478113b7c5968>).
So I'm not exactly clear what the bus_clk was set to before that, or on
the rfnoc-devel branch...
But unless I'm misunderstanding, having multiple RFNoC blocks running at
a full 200 Msps might saturate the bus? Is that correct?
E
Hi all,
when working with RFNoC at 200 MSps on the X310 using 10GbE I
experience overruns when using less than 512 samples per packet (spp).
A simple flow graph [RFNoC Radio] -> [RFNoC FIFO] -> [Null sink] with
the spp stream arg set at the RFNoC Radio block shows the following
network utilizatio
Hi all,
when working with RFNoC at 200 MSps on the X310 using 10GbE I
experience overruns when using less than 512 samples per packet (spp).
A simple flow graph [RFNoC Radio] -> [RFNoC FIFO] -> [Null sink] with
the spp stream arg set at the RFNoC Radio block shows the following
network utilizatio
Hi all,
when working with RFNoC at 200 MSps on the X310 using 10GbE I experience
overruns when using less than 512 samples per packet (spp).
A simple flow graph [RFNoC Radio] -> [RFNoC FIFO] -> [Null sink] with the
spp stream arg set at the RFNoC Radio block shows the following network
utiliza
EJ Kreinar wrote:
You can find the "timeout on chan 0" message implemented in
gr-ettus/lib/rfnoc_block_impl.cc. As you suspected (correctly), it is a harmless output that
can be ignored if no data is actually coming from your RFNoC block. It is driven by
receiving a timeout from the streamer->
Hi all,
I have a custom RFNoC block which detects data packets in a stream of
I/Q-samples coming from a file source or the RFNoC Radio block. It only
outputs samples if it detects a packet, otherwise it does not output
anything. This works fine in simulation but when using the synthesized
blo
