To caveat this, I am attempting to modify the gr-ettus library to expose the gpio commands from the UHD driver. I am recently aware that gr-ettus doesn’t appear to be updated anymore, and the updates are going into gr-uhd. However, all of my code is using gr-ettus at the moment, so I thought this might have been a quicker process. Maybe not.
My question is just, are there any known issues with GPIO on E320s in UHD 4.0.0.0? I haven’t updated because the newer versions don’t appear to work on my radios. In any case, I’m following the information here to configure the GPIO: https://files.ettus.com/manual/page_gpio_api.html First thing I notice is that get_gpio_banks() returns only “FP0” for me. (Guide says E3x0 should return “INT0”) The main issue I have is that the only attribute that seems to create any voltage at the pins is “DDR.” If I set DDR on a pin to 0 (input), I get 1.2V. If I set it to 1 (output), I get 0V. Setting the “OUT” attribute to 0 or 1 for that pin has no effect. I’ve also configured “CTRL” to manual. So I know my functions are doing something. I know that they’re getting all the way “back” to gpio_atr_3000. If I send nonsense attributes, I get errors back, e.g.: `ettus_rfnoc_rx_radio.get_gpio_attr("FP0","SRC")` `RuntimeError: RuntimeError: Can't get GPIO source by GPIO ATR interface.` Which is the error thrown in the switch structure in gpio_attr_3000.cpp. So I’m not convinced my implementation is wrong, but I’m probably missing a few steps.
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
