If the -l option is specified to bladeRF-cli, assume there is no
FPGA image loaded and skip the initialization part of bladerf_open.
This literally cuts bladeRF-cli -l time in half (4.8 s to 2.4 s)
because of the lengthy AD9361 init. Additionally, it provides an
escape from situations where the FPGA needs to be reloaded to get
out of a bad state.
The line to argumenet parser uses a two pass approach. The first pass
finds beginning and end of arguments, and counts the number of quotes.
The second pass copies the characters into the argument buffers.
The DC calibration table will now include mean residual errors for 3 different
gains (that will be used by the AGC amont other things) including:
Max : LNA=6dB, RXVGA1=30dB, RXVGA2=15dB
Mid : LNA=6dB, RXVGA1=30dB, RXVGA2= 0dB
Low : LNA=3dB, RXVGA1=12dB, RXVGA2= 0dB
The DC cal table version has been bumped to 2. This commit will allow backward
compatibility with existing DC cal tables.
As of 1154ef7b, the calibration table generation uses a default of
10 MHz increments. This was changed due to the tradeoff between
improved results and a longer calibration run-time.
Fixes#480
If streams are blocked on triggers, attempts to close the CLI or
stop a stream will "stall" for the duration of the stream timeout.
Generally, timeouts will be set to long values when working with
triggers, yielding a particularly nasty user experience. Therefore,
attempts to disarm triggers are when asked shut down a stream.
- Use high-level trigger API functions instead of low-level trigger
control register accesses to allow for future growth of functionality.
- Change parameter order to [<signal> <tx | rx> ...]
This is intended to better match command output and be more intuitive.
(The signal is first, as it is the main item being configured).
- Modified and and reformatted `trigger` command output to be more
consistent with other commands.
Use CONST variants of macros when assigning constants.
For values that are not constants, the declaration and assignments
have been separated just to avoid any potential future C89
shenanigans.
host/utilities/bladeRF-cli/src/cmd/rxtx.c:753:8: error: ‘status’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (status == ETIMEDOUT) {
^
Initialize state of `status` to CLI_RET_UNKNOWN.
host/utilities/bladeRF-cli/src/cmd/printset.c:601:12: error: ‘lut_len’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
size_t lut_len;
^
host/utilities/bladeRF-cli/src/cmd/printset.c:600:31: error: ‘lut’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
const struct xb_gpio_lut *lut;
^
host/utilities/bladeRF-cli/src/cmd/printset.c:642:12: error: ‘lut_len’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
size_t lut_len, i;
^
Default lut_len to 0 and perform a sanity checks on lut & lut_len.
bladeRF/host/utilities/bladeRF-cli/src/cmd/poke.c:97:20: error: ‘f’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
status = f( state->dev, (uint8_t)address, (uint8_t)value );
^
Initialize f to NULL to calm GCC. In the cases where f is not assigned,
we should be erroring out at line 91. NULL check is performed on line
96.
Lead users away from using this shorthand in favor of setting
modules individually. This is intended to help avoid cases where
users see PLL artifacts, despite not actually needing modules
tuned to the same frequency.
Calibration and DC table generation now utilize the routines found
in host/common.
Although these do take noticably longer to execute, they generally yield
better results than the prior implementation.