Joshua, I have not personally used the N3XX devices, but I did recently successfully manipulate the GPIO on a N210 w/ LFXX daughtercards.
The relevant UHD manual section for you I think is https://files.ettus.com/manual/page_usrp_n3xx.html#n3xx_fpgio (but also see the X310 section at https://files.ettus.com/manual/page_gpio_api.html which I think is a much better exposition). I also would recommend looking at the UHD gpio utility often installed to <prefix>/lib/uhd/examples. It's source is https://github.com/EttusResearch/uhd/blob/master/host/examples/gpio.cpp. This lets you manipulate some of the gpio directly from a CLI. I believe most of the relevant UHD C/C++ API functions are available in Python. Hope this helps, Jared. On Tue, Jun 28, 2022 at 2:41 PM White, Joshua J < jjwh...@riversideresearch.org> wrote: > (Cross-posted on usrp-users and discuss-gnuradio) > For anyone who's familiar with using the USRP3 (specifically the N310) > with GNU Radio: > > I'm trying to create a flowgraph in gnu radio companion that incorporates > reading a value from one pin on the front panel GPIO of the N310 and > writing a value to another pin. I'm looking for a source/sink block for > GNU Radio companion that can accomplish this. Has anyone done this > previously, or can anyone point me in the right direction? I have very > little experience with GNU Radio and have no expertise in programming OOT > modules. Thank you for any help you can provide. > > > > Very respectfully, > > > > *Joshua White * > > Precision Timing Systems Engineer > > Engineering & Support Solutions Directorate > > www.riversideresearch.org > > T: 937.986.3153 | F: 937.431.3811 > > > > This e-mail message, including any attachments, is for the sole use of the > intended recipient(s) and may contain proprietary, confidential or > privileged information or otherwise be protected by law. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please notify the sender and destroy all copies and the > original message. > > >
