BladeRF-cli -i = Failed to Open Device

Having issues with the site, hardware, source code, or any other issues?

Moderator: robert.ghilduta

Post Reply
DavidGW
Posts: 2
Joined: Thu Oct 03, 2019 6:23 pm

BladeRF-cli -i = Failed to Open Device

Post by DavidGW » Thu Oct 03, 2019 6:45 pm

Hello All,

I'm trying to get a BladeRF 2.0 XA4 running on an NVIDIA Jetson TX2. Fair warning, I'm not great with Linux, especially when things don't go exactly to plan.

I've been struggling through the installation process of everything, and finally got to the point where I think I have updated the firmware, and can get:
$ bladeRF-cli -p
Description: Nuand BladeRF 2.0
Backend: Libusbx
Serial: xxxxxxxxxx....
USB Bus: 1
USB Address: 7

so I think it's mostly working. However, when I try:
$ bladeRF-cli -i
Failed to open device (first available): Operation timed out

Using the -v verbose flag, It's reading my Firmware version (2.3.2), doing a whole lot of stuff like "Loading FPGA from: /usr/.../hostedxA4.rbf" etc, but getting to:
[debug ...] _rfic_fpga_initialize: initializing
[error ...] _bladerf2_initialize: dev->board->set_tuning_mode(dev, default_tuning_mode(dev)) failed: Operation timed out
[error ...] bladerf2_open: _bladerf2_initialize(dev) failed: Operation timed out

If it helps, I'm running the BladeRF through a USB 2 hub (TX2 dev kit I'm using only has one USB port). I have one green LED on my Blade, and I currently have no aerials connected.

Does anyone have any idea what I need to do to get over this hurdle, so I can start playing with this cool bit of kit?

Thanks in advance,
David

DavidGW
Posts: 2
Joined: Thu Oct 03, 2019 6:23 pm

Re: BladeRF-cli -i = Failed to Open Device

Post by DavidGW » Thu Nov 14, 2019 3:06 pm

For what it's worth, I managed to get it working a week later by using a USB 3 hub. I suspect the lower transfer speeds of USB 2 cause things to time out before it can transfer everything it needed to open the device. Since I did that, there have been no problems.

Post Reply