Hey Martin Braun, First off, I want to thank you guys at Ettus Research for making the tutorials on the wiki and on Github, they're both been really helpful as I'm learning rfnoc. Anyways,I've been doing the new tutorial linked above, but I can't get the final part-building the image to work. rfnocmodtool works fine, I can run flowgraphs with rfnoc blocks in them, but only using the master image, after using uhd_images_downloader and uhd_image_loader. I don't know if rfnoc has been updated (especially since the wiki page was only posted a few days ago!), but it seems like make.py isn't added yet? I've searched the directory fpga-src/usrp3/tools/scripts in both rfnoc-devel and rfnoc-radio-redo, and couldn't find it. Currently, I've been using make in usrp3/top/x300 to build, but that fails (I haven't had enough time yet to debug it, but I've tried once using my custom practice block and another time without it to double check). Thanks, Rich McAllister On Tue, Jul 12, 2016 at 5:04 PM, Martin Braun via USRP-users < usrp-users@lists.ettus.com> wrote: > As more and more people use RFNoC™, we want to make it easy for people > to actually develop and distribute RFNoC code. > > For those using GNU Radio, we have some more updates: If you pull the > latest gr-ettus, it includes a tool called 'rfnocmodtool' (if you think > this sounds a lot like gr_modtool, you're right. It's based on that). > > This way, you will be able to create RFNoC out-of-tree modules very > quickly, won't have to copy stuff into the the UHD and/or FPGA > repositories, and can more easily track your code and distribute it via > public git hosting services. > > Version 1 of a tutorial for this is here: > https://kb.ettus.com/Getting_Started_with_RFNoC_Development > > In a nutshell, this lets you do the following: > - Create an OOT module (e.g., gr-myrfnocstuff) > - Create all boilerplate for Verilog, testbenches, block controllers etc. > - Link your modules into an RFNoC design > > I'm sure there'll be questions, and we'll be updating this page as we go > along. > > Side note: Why are we making a new tool, and not simply using > gr_modtool? We hope that we can consolidate these in the future, but > gr_modtool is not really set up to support multiple types of OOT modules > at the moment. For now, we don't want to pollute people's systems with > stuff they don't need, so if you don't install gr-ettus, you won't get > any RFNoC-related tools installed. > > Cheers, > Martin > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >

Hello Richard, Thank you for your feedback on this. You're right, the make.py has not been added yet, but it will be added soon! The documentation is there because the code is ready. However, it is yet to be included in the next merge. We'll let you and everyone know when it is all set. Cheers, Nicolas On Thu, Jul 14, 2016 at 6:39 AM, Richard Mcallister via USRP-users < usrp-users@lists.ettus.com> wrote: > Hey Martin Braun, > > First off, I want to thank you guys at Ettus Research for making the > tutorials on the wiki and on Github, they're both been really helpful as > I'm learning rfnoc. Anyways,I've been doing the new tutorial linked above, > but I can't get the final part-building the image to work. rfnocmodtool > works fine, I can run flowgraphs with rfnoc blocks in them, but only using > the master image, after using uhd_images_downloader and uhd_image_loader. I > don't know if rfnoc has been updated (especially since the wiki page was > only posted a few days ago!), but it seems like make.py isn't added yet? > I've searched the directory fpga-src/usrp3/tools/scripts in both > rfnoc-devel and rfnoc-radio-redo, and couldn't find it. Currently, I've > been using make in usrp3/top/x300 to build, but that fails (I haven't had > enough time yet to debug it, but I've tried once using my custom practice > block and another time without it to double check). > > Thanks, > Rich McAllister > > > > On Tue, Jul 12, 2016 at 5:04 PM, Martin Braun via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> As more and more people use RFNoC™, we want to make it easy for people >> to actually develop and distribute RFNoC code. >> >> For those using GNU Radio, we have some more updates: If you pull the >> latest gr-ettus, it includes a tool called 'rfnocmodtool' (if you think >> this sounds a lot like gr_modtool, you're right. It's based on that). >> >> This way, you will be able to create RFNoC out-of-tree modules very >> quickly, won't have to copy stuff into the the UHD and/or FPGA >> repositories, and can more easily track your code and distribute it via >> public git hosting services. >> >> Version 1 of a tutorial for this is here: >> https://kb.ettus.com/Getting_Started_with_RFNoC_Development >> >> In a nutshell, this lets you do the following: >> - Create an OOT module (e.g., gr-myrfnocstuff) >> - Create all boilerplate for Verilog, testbenches, block controllers etc. >> - Link your modules into an RFNoC design >> >> I'm sure there'll be questions, and we'll be updating this page as we go >> along. >> >> Side note: Why are we making a new tool, and not simply using >> gr_modtool? We hope that we can consolidate these in the future, but >> gr_modtool is not really set up to support multiple types of OOT modules >> at the moment. For now, we don't want to pollute people's systems with >> stuff they don't need, so if you don't install gr-ettus, you won't get >> any RFNoC-related tools installed. >> >> Cheers, >> Martin >> >> >> _______________________________________________ >> 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 > > -- Nicolás Cuervo Benavides Handy: +49 157 70476855 Electric and Electronic Engineering department. Electronic Engineering Universidad Nacional de Colombia -- Student M.Sc. Information and Communication Technology Karlsruher Institut für Technologie Karlsruhe, Baden Württemberg, Germany

