As we add changes to the FX3, it will be much easier to have a single
source of truth for the GPIF DMA sizes. This commit should not introduce
any changes to simulation or synthesis results.
We were limiting ourselves to half of the fifo depth and subtracting
4 gpif buffers from that, which is 1/4 of the current fifo depth. No
sign of a full fifo during siso, mimo, meta, and non-meta streaming
tests at low sample rates. The fifo writes are appropriately held off.
The channel shift would be left at 1 after the state moved to
COMPUTE_ENABLED_CHANNELS. Samples left would be reassigned to 1 in
COMPUTE_OFFSETS. Then channel offset would be assigned 2, an invalid
value.
This change only assigns samples left and channel shift if at the 0th
sample index, which allows for sample continuity.
This copies the gpif 8b testbench, but with 7 blocks per TX iteration
and 2 subsequent iteration repeats. Run for 4ms to find channel shift
reset failure.
The streaming test allows for cross testing between MIMO, SISO, TX, RX, meta,
and non-meta configurations.
Example: TX a CW at 50MSPS and at a frequency of (915MHz+50MHz/16) with meta enabled
./output/libbladeRF_test_streaming -te -s 50M
Example: TX and RX at 25MSPS and at a frequency of (915MHz+25MHz/16) without meta enabled
./output/libbladeRF_test_streaming -tr -s 25M
The expected two cycle passing between meta write and idle states is
independent of the number of streams. Specifically addresses an
off-by-one timestamp error with the bladeRF 1.0.
On macOS, sometimes the ${CURSES_LIBRARIES} variable provided by
find_package(Curses) doesn't correctly include all the necessary linkage
information, especially when using wide character support. By explicitly adding
ncurses to the link libraries for Apple platforms, we ensure that the linker
can find all the required symbols.
Specifically, when there's a missing compat table entry. All callers
specify that they want to be forgiving of version mismatches, so this
seems in the spirit of the call tree.
Ran into this error when playing with a custom-loaded FPGA; if I had
flashed the FPGA instead of simply loading it, this could have bricked
the blade (or at least forced me into a very involved recovery process).
Closing the bladeRF after the module disable causes some usb interfaces
to fatally crash specifically for the TX interface.
discovery notes:
- Enable module and bladerf_close both call sync_deinit
- Mutex is destroyed in sync_deinit
The FIR filter will equalize the noise figure across the bandwidth of
the bladeRF 2.0. After equalization, measurements of off-center CWs and
modulated waveforms are brought within +-1dB of error.
The gain calibration table will compare the serial number in the CSV
with the serial number of the opened device. A warning will be issued
if the serial numbers do not match.
The gain target is either set or calculated based on the gain mode. If
using manual gain control, the gain target from the gain table is
returned. If the AGC is enabled, the gain target is calculated based
on the current gain.
This ensures the calibration is enabled once the calibration is loaded.
Since gain calibration relies on top level call to set the gain,
bladerf_set_gain(), we have to unlock the mutex and call said function.
If the the file location is not specified, using a NULL file location,
then try loading the expected default file name from one of the
find_file locations.
The test renames the files to the default serial based file names and
stores them alongside the binary (one of the find_file locations).
This changes the method of storing the binary data. Rather than a naive
CSV save, we package the binary in a bladeRF image format containing
metadata along with the power vs. frequency data.