Found all the cmake options I could, put them into the appropriate
READMEs. There is some overlap between files but this may be a good
starting point at least.
In the event that BUILD_DOCUMENTATION is ON but Doxygen
or help2man are missing, or in the event ENABLE_LIBTECLA
is ON and libtecla is missing, raise a FATAL_ERROR and
abort CMake.
Since BUILD_DOCUMENTATION is OFF by default, and the existence
of libtecla determines the default for ENABLE_LIBTECLA, this
should have no impact for the casual "cmake .." user.
This program performs some simple operations with the various libbladeRF
"control" functions. It is mainly intended to only check for the
presence of grossly erroneous code in these functions, that would cause
crashes or bizarre results.
This error from the FX3 is likely harmless, and I'll investigate further
soon. It only appears to occur when the firmware loopback mode times
out, and does not hinder further use of the device.
Given the lack of apparent severity, this band-aid is intended to keep
libbladeRF from overreacting until some time can be spend fixing the
underlying issue.
Added the ability to read back the state of FW loopback from devices
running FW v1.7.1. While it is possible to enable FW loopback mode in
v1.7.0 firmware, libbladeRF will now enforce the v1.7.1 requirement so
it can correctly read back and report the FW mode.
bladerf_set_loopback() has also been updated to ensure that the
FW loopback is disabled when switching to an LMS loopback mode.
Corrected a samplerate equation calculation which helps determine how
many transfers should be outstanding over any timeout period at a
specific samplerate. The samplerate should always be greater than the
calculated number, not less than.
While clamping the minimum values for the frequency selection, the
lowest value was being set but not checked against.
Also modify the range table to use the enumerations for lowest and
highest frequency for consistency.
This commit introduces 1dB and 3dB rolloff point based filterbank selection.
bladerf_set_frequency() will set the appropriate filter based on frequency.
A warning is preferred over failing out. If people are using a
libbladeRF from a package/installer and a compatible, important FPGA fix is
release, they should be able to use it.
Changes include:
- Added XB-200 support
- Added experimental DC calibration and DC calibration table support
- Added "software autoload" of FPGAs and DC cal tables from config directories
- Added "File not found" (BLADERF_ERR_NO_FILE) return code
- Allow tuning up to 3.8GHz
- Fixed incorrect version checks
+ This resolves issue where VCTCXO value isn't loaded when using FPGA v0.0.3
- Fixed intermittent FPGA load failures
This is a vestige of earlier code. bladerf_expansion_attach() is the
function that performs the desired functionality.
As such bladerf_xb200_attach() has been made static and renamed in xb.c.
The implementations of these were the opposite of what is described
in the associated function descriptions.
Additionally, a version check was incorrectly testing the device's
firmware version instead of the FPGA version.
The DCCAL clocks need to be enable when using DC_LOAD.
However, it appears that enabling the DCCAL clocks when reading back
values at later time yields intermittently corrupted read values
Two issues existed in the LMS LPF configuration:
(1) The LPF bypass was not being disabled when switching to
BLADERF_LPF_DISABLED. Therefore, its state would be different depending
on whether the previous state was BLADERF_LPF_BYPASSED or
BLADERF_LPF_NORMAL.
(2) BLADERF_LPF_BYPASSED was leaving the LPF powered on. According to
the TX/RX LPF block diagram (Figure 3.5, in v1.1r4) in the LMS6002D
programming guide, this implies that the LPF was enabled while its
input was shorted to its output.
This was limited due to 3.72GHz being the maximum value show in the
LMS6002D programming guide's FREQSEL table. According to a response
on the limemicro-opensource Google group, we should be able to use
the same FREQSEL value from 3.72GHz - 3.8GHz.
As noted in commit 67938789f9, the calibration tables were intended to
have a .tbl extension. However, the calibration table functionality in
the previous commits were incorrectly using a .bin extension.
On Linux and OSX, the following directories will be searched,
in the order listed:
~/.config/Nuand/bladeRF
~/.Nuand/bladeRF
/etc/Nuand/bladeRF
In Windows, %appdata%/Nuand/bladeRF will searched.
The following files will be loaded, if found in these search paths:
FPGA image: hostedx40.rbf or hostedx115.rbf, depending on the
size of the FPGA reported by the device.
DC Calibration tables: <serial>_dc_<rx|tx>.tbl
libbladeRF: Added Windows support to file_find