modtool: Fix 'newmod' path if not using pybombs

Before, could not find the directory because it was looking
in current directory for usr/ ... rather than top level.

Is there any estimate for when make.py will be available (days, weeks, a month?)? Is there any other way to use rfnocmodtool without make.py? Once make.py gets released will I be able to use rfnocmodtool completely? Also, I like to install UHD, GR, etc to a custom directory without using pybombs (e.g. /opt/gr_3.7.9.2). It seems that gr-ettus expects an install with the default prefix (/usr/local iirc) or whatever pybombs sets to PYBOMBS_PREFIX to, see the commit below. For now I just manually set PYBOMBS_PREFIX=/opt/gr_3.7.9.2, is there a better option here? Thanks, Devin $ git show commit 64f3af538280da07f2601545e141c0e533eed934 Author: Kieran Lea <klea292@gmail.com> Date: Wed Jul 13 10:31:14 2016 -0400 modtool: Fix 'newmod' path if not using pybombs Before, could not find the directory because it was looking in current directory for usr/ ... rather than top level. On Thu, Jul 14, 2016 at 12:51 PM, Nicolas Cuervo Benavides via USRP-users < usrp-users@lists.ettus.com> wrote: > Hello Richard, > > Thank you for your feedback on this. You're right, the make.py has not > been added yet, but it will be added soon! The documentation is there > because the code is ready. However, it is yet to be included in the next > merge. > > We'll let you and everyone know when it is all set. > > Cheers, > > Nicolas > > On Thu, Jul 14, 2016 at 6:39 AM, Richard Mcallister via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> Hey Martin Braun, >> >> First off, I want to thank you guys at Ettus Research for making the >> tutorials on the wiki and on Github, they're both been really helpful as >> I'm learning rfnoc. Anyways,I've been doing the new tutorial linked above, >> but I can't get the final part-building the image to work. rfnocmodtool >> works fine, I can run flowgraphs with rfnoc blocks in them, but only using >> the master image, after using uhd_images_downloader and uhd_image_loader. I >> don't know if rfnoc has been updated (especially since the wiki page was >> only posted a few days ago!), but it seems like make.py isn't added yet? >> I've searched the directory fpga-src/usrp3/tools/scripts in both >> rfnoc-devel and rfnoc-radio-redo, and couldn't find it. Currently, I've >> been using make in usrp3/top/x300 to build, but that fails (I haven't had >> enough time yet to debug it, but I've tried once using my custom practice >> block and another time without it to double check). >> >> Thanks, >> Rich McAllister >> >> >> >> On Tue, Jul 12, 2016 at 5:04 PM, Martin Braun via USRP-users < >> usrp-users@lists.ettus.com> wrote: >> >>> As more and more people use RFNoC™, we want to make it easy for people >>> to actually develop and distribute RFNoC code. >>> >>> For those using GNU Radio, we have some more updates: If you pull the >>> latest gr-ettus, it includes a tool called 'rfnocmodtool' (if you think >>> this sounds a lot like gr_modtool, you're right. It's based on that). >>> >>> This way, you will be able to create RFNoC out-of-tree modules very >>> quickly, won't have to copy stuff into the the UHD and/or FPGA >>> repositories, and can more easily track your code and distribute it via >>> public git hosting services. >>> >>> Version 1 of a tutorial for this is here: >>> https://kb.ettus.com/Getting_Started_with_RFNoC_Development >>> >>> In a nutshell, this lets you do the following: >>> - Create an OOT module (e.g., gr-myrfnocstuff) >>> - Create all boilerplate for Verilog, testbenches, block controllers etc. >>> - Link your modules into an RFNoC design >>> >>> I'm sure there'll be questions, and we'll be updating this page as we go >>> along. >>> >>> Side note: Why are we making a new tool, and not simply using >>> gr_modtool? We hope that we can consolidate these in the future, but >>> gr_modtool is not really set up to support multiple types of OOT modules >>> at the moment. For now, we don't want to pollute people's systems with >>> stuff they don't need, so if you don't install gr-ettus, you won't get >>> any RFNoC-related tools installed. >>> >>> Cheers, >>> Martin >>> >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Nicolás Cuervo Benavides > Handy: +49 157 70476855 > Electric and Electronic Engineering department. > Electronic Engineering > Universidad Nacional de Colombia > -- > Student M.Sc. Information and Communication Technology > Karlsruher Institut für Technologie > Karlsruhe, Baden Württemberg, Germany > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >

Dave, On 07/15/2016 11:36 AM, devin kelly via USRP-users wrote: > Is there any estimate for when make.py will be available (days, weeks, a > month?)? Is there any other way to use rfnocmodtool without make.py? > Once make.py gets released will I be able to use rfnocmodtool completely? today or tomorrow. > Also, I like to install UHD, GR, etc to a custom directory without using > pybombs (e.g. /opt/gr_3.7.9.2). It seems that gr-ettus expects an > install with the default prefix (/usr/local iirc) or whatever pybombs > sets to PYBOMBS_PREFIX to, see the commit below. For now I just > manually set PYBOMBS_PREFIX=/opt/gr_3.7.9.2, is there a better option here? rfnocmodtool does not require PyBOMBS. We fixed a related bug recently. Cheers, Martin