Difference between revisions of "Example getkey"

From wiki.emacinc.com
Jump to: navigation, search
Line 45: Line 45:
 
'''Note''' Arguments are evaluated in order. If blocking or device specifications are used, they must be declared before the matrix arguments on the command line.
 
'''Note''' Arguments are evaluated in order. If blocking or device specifications are used, they must be declared before the matrix arguments on the command line.
  
===Usage Example. Displaying the Matrix Presently Associated with the Keypad===
+
===Usage Example. Mapping the Keypad to a Matrix File===
  
     <code>./getkey -d /dev/keypad0 -g</code>
+
     <code>./getkey -d /dev/keypad0 -s Key-E020-21</code>
  
The program will display the matrix presently associated with the keypad at <code>/dev/keypad0''</code>.
+
The program will map the keypad at <code>/dev/keypad0</code> to the matrix file <code>Key-E020-21</code>.
  
 
'''example output'''
 
'''example output'''
  
===Usage Example. Mapping the Keypad to a Matrix File===
+
===Usage Example. Displaying the Matrix Presently Associated with the Keypad===
  
     <code>./getkey -d /dev/keypad0 -s Key-E020-21</code>
+
     <code>./getkey -d /dev/keypad0 -g</code>
  
The program will map the keypad at <code>/dev/keypad0</code> to the matrix file <code>Key-E020-21</code>.
+
The program will display the matrix presently associated with the keypad at <code>/dev/keypad0''</code>.
  
 
'''example output'''
 
'''example output'''

Revision as of 13:49, 19 November 2013

TODO: {{#todo:InProgress(11.14.13-11:41->JG+);(11.14.13-15:30->MD-);(11.19.13-09:13->JG+)|Jgreene|oe 4,oe 5,jg,md,Review}}

This procedure provides an overview of how to open, build and run the getkey C example project using the Eclipse IDE.

Opening, Building and Uploading the Project Files

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

stub

2. Open the getkey project files.

stub

3. Build the getkey project.

stub

4. Upload the getkey binary to the target machine.

stub

Description, Usage and Expected Behaviour

This is an example program for mapping keypad input to a character matrix using the keypad interface on the SOM-150ES.

To use this program you will need the appropriate hardware:
A SOM-150ES carrier board.
A compatible SoM for that carrier board (SOM-9260M, SOM-9620M and SOM-9X25 are all compatible and available from EMAC).
A compatible keypad (Available from EMAC, item# E202-21).

Usage for getkey

   getkey [-d device -b -g -s file]
d Specifies the device node. The default is /dev/keypad
b Activates read blocking. The program will sleep until a key on the keypad is pressed.
g Returns the current keypad matrix.
s Sets the keypad matrix to that of the specified matrix file. (See project for example file Key-E020-21). If a matrix operation is not specified then the last key pressed is returned.

Note Arguments are evaluated in order. If blocking or device specifications are used, they must be declared before the matrix arguments on the command line.

Usage Example. Mapping the Keypad to a Matrix File

   ./getkey -d /dev/keypad0 -s Key-E020-21

The program will map the keypad at /dev/keypad0 to the matrix file Key-E020-21.

example output

Usage Example. Displaying the Matrix Presently Associated with the Keypad

   ./getkey -d /dev/keypad0 -g

The program will display the matrix presently associated with the keypad at /dev/keypad0.

example output

Usage Example. Displaying the Character Presently Mapped to a Key on the Keypad

   ./getkey -d /dev/keypad0 -b

The program will wait until a key is pressed on the keypad. When a key is pressed it will display the corresponding character mapped to that pressed key, as specified in the matrix file.

example output