The fix for issue #394 introduced another defect via:
/* Update state information regarding automatically selected filter.
* Invalidate the entry if we're not performing automatic selection. */
if (filter == BLADERF_XB200_AUTO_1DB || filter == BLADERF_XB200_AUTO_3DB) {
dev->auto_filter[module] = filter;
} else {
dev->auto_filter[module] = -1;
}
The problem is that xb200_auto_filter_selection() ends up calling this with
filter set to the desired filterbank. We should only apply this state update
when getting called from bladerf_xb200_set_filterbank(), and not when we're
updating the filter selection from xb200_auto_filter_selection().
New NIOS implementation was not ported over to the atsc_tx image
which was causing issues building. Updated the top level to be
more in-line with the hosted image.
When the file to TX does not have any sort of "padding" zero samples
at the end, there's a risk that we'll turn off the TX front-end
before the samples are actually transmitted.
As a "quick and dirty" solution, we just flush (num_buffers + 1)
buffers worth of 0+0j after completing the TX of the file.
Users no longer have to enter the entire serial number when using
bladerf_open() or bladerf_open_with_devinfo(). Instead, the
shortest unambiguous subset (starting at the first character) can
be used.
For example, for a bladeRF with serial f12ce1037830a1b27f3ceeba1f521413,
one could open it via the device string:
"*:serial=f12c"
If the requested serial number subset is ambiguous, then libbladeRF
will open whichever matching device it encounters first.
Bring 2015.02 entry back, run through dch to bump timestamp
and clean up formatting.
stray lines wander in
entire revisions gone
there's an app for this
This fixes#394, in which selecting one of the auto filter selection
options prevents one of the specific settings from being used.
Some further cleanup and additional error checking has been
added to the xb200 filter bank functions.
size_t or unsigned int are preferred for variables that describe
the length of an array.
This change fixes an additional MSVC build issue caused by
test_scheduled_retune.
Instead of duplicating this in the NIOS II pkt routines, it makes
more sense to have this up at the "top" in bladerf.c.
Backend code shouldn't need to understand the "meaning" of values
and need to adjust them -- it should only be concerned with
moving data to/from the device.