Difference between revisions of "Example atod"
| Line 1: | Line 1: | ||
{{todo|Review(11.13.13-12:59->JG+)|Jgreene|project=oe 4,oe 5,jg,md,Review}} | {{todo|Review(11.13.13-12:59->JG+)|Jgreene|project=oe 4,oe 5,jg,md,Review}} | ||
This is a guide to the <code>atod_test</code> C example project included in the EMAC OE SDK. | This is a guide to the <code>atod_test</code> C example project included in the EMAC OE SDK. | ||
| + | |||
| + | This application reads all channels of an ''indexed atod device'' (see hardware requirements, below) on EMAC OE Linux. | ||
| + | |||
| + | The <code>atod_test</code> project builds one executable: <code>indexed_atod_test</code>. | ||
<intro> | <intro> | ||
| Line 25: | Line 29: | ||
===Hardware Requirements=== | ===Hardware Requirements=== | ||
| − | + | ||
Usage:<br /> | Usage:<br /> | ||
Revision as of 13:59, 11 December 2013
This is a guide to the atod_test C example project included in the EMAC OE SDK.
This application reads all channels of an indexed atod device (see hardware requirements, below) on EMAC OE Linux.
The atod_test project builds one executable: indexed_atod_test.
<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
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).
