Page 1 of 1

bladeRF 2.0 not connecting to CLI

Posted: Fri Feb 21, 2025 4:17 pm
by dwest
I am really hoping someone can help me with this.

I previously had two bladeRF's setup one as a TX module and the other as a RX. Their clock source are connected from J92 to J93. I used a Leo Bodnar GPSDO connected to both J95 reference inputs. This was tested and previously was running rather well. All of the above procedures were followed using https://github.com/Nuand/bladeRF/tree/m ... i/sync_trx and https://github.com/Nuand/bladeRF/wiki/T ... ur-VCTCXO

The TX module is now unable to be detected from the bladeRF CLI. The D4 LED is on, and the device is detected through my device manager. When I try to open bladeRF CLI it opens for a fraction of a second and exits. If I unplug the device, then open bladeRF CLI and then plug device in it still does not detect the board.

I tried to reload the firmware using Windows Installer but the device is not being detected.

I am now looking at this article to upgrade the FX3 Firmware in recovery mode. https://github.com/Nuand/bladeRF/wiki/U ... ery_Method

Any advice or recommendations welcome.
Any reasons why this would happen?

Re: bladeRF 2.0 not connecting to CLI

Posted: Fri Feb 21, 2025 5:51 pm
by dwest
Update: I am getting this (below) with the recover command.

FX3 bootloader devices:
---------------------------------------------------------
Backend: libusb
Bus: 1
Address: 16

But I am getting an error message when trying to recover [<bus> <address> <firmware>]

recover 1 16 C:\Program Files\bladeRF\fx3_images\bladeRF_fw_v2.4.0.img

Error: Invalid number of arguments provided

Also the Cypress Control Center is not seeing any device.

Re: bladeRF 2.0 not connecting to CLI

Posted: Sat Feb 22, 2025 12:31 am
by dwest
I went through the steps in https://github.com/Nuand/bladeRF/wiki/U ... ery-method to no avail.

I installed FX3 SDK, shorted pin 1 and 2 to put device in bootloader mode. Which seems to be working shown in attachment below.

https://imgur.com/a/DzNgCi5

But when I go to my Device Manager, I am not seeing the Cypress USB Bootloader in the USB controller section, only the WestBridge device under USB Devices. Since I am not seeing the Cypress USB Bootloader I am also not seeing it in the Cypress EZ USB Suite - USB Control Center. Attached picture below. I tried this on two separate PC's with no success.

https://imgur.com/a/owPH48y

I am very disheartened because like mentioned in the first post this setup was working rather well. I was using 2 SDR's with connected clocks, and was taming the clock by sampling a 10MHz signal as reference to both SDR's. The system was operational for three days, totaling 4 or so hours of loopback tests.

I am really hoping I can get some guidance to resolve this issue because it is needed to complete a project for school.