Wiki

Below is the source of this page. To edit this source as well as other pages on the wiki, you must login.
====== BeMicro FPGA Project for CN0203 with Nios driver ======

===== Supported Devices =====

  * [[adi>AD5660|AD5660-1]]
  * [[adi>AD5750-1]]
===== Reference Circuits =====

  * [[adi>CN0203]]
====== Overview ======

This lab presents the steps to setup an environment for using the **[[adi>EVAL-CN0203-SDPZ]]** evaluation board together with the **[https://www.arrow.com/en/datasheets/89166696/arrow-development-tools/bemicrosdk|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-CN0203-SDPZ Evaluation Board with the BeMicro SDK Platform.

{{ :resources:fpga:altera:bemicro:cn0203_bemicro.jpg?400 }}

{{page>common_sdp}}

Below is presented a picture of **SDP-B** Controller Board with the **EVAL-CN0203-SDPZ** Evaluation Board.

{{ :resources:fpga:altera:bemicro:cn0203_sdp1z.jpg?400 }}

The **EVAL-CN0203-SDPZ** board provides a full function, flexible, programmable analog output solution with only two analog components and meets most requirements for programmable logic controller (PLC) and distributed control system (DCS) applications.

The [[adi>AD5660|AD5660-1]] is a single channel, low cost, low power, rail-torail voltage buffered output nanoDAC integrated with an onchip 1.25 V, 5 ppm/°C reference. The AD5660-1 incorporates a power-on reset circuit to ensure that the DAC output powers up to 0 V and remains there until a valid write command takes place.

The interface between the AD5660-1 DAC and the AD5750-1 driver is simple and requires no external components. The output voltage range of the AD5660-1 is 0 V to 2.5 V, which matches the input range of the AD5750-1. In addition, the reference output voltage of the AD5660-1 is 1.25 V, which precisely matches the reference input requirement of the AD5750-1.

The [[adi>AD5750-1]] is a single-channel, low cost, precision voltage/current output driver with hardware- or software- programmable output ranges. The software ranges are configured via an SPI-/MICROWIRE™-compatible serial interface. The AD5750-1 target applications in PLC and industrial process control. The analog input to the AD5750-1 is provided from a low voltage, single-supply digital-to-analog converter (DAC) and is internally conditioned to provide the desired output current/voltage range. Analog input range available is 0 V to 2.5 V.

The output current range is programmable across five current ranges: 4 mA to 20 mA, 0 mA to 20 mA or 0 mA to 24 mA, ±20 mA, and ±24 mA. An overrange of 2% is available on the unipolar current ranges.

Voltage output is provided from a separate pin that can be configured to provide 0 V to 5 V, 0 V to 10 V, ±5 V, or ±10 V output ranges. An overrange of 20% is available on the voltage ranges.

Analog outputs are short-circuit and open-circuit protected and can drive capacitive loads of 1 μF and inductive loads of 0.1 H.

The device is specified to operate with a power supply range from ±12 V to ±24 V. Output loop compliance is 0 V to AVDD − 2.75 V.

The flexible serial interface is SPI and MICROWIRE compatible and can be operated in 3-wire mode to minimize the digital isolation required in isolated applications. The interface also features an optional PEC error checking feature using CRC-8 error checking, useful in industrial environments where data communication corruption can occur.

The device also includes a power-on reset function, ensuring that the device powers up in a known state (0 V or tristate), and an asynchronous CLEAR pin that sets the outputs to zero scale/midscale voltage output or the low end of the selected current range.

An HW SELECT pin is used to configure the part for hardware or software mode on power-up.

===== More information =====
  * [[adi>CN0203|CN0203 Product Info]] - pricing, samples, datasheet
  * [[adi>AD5660|AD5660-1 Product Info]] - pricing, samples, datasheet
  * [[adi>AD5750-1|AD5750-1 Product Info]] - pricing, samples, datasheet
  * [[adi>CN0203|EVAL-CN0203-SDPZ evaluation board user guide]]
  * [[https://www.arrow.com/en/datasheets/89166696/arrow-development-tools/bemicrosdk|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 ======

The first objective is to ensure that you have all of the items needed and to install the software tools so that you are ready to create and run the evaluation project.


===== Hardware Items =====

Below is presented the list of required hardware items:
  * Arrow Electronics [[https://www.arrow.com/en/datasheets/89166696/arrow-development-tools/bemicrosdk|BeMicro SDK]] FPGA-based MCU Evaluation Board
  * [[https://www.arrow.com/en/datasheets/2957953708/analog-devices/bemicrosdksdpinterposer|BeMicro SDK/SDP Interposer]] adapter board
  * **EVAL-CN0203-SDPZ** evaluation board
  * Intel Pentium III or compatible Windows PC, running at 866MHz or faster, with a minimum of 512MB of system memory


===== Software Tools =====

Below is presented the list of required software tools:
  * [[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
  * [[http://micrium.com/tools/ucprobe/trial/|uC-Probe]] run-time monitoring tool, version 2.5

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 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:cn0203_evalboardlab.zip|Lab Design Files}}
===== Extract the Lab Files =====

Create a folder called “**//ADIEvalBoardLab//**” on your PC and extract the **//cn0203_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 }}

====== ======

{{page>common_usb}}

{{page>common_quick_eval}}

{{page>common_spi_i2c}}

{{page>common}}


====== uC-Probe Interface ======

A notable challenge in embedded systems development is to overcome the lack of feedback that such systems typically provide. Many developers resort to blinking LEDs or instrumenting their code with //printf()// in order to determine whether or not their systems are running as expected. **Micrium** provides a unique tool named **μC-Probe** to assist these developers. With this tool, developers can effortlessly read and write the variables on a running embedded system.
This section presents the steps required to install the **Micrium uC-Probe** software tool and to run the demonstration project for the ADI evaluation board. A description of the **uC-Probe** demonstration interface is provided.

===== Configure uC-Probe =====

Launch **uC-Probe** from the **//Start -> All Programs -> Micrium -> uC-Probe//**.

Select **uC-Probe** options.
  * Click on the **uC-Probe** icon on the top left portion of the screen.
  * Click on the **//Options//** button to open the dialog box.

{{ :resources:fpga:altera:bemicro:ucprobeoptionsbtn.png?300 }}

Set target board communication protocol as **//JTAG UART//**
  * Click on the **//Communication//** tab icon on the top left portion of the dialog box
  * Select the **//JTAG UART//** option.

{{ :resources:fpga:altera:bemicro:image067.png?400 }}

Setup **//JTAG UART//** communication settings
  * Select the **//JTAG-UART//** option from the **//Communication//** tab.
  * Press the **//Open File//** button to select the JTAG Debug Information file (**//.jdi//**)
  * Navigate to the **//ADIEvalBoardLab/FPGA//** folder and select the BeMicroSDK.jdi file. Press Open.
  * Type the value **//1//** in the the **//Device Id//** window.

{{ :resources:fpga:altera:bemicro:ucprobeoptionsjtag.png?400 }}

  * Select **//uCProbe_uart(0)//** from the **//Instance Id//** pulldown menu.

{{ :resources:fpga:altera:bemicro:image073.png?400 }}

  * Press **//Apply//** and **//OK//** to exit the options menu. The embedded target has two UARTs. **uC-Probe** will be communicating with the **//uCProbe_uart//**.

===== Load and Run the Demonstration Project =====

  * Click the **//Open//** option from the **uC-Probe** menu and select the file **//ADIEvalBoardLab/ucProbeInterface/CN0203_Interface.wsp//**.

{{:resources:fpga:altera:bemicro:ucprobeopenfile.png?400}}
{{:resources:fpga:altera:bemicro:cn0203interfaceopen.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.

{{:resources:fpga:altera:bemicro:ucprobeopenelfquickeval.png?400}}{{:resources:fpga:altera:bemicro:ucprobeopenelfnormal.png?400}}

  * Run the demonstration project by pressing the **//Play//** button.

{{ :resources:fpga:altera:bemicro:image081.png?400 }}

====== 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-CN0203-SDPZ** evaluation board.

{{ :resources:fpga:altera:bemicro:cn0203_interface.png?600 }}

**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 a digital value to AD5660-1.

**Section C** is used to display the state of the error bits.

**Section D** is used to toggle the Clear Pin and to specify the JP1 position.

**Section E** is used to modify the output range.

{{page>troubleshooting}}
Analog Devices Wiki

Page Tools
