Commit graph

11 commits

Author SHA1 Message Date
Ryan Thompson
e2f5b369d4 libbladeRF: usleep no longer necessary per fix to stream format config 2023-02-13 03:28:19 -08:00
Ryan Thompson
4150c8fa9b host: test_digital_loopback bitmode select added
The digital loopback test now allows for the selection of 8bit or 16bit
mode from the command line using -b or --bitmode command line
arguments.
2023-02-13 03:28:19 -08:00
Ryan Thompson
6c20bc9e06 host: test_digital_loopback RX stream enable fix
rx module in test_digital_loopback now waits for a running tx stream before enabling
2023-02-13 03:28:19 -08:00
Ryan Thompson
ea0edf3f52 host: comments added to test_digital_loopback
clarified rx, tx, and loopback initializations and enabled stream
sections
2023-02-13 03:28:19 -08:00
Ryan Thompson
15b7d9c3b6 host: squashed cmake warnings
updated cmake requirement from 2.8 to 2.8.12
2023-02-13 03:28:19 -08:00
Rey Tucker
85fd6da22a
host: fix builds on 32-bit platforms (#573)
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.
2018-08-16 18:57:52 -04:00
Rey Tucker
1dc6317b93
host: make low-level API calls generic by removing part numbers (#49)
Instead of using specific part numbers for low-level API calls on the bladeRF micro, use generic functionality-based names.
2018-05-25 10:55:04 -04:00
Rey Tucker
ee55f859b9
host: clean up build warnings across multiple platforms (#21)
With this commit, we build without warnings on Arch Linux; CentOS 7; Debian 8 and 9; latest Fedora; Ubuntu 14.04, 16.04, 17.10, and 18.04; Visual Studio 2017; and macOS 10.13.3 w/ Homebrew.

* host: libbladeRF: compile AD9361 srcs with -std=gnu11

Fixes compile errors involving ‘for’ loop initial declarations only
allowed in C99 or C11 mode, on older GCCs.

* host: libbladeRF/adi: remove stdbool workaround

This is not necessary now that we're building to -std=gnu11, and in
fact, it seems to create a conflict.

* host: libbladeRF: pre-declare loop variables

Some compilers are not happy with declaring the loop variable in the for
statement.  Begrudgingly placate them.

* host: libbladeRF_test: pre-declare loop variables

Some compilers are not happy with declaring the loop variable in the for
statement.  Begrudgingly placate them.

* host: bladeRF-cli: pre-declare loop variables

Some compilers are not happy with declaring the loop variable in the for
statement.  Begrudgingly placate them.

* host: libbladeRF: remove refs to strings.h

Windows doesn't have strings.h, but string.h seems to do just fine.

* host: libbladeRF: fix windows compile errors (WIP)

* host: libbladeRF/ad9361: fix windows compile error

"IGNORE" is #define'd in the Windows environment, creating a conflict.
Renaming this to solve the conflict.

* host: common: add setenv implementation for Windows

* host: libbladeRF: build setenv.c stub on Windows

* host: bladeRF-cli: use setenv stub on Windows

* host: common: fixup spacing consistency in setenv

* host: libbladeRF: cast channel macros to bladerf_channel

Visual Studio is picky about this, and throws warnings.

* host: libbladeRF: bladerf2.c: undo workaround for bladerf_channel

* host: libbladeRF: bladerf_get_gain_stages count type is now size_t

This fixes a Windows compile error, and is also generally more sensible.

* host: bladeRF-cli: fix windows compile errors

* host: ad9361: fix variadic macro syntax

Fixes Windows build errors

* host: ad9361: rename _DEBUG to AD9361_DEBUG

Visual Studio automagically sets _DEBUG if the /MDd option is set. Turns
out that a lot of the debugging sections don't build in Visual Studio,
so this accounts for a large number of the build errors...

* host: libbladeRF: fixes for Visual Studio builds

* host: common: fixes for Visual Studio builds

* host: libbladeRF/ad9361: fixes for Visual Studio builds

* host: libbladeRF_test: fixes for Visual Studio builds

* host: bladeRF-cli: fixes for Visual Studio builds

* host: bladeRF-cli: fix static analysis warnings

Fixes potential memory leak in main

Fixes unused values in set_adf_refclk, set_samplerate

* host: common: fix static analysis warnings

fixes:
unread variable in perform_rx_cal
memory leaks in add_arg, add_opt

* host: libbladeRF: fix static analysis warnings

fixes unused variables in bladerf2_set_gain and xb100_enable
2018-04-03 18:20:51 -04:00
Brian Glod
f06679bf78 host: libbladeRF_test: Fix GCC undefined operation
"state->idx = (++state->idx)" is undefined behavior for the compiler
2018-01-15 13:31:24 -05:00
Rey Tucker
1b066d7ca9 host: libbladeRF_test: test_digital_loopback fixes
Make test_digital_loopback work with bladeRF micro

General cleanup/modernization
2018-01-12 18:07:19 -05:00
Vanya A. Sergeev
0c09e664c2 libbladeRF_test: add digital loopback test 2017-12-21 12:55:04 -05:00