Difference between revisions of "Example getkey"
(→Usage for getkey) |
(→Necessary Hardware) |
||
| Line 29: | Line 29: | ||
* A [http://www.emacinc.com/som/som150es.htm SOM-150ES carrier board] (Available from EMAC).<br /> | * A [http://www.emacinc.com/som/som150es.htm SOM-150ES carrier board] (Available from EMAC).<br /> | ||
| − | * A compatible | + | * A compatible SoM for that carrier board ([http://www.emacinc.com/products/system_on_module/SoM-9260M SOM-9260M], [http://www.emacinc.com/som/som9G20.htm SOM-9G20M] and [http://www.emacinc.com/som/som9x25.htm SOM-9X25] are all compatible and available from EMAC).<br /> |
* A compatible keypad ([http://www.emacinc.com/sbc_microcontroller_addons.htm Available from EMAC], refer to item# E20-21 or E020-25. [https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCsQFjAA&url=http%3A%2F%2Fwww.in2tec.com%2Flib%2Fdownloadfile.php%3Ffilename%3D4000_series_keypads_datasheet.pdf%26loc%3Ddocuments%2F%26ct%3Dpdf&ei=Wf-MUrGxO-nEyQGggoGgCg&usg=AFQjCNEQxIaiH6-gx6uTq4O66o1YVDunZw&bvm=bv.56643336,d.aWc Datasheet]). | * A compatible keypad ([http://www.emacinc.com/sbc_microcontroller_addons.htm Available from EMAC], refer to item# E20-21 or E020-25. [https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCsQFjAA&url=http%3A%2F%2Fwww.in2tec.com%2Flib%2Fdownloadfile.php%3Ffilename%3D4000_series_keypads_datasheet.pdf%26loc%3Ddocuments%2F%26ct%3Dpdf&ei=Wf-MUrGxO-nEyQGggoGgCg&usg=AFQjCNEQxIaiH6-gx6uTq4O66o1YVDunZw&bvm=bv.56643336,d.aWc Datasheet]). | ||
Revision as of 09:41, 21 November 2013
This procedure provides an overview of how to open, build and run the getkey C example project using the Eclipse IDE.
Contents
- 1 Opening, Building and Uploading the Project Files
- 2 Description, Usage and Expected Behaviour
- 2.1 Necessary Hardware
- 2.2 Plugging the Keypad into the SOM-150ES Carrier Board
- 2.3 Usage for getkey
- 2.4 Usage Example. Mapping the Keypad to a Matrix File
- 2.5 Usage Example. Displaying the Matrix Presently Associated with the Keypad
- 2.6 Usage Example. Displaying the Character Presently Mapped to a Key on the Keypad
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.
Necessary Hardware
To use the getkey program you will need the following hardware.
- A SOM-150ES carrier board (Available from EMAC).
- A compatible SoM for that carrier board (SOM-9260M, SOM-9G20M and SOM-9X25 are all compatible and available from EMAC).
- A compatible keypad (Available from EMAC, refer to item# E20-21 or E020-25. Datasheet).
SOM-150ES carrier board with keypad
Plugging the Keypad into the SOM-150ES Carrier Board
Plug the keypad into the HDR5 KEYPAD header of the SOM-150ES Carrier Board.
Make sure that you line up pin 0 of the keypad's ribbon cable with pin 2 of the header.
Usage for getkey
The getkey program is controlled from the console via command line parameters. You can specify the keypad device node, specify the keypad matrix file (see note on the matrix file, below), inspect the current matrix and test individual keys on the keypad.
./getkey [-d device -b -g -s file]
- d
- Specify the keypad device node. The default is
/dev/keypad - b
- Test an individual key-character assignment (via "read blocking"). The program will sleep until a key on the keypad is pressed, then output that key's character to the console.
- g
- Outputs the current keypad matrix (see note on the matrix file, below) to the console.
- 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 on parameter order. Parameters are evaluated in order. If blocking (b) or device specifications (d) are used, they must be declared before the matrix arguments on the command line.
Note on the matrix file. The matrix file specifies which characters are associated with which keypad-keys. A sample matrix file is included with the project: Key-E020-21. This is a standard text file. The character assignments are arranged in a simple grid.
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. AND WHY ON EARTH WOULD I WANT TO DO THAT???
Usage Example. Displaying the Matrix Presently Associated with the Keypad
WHAT IS THIS MATRIX? IS SOMEONE GOING TO ASK ME TO TAKE A BLUE OR RED PILL TO INDICATE WHETHER I WANT THE ANSWER TO THAT QUESTION?
./getkey -d /dev/keypad0 -g
The program will display the matrix presently associated with the keypad at /dev/keypad0.
File:Example getkey terminal session sample 0.png
The matrix displayed here is that of the Key-E020-21 file.
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.
File:Example getkey terminal session sample 1.png
In this case I pressed the 5 key on the keypad.
