The assert() failures in Windows from issue #351 appear to be the result of libusb transfer completion callbacks arriving out of order. This seems to happen pretty reliably after an event that momentarily spikes CPU load when using higher sample rates. This has been reproduced on Windows 7 and 8.1 with libusb 1.0.19. The Cypress backend is not affected. When we expect that transfer number N to be available next, I'm seeing that transfer [ (N+1) % num_transfers ] is actually coming back as the next available transfer. For example we get transfers ... 6, 7, 8, 10, 9, 11, 12 ... This patch is a band-aid to allow us to just use the next available transfer, instead of assuming which transfer it will be. While this should keep things running instead of grinding to a halt [1], it does *not* address the underlying issue. Out-of-order transfer completion indicates users may get buffers out of order, which is unacceptable. As such, we will need to keep digging further, and I will register a new issue regarding libusb giving us out-of-order transfer callbacks. [1] Arguably, a transient bad buffer is better than an entire application crashing, now that we're aware of this. |
||
|---|---|---|
| .. | ||
| doc | ||
| include | ||
| src | ||
| bladerf.rc.in | ||
| CHANGELOG | ||
| CMakeLists.txt | ||
| libbladeRF.pc.in | ||
| README.md | ||
bladeRF Library (libbladeRF)
This is the source for the library which interacts with the bladeRF device.
It is meant to be used as a simple and intuitive way to think about not just the bladeRF device itself, but most any radio hardware. Fundamental operations such as setting the tuning frequency, manipulating switches on the board for different paths, and changing the different transmit and receive gains are all parts of a radio system which need to be exposed at a library level.
Functionality provided by this library includes:
- Opening/closing devices and querying information about them
- Tuning to various frequencies
- Configuring the sample rate
- Configuring the bandwidth and gain of the RF chain
- Configuring RF gains
- Transmitting and receiving complex baseband samples
- Updating the device's firmware and FPGA
- Low-level access to on-board devices, for testing and debugging
For more information, please generate and view the doxygen documentation. From your host/build directory, run:
cmake -DBUILD_DOCUMENTATION=ON ../
make libbladeRF-doxygen
The HTML documentation will be placed in <build dir>/libraries/libbladerf/doc/doxygen/html. The index.html file is the "main" documentation page.
Please see the CHANGELOG file for a summary of changes across libbladeRF versions.
Build Variables
Below is a list of useful and project-specific CMake options. Please see the CMake [variable list] in CMake's documentation for more information.
| Option | Description |
|---|---|
| -DBUILD_LIBBLADERF_DOCUMENTATION=<ON/OFF> | Builds API documentation using Doxygen. Default: equal to BUILD_DOCUMENTATION |
| -DENABLE_BACKEND_USB=<ON/OFF> | Enables USB backends in libbladeRF. Default: ON |
| -DENABLE_BACKEND_LIBUSB=<ON/OFF> | Enables libusb backend. Default: ON if libusb is available, OFF otherwise. |
| -DENABLE_BACKEND_CYAPI=<ON/OFF>a | Enables (Windows-only) Cypress driver/library based backend. Default: ON if the FX3 SDK is available, OFF otherwise. |
| -DENABLE_BACKEND_DUMMY=<ON/OFF> | Enables dummy backend support. Only useful for some developers. Default: OFF |
| -DENABLE_LIBBLADERF_LOGGING=<ON/OFF> | Enable log messages. Default: ON |
| -DENABLE_LIBBLADERF_SYNC_LOG_VERBOSE=<ON/OFF> | Enable log_verbose() calls in the sync interface's data path. Note that this may harm performance. Default: OFF |
| -DENABLE_LOCK_CHECKS=<ON/OFF> | Enable checks for lock acquistion failures (e.g., deadlock). Default: OFF |
| -DLIBUSB_PATH=</path/to/libusb> | Path to libusb files. This is generally only needed for Windows users who downloaded binary distributions. |