Updates the release notes for v2.0 to include more useful information, less useless information, and fewer typos. More consistent and readable, hopefully.
Also fixes one error in the documentation in libbladeRF.h.
* host: libbladeRF/doxygen: improve 2.0.0 relnotes
Some wording/formatting cleanup here and there.
Add \remarks for most sections to suggest some "do not" and "do" items.
Add some quick documentation on the bias tees, PLL, power status, etc.
* host: libbladeRF: fix doc for bladerf_get_timestamp
* host: libbladeRF/doxygen: more relnotes work
Adding a "What is a channel?" section to describe channels
* libbladeRF: 2.0.0 relnotes: soften wording, misc cleanup
* libbladeRF: relnotes: new section on gain ranges, fixup sectioning for Further Info
* libbladeRF: relnotes: more fixes, cleanup
* libbladeRF: relnotes: more tweaks, getting close
* libbladeRF: relnotes: final changes, honest
* libbladeRF: docs: relnotes 2.0.0 -> relnotes 2.0
This is actually more sensible given the versioning.
* libbladeRF: relnotes: fix typos/spelling
* libbladeRF: relnotes: hand-merge ac6b182c
Update wording
The bladeRF-micro has an option to use either its onboard VCTCXO or an
external 38.4 MHz clock as the clock source for components on the
board. This change addresses some ambiguity in the naming of the onboard
option by renaming it from 'vctcxo' to 'onboard'.
The valid options are now:
1. onboard
2. external
Fixes a lockup/crashy bug where bladerf2_get_vctcxo_trim would cause active RX/TX streams to fail. Also ensures that "set trimdac" won't inadvertently re-enable the trim DAC if it is disabled (e.g. because the PLL is enabled).
* host: libbladeRF/bladerf2: cache factory trimdac value
bladerf2_get_vctcxo_trim called spi_flash_rad_vctcxo_trim, which causes
an USB mode change which is incompatible with active sample streaming.
This would cause active RX/TX to fail if someone used "set trimdac" or
even "print".
We now cache the value during initialization, and return the cached
value if it is requested later on.
* host: libbladeRF/bladerf2: preserve trimdac disable state
If bladerf2_trim_dac_write is called with a new value, while the trim
DAC is disabled, make sure we do not inadvertently re-enable the trim
DAC. Save the new value in the board_data struct for later use by
bladerf2_set_trim_dac_enable.
If a pre-2.2.0 firmware is flashed to a bladeRF2 device, there is no way
to fix the problem without jumpering into bootloader because the
initialization aborts with a BLADERF_ERR_UNEXPECTED.
Here, we're looking for the bladeRF2 FPGA signatures, and if we find
them, we return from bladerf1_open() early after printing some useful
tips. This allows firmware flashing to occur, but not much else because
the FPGA is not loaded.
Fixes#572
* "set loopback" command aware of board type
The help dialog was giving incorrect information when a bladeRF2 is connected.
According to the library code, only "firmware", "none" and "rfic_bist"
are valid options for that board.
https://github.com/Nuand/bladeRF/blob/master/host/libraries/libbladeRF/src/board/bladerf2/bladerf2.c#L3837
Now we only display the other options when a bladeRF1 is connected.
Signed-off-by: Josh Farwell <josh.farwell@gmail.com>
* bladeRF-cli: check for bladeRF2 in "set loopback" help
rfic_bist is only a valid mode on bladeRF2, do a check
so we don't display it incorrectly for bladeRF1 users.
Signed-off-by: Josh Farwell <josh.farwell@gmail.com>
Builds were failing in various ways on 32-bit platforms, due to various assumptions (and the fact that pretty much everything is 64-bit nowadays). This PR should fix all of them so that it builds clean.
* host: libbladeRF/thirdparty/adi: fix build error on 32-bit systems
sizeof(void*) is not necessarily equal to sizeof(uint64_t)
* host: libbladeRF/doc: fix 32-bit build failure on doc example
sizeof(size_t) does not always equal sizeof(uint64_t)
* host: docker: remove centos-7-i386 build
it doesn't work, and this is an edgy-enough case that i think we'll be
okay with the ubuntu i386 builds
* host: libbladeRF/bladerf2: explicitly note constant types
On non-64-bit platforms, these integer constants can be ambiguous, which
throws compiler warnings.
* host: libbladeRF_test: explicitly note constant types
On non-64-bit platforms, these integer constants can be ambiguous, which
throws compiler warnings.
Massive changes to bladeRF_rx_gui to allow it to work with the new gain methods
and also allow it to properly inform the user of problems setting gains when
the gain mode (AGC) is set to automatic.
Some platforms have power and temperature monitoring, provide a way for them to
be exposed in matlab. To read the temperature of a device run the following:
> b = bladeRF()
> b.misc.temperature
misc.dc_power can be used to read the current power consumption
misc.dc_source be used to determine if the power is coming from USB or AC
bladeRF_XCVR has to catch up to the new way of doing things in libbladeRF. Low
level gain settings like directly RXLNA, RXVGA1, RXVGA2, TXVGA1, and TXVGA2 have
all been removed to make way for the unified gain setting based on
bladerf_set_gain(). Setting the gain value to 60 for RX indicates maximum RX
gain, while a value of 60 for TX indicates a output power of 0dBm.
Adding the new A4 and A9 boards. Currently some decisions are being made by
identifying the generation of the device. In the future this should be replaced
with a feature and capability mask.
Most of the changes that make libbladeRF return -8 still allow scripts to run
without serious issues. This commit should be changed back after a few releases
once developers have had a chance to update their scripts.
log_get_verbosity returns the current logging level, which may be useful
for situations where a lot of processing is required for verbose
logging, etc.
Fix up the verbose logging on nios_ad9361_spi_read/write so that the
numbers line up, and so that it expands out multi-reads and multi-writes
in a useful fashion.
In the event of a timeout, an error is emitted from the actual place where the timeout occurred.
Also, if ENABLE_LIBBLADERF_SYNC_LOG_VERBOSE is defined, it will now print out a condensed status of all the buffers on each run through the sync state machine.
* host: sync: add error message when wait_for_buffer times out
* host: libusb: add error message for timeout
* clean up wording on libusb.c err a bit
* host: sync_worker: add debug prints on init failures
* host: bladerf2: print wallclock time on enable_module
* host: sync: add more super-verbose debug print
* host: sync: simplify ifdef
* host: libbladeRF: clang-format modified functions
Corrects an issue where enabling multiple RX channels would create some confusing discontinuities in the sample stream.
The first RX channel configured would start samples buffering in the FIFO, but the second configuration would not be apparent until after those samples were read.
This PR also does a general refactoring of bladerf2_enable_module and associated helper functions to make the logic flow more clear.