This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:fpga:xilinx:interposer:ad9279 [23 May 2012 22:32] – Add Atom feed Robin Getz | resources:fpga:xilinx:interposer:ad9279 [11 May 2021 09:46] (current) – [Required Hardware] Meriam Yuson-Aguila | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== AD9279 FMC Interposer & Evaluation Board / Xilinx Reference Design ====== | + | ====== AD9279 |
===== Introduction ===== | ===== Introduction ===== | ||
Line 5: | Line 5: | ||
The [[adi> | The [[adi> | ||
- | **HW Platform:** [[http:// | + | ===== Supported Devices ===== |
- | **System:** Microblaze, AXI, UART | + | |
+ | | ||
+ | * [[adi> | ||
+ | |||
+ | ===== Supported Carriers ===== | ||
+ | |||
+ | * [[xilinx> | ||
===== Quick Start Guide ===== | ===== Quick Start Guide ===== | ||
Line 16: | Line 23: | ||
* ML605 board | * ML605 board | ||
* AD9279-EBZ board & Power supply | * AD9279-EBZ board & Power supply | ||
+ | *{{ : | ||
* ADC FMC interposer board | * ADC FMC interposer board | ||
+ | * Signal generator (clock, optional) | ||
* Signal generator (analog input, for data capture) | * Signal generator (analog input, for data capture) | ||
==== Required Software ==== | ==== Required Software ==== | ||
- | * Xilinx ISE 13.2 (Programmer (IMPACT) is sufficient for the demo and is available on Webpack). | + | * Xilinx ISE 14.1 (Programmer (IMPACT) is sufficient for the demo and is available on Webpack). |
* A UART terminal (Tera Term/ | * A UART terminal (Tera Term/ | ||
Line 37: | Line 46: | ||
==== Running Demo (SDK) Program ==== | ==== Running Demo (SDK) Program ==== | ||
- | |||
- | <note tip>If you are not familiar with ML605 and/or Xilix tools, please visit\\ [[http:// | ||
To begin make the following connections (see image below): | To begin make the following connections (see image below): | ||
Line 46: | Line 53: | ||
* Connect power to ML605 and the AD9279-EBZ boards. | * Connect power to ML605 and the AD9279-EBZ boards. | ||
* Connect two USB cables from the PC to the //JTAG// and //UART// USB connectors on ML605. | * Connect two USB cables from the PC to the //JTAG// and //UART// USB connectors on ML605. | ||
- | * Connect a signal generator to channel A SMA connector. | + | |
+ | | ||
+ | |||
+ | {{: | ||
After the hardware setup, turn the power on to the ML605 and the AD9467-2x0EBZ boards. Start IMPACT, and initialze the JTAG chain. The program should recognize the Virtex 6 device (see screenshot below). Start a UART terminal (set to 57600 baud rate) and then program the device. | After the hardware setup, turn the power on to the ML605 and the AD9467-2x0EBZ boards. Start IMPACT, and initialze the JTAG chain. The program should recognize the Virtex 6 device (see screenshot below). Start a UART terminal (set to 57600 baud rate) and then program the device. | ||
- | |||
- | {{: | ||
If programming was successful, you should be seeing messages appear on the terminal as shown in figure below. After programming the AD9279, the program checks data capture on various test modes. | If programming was successful, you should be seeing messages appear on the terminal as shown in figure below. After programming the AD9279, the program checks data capture on various test modes. | ||
Line 56: | Line 64: | ||
{{: | {{: | ||
- | After patterns and prbs sequences are verified, if no errors are present, you may use the chipscope busplot to see the captured signal (see below). The ADC data is available on pins [23:12] of the chipscope signal. | + | After patterns and prbs sequences are verified, if no errors are present, you may use the chipscope busplot to see the captured signal (see below). The ADC data is available on pins [11:0] of the chipscope signal. Individual channels may be enabled through the processor. The reference design runs internally at 160MHz, so two samples will appear on chipscope for default capture of the signal. The capture may be qualified with the internal data select signal (set trigger to 0x01 as the storage condition). |
- | {{:resources: | + | Chipscope capture (raw):\\ |
- | ===== Using the reference design ===== | + | {{: |
- | The reference design is built on a microblaze based system parameterized for linux. A functional block diagram of the design is given below. | + | Chipscope capture (storage qualified): |
- | {{: | + | {{: |
- | The reference design | + | ===== Using the reference design |
- | The LVDS interface | + | The reference design is built on a microblaze based system parameterized for linux. The reference design consists of three functional modules, a LVDS interface, a PN9/ |
+ | The LVDS interface captures and buffers data from the ADC. The DMA interface then transfers the samples to the external DDR-DRAM. The capture is initiated by the software. The status of capture (overflow, over the range) are reported back to the software. | ||
==== Registers ==== | ==== Registers ==== | ||
- | ^ QW Address< | + | |
- | | 0x00 | 31 | version | 32' | + | Please refer to the regmap.txt file inside pcores. |
- | | 0x03 | 16 | ADC capture start | ADC capture start (a 0x0 to 0x1 initiates start). | | + | |
- | | | 15:0 | ADC capture count | ADC capture count (total count - 1). | | + | |
- | | 0x04 | 2 | DMA underflow | DMA underflow (W1C). | | + | |
- | | | 1 | DMA overflow | DMA overflow (W1C). | | + | |
- | | | 0 | DMA status | DMA idle (0x0) or busy (0x1) status. | | + | |
- | | 0x05 | 0 | PN errors | Spurious sequence mismatches in sync state (OOS == 0). | | + | |
- | | | 0 | PN OOS | If sequence matches for 16 consecutive samples, OOS is cleared. If mismatch occurs for 64 consecutive samples, OOS is set. | | + | |
- | | | 0 | ADC OR | ADC OR (W1C). | | + | |
- | | 0x06 | 31:0 | ADC sample | ADC captured sample (debug purposes only). | | + | |
- | | 0x09 | 7:0 | PN Type | PN9 (0x0) or PN23 (0x1). | | + | |
- | | 0x0a | 0 | ADC capture select | If data pattern mismatch occurs try setting this bit (see notes below) | | + | |
- | | 1. For AXI-Lite byte addresses, multiply by 4. |||| | + | |
- | | 2. All registers defaults to 0x0, unless otherwise specified. |||| | + | |
==== Good To Know ==== | ==== Good To Know ==== | ||
The PN23 sequence is inverted, PN9 is not inverted. | The PN23 sequence is inverted, PN9 is not inverted. | ||
- | |||
===== Downloads ===== | ===== Downloads ===== | ||
+ | FPGA Referece Designs: | ||
+ | <WRAP round download 80%> | ||
+ | * **ML605 (source files)** {{: | ||
+ | * **ML605 (bit/sw files)** {{: | ||
+ | </ | ||
+ | |||
+ | Only Xilinx coregen xco files are provided with the reference design. You must regenerate the IP core files using this file. See [[/ | ||
- | {{: | + | <WRAP round help 80%> |
+ | * Questions? [[ez>fpga|Ask Help & Support]]. | ||
+ | </ | ||
===== Tar file contents ===== | ===== Tar file contents ===== | ||
- | The tar file contains, in most cases, the following files and/or directories. To rebuild the reference design simply double click the XMP file and run the tool. To build SDK, select a workspace and use the C file to build the elf file. Please refer to [[http://www.xilinx.com/support/ | + | The tar file contains, in most cases, the following files and/or directories. To rebuild the reference design simply double click the XMP file and run the tool. To build SDK, select a workspace and use the C file to build the elf file. Please refer to [[xilinx>support/ |
| license.txt | ADI license & copyright information. | | | license.txt | ADI license & copyright information. | | ||
Line 112: | Line 116: | ||
===== More information ===== | ===== More information ===== | ||
- | * [[http:// | + | * [[http:// |
- | * [[ez> | + | * [[ez> |
* Example questions: {{rss> | * Example questions: {{rss> |