Wiki

This version is outdated by a newer approved version.DiffThis version (09 Jan 2021 00:37) was approved by Robin Getz.The Previously approved version (13 Dec 2016 11:09) is available.Diff

This is an old revision of the document!


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.

Block diagram

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

Please note that the projects FMCOMMS2, FMCOMMS3 and FMCOMMS4 are using the same hdl design. The ARRADIO Quartus project uses Arradio hdl design.

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
18 Mar 2016 15:24 · Lucian Sin

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.

resources/eval/user-guides/ad-fmcomms2-ebz/reference_hdl.1610148770.txt.gz · Last modified: 09 Jan 2021 00:32 by Robin Getz