This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
resources:fpga:xilinx:interposer:ad5272 [28 May 2012 15:52] – Approved Alexandru.Tofan | resources:fpga:xilinx:interposer:ad5272 [10 Oct 2013 13:18] – changed source code (without Micrium uC-Probe), added Software Setup, remove programming with Impact Lucian Sin | ||
---|---|---|---|
Line 4: | Line 4: | ||
* [[adi> | * [[adi> | ||
+ | * [[adi> | ||
===== Evaluation Boards ===== | ===== Evaluation Boards ===== | ||
Line 11: | Line 12: | ||
====== Overview ====== | ====== Overview ====== | ||
- | This document presents the steps to setup an environment for using the **[[adi> | + | This document presents the steps to setup an environment for using the **[[adi> |
{{ : | {{ : | ||
- | For component evaluation and performance purposes, as opposed to quick prototyping, | + | {{page>common_sdp}} |
- | * a controller board, like the **[[resources/ | + | |
- | * a compatible Analog Devices SDP [[adi>sdp# | + | |
- | * corresponding PC software | + | |
- | The EVAL-SDP-CB1Z controller board is part of Analog Devices SDP providing USB 2.0 high-speed connectivity to a PC computer running specific component evaluation software. | + | |
Below is presented a picture of **SDP-B** Controller Board with the **EVAL-AD5272SDZ** Evaluation Board. | Below is presented a picture of **SDP-B** Controller Board with the **EVAL-AD5272SDZ** Evaluation Board. | ||
Line 33: | Line 30: | ||
* [[adi>/ | * [[adi>/ | ||
* [[http:// | * [[http:// | ||
- | * [[http:// | ||
====== Getting Started ====== | ====== Getting Started ====== | ||
Line 47: | Line 43: | ||
===== Required Software ===== | ===== Required Software ===== | ||
- | * Xilinx ISE 13.4 (Programmer (IMPACT) is sufficient for the demo and is available on Webpack). | + | * Xilinx ISE 14.6. |
- | * [[http://micrium.com/ | + | * UART Terminal (Termite/Tera Term/Hyperterminal), |
+ | * The EVAL-AD5272 reference project for Xilinx KC705 FPGA. | ||
===== Downloads ===== | ===== Downloads ===== | ||
- | + | <WRAP round download 80%> | |
- | * {{:resources: | + | \\ |
- | + | * **AD5272 Driver:** https://github.com/ | |
- | The following table presents a short description the reference design archive contents. | + | * **AD5272 Commands:** https:// |
- | + | | |
- | ^ **Folder** ^ **Description** ^ | + | * **EDK KC705 Reference |
- | | Bit | Contains the KC705 configuration file that can be used to program the system for quick evaluation. | | + | \\ |
- | | Microblaze | Contains the EDK 13.4 project for the Microblaze softcore that will be implemented in the KC705 FPGA. | | + | </ |
- | | Software | Contains the source files of the software | + | |
- | | uCProbeInterface | Contains the uCProbe interface and the .elf symbols file used by uC-Probe to access data from the Microbalze memory. | | + | |
====== Run the Demonstration Project ====== | ====== Run the Demonstration Project ====== | ||
- | {{page> | + | ===== Hardware setup ===== |
- | + | ||
- | ===== Demonstration Project User Interface | + | |
- | + | ||
- | The following figure presents the **uC-Probe** interface that can be used for monitoring and controlling the operation of the **EVAL-AD5272SDZ** evaluation board. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | **Section A** is used to activate the board and monitor activity. The communication with the board is activated / deactivated by toggling the **// | + | |
- | + | ||
- | **Section B** displays the data that is read from the RDAC register. | + | |
- | + | ||
- | **Section C** is used to write data to RDAC register. | + | |
- | + | ||
- | **Section D** allows access to the control register, enabling or disabling the resistor performance mode, RDAC write protection, and the 50-TP memory. | + | |
- | * 50-TP Program – enables/ | + | <WRAP round important 80%> |
- | * RDAC Write Protect – allows or not update | + | \\ |
- | * Resistor Performance – enables/disables resistor tolerance calibration. | + | Before connecting the ADI evaluation board to the Xilinx KC705 make sure that the VADJ_FPGA voltage |
+ | </WRAP> | ||
- | **Section E** is used to reset and to shutdown | + | |
+ | * Connect the JTAG and UART cables | ||
- | | + | ===== Reference Project Overview ===== |
- | * Hard Reset – sends a reset by hardware. | + | The following commands were implemented in this version of EVAL-AD5272 reference project for Xilinx KC705 FPGA board. |
- | * Power Down – powers down the part. | + | ^ Command ^ Description ^ |
+ | | **help?** | Displays all available commands. | | ||
+ | | **reset!**| Makes a software | ||
+ | | **rdac=** | Writes to the RDAC register. Accepted values:\\ 0 .. 1024 (0 .. 255 for AD5274) - the value written to RDAC. | | ||
+ | | **rdac?** | Displays the last written value in RDAC register. | | ||
+ | | **store!** | Stores the RDAC setting to 50-TP. | | ||
+ | | **50TPValue? | ||
+ | | **50TPAddress? | ||
+ | | **power=** | Turns on/off the device. Accepted values:\\ 1 - normal mode.(default)\\ 0 - shutdown mode. | | ||
+ | | **power?** | Displays the power status of the device. | | ||
- | **Section F** is used read/ | + | Commands can be executed using a serial terminal connected to the UART peripheral of Xilinx KC705 FPGA. |
- | * Blow Fuse – blows the actual RDAC register data in the 50-TP memory. | + | The following image shows a generic list of commands |
- | * Read Fuse Content – reads content of 50-TP memory. | + | {{ : |
- | * Read Fuse Address – reads address of the last 50-TP programmed memory location. | + | |
- | ===== Troubleshooting | + | ===== Software Project Setup ===== |
+ | {{page> | ||
- | In case there is a communication problem with the board the follwing actions can be perfomed in order to try to fix the issues: | ||
- | * Check that the evaluation board is powered as instructed in the board' | ||
- | * In uC-Probe refresh the symbols file by right-clicking on the **//System Browser//** window and selecting **//Refresh Symbols// | ||
- | * If the communication problem persists even after performing the previous steps, restart the uC-Probe application and try to run the interface again. | ||
====== More information ====== | ====== More information ====== | ||
* [[resources: | * [[resources: | ||
{{page> | {{page> |