On Tue, Apr 8, 2025 at 9:45 AM Kevin Williams <kevin.willi...@vastech.co.za>
wrote:

> Hi Martin,
>
>
>
> This is interesting feedback.
>
>
>
> On the streaming, I am using a python create_rx_streamer() directly on the
> graph to the connected to the 1 or 2 outputs of my new rfnoc block, like
> this:
>
>
>
> g_graph  = uhd.rfnoc.RfnocGraph("type=n3xx,addr=10.20.101.1")
>
> stream_args   = uhd.usrp.StreamArgs("fc32", "sc16")
>
> g_rx_streamer = g_graph.create_rx_streamer(2, stream_args)
>

This is good practice!


> I was not aware of the need for forking streaming commands, and I am not
> sure how to do this. I will try and find info in the docs, but if there is
> anything special to know it would be very valuable. (I can compile UHD by
> hand, and have been doing for certain debugging.)
>

My terminology was a bit weird, we usually don't call it forking. I was
doing something fork-related earlier. This is what the addsub block does:

https://github.com/EttusResearch/uhd/blob/master/host/lib/rfnoc/addsub_block_control.cpp#L39

Docs:
https://uhd.readthedocs.io/en/latest/classuhd_1_1rfnoc_1_1node__t.html#a25106f8698788e5882b8354ba8c0efc6

"one_to_fan" means that a stream command on one input will be forwarded to
all outputs (or vice versa). The default is "one_to_one", which will
forward the stream command only to one opposite port.


> On the “consuming of samples” I am under the impression that by me
> asserting TREADY an upstream block will consider that sample “consumed”,
> and of course, I do this on both streams from the (single) radio on the
> N300?
>

That's correct!

--M
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to