mirror of
https://github.com/greatscottgadgets/hackrf.git
synced 2026-03-03 22:15:40 +01:00
Update hardware documentation to cover HackRF Pro.
This commit is contained in:
Martin Ling
BIN
docs/images/hackrf-pro-preliminary-photo.jpg
Normal file
BIN
docs/images/hackrf-pro-preliminary-photo.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
BIN
docs/images/rad1o_8.jpg
Normal file
BIN
docs/images/rad1o_8.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.1 MiB |
@@ -1,8 +1,8 @@
|
||||
Enclosure Options
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
The commercial version of HackRF One from Great Scott Gadgets ships with an injection molded plastic enclosure, but it is designed to fit two optional enclosures:
|
||||
Commercial versions of both HackRF Pro and HackRF One from Great Scott Gadgets ship with an injection molded plastic enclosure, but are also designed to fit two optional enclosures:
|
||||
|
||||
* Hammond 1455J1201: HackRF One fits this extruded aluminum enclosure and other similar models from Hammond Manufacturing. In order to use the enclosure's end plates, you will have to drill them. An end plate template can be found in the HackRF One KiCad layout.
|
||||
* Hammond 1455J1201: Both HackRF Pro and HackRF One fit this extruded aluminum enclosure and other similar models from Hammond Manufacturing. In order to use the enclosure's end plates, you will have to drill them. An end plate template can be found in the relevant HackRF KiCad layout.
|
||||
|
||||
* Acrylic sandwich: You can also use a laser cut acrylic enclosure with HackRF One. This is a good option for access to the expansion headers. A design can be found in the HackRF One hardware directory. Use any laser cutting service or purchase from a `reseller <https://greatscottgadgets.com/hackrf/acrylic-case/>`__.
|
||||
* Acrylic sandwich: You can also use a laser cut acrylic enclosure with either HackRF Pro or HackRF One. This is a good option for access to the expansion headers. A design can be found in the HackRF hardware directory. Use any laser cutting service or purchase from a `reseller <https://greatscottgadgets.com/hackrf/acrylic-case/>`__.
|
||||
|
||||
@@ -1,55 +1,7 @@
|
||||
Expansion Interface
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The HackRF One expansion interface consists of headers P9, P20, P22, and P28. These four headers are installed on the commercial HackRF One from Great Scott Gadgets.
|
||||
|
||||
|
||||
|
||||
P9 Baseband
|
||||
^^^^^^^^^^^
|
||||
|
||||
A direct analog interface to the high speed dual ADC and dual DAC.
|
||||
|
||||
.. list-table ::
|
||||
:header-rows: 1
|
||||
:widths: 1 1
|
||||
|
||||
* - Pin
|
||||
- Function
|
||||
* - 1
|
||||
- GND
|
||||
* - 2
|
||||
- GND
|
||||
* - 3
|
||||
- GND
|
||||
* - 4
|
||||
- RXBBQ-
|
||||
* - 5
|
||||
- RXBBI-
|
||||
* - 6
|
||||
- RXBBQ+
|
||||
* - 7
|
||||
- RXBBI+
|
||||
* - 8
|
||||
- GND
|
||||
* - 9
|
||||
- GND
|
||||
* - 10
|
||||
- TXBBI-
|
||||
* - 11
|
||||
- TXBBQ+
|
||||
* - 12
|
||||
- TXBBI+
|
||||
* - 13
|
||||
- TXBBQ-
|
||||
* - 14
|
||||
- GND
|
||||
* - 15
|
||||
- GND
|
||||
* - 16
|
||||
- GND
|
||||
|
||||
|
||||
The common HackRF expansion interface consists of headers P20, P22, and P28. These headers are present on both HackRF Pro and HackRF One, and support hardware add-ons including PortaPack and Opera Cake.
|
||||
|
||||
P20 GPIO
|
||||
^^^^^^^^
|
||||
@@ -65,15 +17,15 @@ Providing access to GPIO, ADC, RTC, and power.
|
||||
* - 1
|
||||
- VBAT
|
||||
* - 2
|
||||
- RTC_ALARM
|
||||
- RTC_ALARM (One) / PB_5 (Pro)
|
||||
* - 3
|
||||
- VCC
|
||||
- VCC (One) / 3V3AUX (Pro)
|
||||
* - 4
|
||||
- WAKEUP
|
||||
* - 5
|
||||
- GPIO3_8
|
||||
* - 6
|
||||
- GPIO3_0
|
||||
- GPIO3_0 (One) / GPIO3_9 (Pro)
|
||||
* - 7
|
||||
- GPIO3_10
|
||||
* - 8
|
||||
@@ -121,7 +73,7 @@ I2S, SPI, I2C, UART, GPIO, and clocks.
|
||||
* - Pin
|
||||
- Function
|
||||
* - 1
|
||||
- CLKOUT
|
||||
- CLKOUT (One) / P2 (Pro)
|
||||
* - 2
|
||||
- CLKIN
|
||||
* - 3
|
||||
@@ -133,21 +85,21 @@ I2S, SPI, I2C, UART, GPIO, and clocks.
|
||||
* - 6
|
||||
- I2C1_SDA
|
||||
* - 7
|
||||
- SPIFI_MISO
|
||||
- SPIFI_MISO (One) / PB_1 (Pro)
|
||||
* - 8
|
||||
- SPIFI_SCK
|
||||
- SPIFI_SCK (One) / PB_3 (Pro)
|
||||
* - 9
|
||||
- SPIFI_MOSI
|
||||
- SPIFI_MOSI (One) / PA_4 (Pro)
|
||||
* - 10
|
||||
- GND
|
||||
* - 11
|
||||
- VCC
|
||||
- VCC (One) / 3V3AUX (Pro)
|
||||
* - 12
|
||||
- I2S0_RX_SCK
|
||||
- I2S0_RX_SCK (One) / PA_3 (Pro)
|
||||
* - 13
|
||||
- I2S_RX_SDA
|
||||
- I2S0_RX_SDA (One) / I2S0_TX_SDA (Pro)
|
||||
* - 14
|
||||
- I2S0_RX_MCLK
|
||||
- I2S0_RX_MCLK (One) / PB_0 (Pro)
|
||||
* - 15
|
||||
- I2S0_RX_WS
|
||||
* - 16
|
||||
@@ -169,7 +121,7 @@ I2S, SPI, I2C, UART, GPIO, and clocks.
|
||||
* - 24
|
||||
- SDA
|
||||
* - 25
|
||||
- CLK6
|
||||
- CLK6 (One) / AUX_CLK2 (Pro)
|
||||
* - 26
|
||||
- SCL
|
||||
|
||||
@@ -187,7 +139,7 @@ SDIO, GPIO, clocks, and CPLD.
|
||||
* - Pin
|
||||
- Function
|
||||
* - 1
|
||||
- VCC
|
||||
- VCC (One) / 3V3AUX (Pro)
|
||||
* - 2
|
||||
- GND
|
||||
* - 3
|
||||
@@ -211,25 +163,69 @@ SDIO, GPIO, clocks, and CPLD.
|
||||
* - 12
|
||||
- GND
|
||||
* - 13
|
||||
- GCK2
|
||||
- GCK2 (One) / P5_6 (Pro)
|
||||
* - 14
|
||||
- GCK1
|
||||
- GCK1 (One) / P5_7 (Pro)
|
||||
* - 15
|
||||
- B1AUX14 (trigger output)
|
||||
- Trigger out: B1AUX14 (One) / TRIGGER.OUT (Pro)
|
||||
* - 16
|
||||
- B1AUX13 (trigger input)
|
||||
- Trigger in: B1AUX13 (One) / TRIGGER.IN (Pro)
|
||||
* - 17
|
||||
- CPLD_TCK
|
||||
* - 18
|
||||
- BANK2F3M2
|
||||
- BANK2F3M2 (One) / PE_0 (Pro)
|
||||
* - 19
|
||||
- CPLD_TDI
|
||||
- CPLD_TDI (One) / I2S0_RX_SDA (Pro)
|
||||
* - 20
|
||||
- BANK2F3M6
|
||||
- BANK2F3M6 (One) / P9_1 (Pro)
|
||||
* - 21
|
||||
- BANK2F3M12
|
||||
- BANK2F3M12 (One) / P5_3 (Pro)
|
||||
* - 22
|
||||
- BANK2F3M4
|
||||
- BANK2F3M4 (One) / P1_7 (Pro)
|
||||
|
||||
P9 Baseband (HackRF One)
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
A direct analog interface to the high speed dual ADC and dual DAC.
|
||||
|
||||
.. list-table ::
|
||||
:header-rows: 1
|
||||
:widths: 1 1
|
||||
|
||||
* - Pin
|
||||
- Function
|
||||
* - 1
|
||||
- GND
|
||||
* - 2
|
||||
- GND
|
||||
* - 3
|
||||
- GND
|
||||
* - 4
|
||||
- RXBBQ-
|
||||
* - 5
|
||||
- RXBBI-
|
||||
* - 6
|
||||
- RXBBQ+
|
||||
* - 7
|
||||
- RXBBI+
|
||||
* - 8
|
||||
- GND
|
||||
* - 9
|
||||
- GND
|
||||
* - 10
|
||||
- TXBBI-
|
||||
* - 11
|
||||
- TXBBQ+
|
||||
* - 12
|
||||
- TXBBI+
|
||||
* - 13
|
||||
- TXBBQ-
|
||||
* - 14
|
||||
- GND
|
||||
* - 15
|
||||
- GND
|
||||
* - 16
|
||||
- GND
|
||||
|
||||
Additional unpopulated headers and test points are available for test and development, but they may be incompatible with some enclosure or expansion options.
|
||||
|
||||
|
||||
@@ -1,9 +1,17 @@
|
||||
===========================================
|
||||
External Clock Interface (CLKIN and CLKOUT)
|
||||
===========================================
|
||||
========================
|
||||
External Clock Interface
|
||||
========================
|
||||
|
||||
.. _external_clock_interface:
|
||||
|
||||
HackRF Pro
|
||||
~~~~~~~~~~
|
||||
|
||||
HackRF Pro has two configurable SMA ports, P1 and P2. By default, P1 is configured as CLKIN and P2 as CLKOUT. The default behaviour of these signals is as described for HackRF One below.
|
||||
|
||||
HackRF One
|
||||
~~~~~~~~~~
|
||||
|
||||
HackRF One produces a 10 MHz clock signal on CLKOUT. The signal is a 3.3 V, 10 MHz square wave intended for a high impedance load.
|
||||
|
||||
The CLKIN port on HackRF One is a high impedance input that expects 3.3 V square wave at 10 MHz. Do not exceed 3.3 V or drop below 0 V on this input. Do not connect a clock signal at a frequency other than 10 MHz (unless you modify the firmware to support this). You may directly connect the CLKOUT port of one HackRF One to the CLKIN port of another HackRF One.
|
||||
|
||||
@@ -2,6 +2,6 @@
|
||||
Connectors
|
||||
==========
|
||||
|
||||
The connectors on HackRF One are SMA.
|
||||
The connectors on both HackRF Pro and HackRF One are SMA.
|
||||
|
||||
**Note:** SMA connectors and RP-SMA connectors are visually very similar. If you connect an RP-SMA antenna to HackRF One, it will seem to connect snugly but won't function at all because neither the male nor female side has a center pin. RP-SMA connectors are most common on 2.4 GHz antennas and are popular on Wi-Fi equipment. Adapters are available.
|
||||
**Note:** SMA connectors and RP-SMA connectors are visually very similar. If you connect an RP-SMA antenna to a HackRF, it will seem to connect snugly but won't function at all because neither the male nor female side has a center pin. RP-SMA connectors are most common on 2.4 GHz antennas and are popular on Wi-Fi equipment. Adapters are available.
|
||||
|
||||
@@ -2,10 +2,12 @@
|
||||
HackRF One
|
||||
================================================
|
||||
|
||||
.. _hackrf_one:
|
||||
|
||||
.. image:: ../images/HackRF-One-fd0-0009.jpeg
|
||||
:alt: HackRF One
|
||||
|
||||
HackRF One is the current hardware platform for the HackRF project. It is a Software Defined Radio peripheral capable of transmission or reception of radio signals from 1 MHz to 6 GHz. Designed to enable test and development of modern and next generation radio technologies, HackRF One is an open source hardware platform that can be used as a USB peripheral or programmed for stand-alone operation.
|
||||
HackRF One was the first production hardware platform for the HackRF project. It is a Software Defined Radio peripheral capable of transmission or reception of radio signals from 1 MHz to 6 GHz. Designed to enable test and development of modern and next generation radio technologies, HackRF One is an open source hardware platform that can be used as a USB peripheral or programmed for stand-alone operation.
|
||||
|
||||
| `Product page <https://greatscottgadgets.com/hackrf/one/>`_
|
||||
| `Where to buy <https://greatscottgadgets.com/hackrf/one/#purchasing>`_
|
||||
|
||||
50
docs/source/hackrf_pro.rst
Normal file
50
docs/source/hackrf_pro.rst
Normal file
@@ -0,0 +1,50 @@
|
||||
================================================
|
||||
HackRF Pro
|
||||
================================================
|
||||
|
||||
.. image:: ../images/hackrf-pro-preliminary-photo.jpg
|
||||
:alt: HackRF Pro
|
||||
|
||||
HackRF Pro is the current hardware platform for the HackRF project. It is a Software Defined Radio peripheral capable of transmission or reception of radio signals from 100 kHz to 6 GHz. HackRF Pro is designed to be backwards compatible with software and hardware developed for use with
|
||||
:ref:`HackRF One <hackrf_one>`,
|
||||
whilst introducing many new features and improvements.
|
||||
|
||||
| `Product page <https://greatscottgadgets.com/hackrf/pro/>`_
|
||||
| `Where to buy <https://greatscottgadgets.com/hackrf/pro/#purchasing>`_
|
||||
|
||||
Features
|
||||
~~~~~~~~
|
||||
|
||||
* 100 kHz to 6 GHz operating frequency
|
||||
* Tunable from 0 Hz to 7.1 GHz
|
||||
* Half-duplex transceiver
|
||||
* Up to 20 million samples per second
|
||||
* 8-bit quadrature samples (8-bit I and 8-bit Q)
|
||||
* Compatible with GNU Radio, SDR#, and more
|
||||
* Software-configurable RX and TX gain and baseband filter
|
||||
* Software-controlled RF port power (50 mA at 3.3 V)
|
||||
* SMA RF connector
|
||||
* SMA clock input and output for synchronization and triggering
|
||||
* Convenient buttons for programming
|
||||
* Internal pin headers for expansion
|
||||
* High-Speed USB 2.0 with Type-C connector
|
||||
* USB-powered
|
||||
* Open source hardware
|
||||
|
||||
Compared to HackRF One, HackRF Pro introduces a host of new and updated features, including:
|
||||
|
||||
* Wider operating frequency range
|
||||
* Improved RF performance with flatter frequency response
|
||||
* Modern USB Type-C connector
|
||||
* Built-in TCXO crystal oscillator for superior timing stability
|
||||
* Logic upgrade from a CPLD to a power-efficient FPGA
|
||||
* Elimination of the DC spike
|
||||
* Extended-precision mode with 16-bit samples for low sample rates (typical ENOB: 9-11)
|
||||
* Half-precision mode with 4-bit samples at up to 40 Msps
|
||||
* More RAM and flash memory for custom firmware
|
||||
* Installed shielding around the radio section
|
||||
* Trigger input and output accessible through clock connectors
|
||||
* Cutout in the PCB provides space for future add-ons
|
||||
* Improved power management
|
||||
* Enhanced RF port protection
|
||||
* Facility to hardware-disable transmit mode
|
||||
@@ -2,10 +2,12 @@
|
||||
Buttons
|
||||
=======
|
||||
|
||||
This information is applicable to both HackRF Pro and HackRF One.
|
||||
|
||||
The **RESET button** resets the microcontroller. This is a reboot that should result in a USB re-enumeration.
|
||||
|
||||
The **DFU button** invokes a USB DFU bootloader located in the microcontroller's ROM. This bootloader makes it possible to unbrick a HackRF One with damaged firmware because the ROM cannot be overwritten.
|
||||
The **DFU button** invokes a USB DFU bootloader located in the microcontroller's ROM. This bootloader makes it possible to unbrick a HackRF with damaged firmware because the ROM cannot be overwritten.
|
||||
|
||||
The DFU button only invokes the bootloader during reset. This means that it can be used for other functions by custom firmware.
|
||||
|
||||
To invoke DFU mode: Press and hold the DFU button. While holding the DFU button, reset the HackRF One either by pressing and releasing the RESET button or by powering on the HackRF One. Release the DFU button.
|
||||
To invoke DFU mode: Press and hold the DFU button. While holding the DFU button, reset the HackRF either by pressing and releasing the RESET button or by powering on the HackRF. Release the DFU button.
|
||||
|
||||
@@ -2,32 +2,6 @@
|
||||
Hardware Components
|
||||
================================================
|
||||
|
||||
Major parts used in HackRF One:
|
||||
|
||||
* `MAX2837 2.3 to 2.7 GHz transceiver <https://www.analog.com/en/products/max2837.html>`__
|
||||
* `Datasheet <https://www.analog.com/media/en/technical-documentation/data-sheets/max2837.pdf>`__
|
||||
* `MAX2839 2.3 to 2.7 GHz transceiver <https://www.analog.com/en/products/max2839.html>`__
|
||||
* `Datasheet <https://www.analog.com/media/en/technical-documentation/data-sheets/max2839.pdf>`__
|
||||
* substitution for MAX2837.
|
||||
* `MAX5864 ADC/DAC <https://www.analog.com/en/products/max5864.html>`__
|
||||
* `Datasheet <https://www.analog.com/media/en/technical-documentation/data-sheets/MAX5864.pdf>`__
|
||||
* `Si5351 clock generator <http://www.silabs.com/products/clocksoscillators/clock-generator/Pages/lvcmos-clocks-5-outputs.aspx>`__
|
||||
* `AN619: Manually Generating an Si5351 Register Map <http://www.silabs.com/Support%20Documents/TechnicalDocs/AN619.pdf>`__
|
||||
* `Datasheet <http://www.silabs.com/Support%20Documents/TechnicalDocs/Si5351.pdf>`__ - see AN619 for the complete register map.
|
||||
* `Other Documentation <http://www.silabs.com/products/clocksoscillators/clock-generators-and-buffers/Pages/clock+vcxo.aspx>`__ - includes application notes, user guides, and white papers.
|
||||
* CoolRunner-II CPLD
|
||||
* `LPC43xx ARM Cortex-M4 microcontroller <http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/lpc-arm-cortex-m-mcus/lpc-dual-core-cortex-m0-m4f/lpc4300:MC_1403790133078>`__
|
||||
* `User Manual <http://www.nxp.com/documents/user_manual/UM10503.pdf>`__
|
||||
* `Datasheet <http://www.nxp.com/documents/data_sheet/LPC4350_30_20_10.pdf>`__
|
||||
* `Other Documentation (LPC4330FBD144) <http://www.nxp.com/products/microcontrollers/cortex_m4/lpc4300/LPC4330FBD144.html#documentation>`__ - includes errata and application notes.
|
||||
* `ARM-standard JTAG/SWD connector pinout <http://www.keil.com/support/man/docs/ulink2/ulink2_hw_connectors.htm>`__
|
||||
* `BSDL file for the LPC43xx (For boundary scan) <http://www.lpcware.com/system/files/LPC18xx_43xx%20BSDL%20files%2020121127_0.zip>`__
|
||||
* `RFFC5072 mixer/synthesizer <http://www.rfmd.com/store/rffc5072-1.html>`__
|
||||
* `Datasheet <http://www.rfmd.com/CS/Documents/RFFC5071_2DS.pdf>`__
|
||||
* `Other Documentation <http://www.rfmd.com/store/rffc5072-1.html>`__ ; click "Technical Documents" - includes programming guides and application notes.
|
||||
* `W25Q80BV 8M-bit Flash <https://www.winbond.com/resource-files/w25q80bv%20revk%2020151203.pdf>`__
|
||||
|
||||
|
||||
Block Diagrams
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
@@ -37,10 +11,43 @@ HackRF One r1-r8 Block Diagram
|
||||
.. image:: ../images/block-diagram.png
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
HackRF One r9 Block Diagram
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
.. image:: ../images/block-diagram-r9.png
|
||||
:align: center
|
||||
|
||||
Key Components
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
Major parts used in HackRF:
|
||||
|
||||
* `MAX2831 2.3 to 2.6 GHz transceiver <https://www.analog.com/en/products/max2831.html>`__
|
||||
* Used on HackRF Pro.
|
||||
* `Datasheet <https://www.analog.com/media/en/technical-documentation/data-sheets/MAX2831-MAX2832.pdf>`__
|
||||
|
||||
* `MAX2837 2.3 to 2.7 GHz transceiver <https://www.analog.com/en/products/max2837.html>`__
|
||||
* Used on HackRF One (except revision r9), Jawbreaker and rad1o.
|
||||
* `Datasheet <https://www.analog.com/media/en/technical-documentation/data-sheets/max2837.pdf>`__
|
||||
* `MAX2839 2.3 to 2.7 GHz transceiver <https://www.analog.com/en/products/max2839.html>`__
|
||||
* Substitution for MAX2837, used on HackRF One revision r9.
|
||||
* `Datasheet <https://www.analog.com/media/en/technical-documentation/data-sheets/max2839.pdf>`__
|
||||
* `MAX5864 ADC/DAC <https://www.analog.com/en/products/max5864.html>`__
|
||||
* `Datasheet <https://www.analog.com/media/en/technical-documentation/data-sheets/MAX5864.pdf>`__
|
||||
* `Si5351 clock generator <http://www.silabs.com/products/clocksoscillators/clock-generator/Pages/lvcmos-clocks-5-outputs.aspx>`__
|
||||
* `AN619: Manually Generating an Si5351 Register Map <http://www.silabs.com/Support%20Documents/TechnicalDocs/AN619.pdf>`__
|
||||
* `Datasheet <http://www.silabs.com/Support%20Documents/TechnicalDocs/Si5351.pdf>`__ - see AN619 for the complete register map.
|
||||
* `Other Documentation <http://www.silabs.com/products/clocksoscillators/clock-generators-and-buffers/Pages/clock+vcxo.aspx>`__ - includes application notes, user guides, and white papers.
|
||||
* `ice40 UltraPlus FPGA <https://www.latticesemi.com/en/Products/FPGAandCPLD/iCE40UltraPlus>`__ (HackRF Pro)
|
||||
* CoolRunner-II CPLD (all other platforms)
|
||||
* `LPC43xx ARM Cortex-M4 microcontroller <http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/lpc-arm-cortex-m-mcus/lpc-dual-core-cortex-m0-m4f/lpc4300:MC_1403790133078>`__
|
||||
* `User Manual <http://www.nxp.com/documents/user_manual/UM10503.pdf>`__
|
||||
* `Datasheet <http://www.nxp.com/documents/data_sheet/LPC4350_30_20_10.pdf>`__
|
||||
* `Other Documentation (LPC4330FBD144) <http://www.nxp.com/products/microcontrollers/cortex_m4/lpc4300/LPC4330FBD144.html#documentation>`__ - includes errata and application notes.
|
||||
* `ARM-standard JTAG/SWD connector pinout <http://www.keil.com/support/man/docs/ulink2/ulink2_hw_connectors.htm>`__
|
||||
* `BSDL file for the LPC43xx (For boundary scan) <http://www.lpcware.com/system/files/LPC18xx_43xx%20BSDL%20files%2020121127_0.zip>`__
|
||||
* `RFFC5072 mixer/synthesizer <http://www.rfmd.com/store/rffc5072-1.html>`__
|
||||
* `Datasheet <http://www.rfmd.com/CS/Documents/RFFC5071_2DS.pdf>`__
|
||||
* `Other Documentation <http://www.rfmd.com/store/rffc5072-1.html>`__ ; click "Technical Documents" - includes programming guides and application notes.
|
||||
* `W25Q32 32M-bit Flash <https://www.winbond.com/resource-files/W25Q32JV%20RevJ%2012242024%20Plus.pdf>`__ (HackRF Pro)
|
||||
* `W25Q80BV 8M-bit Flash <https://www.winbond.com/resource-files/w25q80bv%20revk%2020151203.pdf>`__ (all other platforms)
|
||||
|
||||
@@ -4,26 +4,52 @@
|
||||
Hardware Triggering
|
||||
===================
|
||||
|
||||
HackRF One transmit and receive operations can be synchronized with another HackRF One or with other external equipment by using the trigger input and output on pin header P28. Triggering provides time synchronization with error of less than one sample period.
|
||||
HackRF transmit and receive operations can be synchronized with another HackRF or with other external equipment by using the trigger input and output. Triggering provides time synchronization with error of less than one sample period.
|
||||
|
||||
HackRF Pro has two configurable SMA ports, P1 and P2, which can be set up to provide both clock synchronization and triggering.
|
||||
|
||||
HackRF One has CLKIN and CLKOUT ports for clock synchronization, but hardware triggering requires opening the case to access the P28 header.
|
||||
|
||||
Clock Synchronization
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When triggering one HackRF One from another, it is often desirable to first ensure that the two devices share a common frequency reference. This has an added benefit of grounding the HackRFs to each other, eliminating one of the wires required for triggering. See :ref:`External Clock Interface <external_clock_interface>` for instructions.
|
||||
When triggering one HackRF from another, it is often desirable to first ensure that the two devices share a common frequency reference. This has an added benefit of grounding the HackRFs to each other, eliminating one of the wires required for triggering. See :ref:`External Clock Interface <external_clock_interface>` for instructions.
|
||||
|
||||
Either HackRF One may serve as the clock source for the other regardless of which is providing the trigger output.
|
||||
Either HackRF may serve as the clock source for the other regardless of which is providing the trigger output.
|
||||
|
||||
Usage
|
||||
~~~~~
|
||||
|
||||
Use ``hackrf_info`` to discover the serial numbers of both HackRFs. Using the serial number of the HackRF to be triggered, use ``hackrf_transfer -H`` to set up a triggered operation. For example:
|
||||
|
||||
* ``hackrf_transfer -H -d <serial number> -a 0 -l 32 -g 32 -r rx1.cs8``
|
||||
|
||||
The command will print "Waiting for trigger..." until a trigger signal is detected on the device's trigger input.
|
||||
|
||||
In another terminal, use the serial number of the triggering HackRF One to initiate an operation to take place at the same time as the triggered operation. For example:
|
||||
|
||||
* ``hackrf_transfer -d <serial number> -a 0 -l 32 -g 32 -r rx2.cs8``
|
||||
|
||||
Note that no special argument is required to activate the trigger output.
|
||||
|
||||
Both ``hackrf_transfer`` commands will start sampling RF signals at the same time, accurate to less than one sample period.
|
||||
|
||||
|
||||
Requirements
|
||||
~~~~~~~~~~~~
|
||||
Additional Devices
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Multiple HackRFs may be triggered by a single HackRF. Ensure that all the devices share a common ground and then connect one device's trigger output to the trigger inputs of the other devices (with jumpers connected via a breadboard, for example).
|
||||
|
||||
Equipment other than a HackRF may be connected to a HackRF's trigger input or output. The trigger signal is a 3.3 V pulse that triggers on the rising edge.
|
||||
|
||||
HackRF One Triggering Requirements
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
To connect two HackRF Ones for triggering you will need:
|
||||
|
||||
* a male-to-male jumper wire for 0.1" pin headers
|
||||
* an SMA cable for clock synchronization or a second jumper wire
|
||||
|
||||
|
||||
.. _open_your_hackrf_one:
|
||||
|
||||
Open Your HackRF One
|
||||
@@ -49,32 +75,6 @@ First ensure that the two devices share a common ground. This may be accomplishe
|
||||
Next use a jumper wire to connect P28 pin 15 (trigger output) on one HackRF One to P28 pin 16 (trigger input) on the other HackRF One.
|
||||
|
||||
|
||||
Usage
|
||||
~~~~~
|
||||
|
||||
Use ``hackrf_info`` to discover the serial numbers of both HackRF Ones. Using the serial number of the HackRF One to be triggered, use ``hackrf_transfer -H`` to set up a triggered operation. For example:
|
||||
|
||||
* ``hackrf_transfer -H -d <serial number> -a 0 -l 32 -g 32 -r rx1.cs8``
|
||||
|
||||
The command will print "Waiting for trigger..." until a trigger signal is detected on the device's trigger input.
|
||||
|
||||
In another terminal, use the serial number of the triggering HackRF One to initiate an operation to take place at the same time as the triggered operation. For example:
|
||||
|
||||
* ``hackrf_transfer -d <serial number> -a 0 -l 32 -g 32 -r rx2.cs8``
|
||||
|
||||
Note that no special argument is required to activate the trigger output.
|
||||
|
||||
Both ``hackrf_transfer`` commands will start sampling RF signals at the same time, accurate to less than one sample period.
|
||||
|
||||
|
||||
Additional Devices
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Multiple HackRF Ones may be triggered by a single HackRF One. Ensure that all the devices share a common ground and then connect one device's trigger output to the trigger inputs of the other devices (with jumpers connected via a breadboard, for example).
|
||||
|
||||
Equipment other than a HackRF One may be connected to a HackRF One's trigger input or output. The trigger signal is a 3.3 V pulse that triggers on the rising edge.
|
||||
|
||||
|
||||
References
|
||||
~~~~~~~~~~
|
||||
|
||||
|
||||
@@ -13,9 +13,17 @@ Welcome to HackRF's documentation!
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:caption: HackRF One Hardware
|
||||
:caption: Hardware Platforms
|
||||
|
||||
hackrf_pro
|
||||
hackrf_one
|
||||
rad1o
|
||||
jawbreaker
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:caption: Hardware Information
|
||||
|
||||
hackrf_one
|
||||
hackrf_minimum_requirements
|
||||
list_of_hardware_revisions
|
||||
hardware_components
|
||||
@@ -29,13 +37,6 @@ Welcome to HackRF's documentation!
|
||||
usb_cables
|
||||
rf_shield_installation
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:caption: Jawbreaker Hardware
|
||||
|
||||
jawbreaker
|
||||
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:caption: Firmware
|
||||
|
||||
@@ -2,8 +2,19 @@
|
||||
LEDs
|
||||
====
|
||||
|
||||
HackRF Pro
|
||||
~~~~~~~~~~
|
||||
|
||||
When HackRF Pro is plugged in to a USB host, four LEDs should turn on: MCU, FPGA, RF, and USB. The MCU LED indicates that the primary internal power supply is working properly. The FPGA and RF LEDs indicate that firmware is running and has switched on additional internal power supplies. The USB LED indicates that the HackRF Pro is communicating with the host over USB.
|
||||
|
||||
HackRF One
|
||||
~~~~~~~~~~
|
||||
|
||||
When HackRF One is plugged in to a USB host, four LEDs should turn on: 3V3, 1V8, RF, and USB. The 3V3 LED indicates that the primary internal power supply is working properly. The 1V8 and RF LEDs indicate that firmware is running and has switched on additional internal power supplies. The USB LED indicates that the HackRF One is communicating with the host over USB.
|
||||
|
||||
Both versions
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
The RX and TX LEDs indicate that a receive or transmit operation is currently in progress.
|
||||
|
||||
Each LED is a single color. There are no multi-colored LEDs on HackRF One. Adjacent LEDs are different colors in order to make them easier to distinguish from one another. The colors do not mean anything.
|
||||
Each LED is a single color. There are no multi-colored LEDs on either HackRF One or HackRF Pro. Adjacent LEDs are different colors in order to make them easier to distinguish from one another. The colors do not mean anything.
|
||||
|
||||
@@ -2,11 +2,15 @@
|
||||
Hardware Revisions
|
||||
================================================
|
||||
|
||||
HackRF One hardware revisions exist mainly to deal with changes in component availability. Each of the revisions meet the same performance specifications that are measured in the factory.
|
||||
Hardware revisions exist mainly to deal with changes in component availability. Each revision of a product meets the same performance specifications that are measured in the factory.
|
||||
|
||||
HackRF Pro
|
||||
~~~~~~~~~~
|
||||
|
||||
List of Hardware Revisions
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
The initial production revision of HackRF Pro is r1.2.1.
|
||||
|
||||
HackRF One
|
||||
~~~~~~~~~~
|
||||
|
||||
HackRF One r1–r4
|
||||
^^^^^^^^^^^^^^^^
|
||||
|
||||
16
docs/source/rad1o.rst
Normal file
16
docs/source/rad1o.rst
Normal file
@@ -0,0 +1,16 @@
|
||||
=====
|
||||
rad1o
|
||||
=====
|
||||
|
||||
rad1o is the badge from the 2015 Chaos Communication Camp.
|
||||
|
||||
The rad1o badge contains a full-featured SDR (software defined radio) half-duplex transceiver, operating in a frequency range of about 50 MHz - 4000 MHz, and is software compatible to the HackRF.
|
||||
|
||||
.. image:: ../images/rad1o_8.jpg
|
||||
:alt: rad1o
|
||||
|
||||
(rad1o picture provided by Christoph Krichenbauer with Creative Commons License CC-BY-NC_SA)
|
||||
|
||||
More information can be found at the `rad1o badge wiki <https://rad1o.badge.events.ccc.de/start>`__
|
||||
|
||||
Compared to HackRF One, the rad1o badge uses a different mixer (MAX2871) with a reduced frequency range.
|
||||
@@ -2,6 +2,8 @@
|
||||
RF Shield Installation Instructions
|
||||
===============================================
|
||||
|
||||
HackRF Pro ships with an RF shield as standard.
|
||||
|
||||
Official Great Scott Gadgets HackRF Ones do not come from the factory with an RF shield installed around the radio section of the PCB. They do, however, have pads in place so that one may be installed if a user has a reason and an inclination to do so. The reason that they do not come preinstalled is that early testing revealed that the RF shield did little to improve the performance of the HackRF One. The recommended RF shield is the BMI-S-230-F-R (frame) with the BMI-S-230-C (shield). A two part RF shield is recommended because the shield section can be removed to allow access to the RF section of the HackRF One. This can be important if it becomes necessary to probe any part of the RF section, or to replace any parts of the RF section. However, even with a two part RF shield, it can be difficult to access the RF section of the HackRF One in certain situations. The following steps are a basic set of instructions for installing a RF shield on a HackRF One.
|
||||
|
||||
**CAUTION: Soldering a RF shield onto a HackRF One comes with a certain amount of risk. Beyond the inherent risks of soldering itself, this process may damage the HackRF One and no warranty is available to cover damage incurred from this process. If you do choose to install a RF shield on your HackRF One please proceed with caution.**
|
||||
|
||||
@@ -21,7 +21,7 @@ The before and after images were both taken with the preamp on and the LNA and V
|
||||
|
||||
|
||||
|
||||
Why isn't my HackRF One detectable after I plug it into my computer?
|
||||
Why isn't my HackRF detectable after I plug it into my computer?
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
If your HackRF One isn't immediately detectable it is very possible that your Micro USB cable is not meeting HackRF One's requirements. HackRF One requires quite a bit of supply current and solid USB 2.0 high speed communications to operate. It is common for HackRF One to reveal cables with deficiencies such as carrying power but not data, carrying data but not enough power, etc. Please try multiple cables to resolve this issue. More than once people have gotten their HackRF One to work after trying their fifth cable.
|
||||
If your HackRF isn't immediately detectable it is very possible that your USB cable is not meeting HackRF's requirements. HackRF requires quite a bit of supply current and solid USB 2.0 high speed communications to operate. It is common for HackRF to reveal cables with deficiencies such as carrying power but not data, carrying data but not enough power, etc. Please try multiple cables to resolve this issue. More than once people have gotten their HackRF to work after trying their fifth cable.
|
||||
|
||||
Reference in New Issue
Block a user