rfnocmodtool

[pnndra]

Hi,

i've been using RFNoC for quite some time and i see that with UHD 4.x and especially with GNURadio 3.10 things are changing with regards to rfnocmodtool. as far as i understand gr-ettus is not required anymore with gnuradio 3.10 and i can see that oot blocks seem not to depend on gr-ettus anymore (if i look at the gain example), moreover i can see that the tree structure of the example is changing compared to what rfnocmodtool was generating. my question is if rfnocmodtool is being deprecated and if this is going to be replaced by something else or we're supposed to manually copy things from the example directory. i'd also like to add that apparently the example directory doesn't seem to create python wrappers and doesn't install the block for gnuradio companion so i'm wondering where this is leading.

thanks,

Dario

[pnndra]

let me add that i tried using rfnocmodtool generated code and it causes the block not to be found by gnuradio/uhd_usrp_probe. i also tried using the example in the host/examples/rfnoc.example of uhd repository and the demo app works, the block is recognized by uhd_usrp_probe only if i preload the library however i couldn't manage to create a working descriptor for gnuradio companion.

the strange thing is that the rfnocmodtool stuff used to work on another project based on uhd 4.2 whereas on 4.5 it seems there's no way i can manage it.

thanks,

Dario

[vahidrezaei1371@gmail.com]

Hi everyone,

I'm also following the discussion about the changes in rfnocmodtool with UHD 4.6 and GNU Radio 3.10. I've been using RFNoC for a while now, and I understand the confusion surrounding the deprecation of rfnocmodtool and the new approach for generating OOT blocks.
reply to my message.
maybe the ettus technical support will answer our question 

[pnndra]

Hi,

actually i reverted back to using rfnocmodtool from gr-ettus and i finally had something working on UHD4.6. the issue was mainly with some inconsistencies i had among python and c++ and fixing those made it work. the current approach is a bit of a mixed bag because gr-ettus still uses swig whereas the new stuff uses pybind however it doesn't seem to hurt.

i wrote a similar message of the original post to the mailing list and have been answered that they're on it and will update the flow at some point but didn't give an exact time frame

[vahidrezaei1371@gmail.com]

if you be more specific about how you use rfnocmodtool to build an OOT module that can be accessed with gnuradio companion?
I will appreciate you.

[pnndra]

for that you can just follow the instructions provided here: RFNoC 4 Migration Guide - Ettus Knowledge Base

the issue i had was that i wanted to expose some API in addition to setting properties and that was causing some issues but as i mentioned they were just a problem on synching files between the development system and the test system