This version is outdated by a newer approved version.
This version (28 Apr 2016 10:55) is a draft.
Approvals: 0/1The Previously approved version (18 Mar 2016 16:12) is available.
This version (28 Apr 2016 10:55) is a draft.Approvals: 0/1The Previously approved version (18 Mar 2016 16:12) is available.
This is an old revision of the document!
Table of Contents
AD9361 HDL Reference Designs
Functional Overview
The reference design is a processor based (ARM, MicroBlaze, or NioS) embedded system. A functional block diagram of the system is given below. The device interface is a self-contained peripheral similar to other such pcores in the system. The core is programmable through an AXI-lite interface. The data path consists of a VDMA and DMA interface for the transmit and receive path respectively.
Digital Interface
The digital interface consists of 12bits of DDR data and supports full duplex operation in all configurations up to 2×2. The transmit and receive data paths share a single clock. The data is sent or received based on the configuration (programmable) from separate transmit and to separate receive chains.
Transmit
In the transmit direction, complex I and Q signals are generated for each RF. The digital source could either be an internal DDS or from the external DDR via VDMA. The internal DDS phase and frequency are programmable.
Receive
In the receive direction, each component of the delineated data is passed to a PN monitor. The monitors validates the digital interface signal capture and timing. The data then optionally DC-filtered, corrected for I/Q offset and phase mismatches and is written to the external DDR memory via DMA. An optional off-line FFT core may be used to generate a spectrum plot.
Control and SPI
The device control and monitor signals are interfaced to a GPIO module. The SPI signals are controlled by a separate AXI based SPI core.
Multi-Cores Operation (ADFMCOMMS5)
The core supports multiple instances of the same synchronized to a common clock. The ADFMCOMMS5 uses two instances of this core synchronized to a common clock. The data is recovered in each individual clock domain and transfers the data to a single clock domain. The multiple cores must all be using the same clock.
Supported Devices
Supported Carriers
These are the supported carriers for the HDL - not the complete package (software and HDL). Typically the software lags behind the HDL, so if you don't see the these listed on the main project page - it is not yet done.
For the FMCOMMS2, 3, 4 based boards, supported carriers include the Xilinx Zynq based systems:
but it also works on the Xilinx fabric only solutions (for experts, who have used the zynq based systems in the past).
For Altera SoC based systems and the ARRADIO board, we support ARRADIO :
Download HDL
FMCOMMS2/FMCOMMS3/FMCOMMS4
| Hardware | Project | Carriers | Resource Utilization | Library Cores |
|---|---|---|---|---|
| AD-FMCOMMS2-EBZ | fmcomms2 | kc705 | fmcomms2_kc705 | axi_ad9361 |
| AD-FMCOMMS3-EBZ | kcu105 | fmcomms2_kcu105 | axi_clkgen | |
| AD-FMCOMMS4-EBZ | vc707 | fmcomms2_vc707 | axi_dmac | |
| zc702 | fmcomms2_zc702 | axi_hdmi_tx | ||
| zc706 | fmcomms2_zc706 | axi_i2s_adi | ||
| zcu102 | fmcomms2_zcu102 | axi_spdif_tx | ||
| zed | fmcomms2_zed | axi_sysid | ||
| sysid_rom | ||||
| util_clkdiv | ||||
| util_cpack2 | ||||
| util_i2c_mixer | ||||
| util_rfifo | ||||
| util_tdd_sync | ||||
| util_upack2 |
FMCOMMS5
| Hardware | Project | Carriers | Resource Utilization | Library Cores |
|---|---|---|---|---|
| AD-FMCOMMS5-EBZ | fmcomms5 | zc702 | fmcomms5_zc702 | axi_ad9361 |
| zc706 | fmcomms5_zc706 | axi_clkgen | ||
| zcu102 | fmcomms5_zcu102 | axi_dmac | ||
| axi_hdmi_tx | ||||
| axi_spdif_tx | ||||
| axi_sysid | ||||
| sysid_rom | ||||
| util_clkdiv | ||||
| util_cpack2 | ||||
| util_rfifo | ||||
| util_upack2 |
ARRadio
| Hardware | Project | Carriers | Resource Utilization | Library Cores |
|---|---|---|---|---|
| ARRadio | arradio | c5soc | NA | axi_ad9361 |
| axi_dmac | ||||
| axi_hdmi_tx | ||||
| axi_sysid | ||||
| sysid_rom | ||||
| util_cpack2 | ||||
| util_rfifo | ||||
| util_upack2 |
- Questions? Ask Help & Support.
Generating Xilinx netlist files
The repository will not contain Xilinx netlist files, only Xilinx coregen xco files are provided with the reference design. You must regenerate the IP core files using this file. See generating Xilinx netlist/verilog files from xco files for details.
Navigation - AD-FMCOMMS2-EBZ
resources/eval/user-guides/ad-fmcomms2-ebz/reference_hdl.1461833721.txt.gz · Last modified: 28 Apr 2016 10:55 by Dominik Rieth