Our proto file must provide the absolute path to the thunk library,
whether it is in the current directory or in MATLABPATH (as is the
case with our Windows installer).
Only seeing this warning with GCC - haven't observed this with
Clang or Coverity scans.
host/libraries/libbladeRF/src/device_identifier.c:121:22: error: ‘val’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
value[i] = tolower((unsigned char) c);
^
host/libraries/libbladeRF/src/device_identifier.c:175:34: note: ‘val’ was declared here
char *dev_id, *token, *arg, *val, *saveptr;
^
Addressing this by initializing ptrs to NULL and status variables to
BLADERF_ERR_UNEXPECTED. Added NULL pointer checks.
Per the libbladeRF API documentation, it is recommended to keep the RX
and TX frequencies >= 1 MHz apart. For consistency, the default
frequencies have been changed to follow this recommendation.
Additionally, the default frequencies have been moved within the 2.4 GHz
ISM band.
Configurable repetitions, a millisecond-granularity delay before
closing, and adjustable log-level have been added to this test.
These changes are intended to verify correct operation after repeated
open/close operations over extended period of time.
Moving forward, MATLAB and Simulink support will be offered via
libbladeRF bindings maintained in this repository. These MATLAB bindings
are implemented as a thin object-oriented interface that utilizes
loadlibrary() and calllib().
Simulink support is achieved through a MATLAB System block
implementation that uses bladeRF.m. Users are welcome to adapt the
provided bladeRF_Simulink.m implementation to their particular needs.
This provides a non-blocking variant of bladerf_submit_stream_buffer(),
which provides API users with more control over how they might want
to handle asynchronous buffer submission.
This API functionality has been exposed to allow users to implement
schemes similar to that used to address Issue #438.
This fixes issue #438, in which the bladerf_sync_tx() implementation
was limited by the number of transfers, and not taking advantage
of the available TX buffers (beyond N=<num_transfers>).
This is addressed by allowing the bladerf_sync_tx() context to defer
buffer submission to the sync TX callback handler when it is unable to
submit filled buffers.
Once assigned the responsibility of submitting deferred (filled)
buffers, the sync TX callback will continue to do so until
no filled buffers are available. At this point, the callback
relinquishes its submission duty back to the bladerf_sync_tx() context.
This is one step towards addressing issue #438; we must first
know that we are unable to submit a buffer so that we can defer
its submission to a later callback.