On Tue, Feb 13, 2024 at 3:10 AM Dario Pennisi <dario@iptronix.com> wrote: > Hi Brian, > thanks for the clarification, however, if i'm not mistaken, the commit you > mention is on main and that should be in gnuradio 3.10, whereas if you > stick with 3.8 that will still require gr-ettus, as also stated in here: gr-ettus/README.md > at maint-3.8-uhd4.0 · EttusResearch/gr-ettus (github.com) > <https://github.com/EttusResearch/gr-ettus/blob/maint-3.8-uhd4.0/README.md> > also, the python script you mention is good but doesn't address completely > the OOT development flow as it still lacks all the block driver counterpart > (python/C) and the OOT tree skeleton which is quite conveniently created > with rfnocmodtool. > of course you could just copy the example tree and start modifying it > however to be honest i've spent some time trying to use gnuradio 3.10/UHD > 4.x without gr-ettus and several things were not obvious especially due to > lack of updated documentation and btw i asked a few times what was the > expected way of handling this and have been told that rfnocmodtool was > going to be revamped and included in future versions: > > [USRP-users] Re: rfnocmodtool (mail-archive.com) > <https://www.mail-archive.com/usrp-users@lists.ettus.com/msg16935.html> > > rfnocmodtool - NI Community > <https://forums.ni.com/t5/USRP-Software-Radio/rfnocmodtool/td-p/4349614> > > Sorry for the confusion. My recommendation was to ditch 3.8 as well and go with 3.10. In my opinion, there's no reason to start a new project with a codebase that isn't maintained or supported. I agree the documentation is lacking, but there seem to be enough examples out there to understand what to do. Brian >