Hello Matthias, thanks for the feedback. We are planning to add such file structure near in the future. Please have a look at this example [1] which you can adapt to your OOT module in order to add the IP. Keep in mind that rfnocmodtool as of now generates both the Makefile.srcs and the Makefile.inc files in order to support the legacy OOT modules versions.
Additionally I think in one commit a few days ago to the noc_block template > a “.” before set_time() is missing. This leads to an error while building > an image with a fresh OOT. Yes, we are aware of this and has already been fixed. It just needs to be pushed public. Regards, -Nicolas [1] https://github.com/ejk43/rfnoc-ootexample/ On Sat, May 19, 2018 at 1:24 PM, Matthias Schraml via USRP-users < usrp-users@lists.ettus.com> wrote: > Hi all, > > > > creating RFNoC-OOT without Xilinx IP blocks works fine, but somehow I > struggle with adding the Xilinx IP xcix files from Vivado to the RFNoC-OOT. > > The rfnocmodtool creates a Makefile.srcs (manually modifying this file is > not recommended according to the tutorial). In contrast, some other > RFNoC-OOTs use Makefile.inc files. So am I supposed to create these > Makefile.inc files manually and how do I add xcix files? > > It might be useful to have an “add-ip” (or “add-hls”) function in the > rfnocmodtool to create the Makefiles and the folder structure for Xilinx IP > blocks or HLS files. > > > > Additionally I think in one commit a few days ago to the noc_block > template a “.” before set_time() is missing. This leads to an error while > building an image with a fresh OOT. > > > > Thanks in advance for your help! > > > > Best regards, > > Matthias > > > > _______________________________________________ > 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