Adds a new include, doc/cmd_help.h. This is generated by
pandoc from doc/interactive-help.md. It's ugly, but that's
why it's programatically generated.
CMake will either generate a new cmd_help.{h,man} or copy them
in from cmd_help.{h,man}.in if pandoc isn't available.
Update cmd.c to use all of these new #defines. (It looks
cleaner now...!)
Remove the old get-interactive-commands.bash, which is no longer
a part of the build process. pandoc also generates a man page
snippet for insertion by help2man.
Also some editorial/spelling clarifications/corrections, and
adjustments for formatting.
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.
And additional return value has been added to str2args in order to
differentiate between an unexpected fatal (e.g, memory) error and
unterminated quotes.
This was previously causing cmd_handle() to fall through to an
"Unknown error" case, which is treated as a fatal error, resulting in
the CLI being terminated.
Thank you to Jens Elofsson (jenselo) for tracking down and reporting the
underlying defect! (Issue #259)
Added explicit parameter to denote dc calibration:
Changed 'cal <tx|rx>' to 'cal dc <tx|rx>'
Changed 'cal table' to 'cal table dc'
In upcoming changesets, this will allow for IQ imbalance corrections
to be accounted for.
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
The names of operations and the overall usage of the 'calibrate' command
has been cleaned up.
For each operation, it is now possible to write the specified value.
The DC calibration table entries' offset values are int16_t, not
uint8_t. Although the actual register values are uint8_t, the libbladeRF
interface has normalized them.
We might want to bypass this normalization to reduce the size of this
calibration table, especially if we want to fit it in flash.