It's true that uhd_image_builder.py will pull in all RFNOC IPs automatically, but if you go to simulate an OOT rfnoc block that relies on an IP, in my experience, you have to launch Vivado and add the UHD IP directory to your project.
On Mon, Sep 3, 2018 at 8:43 PM, Jon Pendlum via USRP-users < usrp-users@lists.ettus.com> wrote: > Hey Rich, > > Do you want to customize the FFT IP or use it as is? If you are using it > as is, there is no need to do anything. All in-tree code and IP is > automatically included as part of the FPGA build. If you want to customize > it, I suggest copying the FFT IP into your OOT and using > https://github.com/ejk43/rfnoc-ootexample as an example on how to add it > (see the rfnoc/ip directory). Use viv_modify_ip (available after you source > setupenv.sh) to customize the FFT IP. You'll want to rename it as well so > it does not conflict with the in-tree FFT IP. > > Jonathon > > On Tue, Sep 4, 2018 at 9:58 AM Rich Maes via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> Is there an example of modifying a out of tree (OOT) module and block to >> pull in a rfnoc library. Specifically I would like to pull in the AXI_FFT >> generated code and make my own custom FFT block. I can’t quite figure out >> how to modify the CMAKE files, (I assume that is the proper method) to >> reference that RFNOC library/source. >> >> Thanks in advance. >> Rich >> >> >> _______________________________________________ >> 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 > > -- Information contained, linked, or attached to this email and all verbal communications from WhiteFox Defense to your entity in the prior 30 days constitute proprietary and confidential information unless otherwise indicated and is therefore subject to obligations in any executed confidentiality agreements. Further, this email is intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient and this message has been addressed to you in error, please promptly notify i...@whitefoxdefense.com <mailto:i...@whitefoxdefense.com> and destroy all copies of the message and any attachments. This email and attachments may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10 or the Export Administration Regulations (EAR) 15 CFR Parts 730 – 780. Export of this material may be controlled by these regulations and may not be exported or transferred to non-U.S. persons without prior written approval from the U.S. government.
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
