| Next revision | Previous revision |
| resources:fpga:altera:bemicro:ad5421 [19 Sep 2011 14:43] – created Alexandru Tofan | resources:fpga:altera:bemicro:ad5421 [26 Jan 2021 01:20] (current) – update arrow links after their web site update Robin Getz |
|---|
| ====== AD5421 16 Bit, Serial Input, Loop-Powered, 4 mA to 20 mA DAC ====== | ====== BeMicro FPGA Project for AD5421 with Nios driver ====== |
| |
| |
| ====== Overview ====== | ===== Supported Devices ===== |
| |
| This lab presents the steps to setup an environment for using the **EVAL-AD5421SDZ** evaluation board together with the **BeMicro SDK** USB stick, the Nios II Embedded Development Suite (EDS) and the Micrium uC-Probe run-time monitoring tool. A picture of the EVAL-AD5421SDZ Evaluation Board with the BeMicro SDK Platform is presented below. | * [[adi>AD5421]] |
| |
| {{ :resources:fpga:altera:bemicro:adn2850_bemicro.png?400 }} | ===== Evaluation Boards ===== |
| |
| For component evaluation and performance purposes, as opposed to quick prototyping, the user is directed to Analog Devices System Demonstration Platform (**SDP**). The **SDP** consists of the **EVAL-SDP-CB1Z (SDP-B)** controller board, various Analog Devices component evaluation daughter boards such as the **EVAL-AD5421SDZ** and 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. Each SDP evaluation daughter board includes the necessary installation files needed for this performance testing. Below is presented a picture of **SDP-B** Controller Board with the **EVAL-AD5421SDZ** Evaluation Board. | * [[adi>EVAL-AD5421SDZ]] |
| |
| {{ :resources:fpga:altera:bemicro:adn2850_blackfin.png?400 }} | ====== Overview ====== |
| |
| The **EVAL-AD5421SDZ** evaluation board is a member of a growing number of boards available for the **SDP**. Designed to help customers evaluate performance or quickly prototype new **AD5421** circuits and reduce design time, the **EVAL-AD5421SDZ** evaluation board can operate in single-supply and dual-supply mode and incorporates an internal power supply powered from the USB. | This lab presents the steps to setup an environment for using the **[[adi>EVAL-AD5421SDZ]]** evaluation board together with the **[[https://www.intel.com/content/www/us/en/programmable/b/bemicro-sdk.html|BeMicro SDK]]** USB stick, the Nios II Embedded Development Suite (EDS) and the [[http://micrium.com/tools/ucprobe/overview/|Micrium μC-Probe]] run-time monitoring tool. Below is presented a picture of the EVAL-AD5421SDZ Evaluation Board with the BeMicro SDK Platform. |
| |
| The [[adi>AD5421]] is a complete, loop-powered, 4 mA to 20 mA digital-to-analog converter (DAC) designed to meet the needs of smart transmitter manufacturers in the industrial control industry. The DAC provides a high precision, fully integrated, low cost solution in a compact TSSOP package. The AD5421 includes a regulated voltage output that is used to power itself and other devices in the transmitter, and 1.22 V and 2.5 V references. | {{ :resources:fpga:altera:bemicro:ad5421_-_bemicro.png?400 }} |
| Complete specifications for the AD5421 part can be found in the datasheet available at: [[adi>AD5421|AD5421 Product page]]. | |
| |
| Complete specifications for the EVAL-AD5421SDZ board can be found in the [[adi>/static/imported-files/user_guides/UG-250.pdf|evaluation’s board user guide]]. | {{page>common_sdp}} |
| |
| Complete specifications for the EVAL-SDP-CB1Z board can be found in the [[adi>/static/imported-files/user_guides/UG-276.pdf/UG-277.pdf|controller board user guide]]. | Below is presented a picture of **SDP-B** Controller Board with the **EVAL-AD5421SDZ** Evaluation Board. |
| |
| Complete specifications for the BeMicro SDK are available at: | {{ :resources:fpga:altera:bemicro:ad5421_-_sdp1z.png?400 }} |
| [[http://www.arrownac.com/solutions/bemicro-sdk]] | |
| |
| Complete specifications for the Nios II Embedded Development Suite (EDS) can be found at: | The **EVAL-AD5421SDZ** evaluation board is a member of a growing number of boards available for the **SDP**. Designed to help customers evaluate performance or quickly prototype new **AD5421** circuits and reduce design time, the **EVAL-AD5421SDZ** evaluation board can operate in single-supply and dual-supply mode and incorporates an internal power supply powered from the USB. |
| [[http://www.altera.com/devices/processor/nios2]] | |
| | The [[adi>AD5421]] is a complete, loop-powered, 4 mA to 20 mA digital-to-analog converter (DAC) designed to meet the needs of smart transmitter manufacturers in the industrial control industry. The DAC provides a high precision, fully integrated, low cost solution in a compact TSSOP package. The AD5421 includes a regulated voltage output that is used to power itself and other devices in the transmitter, and 1.22 V and 2.5 V references. |
| |
| Complete specifications for the Micrium uC-Probe) can be found at: | ===== More information ===== |
| [[http://micrium.com/page/products/tools/probe]] | * [[adi>AD5421|AD5421 Product Info]] - pricing, samples, datasheet |
| | * [[adi>/static/imported-files/user_guides/UG-250.pdf|EVAL-AD5421SDZ evaluation board user guide]] |
| | * [[https://www.intel.com/content/www/us/en/programmable/b/bemicro-sdk.html|BeMicro SDK]] |
| | * [[http://www.altera.com/devices/processor/nios2|Nios II Embedded Development Suite (EDS)]] |
| | * [[http://micrium.com/tools/ucprobe/overview/|Micrium uC-Probe]] |
| |
| ====== Getting Started ====== | ====== Getting Started ====== |
| |
| A list of required hardware items is presented below: | A list of required hardware items is presented below: |
| * Arrow Electronics [[http://www.arrow.com/bemicrosdk/|BeMicro SDK]] FPGA-based MCU Evaluation Board | * Arrow Electronics [[https://www.intel.com/content/www/us/en/programmable/b/bemicro-sdk.html|BeMicro SDK]] FPGA-based MCU Evaluation Board |
| * [[http://www.arrownac.com/solutions/adi_interposer/|BeMicro SDK/SDP Interposer]] adapter board | * [[adi>sdp-bemicro|BeMicro SDK/SDP Interposer]] adapter board |
| * **EVAL-AD5421SDZ** evaluation board | * **EVAL-AD5421SDZ** evaluation board |
| * Intel Pentium III or compatible Windows PC, running at 866MHz or faster, with a minimum of 512MB of system memory | * Intel Pentium III or compatible Windows PC, running at 866MHz or faster, with a minimum of 512MB of system memory |
| * [[http://www.altera.com/products/software/quartus-ii/web-edition/qts-we-index.html|Quartus II Web Edition]] design software v11.0 | * [[http://www.altera.com/products/software/quartus-ii/web-edition/qts-we-index.html|Quartus II Web Edition]] design software v11.0 |
| * [[https://www.altera.com/download/software/nios-ii|Nios II EDS]] v11.0 | * [[https://www.altera.com/download/software/nios-ii|Nios II EDS]] v11.0 |
| * [[http://micrium.com/page/products/tools/probe|uC-Probe]] run-time monitoring tool | * [[http://micrium.com/tools/ucprobe/trial/|uC-Probe]] run-time monitoring tool, version 2.5 |
| * {{:resources:fpga:altera:bemicro:adievalboardlab.zip|Lab Design Files}} | |
| |
| The **Quartus II** design software and the **Nios II EDS** is available via the Altera Complete Design Suite DVD or by downloading from the web. | The **Quartus II** design software and the **Nios II EDS** is available via the Altera Complete Design Suite DVD or by downloading from the web. |
| |
| The **Micrium uC/Probe Trial** version is available via download from the web at [[http://micrium.com/download/Micrium-uC-Probe-Setup-Trial.exe]]. After installation add to the “Path” system variable the entry "//%QUARTUS_ROOTDIR%\bin\//“ on the third position in the list. | The **Micrium uC/Probe Trial** version 2.5 is available via download from the web at [[http://micrium.com/tools/ucprobe/trial/]]. After installation add to the “Path” system variable the entry "//%QUARTUS_ROOTDIR%\bin\//“ on the third position in the list. |
| |
| | ===== Downloads ===== |
| | * {{:resources:fpga:altera:bemicro:ad5421_evalboardlab.zip|Lab Design Files}} |
| ===== Extract the Lab Files ===== | ===== Extract the Lab Files ===== |
| |
| Create a folder called “**//ADIEvalBoardLab//**” on your PC and extract the **//ADIEvalBoardLab.zip//** archive to this folder. Make sure that there are **//NO SPACES//** in the directory path. After extracting the archive the following folders should be present in the **//ADIEvalBoardLab//** folder: **//FPGA//**, **//Software//**, **//ucProbeInterface//**, **//NiosCpu//**. | Create a folder called “**//ADIEvalBoardLab//**” on your PC and extract the **//ad5421_evalboardlab.zip//** archive to this folder. Make sure that there are **//NO SPACES//** in the directory path. After extracting the archive the following folders should be present in the **//ADIEvalBoardLab//** folder: **//FPGA//**, **//Software//**, **//ucProbeInterface//**, **//NiosCpu//**. |
| |
| {{ :resources:fpga:altera:bemicro:labfolders.png?500 }} | {{ :resources:fpga:altera:bemicro:labfolders.png?500 }} |
| {{page>common_usb}} | {{page>common_usb}} |
| |
| | ====== Quick Evaluation ====== |
| {{page>common_quick_eval}} | {{page>common_quick_eval}} |
| |
| | ====== FPGA Design ====== |
| {{page>common_spi_i2c}} | {{page>common_spi_i2c}} |
| |
| | ====== NIOS II Software Design ====== |
| {{page>common}} | {{page>common}} |
| |
| ===== Load and Run the Demonstration Project ===== | ===== Load and Run the Demonstration Project ===== |
| |
| * Click the **//Open//** option from the **uC-Probe** menu and select the file **//ADIEvalBoardLab/ucProbeInterface/ADN5421_Interface.wsp//**. | * Click the **//Open//** option from the **uC-Probe** menu and select the file **//ADIEvalBoardLab/ucProbeInterface/AD5421_Interface.wsp//**. |
| |
| {{:resources:fpga:altera:bemicro:ucprobeopenfile.png?400}} | {{:resources:fpga:altera:bemicro:ucprobeopenfile.png?400}} |
| {{:resources:fpga:altera:bemicro:ad2850interfaceopen.png?400}} | {{:resources:fpga:altera:bemicro:ad5421openinterface.png?400}} |
| |
| * Before opening the interface **uC-Probe** will ask for a symbols file that must be associated with the interface. If the lab was done according to the steps provided in the **Quick Evaluation** section, select the file **//ADIEvalBoardLab/ucProbeInterface/ADIEvalBoard.elf//** to be loaded as a symbol file, otherwise select the file **//ADIEvalBoardLab/FPGA/software/ADIEvalBoard/ADIEvalBoard.elf//** to be loaded as a symbol file. | * Before opening the interface **uC-Probe** will ask for a symbols file that must be associated with the interface. If the lab was done according to the steps provided in the **Quick Evaluation** section, select the file **//ADIEvalBoardLab/ucProbeInterface/ADIEvalBoard.elf//** to be loaded as a symbol file, otherwise select the file **//ADIEvalBoardLab/FPGA/software/ADIEvalBoard/ADIEvalBoard.elf//** to be loaded as a symbol file. |
| |
| |
| **Section A** is used to activate the board and monitor activity. The communication with the board is activated / deactivated by toggling the **//ON/OFF//** switch. The **//Activity//** LED turns green when the communication is active. If the **//ON/OFF//** switch is set to **//ON//** and the **//Activity//** LED is **//BLACK//** it means that there is a communication problem with the board. | **Section A** is used to activate the board and monitor activity. The communication with the board is activated / deactivated by toggling the **//ON/OFF//** switch. The **//Activity//** LED turns green when the communication is active. If the **//ON/OFF//** switch is set to **//ON//** and the **//Activity//** LED is **//BLACK//** it means that there is a communication problem with the board. See the **Troubleshooting** section for indications on how to fix the communication problems. |
| |
| **Section B** is used to load different values into the AD5421 registers. | **Section B** is used to load different values into the AD5421 registers. |
| * Fault register - Each LED turns on if a bit in the Fault register is set. See AD5421 datasheet page 27 for more details about each fault | * Fault register - Each LED turns on if a bit in the Fault register is set. See AD5421 datasheet page 27 for more details about each fault |
| |
| | {{page>troubleshooting}} |
| |
| |
