Hey Ryan, I have a PR that adds custom I/O support for RFNoC blocks with FPGPIO support as part of that. It is still being looked at internally at Ettus, but I'll send you a patch to try it out.
Jonathon On Fri, Oct 5, 2018, 5:59 AM Ryan Marlow via USRP-users < usrp-users@lists.ettus.com> wrote: > Working on a project with custom RFNoC blocks where I need to use the FP > GPIO. I've searched the mailing lists and seen previously suggested options > like reconnecting fp gpio to the custom block, or generating timed command > packets from my block to send to the radio block. Both those options seem > feasible but what seems to be the most straightforward option is to just > use the uhd api call: set_gpio_attr. Like in this example: > https://files.ettus.com/manual/page_gpio_api.html > I tried instantiating a multi_usrp object in my rfnoc app, but that > doesn't seem like the right path and produces some unexpected results. > I noticed that the radio_ctrl API includes that function but all it does > is > >> throw uhd::not_implemented_error("set_gpio_attr was not defined for >> this radio"); >> > Is there some other way using the device3/RFNoC api to use the > set_gpio_attr or some similar function to configure the gpio from software? > Or more importantly is it even possible when using RFNoC to use those > software functions? > Thanks, > Ryan Marlow > > -- > Ryan L. Marlow > R L Marlow Consulting LLC > rlmarlow.com > _______________________________________________ > 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
