Hello Leo, You are correct, use of custom RFNoC blocks is only supported on the rfnoc-devel branch at this time. The full RFNoC support will be exposed on the main branches in the future, the UHF 4.0.0.0 release is the currently planned time for doing that.
Regards, Derek On Wed, Apr 11, 2018 at 6:39 PM, Leandro EchevarrÃa via USRP-users < usrp-users@lists.ettus.com> wrote: > Hey everybody, > > I was able to make an example block by installing uhd+gr-ettus with > PyBombs rfnoc-devel recipes, then using rfnocmodtool, generating .xml and > .v files, and then "compiling and installing" the block from the > previously generated makefiles. > I also included the block in the FPGA code, and uhd_usrp_probe finds it > without an issue. > > The thing is this works only inside a sandboxed version of UHD (from > branch rfnoc-devel). If I run uhd_usrp_probe from my system version > (compiled from the last release of maint branch), the new block appears > only as Block_0. > > Is there any way for UHD v3.1.0.1 to recognize my block properly (beyond > its name, I'm of course intersted in it recognizing all its ports and > registers). I tried copying the .xml declaration file to > /usr/local/share/uhd/rfnoc/blocks/, but that doesn't seem to be enough. > Should I recompile some library? Or is there no other way than using > rfnoc-devel? > > Thank you again, > > Leo > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
