
With both counters in place, the number of bytes in the buffer is now indicated by the difference between the M0 and M4 counts. The M4 count needs to be increased whenever the M4 produces or consumes data in the USB bulk buffer, so that the two counts remain correctly synchronised. There are three places where this is done: 1. When a USB bulk transfer in or out of the buffer completes, the count is increased by the number of bytes transferred. This is the most common case. 2. At TX startup, the M4 effectively sends the M0 16K of zeroes to transmit, before the first host-provided data. This is done by zeroing the whole 32K buffer area, and then setting up the first bulk transfer to write to the second 16K, whilst the M0 begins transmission of the first 16K. The count is therefore increased by 16K during TX startup, to account for the initial 16K of zeros. 3. In sweep mode, some data is discarded. When this is done, the count is incremented by the size of the discarded data. The USB IRQ is masked whilst doing this, since a read-modify-write is required, and the bulk transfer completion callback may be called at any point, which also increases the count.
This repository contains host software (Linux/Windows) for HackRF, a project to produce a low cost, open source software radio platform.
How to build the host software on Linux:
Prerequisites for Linux (Debian/Ubuntu):
sudo apt-get install build-essential cmake libusb-1.0-0-dev pkg-config libfftw3-dev
Build host software on Linux:
mkdir host/build
cd host/build
cmake ..
make
sudo make install
sudo ldconfig
By default this will attempt to install an udev rule to /etc/udev/rules.d
to
provide the usb
or plugdev
group access to HackRF. If your setup requires
the udev rule to be installed elsewhere you can modify the path with
-DUDEV_RULES_PATH=/path/to/udev
.
Note: The udev rule is not installed by default for PyBOMBS installs as they do not ususally get installed with root privileges.
Clean CMake temporary files/dirs:
cd host/build
rm -rf *
How to build host software on Windows:
Prerequisites for Cygwin, MinGW, or Visual Studio:
- cmake-2.8.12.1 or later from http://www.cmake.org/cmake/resources/software.html
- libusbx-1.0.18 or later from http://sourceforge.net/projects/libusbx/files/latest/download?source=files
- fftw-3.3.5 or later from http://www.fftw.org/install/windows.html
- Install Windows driver for HackRF hardware or use Zadig see http://sourceforge.net/projects/libwdi/files/zadig
- If you want to use Zadig select HackRF USB device and just install/replace it with WinUSB driver.
Note for Windows build: You shall always execute hackrf-tools from Windows command shell and not from Cygwin or MinGW shell because on Cygwin/MinGW Ctrl C is not managed correctly and especially for hackrf_transfer the Ctrl C(abort) will not stop correctly and will corrupt the file.
For Cygwin:
mkdir host/build
cd host/build
cmake ../ -G "Unix Makefiles" -DCMAKE_LEGACY_CYGWIN_WIN32=1 -DLIBUSB_INCLUDE_DIR=/usr/local/include/libusb-1.0/
make
make install
For MinGW:
mkdir host/build
cd host/build
cmake ../ -G "MSYS Makefiles" -DLIBUSB_INCLUDE_DIR=/usr/local/include/libusb-1.0/
make
make install
For Visual Studio 2015 x64
Create library definition for MSVC to link to
C:\fftw-3.3.5-dll64> lib /machine:x64 /def:libfftw3f-3.def
c:\hackrf\host\build> cmake ../ -G "Visual Studio 14 2015 Win64" \
-DLIBUSB_INCLUDE_DIR=c:\libusb-1.0.21\libusb \
-DLIBUSB_LIBRARIES=c:\libusb-1.0.21\MS64\dll\lib\libusb-1.0.lib \
-DTHREADS_PTHREADS_INCLUDE_DIR=c:\pthreads-w32-2-9-1-release\Pre-built.2\include \
-DTHREADS_PTHREADS_WIN32_LIBRARY=c:\pthreads-w32-2-9-1-release\Pre-built.2\lib\x64\pthreadVC2.lib \
-DFFTW_INCLUDES=C:\fftw-3.3.5-dll64 \
-DFFTW_LIBRARIES=C:\fftw-3.3.5-dll64\libfftw3f-3.lib
CMake will produce a solution file named HackRF.sln
and a series of
project files which can be built with msbuild as follows:
c:\hackrf\host\build> msbuild HackRF.sln
How to build host the software on FreeBSD
You can use the binary package:
# pkg install hackrf
You can build and install from ports:
# cd /usr/ports/comms/hackrf
# make install
principal author: Michael Ossmann mike@ossmann.com