This PR creates a git submodule for the analogdevicesinc/no-OS code, moving it from host/libraries/libbladeRF/src/driver/thirdparty/adi/ to thirdparty/analogdevicesinc/no-OS and adjusting the build process accordingly.
The build process will handle the git submodule init / git submodule update as required, or it may be done manually before the build. It will then copy the necessary files to the build tree, apply a series of patches for local modifications, and then build it as libad936x.
There are no changes to the build steps, although the build will fail if git submodule init/update needs to happen but can't (e.g. if github is not reachable).
* thirdparty: add no-OS library submodule
Adds a submodule for https://github.com/analogdevicesinc/no-OS/, pinned
at commit 0bba46e.
* thirdparty: patch and build libad936x
Add cmake file for libad936x
Move our local mods into patch files
* host: libbladeRF: transition to libad936x
Transitions libbladeRF (particularly bladerf2.c) to use the libad936x
package, compiled separately.
This also adds ad936x.h, a driver header file that contains the
necessary things from libad936x. This is cleaner than just importing
ad9361_api.h, due to the significant dependency/include challenges that
ensue...
* host: fix up libad936x build
Don't use ExternalProject, instead just add it as a subdirectory
Create a FindPatcher.cmake for the patch-or-git selector
Clean up and streamline the ad936x cmakelists
Clean up libbladeRF cmakelist formatting
* thirdparty: fix no-OS patch 0003
* host: ad936x: fixup build errors/warnings on macOS
* thirdparty/adi: patch to chop out ad9361_parse_fir
ad9361_parse_fir refers to sscanf, which is not readily available in the
Nios II library. We don't use this function, so it can go.
* libbladeRF: remove vestigial adi files
* debian: rm thirdparty ADI tree from license file
* host: thirdparty: fix git package handling
* host: thirdparty/ad936x: specify patches in order
It turns out that there's no guarantee that file(GLOB)
will output the patch files in the alphabetical order.
* Revert "debian: rm thirdparty ADI tree from license file"
This reverts commit 36cf335c0e.
* debian: update path in ADI copyright
This release introduces new functionality and bug fixes, generally expanding
support for the bladeRF 2.0 Micro. It consists of the following versions:
* FPGA bitstream v0.9.0
* FX3 firmware v2.3.1
* libbladeRF v2.1.0
* bladeRF-cli v1.7.0
* MATLAB & Simulink bindings v1.0.2
* Python bindings v1.1.0
Note to bladerf1 (x40/x115) users: AGC will not work with FPGA versions
older than v0.8.0, due to a change in the control register mapping. A warning
will be printed during device initialization if you are using an affected
FPGA version.
Summary of changes since 2018.08:
* FPGA
- Support for the ADS-B core on bladeRF micro
- Add metadata flags for miniexp{1,2} IO pin status
- Fix race condition during FX3/Nios UART initialization
- Fix bugs in bladeRF AGC control
- Timing closure improvements
- Build system fixes
* FX3
- Fix USB device reset interrupting SPI flash autoloading of FPGA images
- Add BLADE_USB_CMD_QUERY_FLASH_ID command
- Add BLADE_USB_CMD_QUERY_FPGA_SOURCE command
* libbladeRF
- API additions:
- Add format macros for bladerf_frequency and bladerf_timestamp
- Add 'manufacturer' and 'product' device description strings to
bladerf_devinfo struct
- Add bladerf_get_serial_struct() API function
- Add bladerf_get_flash_size() API function
- Add bladerf_trigger_signal values for J51-1 (bladerf2) and Miniexp-1
(generic)
- Add bladerf_get_fpga_source() API function
- Add meta RX hardware flags for underflow, miniexp{1,2}
- Fixes:
- bladerf2: support TX frequencies down to 47 MHz
- bladerf2: support sample rates down to 0.521 Msps
- bladerf1: fix BLADERF_GPIO_AGC_ENABLE
- bladerf2: fix bladerf_trigger_arm implementation
- streaming: extend USB transfer timeout to match the configured stream
timeout
- Misc:
- Install the doxygen docs, if generated
- Adjust RX gain mode lists for clarity
- bladerf1: implement bladerf_{get,set}_rf_port[s]
- bladerf1: skip initialization if BLADERF_FORCE_NO_FPGA_PRESENT is set
* bladeRF-cli
- Add libedit support
- Ensure device is initialized after deferred open
- info: display manufacturer, product, flash size
- print: show RF routing on bladerf1
- print: display supported ranges for sample rate, bandwidth, frequency
- probe: handle already-open devices
- version: display FPGA configuration source
* MATLAB & Simulink bindings
- Add missing BB_TXVGA1_RXLPF loopback option
- Fix tx_gain property handling in simulink
* Python
- Fix rx_channel_count, tx_channel_count
- Update with latest API functions
* Windows installer
- install-drivers: install a driver for the bootloader VID/PID (04b4:00f3),
allowing easier FX3 bootloader recovery operations
- Upgrade to libusb 1.0.22
This release introduces new functionality and bug fixes, particularly support
for the bladeRF 2.0 Micro product. It consists of the following versions:
* FPGA bitstream v0.7.3
* FX3 firmware v2.2.0
* libbladeRF v2.0.2
* bladeRF-cli v1.6.1
* MATLAB & Simulink bindings v1.0.1
* Python bindings v1.0.1
*****************************************************************************
*** libbladeRF v2.0 introduces a number of breaking changes !! ***
*****************************************************************************
*** Please see relnotes_2_0 in the Doxygen documentation for a full ***
*** discussion of the changes in libbladeRF v2.0. ***
*****************************************************************************
Summary of changes since 2016.06:
* FPGA
- Added support for Automatic Gain Control
- Redesign build system to support multiple product models
- Initial release with bladeRF Micro support
- Refactoring, bug fixes, and other misc. improvements
* FX3
- Add support for the bladeRF 2.0 (2cf0:5250).
- Fix loading FPGA bitstreams from flash when there is nothing connected to
the USB connector.
- Move USB descriptor consts to .usbdscr section so the linker glomps them.
* libbladeRF
- Added support for Automatic Gain Control
- Added bladeRF.conf config option file
- Refactor to support for multiple product lines
- Add support for the bladeRF Micro product
- API: replace bladerf_module with bladerf_channel, a reverse-compatible
change to handle products with multiple independent RF paths in the same
direction
- API: BREAKING CHANGE - on bladerf_set_frequency, et al, the frequency
parameter is now uint64_t instead of unsigned int
- Add typedefs for common param types, e.g. bladerf_frequency -> uint64_t
* bladeRF-cli
- Added support for Automatic Gain Control
- No longer initializes the bladeRF before loading a new FPGA image, to
avoid potential catch-22 problems
- bladeRF 2.0 Micro support
- Support for MIMO RX and TX using "channel=" parameter on rx/tx config
- Various code quality fixups
* MATLAB & Simulink bindings
- Add support for bladeRF 2.0 (Micro) products
- Change "not supported" (-8) library errors to Matlab warnings
temporarily, to permit some grace while others' scripts are updated.
- Update bladeRF_XCVR to use new unified gain control
- Add bladeRF_Misc for misc measurements and controls
- Update bladeRF_rx_gui to support unified gain
- Update Simulink block to match libbladeRF v2.0.0
* Python
- New in 2018.08
Updates control file version from 3.9.5 to 4.1.4.
Replaces http: URLs with https: URLs where applicable.
Updates copyright file to match restructuring in libbladeRF 2.
Include COPYING and legal/* files when installing docs.
Fix maintainer name :)
The mktemp/wget workflow creates the data files chmod 0600, which breaks
loading of firmware for non-root users. Explicitly chmod 0444 to allow
all users to read.
If wget fails, it's clobbering the FPGA/firmware storage
in /usr/share/Nuand/bladeRF, leading to terrible results.
Download to a temp file, then copy that if wget was
successful.
An MITM where a trusted proxy is frobulating HTTPS is
still possible; checking the md5sum again is probably
a great idea.
It looks like GNUInstallDirs, which determines CMAKE_INSTALL_LIBDIR, was
not working on Ubuntu 12.04.
This change introduces the use of a CMAKE_INSTALL_LIBDIR override, and
uses this in debian/rules to specify the value extracted from
dpkg-architecture.
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
Ubuntu vivid (and I believe Debian) has renamed libtecla1-dev to
just plain libtecla-dev. Either is OK for our purposes.
Also bump standards version to 3.9.5, and wrap the Build-Depends
line for clarity.