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.
This will be returned by API functions when an operation would need
to block to complete, but the caller has requested non-blocking
operation. In this situation, the caller may need to wait and
resubmit the request at a later time.
This regression was introduced around 2015-09-01 when I added support
for accessing individual pins. Support for setting the XB GPIO via
the full register word was intended to be retained, but was not.
This commit re-adds this functionality.
The purpose of this flowgraph is to exemplify control of the bladeRF via
the gr-osmosdr source. A README.md highlighting these various controls
will follow soon in another commit.
This allows rates to be specified via the numerator and denominator
only. For example, to specify Fs = (4.5*684*1e6) / 286
set samplerate rx 0 3078000000 286
Adding the ability to set the SMB frequency when in MIMO master mode.
Also fix a bug where attaching the xb200 and setting MIMO master
would turn off the other clock not allowing an xb200 enabled device
to ever be a master clock supplier.
Being able to set the master frequency is useful when you want to
lock test equipment to the bladeRF oscillator.