Wiki

Analog Devices Wiki

English
English
简体中文
简体中文
日本語
日本語
Руccкий
Руccкий

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
resources:eval:user-guides:ad-fmcomms2-ebz:reference_hdl [24 Sep 2014 21:46] – [Control and SPI] rejeesh kuttyresources:eval:user-guides:ad-fmcomms2-ebz:reference_hdl [09 Jan 2021 00:32] – user interwiki links Robin Getz
Line 1: Line 1:
- +====== AD9361 HDL Reference Designs ======
-====== AD-FMCOMMS2-EBZ / AD-FMCOMMS3-EBZ / AD-FMCOMMS4-EBZ HDL / AD-FMCOMMS5-EBZ HDL Reference Design ======+
  
 ===== Functional Overview ===== ===== Functional Overview =====
  
-The reference design is a processor based (ARM or Microblaze) 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.+The reference design is a processor based (ARM, [[wp>MicroBlaze]], or [[wp>Nios_II|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.
  
  
Line 29: Line 28:
  
 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. 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 Devices =====
Line 38: Line 35:
   * [[adi>AD-FMCOMMS4-EBZ]]   * [[adi>AD-FMCOMMS4-EBZ]]
   * [[adi>AD-FMCOMMS5-EBZ]]   * [[adi>AD-FMCOMMS5-EBZ]]
 +  * [[../arradio|ARRADIO]]
 +  * [[../picozed_sdr|PicoZed SDR]]
  
 ===== Supported Carriers ===== ===== Supported Carriers =====
Line 43: Line 42:
 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. 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.
  
-Our recommended plaforms are the Zynq based systems:+For the FMCOMMS2, 3, 4 based boards, supported carriers include the Xilinx Zynq based systems:
   * [[xilinx>ZC702]]    * [[xilinx>ZC702]] 
   * [[xilinx>ZC706]]    * [[xilinx>ZC706]] 
   * [[http://www.zedboard.org|Zed Board]]    * [[http://www.zedboard.org|Zed Board]] 
  
-but it also works on the fabric only solutions (for experts, who have used the zynq based systems in the past).+but it also works on the Xilinx fabric only solutions (for experts, who have used the zynq based systems in the past).
   * [[xilinx>KC705]]    * [[xilinx>KC705]] 
   * [[xilinx>VC707]]    * [[xilinx>VC707]] 
  
 +For Altera SoC based systems and the ARRADIO board, we support [[ :resources:eval:user-guides:arradio| ARRADIO  ]] :
  
-===== Download ======+  * [[https://www.arrow.com/en/products/sockit/arrow-development-tools|SoC Kit]] 
  
-FPGA Reference Designs on GitHub :+======  ====== 
 +{{page>:resources:eval:user-guides:ad-fmcomms2-ebz:downloads#download_hdl}}
  
-<WRAP round download 80%> 
-  * **Vivado Downloads** 
-  * https://github.com/analogdevicesinc/hdl (This is our main repository and contents change frequently. A release (more stable) branch will be available soon.) 
- 
- 
-  * **XPS/EDK Downloads** 
-  * https://github.com/analogdevicesinc/fpgahdl_xilinx/archive/ad_fmcomms2_ebz_edk_14_4_2013_10_22.tar.gz 
-  * https://github.com/analogdevicesinc/fpgahdl_xilinx/archive/ad_fmcomms2_ebz_edk_14_4_2013_10_22.zip 
- 
-  * **Previous Releases & Tags** 
-  * https://github.com/analogdevicesinc/fpgahdl_xilinx/tags 
-  * https://github.com/analogdevicesinc/fpgahdl_xilinx/releases 
- 
-  * **Git Repository** 
-  * https://github.com/analogdevicesinc/fpgahdl_xilinx.git 
-</WRAP> 
  
 <WRAP round help 80%> <WRAP round help 80%>
-  * Questions? [[http://ez.analog.com/post!input.jspa?containerType=14&container=2061|Ask Help & Support]].+  * Questions? [[/resources/eval/user-guides/ad-fmcomms2-ebz/help_and_support|Ask Help & Support]].
 </WRAP> </WRAP>
  
 ===== Generating Xilinx netlist files ====== ===== 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 [[http://wiki.analog.com/resources/eval/user-guides/ad-fmcomms1-ebz/reference_hdl|generating Xilinx netlist/verilog files from xco files]] for details. +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 [[/resources/eval/user-guides/ad-fmcomms1-ebz/reference_hdl|generating Xilinx netlist/verilog files from xco files]] for details.
  
-{{navigation AD-FMCOMMS2-EBZ#Hardware#.:|Overview#Software}} 
resources/eval/user-guides/ad-fmcomms2-ebz/reference_hdl.txt · Last modified: 01 Feb 2023 02:07 by Joyce Velasco

Page Tools