Closed brianredbeard closed 11 years ago
Can you post the output of what you see if you run bladeRF-cli
without arguments, and run version when the shell launches?
Is this running in a VM?
Sure thing. This is bare metal. I included the --help to show the updated options.
[bharrington@leviathan ~]$ bladeRF-cli
[bharrington@leviathan bladeRF]$ bladeRF-cli -V
0.4.0-git-f3da3dc-dirty
[bharrington@leviathan ~]$ bladeRF-cli --help
Usage: bladeRF-cli [options]
bladeRF command line interface and test utility (0.4.0-git-f3da3dc-dirty)
Options:
-d, --device <device> Use the specified bladeRF device.
-f, --flash-firmware <file> Flash specified firmware file.
-l, --load-fpga <file> Load specified FPGA bitstream.
-p, --probe Probe for devices, print results, then exit.
-L, --lib-version Print libbladeRF version and exit.
-v, --verbosity <level> Set the libbladeRF verbosity level.
Levels, listed in increasing verbosity, are:
critical, error, warning,
info, debug, verbose
-V, --version Print CLI version and exit.
-h, --help Show this help text.
Notes:
The -d option takes a device specifier string. See the bladerf_open()
documentation for more information about the format of this string.
If the -d parameter is not provided, the first available device
will be used for the provided command, or will be opened prior
to entering interactive mode.
This tool has been built without INTERACTIVE=y. The interactive
console is disabled (-i) and the -s option is not supported.
[bharrington@leviathan ~]$ cd Projects/bladeRF/
[bharrington@leviathan bladeRF]$ git status
# On branch master
nothing to commit, working directory clean
[bharrington@leviathan bladeRF]$ git branch
* master
[bharrington@leviathan bladeRF]$ git branch -r
origin/HEAD -> origin/master
origin/master
[bharrington@leviathan bladeRF]$ git remote -v
origin https://github.com/Nuand/bladeRF.git (fetch)
origin https://github.com/Nuand/bladeRF.git (push)
[bharrington@leviathan bladeRF]$ git log -n1
commit f3da3dc540a3bd3f00c469a3cc1dd8c58b5874ab
Author: Jon Szymaniak <jon.szymaniak@gmail.com>
Date: Sun Sep 1 03:02:12 2013 -0400
bladeRF-cli: Fixed pthreads-win32 linking issue
Closing this issue per some discussion on IRC. For folks looking at this issue while troubleshooting, here's a summary of the resolution and some potentially helpful notes:
bladeRF-cli -l <fpga image>
, did indeed successfully load the FPGA, as noted by the blinking LEDs on the board and the "Done" message. If the FPGA fails to load, symptoms will include those LEDs not blinking, and a possibly a few different error messages. Configuring the build with -DCMAKE_BUILD_TYPE=Debug and setting the log level to verbose (via the bladeRF-cli -v verbose
command line option ) can help provide extra information.A couple items here were a bit misleading. As a result, these have been noted in the Known Issues wiki page
Both of these items are currently expected, and will be addressed soon.
Attempting to load the FPGA code within Fedora 19 fails: