Hi Alexey, Your initial testing with rfnoc_graph::make() is the way to connect in UHD4. You cannot use multi_usrp (in UHD 3 or UHD 4) because this class creates a fixed rfnoc_graph that does not include your OOT block. Therefore, in order to use your OOT block, you need to use the rfnoc_graph::make() and the various controllers (Radio / DDC / DUC / etc) to control the streaming. You can look at the Ettus "multi_usrp_rfnoc" class source code to see how Ettus handles an RFNoC graph from within multi_usrp for inspiration. Rob
On Wed, Jul 20, 2022 at 5:42 AM Alexey Kosinov via USRP-users < [email protected]> wrote: > Hello! > > I created oot-module that have some registers and stuff. > I tested it (through *uhd::rfnoc::rfnoc_graph::make()* and so on … ) > works fine! > Now i want to include that module into the open source project that use > *uhd::usrp::multi_usrp::make(**)* instead of > *uhd::rfnoc::rfnoc_graph::make()* to create the device object and that > was i part where i completely lost. > I cannot create both objects. > I saw some people used device3 library that dissapeared in the uhd 4. > My question is how can i get access to oot-module (find_blocks, get_blocks > and eventualy read/write some data to it) like i did it before, using > standalone app (rfnoc-example/apps/init_gain_block.cpp for example)? > Is there is possible in the uhd 4? > If there is so can you provide simple example > > USRP N300 > uhd 4.1.0.4 > > Thanks! > > > Best regards, > Alexey Kosinov > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
