Difference between revisions of "Example atod"

From wiki.emacinc.com
Jump to: navigation, search
Line 1: Line 1:
{{todo|InProgress(11.13.13-12:59->JG+)|Jgreene|project=oe 4,oe 5,jg,md,InProgress}}
+
{{todo|Review(11.13.13-12:59->JG+)|Jgreene|project=oe 4,oe 5,jg,md,Review}}
<big>This procedure provides an overview of how to compile and run the ''atod_test'' C example project. It assumes familiarity with the C programming language and is intended to be used by experienced programmers who are looking to learn the EMAC SDK.</big>
+
This is a guide to the <code>atod_test</code> C example project included in the EMAC OE SDK.
  
====1. Open the ''C/C++'' editing perspective====
+
<intro>
  
From the Eclipse menubar select ''Window->Open Perspective->Other...''
+
== Opening, Building and Uploading the Project Files ==
  
Select ''C/C++'' and click ''OK''.
+
<big>1. Open the C/C++ editing perspective.</big>
  
[[File:Open_perspective.jpg|left|Figure 1: Select C/C++ Perspective.]]
+
stub
  
<br clear=all>
+
<big>2. Open the project files.</big>
  
====2. Open the ''atod_test'' project====
+
stub
  
From the Eclipse menubar select ''File->New->Makefile Project With Existing Code...''
+
<big>3. Build the project.</big>
  
Click the ''Browse'' button and navigate to the directory of the ''atod_test'' example project.
+
stub
  
The ''atod_test'' example project source can be found in the projects/ subdirectory of the EMAC OE SDK root directory. The full path is:<br />
+
<big>4. Upload the executables to the target system.</big>
    <code bash> /path/to/sdk/EMAC-OE-arm-linux-gnueabi-SDK_4.0/projects/atod_test/ </code>
 
  
After you have successfully specified the path to the ''atod_test'' project directory, click ''Finish''.<br />
+
stub
  
[[File:Example_atod_Import_existing_code.jpg|450px|left|Figure 2: Specify the location of the atod_test project.]]
+
==Usage and Behavior==  
 
 
<br clear=all>
 
 
 
 
 
 
 
====3. Build, upload and run====
 
<br /><br />
 
 
 
 
 
 
 
==What it does==
 
  
 +
===Hardware Requirements===
 
''atod_test'' reads all channels of an indexed atod device and outputs the results to the terminal.
 
''atod_test'' reads all channels of an indexed atod device and outputs the results to the terminal.
  

Revision as of 13:43, 11 December 2013

TODO: {{#todo:Review(11.13.13-12:59->JG+)|Jgreene|oe 4,oe 5,jg,md,Review}}

This is a guide to the atod_test C example project included in the EMAC OE SDK.

<intro>

Opening, Building and Uploading the Project Files

1. Open the C/C++ editing perspective.

stub

2. Open the project files.

stub

3. Build the project.

stub

4. Upload the executables to the target system.

stub

Usage and Behavior

Hardware Requirements

atod_test reads all channels of an indexed atod device and outputs the results to the terminal.

Usage:
indexed_atod_test DEVICE CHANNELS
i.e. : ./indexed_atod_test /dev/indexed_atod 4

From the comments in index_atod_test.c

   Example application for reading all channels of an indexed atod device
   on EMAC OE Linux. Examples of this type of device are the processor
   AtoDs on the SoM-9260/9G20 and the IPAC-9302 and the mcp3208 external
   AtoD devices on the SoM-150ES carrier (through the /dev/mcp3208-gpio
   device. This interface uses the EMAC ioex class to provide a GPIO-like
   device where each channel can be read directly.(see also the egpc project).