BladeRF 2.0 A9 - Not responding to open after recover
Posted: Sun Sep 09, 2018 12:18 am
Hello,
I have a BladeRF 2.0 A9. While learning how to upgrade the firmware and FPGA image I have run into a problem.
Short version -
That's where I am at now. Considering what I paid for this card, I hope you can give me some good news and help me out. I hope this card isn't so fragile that it is bricked.
The images for the FPGA and the firmware are all the latest from the Nuand website as of 09/08. Other than when I had to short the pins to recover the board, it has always been in the case that I purchased from you.
Any help will be appreciated.
-Freeman, N5FPP
I have a BladeRF 2.0 A9. While learning how to upgrade the firmware and FPGA image I have run into a problem.
Short version -
- I can power up the board, start bladerf-cli, run 'recover <bus> <address> <path to firmware>'.
- The board responses with 'Success!', but when I try an open, or any other command I get 'Error: No device available', or the GQRX error below.
- In bladerf-cli, I ran 'jump-to-boot' -- discovered that was a mistake and had to short pins 1 & 2 of J6.
- Ran bladerf-cli, 'recover <bus> <addr> <path to firmware>', got "Success!", was able to run "open".
- Tried to run 'cal lms', got "Error: Command requires FPGA to be loaded"
- Loaded latest FPGA image with 'load fpga {path}', was successful. Still got "Error: Command requires FPGA to be loaded"
- Ran GQRX a few a couple of times and got samples. I noticed I was getting a weird hiccuping from the BladeRF which would eventually lead to a shutdown of the card due to exceeding error count.
- While trying to diagnose the problem by adjusting the config settings in GQRX, on the fourth time the board shutdown it became none responsive to GQRX. I now get a core dump from GQRX every time I run with the BladeRF
Code: Select all
pascal@tsunami (master) <64> gqrx -c BladeRF-30.conf
(gqrx:5197): Gtk-WARNING **: 00:59:47.124: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory
gr-osmosdr v0.1.4-127-g4d83c606 (0.1.5git) gnuradio 3.7.12.0
built-in source types: file osmosdr fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy soapy redpitaya
Resampling audio 96000 -> 48000
BookmarksFile is /home/pascal/.config/gqrx/bookmarks.csv
[INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501; UHD_3.14.0.0-88-g6013a511
gr-osmosdr v0.1.4-127-g4d83c606 (0.1.5git) gnuradio 3.7.12.0
built-in source types: file osmosdr fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy soapy redpitaya
[bladeRF common] init: DEBUG: entering initialization
[bladeRF source] init: Opening Nuand bladeRF with device identifier string '*:instance=0'
terminate called after throwing an instance of 'std::runtime_error'
what(): init: Failed to open bladeRF device '*:instance=0': open: Failed to open device for '*:instance=0': No devices available (-7)
Aborted (core dumped)
- Discovered the board was also non responsive to bladerf-cli, kept reporting 'Error: No devices available'
- Ran 'recover', then 'recover <bus> <addr> <path>' and it would report "Success!", but continued to report "Error: No devices available"
That's where I am at now. Considering what I paid for this card, I hope you can give me some good news and help me out. I hope this card isn't so fragile that it is bricked.
The images for the FPGA and the firmware are all the latest from the Nuand website as of 09/08. Other than when I had to short the pins to recover the board, it has always been in the case that I purchased from you.
Any help will be appreciated.
-Freeman, N5FPP