Hi,
In case anyone finds this unresolved entry, I think I found the error I was
making, it probably had to do with thread handling. I would recommend
always creating a thread group (boost::thread_group tg), and then calling
two separate threads, one for RX
(tg.create_thread(boost::bind(&receive_th
Hi Rob,
Thanks again for your response. Enabling UHD logging didn't give much more
information about my "No upstream blocks." message or about anything that
might give any clues to make the program work.
I'll attach my .cpp in this mail in case anyone sees anything off with it
(as a quick reminde
Hi Jorge,
I don't immediately see what the problem is. I can tell you that it is
certainly possible to do what you are doing. You can do so with as few as
one rfnoc block or you can use a chain. I have done this often.
Typically, after I verify my custom rfnoc block with a testbench, I will
buil
Hi Rob,
Thank you for your quick response. I'm sorry if I didn't specifically
mention that. I did connect the blocks calling the connect() function like
so:
uhd::rfnoc::graph::sptr txrx_graph = usrp3->create_graph("txrx");
usrp3->clear();
txrx_graph->connect(dmafifo_blockid, 0, gain_b
Hi Jorge,
I don't see any indication that you are calling the Connect() function to
connect the RFNoC blocks in the FPGA.
Rob
On Mon, Nov 9, 2020 at 1:35 PM Jorge Arroyo Giganto via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Hi all,
>
> After testing a loopback in GNU Radio with a custom b
Hi all,
After testing a loopback in GNU Radio with a custom block (the gain example
from the Getting Started with RFNoC guide), I managed to get the samples
going from the host to the "RFNoC domain" and back to the host, without
involving the radio cores at all. My flowgraph was Signal Source (Hos
