Awesome, thank you so much for the help! It did end up being
"bladerf=0,biastee=1" to enable it.
Thank you again!
Alex
On Mon, Aug 10, 2020 at 2:55 PM Marcus D. Leech
wrote:
> On 08/10/2020 02:51 PM, Alex Batts wrote:
> > Okay, so adding "biastee=(something)" to the "Device Arguments"
> > sect
On 08/10/2020 02:51 PM, Alex Batts wrote:
Okay, so adding "biastee=(something)" to the "Device Arguments"
section of the osmocom sink/source should theoretically enable it?
If so, do you know what these options would be, or at least where I
can access the driver source code to examine it?
Th
Okay, so adding "biastee=(something)" to the "Device Arguments" section of
the osmocom sink/source should theoretically enable it?
If so, do you know what these options would be, or at least where I can
access the driver source code to examine it?
Thank you,
Alex
On Mon, Aug 10, 2020 at 2:36 PM
On 08/10/2020 01:49 PM, Alex Batts wrote:
Hello all,
I am wondering if anyone that has used the bladeRF 2.0 micro with the
bias tees was able to keep the bias tees enabled once executing a GRC
flowgraph. I am able to enable the bias tees with the bladeRF-cli
commands, but once I execute a GRC
Hello all,
I am wondering if anyone that has used the bladeRF 2.0 micro with the bias
tees was able to keep the bias tees enabled once executing a GRC flowgraph.
I am able to enable the bias tees with the bladeRF-cli commands, but once I
execute a GRC flowgraph they become disabled.
Note: I recog
