eLinux.org - User contributions [en]

ECE497 Project: Kinect

2012-11-14T06:28:07Z

Astroricks: /* Theory of Operation */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

==== Overview ====
The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

==== 1. Download the image package and burn it into the SD card ====

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

==== 2. Run the sample application ====

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

==== 3. Setting up your Linux development PC ====

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

==== 4. Setting up the BeagleBoard-xM ====

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

== User Instructions ==

===Building and running samples===

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

===The Snake Game===

The Snake Game can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM. To play with it you should copy the folder to the root directory of SD card. Since what we did is combining the Snake Game source code into the Tracking Sample, running this application would be the same way as running the samples.

We suggest playing with the following command:

beagle$ cd Tracking_Sanke/bin/
beagle$ ./QtTracking-SDK –qws -upper

When the application is running, we suggest pressing the "setting" button first to enable the wall-cross mode, which could make it not so easily "game over". To start the game, you need to press Up Arrow(or Arrows of other directions) on the keyboard. And the player would get a better playing experience if he/she stands in front of the Kinect with a distance of about 1.5m - 2m. The player should control the snake with his '''right hand''' moving up and down, left and right.

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can modify the codes to change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

=== The Control Strategy ===
Judging gestures simply from the changing of coordinate is hard and may lead to mistakes commonly. To improve the playing experience, we combined two methods to guess which control direction the player wants to make.

1. Compare the current coordinate with the last time. When the date is refreshed, we can compare the current coordinate of player's right-hand withe the last time value. If the difference between the coordinates of x or y is larger than the threshold, it is reasonable to think that the player may want the snake to make a move in this direction.

2. See where the hand locates. After making a upward movement, it has a high possibility that the y coordinate locates in the up area. Similar situation appears in other movement directions. So by checking the current value of the x and y coordinates we can know which direction the player want to make move.

Only when the same direction is implied by both methods, we move the snake in this direction. It seems that this control strategy works pretty well.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T05:52:23Z

Astroricks: /* Highlights */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

==== Overview ====
The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

==== 1. Download the image package and burn it into the SD card ====

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

==== 2. Run the sample application ====

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

==== 3. Setting up your Linux development PC ====

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

==== 4. Setting up the BeagleBoard-xM ====

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

== User Instructions ==

===Building and running samples===

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

===The Snake Game===

The Snake Game can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM. To play with it you should copy the folder to the root directory of SD card. Since what we did is combining the Snake Game source code into the Tracking Sample, running this application would be the same way as running the samples.

We suggest playing with the following command:

beagle$ cd Tracking_Sanke/bin/
beagle$ ./QtTracking-SDK –qws -upper

When the application is running, we suggest pressing the "setting" button first to enable the wall-cross mode, which could make it not so easily "game over". To start the game, you need to press Up Arrow(or Arrows of other directions) on the keyboard. And the player would get a better playing experience if he/she stands in front of the Kinect with a distance of about 1.5m - 2m. The player should control the snake with his '''right hand''' moving up and down, left and right.

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can modify the codes to change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T05:51:11Z

Astroricks: /* The Snake Game */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

==== Overview ====
The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

==== 1. Download the image package and burn it into the SD card ====

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

==== 2. Run the sample application ====

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

==== 3. Setting up your Linux development PC ====

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

==== 4. Setting up the BeagleBoard-xM ====

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

== User Instructions ==

===Building and running samples===

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

===The Snake Game===

The Snake Game can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM. To play with it you should copy the folder to the root directory of SD card. Since what we did is combining the Snake Game source code into the Tracking Sample, running this application would be the same way as running the samples.

We suggest playing with the following command:

beagle$ cd Tracking_Sanke/bin/
beagle$ ./QtTracking-SDK –qws -upper

When the application is running, we suggest pressing the "setting" button first to enable the wall-cross mode, which could make it not so easily "game over". To start the game, you need to press Up Arrow(or Arrows of other directions) on the keyboard. And the player would get a better playing experience if he/she stands in front of the Kinect with a distance of about 1.5m - 2m. The player should control the snake with his '''right hand''' moving up and down, left and right.

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T05:38:51Z

Astroricks: /* User Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

==== Overview ====
The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

==== 1. Download the image package and burn it into the SD card ====

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

==== 2. Run the sample application ====

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

==== 3. Setting up your Linux development PC ====

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

==== 4. Setting up the BeagleBoard-xM ====

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

== User Instructions ==

===Building and running samples===

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

===The Snake Game===

The Snake Game can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM. To play with it you should copy the folder to the root directory of SD card. Since what we did is combining the Snake Game source code into the Tracking Sample, running this application would be the same way as running the samples.

We suggest playing with the following command:

beagle$ cd Tracking_Sanke/bin/
beagle$ ./QtTracking-SDK –qws -upper

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T05:38:37Z

Astroricks: /* The Snake Game */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

==== Overview ====
The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

==== 1. Download the image package and burn it into the SD card ====

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

==== 2. Run the sample application ====

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

==== 3. Setting up your Linux development PC ====

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

==== 4. Setting up the BeagleBoard-xM ====

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

== User Instructions ==

===Building and running samples=== (if you want to)

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

===The Snake Game===

The Snake Game can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM. To play with it you should copy the folder to the root directory of SD card. Since what we did is combining the Snake Game source code into the Tracking Sample, running this application would be the same way as running the samples.

We suggest playing with the following command:

beagle$ cd Tracking_Sanke/bin/
beagle$ ./QtTracking-SDK –qws -upper

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T05:37:50Z

Astroricks: /* User Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

==== Overview ====
The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

==== 1. Download the image package and burn it into the SD card ====

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

==== 2. Run the sample application ====

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

==== 3. Setting up your Linux development PC ====

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

==== 4. Setting up the BeagleBoard-xM ====

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

== User Instructions ==

===Building and running samples=== (if you want to)

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

===The Snake Game===

The Snake Game can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM. To play with it you should copy the folder to the root directory of SD card. Since what we did is combining the Snake Game source code into the Tracking Sample, running this application would be the same way as running the samples.

We suggest playing with the following command:

beagle$ cd Tracking_Sanke/bin/

beagle$ ./QtTracking-SDK –qws -upper

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T05:07:46Z

Astroricks: /* User Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

==== Overview ====
The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

==== 1. Download the image package and burn it into the SD card ====

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

==== 2. Run the sample application ====

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

==== 3. Setting up your Linux development PC ====

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

==== 4. Setting up the BeagleBoard-xM ====

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

== User Instructions ==

'''Building and running samples''' (if you want to)

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

'''The Snake Game'''

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T04:55:09Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

=== Hardware ===

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

=== Software ===

The source files for the project can be downloaded from https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM . Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

=== The Main Idea ===
We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

=== The Technics Used ===
Technically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

=== Yue Zhang ===
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
=== Xinyu Cheng ===
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
=== Xia Li ===
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T04:52:21Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

'''Hardware'''

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

'''Software'''

The source files for the project can be downloaded from [https://github.com/Astroricks/Snake-Game-with-Kinect-on-BeagleBoard-xM/tree/master/Tracking_Snake github]. Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Our project is about how to use Microsoft Kinect Sensor to play snake game by the motion of you right hand(You can change to any part of your body if you would like to). We set a score section to record the highest score. Anybody who want to break our record are welcome(Currently the record is holding by Xinyu Cheng at 260). We've created a play demo and uploaded it to YouTube:

=== Play snake game with Kinect sensor on BeagleboardxM ===
{{#ev:youtube|uBW6LkVUi9I}}

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

Tenically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
''' Xia Li '''
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Yue Zhang Project

2012-11-14T04:33:43Z

Astroricks: Blanked the page

ECE497 Project: Kinect

2012-11-14T04:03:28Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

'''Hardware'''

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x DVI to HDMI wire

1 x Monitor

1 x Keyboard

1 x Mouse

'''Software'''

The source files for the project can be downloaded from'''github'''. Once you have set up the developing environment as in the following instructions, you can download the files, playing with the game or making changes.

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought, and errors came out occasionally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

Note: The following instruction is about how to set up the environment for developing. If you don't want to do the development, you can just skip that.

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

Tenically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
''' Xia Li '''
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T03:33:59Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

'''Hardware'''

1 x [http://www.microsoftstore.com/store/msstore/en_US/pd/ThemeID.27509700/Kinect-for-Xbox-360/productID.216507400 Kinect]

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x Keyboard

1 x Mouse

1 x DVI to HDMI wire

1 x Power Supply

1 x Monitor

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

Tenically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
''' Xia Li '''
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T03:31:32Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

'''Hardware'''

1 x Kinect

1 x [http://www.digikey.com/product-highlights/us/en/texas-instruments-beagleboard/685 BeagleBoard xM]

1 x Keyboard

1 x Mouse

1 x DVI to HDMI wire

1 x Power Supply

1 x Monitor

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motion of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

Tenically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motion based algorithm which makes the application runs more smoothly.
* Programmed for the part of motion algorithm.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
''' Xia Li '''
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motion based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-14T03:03:01Z

Astroricks: /* Executive Summary */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

I believe that almost every college students have played a game called "Greedy Snake" in our childhood. At that time, we played it on the cellphone, on the computer or on the PSP. However, we are always using the keyboard to control the games we played. Now, our final project could bring you something new, that is a "Gesture Controlled Greedy Snake". It means that, using the gesture, the keyboard is never required to play the game. Amazing? Read the following wiki to know how we make it happens!

Basically, we are using the kinect from Microsoft and the Beagle Board XM from Texas Instrument to accomplish our gesture game. The program for the game is programmed on the QT-Linux. Besides, we use the cross compiling to compile the program to make the game run on the beagle board.

After our previous work, our "Gesture Greedy Snake" is completed, and works pretty good. The snake can be controlled by our gestures smoothly. The game reminds us a different style of childhood memory.

== Installation Instructions ==

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

host$ cd ''<DownloadDirectory>''

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''Update:''The free version Qt Creator can not be used in this project since it doesn't have cross-compile option with it.

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible for us to get the coordinate of many joints of the body. In this case, we can judge the position and the motivation of our hands or any other joints. Then, we can use the direction we get from the previous judgement to control the Greedy Snake. Our project is running with the idea.

Tenically, we can use QT to design our program and then cross-complie our project to the beagle-board. The Greedy Snake is an open-source QT game, and the tracking of the joint can be accomplished from modifying the Omek SDK. We have to modify both of their codes to connect the two parts together.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
* Implemented the motivation based algorithm which makes the application runs more smoothly.
* Programmed for the part of motivation algorithm.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Accomplished the cross-compiling on QT.
* Programming for the connection between the Snake Game and the Kinect SDK.
* Designed and Implemented the coordinate based algorithm.
''' Xia Li '''
* Researched how to run the provided SDK demo.
* Speed up for the demo.
* Designed the motivation based algorithm.
* Programmed to improved the accuracy and speed of the game.

== Future Work ==

Now, our game can work pretty good and smoothly. The future work for the project will mainly about how to improve the user interface and the game rules. We can also improve our algorithm for the direction judgement.

== Conclusions ==

Conculsionly, our project works pretty good. Our Greedy Snake game runs very good and brings a lot of fun for us. During the develop process, we met lots of difficulties, we tried to solve them one by one. Finally, we solved almost all the problems and end up with a nice project.

{{YoderFoot}}

ECE497 Contributions and Project Status

2012-11-13T21:40:18Z

Astroricks: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list.
Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
| [[Special:Contributions/atniptw|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Rover | Rover]]
| [https://github.com/brannojs/ brannojs]
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
| [[Special:Contributions/Xinyu1991|contrib]]
| [[ECE497_Project:_Kinect | Kinect]]
| [https://github.com/xinyu1991/ Xinyu Cheng]
|-
| [[User:correlbn | Bryan Correll]]
| [[Special:Contributions/correlbn|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/correlbn/My-Beagle-Project/ Correlbn]
|-
| [[User:draneaw | Alex Drane]]
| [[Special:Contributions/draneaw|contrib]]
| [[ECE497: Remote Web Cam Viewer Final Project| Remote Web Cam Viewer]]
| [https://github.com/draneaw/ Draneaw]
|-
| [[User:duganje | Josh Dugan]]
| [[Special:Contributions/duganje|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
| [[Special:Contributions/geislekj|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
| [[Special:Contributions/Chris.good|contrib]]
| [[ECE497 Project RoverGUI | RoverGUI]]
| [https://github.com/goodca/ goodca]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 Project Rover | Rover]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 Project Rover | Rover]]
| [https://github.com/jungeml/ Jungeml]
|-
| [[User:larmorgs | Greg Larmore]]
| [[Special:Contributions/larmorgs|contrib]]
| [[ECE497 SPI Project | SPI Project]]
| [https://github.com/larmorgs Greg Larmore]
|-
| [[User:Lobdeljt | John Lobdell]]
|
| [[ECE 497 lobdeljt Project | My Beagle Project]]
| [https://github.com/jtlobdell jtlobdell]
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Project: Kinect | Kinect]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:Millerap | Andrew Miller]]
| [[Special:Contributions/Millerap|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/millerap millerap]
|-
| [[User:mmoravec | Matthew Moravec]]
| [[Special:Contributions/mmoravec|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/mmoravec/ mmoravec]
|-
| [[User:ngop | Peter Ngo]]
| [[Special:Contributions/ngop|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/ngop/ ngop]
|-
| [[User:Popenhjc | James Popenhagen]]
| [[Special:Contributions/Popenhjc|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Richarsm | Sean Richardson]]
| [[Special:Contributions/Richarsm|contrib]]
| [[ECE497 SPI Project | SPI Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 SLAM via ROS | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
| [[Special:Contributions/ruff|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/ruffsl/ ruffsl]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Astroricks | Yue Zhang]]
| [[Special:Contributions/Astroricks | contrib]]
| [[ECE497_Project:_Kinect | Kinect]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

ECE497 Contributions and Project Status

2012-11-13T21:39:50Z

Astroricks: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list.
Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
| [[Special:Contributions/atniptw|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Rover | Rover]]
| [https://github.com/brannojs/ brannojs]
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
| [[Special:Contributions/Xinyu1991|contrib]]
| [[ECE497_Project:_Kinect | Kinect]]
| [https://github.com/xinyu1991/ Xinyu Cheng]
|-
| [[User:correlbn | Bryan Correll]]
| [[Special:Contributions/correlbn|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/correlbn/My-Beagle-Project/ Correlbn]
|-
| [[User:draneaw | Alex Drane]]
| [[Special:Contributions/draneaw|contrib]]
| [[ECE497: Remote Web Cam Viewer Final Project| Remote Web Cam Viewer]]
| [https://github.com/draneaw/ Draneaw]
|-
| [[User:duganje | Josh Dugan]]
| [[Special:Contributions/duganje|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
| [[Special:Contributions/geislekj|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
| [[Special:Contributions/Chris.good|contrib]]
| [[ECE497 Project RoverGUI | RoverGUI]]
| [https://github.com/goodca/ goodca]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 Project Rover | Rover]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 Project Rover | Rover]]
| [https://github.com/jungeml/ Jungeml]
|-
| [[User:larmorgs | Greg Larmore]]
| [[Special:Contributions/larmorgs|contrib]]
| [[ECE497 SPI Project | SPI Project]]
| [https://github.com/larmorgs Greg Larmore]
|-
| [[User:Lobdeljt | John Lobdell]]
|
| [[ECE 497 lobdeljt Project | My Beagle Project]]
| [https://github.com/jtlobdell jtlobdell]
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Project: Kinect | Kinect]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:Millerap | Andrew Miller]]
| [[Special:Contributions/Millerap|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/millerap millerap]
|-
| [[User:mmoravec | Matthew Moravec]]
| [[Special:Contributions/mmoravec|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/mmoravec/ mmoravec]
|-
| [[User:ngop | Peter Ngo]]
| [[Special:Contributions/ngop|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/ngop/ ngop]
|-
| [[User:Popenhjc | James Popenhagen]]
| [[Special:Contributions/Popenhjc|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Richarsm | Sean Richardson]]
| [[Special:Contributions/Richarsm|contrib]]
| [[ECE497 SPI Project | SPI Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 SLAM via ROS | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
| [[Special:Contributions/ruff|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/ruffsl/ ruffsl]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497_Project:_Kinect | Kinect]]
| [[Special:Contributions/Astroricks | contrib]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

User:Xinyu1991

2012-11-11T01:56:20Z

Astroricks:

[[Category: ECE497 |UX]]

ECE497 Project: Kinect

2012-11-08T20:33:17Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Our project is using kinect to accomplish a kind of "Gesture Game", which is operated through our gestures and motions. Compared to the traditional games, the gesture game can provide better interactive enjoy without the complex operation from the keyboard and mouse.

Through our previous work, we have alread completed the configuration of our project successfully. The configuration work includes the configure of the Beagle Board and the configure of the QT IDE. Now, we can run the Tracking Demo and the Gesture Demo on the Beagle Board. We can also download our projects to the Beagle Board through cross-compiling.

Our work ahead is looking for an interative game, and transplant the game to the QT platform. Then, download the game to the Beagle Board. In that case, the game can be played on the Kinect.

Until now, we have a good begining with the demos runs succefully. We still need some time to finish the following work.

== Installation Instructions ==

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''To '''Li Xia''': Qt Creator has commercial version on http://qt.nokia.com/downloads . I'm using it but I can only try it for 30 days. I just find the free version above but haven't tried it. Please try the free version and see if it works. If nothing's wrong, just simply remove this paragraph afterwards.''

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible to recognize our gesture and motion. In this case, the gesture and motion can take the place of the mouse. Our project is running with the idea.

We can use QT to design our program and then cross-complie our project to the beagle-board. According to the cross-compiling of the sample project: Tracking-SDK, we have got a pretty good demo. Hence, it is possible for us to design an interesting gesture game on the QT platform and then run it on the beagle board with the kinect.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Realize the cross-compiling on QT.
''' Xia Li '''
* Researched how to run the provided demo.
* How to speed up the demo.

== Future Work ==

Our future work is to design an interactive game which can be controlled through our gestures.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Contributions and Project Status

2012-11-08T20:26:25Z

Astroricks: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list.
Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
| [[Special:Contributions/atniptw|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Rover | Rover]]
| [https://github.com/brannojs/ brannojs]
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
| [[Special:Contributions/Xinyu1991|contrib]]
| [[ECE497_Project:_Kinect | Kinect]]
| [https://github.com/xinyu1991/ Xinyu Cheng]
|-
| [[User:correlbn | Bryan Correll]]
| [[Special:Contributions/correlbn|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/correlbn/My-Beagle-Project/ Correlbn]
|-
| [[User:draneaw | Alex Drane]]
| [[Special:Contributions/draneaw|contrib]]
| [[ECE497: Remote Web Cam Viewer Final Project| Remote Web Cam Viewer]]
| [https://github.com/draneaw/ Draneaw]
|-
| [[User:duganje | Josh Dugan]]
| [[Special:Contributions/duganje|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
| [[Special:Contributions/geislekj|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
| [[Special:Contributions/Chris.good|contrib]]
| [[ECE497 Project RoverGUI | RoverGUI]]
| [https://github.com/goodca/ goodca]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 Project Rover | Rover]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 Project Rover | Rover]]
| [https://github.com/jungeml/ Jungeml]
|-
| [[User:larmorgs | Greg Larmore]]
| [[Special:Contributions/larmorgs|contrib]]
| [[ECE497 SPI Project | SPI Project]]
| [https://github.com/larmorgs Greg Larmore]
|-
| [[User:Lobdeljt | John Lobdell]]
|
| [[ECE 497 lobdeljt Project | My Beagle Project]]
| [https://github.com/jtlobdell jtlobdell]
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Project: Kinect | Kinect]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:Millerap | Andrew Miller]]
| [[Special:Contributions/Millerap|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/millerap millerap]
|-
| [[User:mmoravec | Matthew Moravec]]
| [[Special:Contributions/mmoravec|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/mmoravec/ mmoravec]
|-
| [[User:ngop | Peter Ngo]]
| [[Special:Contributions/ngop|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/ngop/ ngop]
|-
| [[User:Popenhjc | James Popenhagen]]
| [[Special:Contributions/Popenhjc|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Richarsm | Sean Richardson]]
| [[Special:Contributions/Richarsm|contrib]]
| [[ECE497 SPI Project | SPI Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 SLAM via ROS | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
| [[Special:Contributions/ruff|contrib]]
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/ruffsl/ ruffsl]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497_Project:_Kinect | Kinect]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

User:Astroricks

2012-11-08T16:50:00Z

Astroricks:

Yue Zhang

Electrical and Computer Engineering Major, Class of 2012.
[[Category:ECE497 |Ua]]

[[ECE497 Yue Zhang Project]]

ECE497 Project: Kinect

2012-11-05T16:56:02Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Our project is using kinect to accomplish a kind of "Gesture Game", which is operated through our gestures and motions. Compared to the traditional games, the gesture game can provide better interactive enjoy without the complex operation from the keyboard and mouse.

Through our previous work, we have alread completed the configuration of our project successfully. The configuration work includes the configure of the Beagle Board and the configure of the QT IDE. Now, we can run the Tracking Demo and the Gesture Demo on the Beagle Board. We can also download our projects to the Beagle Board through cross-compiling.

Our work ahead is looking for an interative game, and transplant the game to the QT platform. Then, download the game to the Beagle Board. In that case, the game can be played on the Kinect.

Until now, we have a good begining with the demos runs succefully. We still need some time to finish the following work.

== Installation Instructions ==

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page, and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and not detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''To '''Li Xia''': Qt Creator has commercial version on http://qt.nokia.com/downloads . I'm using it but I can only try it for 30 days. I just find the free version above but haven't tried it. Please try the free version and see if it works. If nothing's wrong, just simply remove this paragraph afterwards.''

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible to recognize our gesture and motion. In this case, the gesture and motion can take the place of the mouse. Our project is running with the idea.

We can use QT to design our program and then cross-complie our project to the beagle-board. According to the cross-compiling of the sample project: Tracking-SDK, we have got a pretty good demo. Hence, it is possible for us to design an interesting gesture game on the QT platform and then run it on the beagle board with the kinect.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Realize the cross-compiling on QT.
''' Xia Li '''
* Researched how to run the provided demo.
* How to speed up the demo.

== Future Work ==

Our future work is to design an interactive game which can be controlled through our gestures.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-05T09:23:19Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Our project is using kinect to accomplish a kind of "Gesture Game", which is operated through our gestures and motions. Compared to the traditional games, the gesture game can provide better interactive enjoy without the complex operation from the keyboard and mouse.

Through our previous work, we have alread completed the configuration of our project successfully. The configuration work includes the configure of the Beagle Board and the configure of the QT IDE. Now, we can run the Tracking Demo and the Gesture Demo on the Beagle Board. We can also download our projects to the Beagle Board through cross-compiling.

Our work ahead is looking for an interative game, and transplant the game to the QT platform. Then, download the game to the Beagle Board. In that case, the game can be played on the Kinect.

Until now, we have a good begining with the demos runs succefully. We still need some time to finish the following work.

== Installation Instructions ==

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''To '''Li Xia''': Qt Creator has commercial version on http://qt.nokia.com/downloads . I'm using it but I can only try it for 30 days. I just find the free version above but haven't tried it. Please try the free version and see if it works. If nothing's wrong, just simply remove this paragraph afterwards.''

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible to recognize our gesture and motion. In this case, the gesture and motion can take the place of the mouse. Our project is running with the idea.

We can use QT to design our program and then cross-complie our project to the beagle-board. According to the cross-compiling of the sample project: Tracking-SDK, we have got a pretty good demo. Hence, it is possible for us to design an interesting gesture game on the QT platform and then run it on the beagle board with the kinect.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Realize the cross-compiling on QT.
''' Xia Li '''
* Researched how to run the provided demo.
* How to speed up the demo.

== Future Work ==

Our future work is to design an interactive game which can be controlled through our gestures.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-05T09:21:42Z

Astroricks: /* User Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Our project is using kinect to accomplish a kind of "Gesture Game", which is operated through our gestures and motions. Compared to the traditional games, the gesture game can provide better interactive enjoy without the complex operation from the keyboard and mouse.

Through our previous work, we have alread completed the configuration of our project successfully. The configuration work includes the configure of the Beagle Board and the configure of the QT IDE. Now, we can run the Tracking Demo and the Gesture Demo on the Beagle Board. We can also download our projects to the Beagle Board through cross-compiling.

Our work ahead is looking for an interative game, and transplant the game to the QT platform. Then, download the game to the Beagle Board. In that case, the game can be played on the Kinect.

Until now, we have a good begining with the demos runs succefully. We still need some time to finish the following work.

== Installation Instructions ==

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''To '''Li Xia''': Qt Creator has commercial version on http://qt.nokia.com/downloads . I'm using it but I can only try it for 30 days. I just find the free version above but haven't tried it. Please try the free version and see if it works. If nothing's wrong, just simply remove this paragraph afterwards.''

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

To build QtTracking Sample:

1. Start Qt Creator.

2. Go to: File > Open File or Project, select the QtTracking-SDK.pro project (from Beckon-SDK-{version}/samples/QtTracking) and click Open. Select Embedded Linux instead of Desktop.

3. Click Finish.

4. Go to Projects tab (on the left), In Qt version select Qt [4.x.x (qt-arm)]/.

5. Run Build -> Build Project command.

The result executable can be found in the Beckon-SDK-{version}/bin directory.

To run the QtTracking Sample:

1. Mount or copy the bin directory to the BeagleBoard.

''Note: Run the reset.sh script inside the "bin" folder of the SDK before each sample run, to reset the DSP.''

Run the following:

beagle$ ./QtTracking-SDK –qws

''Note: Developer's guide has more instructions on running the sample''

Others are coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible to recognize our gesture and motion. In this case, the gesture and motion can take the place of the mouse. Our project is running with the idea.

We can use QT to design our program and then cross-complie our project to the beagle-board. According to the cross-compiling of the sample project: Tracking-SDK, we have got a pretty good demo. Hence, it is possible for us to design an interesting gesture game on the QT platform and then run it on the beagle board with the kinect.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Realize the cross-compiling on QT.
''' Xia Li '''
* Researched how to run the provided demo.
* How to speed up the demo.

== Future Work ==

Our future work is to design an interactive game which can be controlled through our gestures.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-05T09:11:26Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Our project is using kinect to accomplish a kind of "Gesture Game", which is operated through our gestures and motions. Compared to the traditional games, the gesture game can provide better interactive enjoy without the complex operation from the keyboard and mouse.

Through our previous work, we have alread completed the configuration of our project successfully. The configuration work includes the configure of the Beagle Board and the configure of the QT IDE. Now, we can run the Tracking Demo and the Gesture Demo on the Beagle Board. We can also download our projects to the Beagle Board through cross-compiling.

Our work ahead is looking for an interative game, and transplant the game to the QT platform. Then, download the game to the Beagle Board. In that case, the game can be played on the Kinect.

Until now, we have a good begining with the demos runs succefully. We still need some time to finish the following work.

== Installation Instructions ==

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''To '''Li Xia''': Qt Creator has commercial version on http://qt.nokia.com/downloads . I'm using it but I can only try it for 30 days. I just find the free version above but haven't tried it. Please try the free version and see if it works. If nothing's wrong, just simply remove this paragraph afterwards.''

After Qt Creator is successfully installed, start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible to recognize our gesture and motion. In this case, the gesture and motion can take the place of the mouse. Our project is running with the idea.

We can use QT to design our program and then cross-complie our project to the beagle-board. According to the cross-compiling of the sample project: Tracking-SDK, we have got a pretty good demo. Hence, it is possible for us to design an interesting gesture game on the QT platform and then run it on the beagle board with the kinect.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Realize the cross-compiling on QT.
''' Xia Li '''
* Researched how to run the provided demo.
* How to speed up the demo.

== Future Work ==

Our future work is to design an interactive game which can be controlled through our gestures.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-05T09:09:25Z

Astroricks: /* Installation Instructions */

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]], [[user:Xinyu1991|Xinyu Cheng]], [[user:Lix|Xia Li]].

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Our project is using kinect to accomplish a kind of "Gesture Game", which is operated through our gestures and motions. Compared to the traditional games, the gesture game can provide better interactive enjoy without the complex operation from the keyboard and mouse.

Through our previous work, we have alread completed the configuration of our project successfully. The configuration work includes the configure of the Beagle Board and the configure of the QT IDE. Now, we can run the Tracking Demo and the Gesture Demo on the Beagle Board. We can also download our projects to the Beagle Board through cross-compiling.

Our work ahead is looking for an interative game, and transplant the game to the QT platform. Then, download the game to the Beagle Board. In that case, the game can be played on the Kinect.

Until now, we have a good begining with the demos runs succefully. We still need some time to finish the following work.

== Installation Instructions ==

We are using the drivers provided by [http://www.omekinteractive.com/ Omek]. The driver files can be found at the Beckon™ SDK 2.4 – BeagleBoard-xM Edition [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation installation] page and a developer's guide is provided at the [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/34/11/documentation documentation] page. (You may need to register first.) Instructions in this [http://treyweaver.blogspot.com/2010/10/setting-up-qt-development-environment.html blog] are also very useful.

Although the developer's guide introduces how to do the installation and configuration, we have found that it takes much longer than we originally thought and errors came out occationally. It seems that the developer's guide is not very well organized and detailed enought anyway. So we arranged our instruction and configuration procedures as below:

1. Download the image package and burn it into the SD card

Download the image package [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-Image-2.4.19872.tar.gz] as mentioned above onto your Linux PC. Then extract it by entering

host$ tar -xvzf ''<ImageFileName>''

Run the following command to make sure you have bash installed.

host$ sudo apt-get install bash

Insert your SD card using a card reader/writer. Run the following command:

host$ sudo bash mkcard.sh /dev/''<sdX>'' beagle-omek

''Note: This action will wipe out and rewrite the SD card so make sure the files in it are backed up. The name of the SD card can be viewed in Disk Utility. If you mistakenly use the main OS device name this script can erase your entire OS.''

2. Run the sample application

Plug the sensor into the BeagleBoard-xM USB port. Ensure the mouse and keyboard are connected to the BeagleBoard-xM USB port. Connect the BeagleBoard-xM to the monitor with an HDMI cable. Connect the BeagleBoard-xM power supply and wait for the boot process to reach the login prompt, login as user root (no password is required). Now it's ready to run the sample applications on the BeagleBoard-xM.

''Note: Details about running the samples can be found in the developer's guide from page 9 to 11. The Kinect will react properly only if the player is within an appropriate distance (about 1m - 5m). ''

3. Setting up your Linux development PC

Download [http://support.omekinteractive.com/index.php?/TI/managedownloads/Download/View/32/11/installation Beckon-SDK-2.4.19872.tar.gz] and extract it onto your host PC (this is the actual SDK which contains headers, libraries, documentation, makefiles, etc...) The SDK provides the tools to develop a motion-tracking and gesture-based application that can run on the BeagleBoard-xM. After developing the application, cross-compile it onto the Linux PC and then copy the image onto the BeagleBoard-xM via external USB storage.

1) Download the Linux ARM cross toolchain:

For 32-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

For 64-bit Ubuntu you will want to download this file: http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

Extract the downloaded archive into your system root directory:

host$ sudo tar -xvjf ''<ToolchainFileName>'' -C /

''Note: If you extract the archive into a different directory, you should adjust the following instructions as well as the samples' makefiles accordingly.''

2) Install the Qt embedded SDK for Angstrom/BeagleBoard:

Now that you have your cross compiler installed, you can compile Qt with it. First thing to do is to install zlib library:

host$ sudo apt-get install zlib1g-dev

Then download the Open Source LGPL version of Qt libraries 4.6.2 for Embedded Linux [get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz here].

''Note: Newest version of Qt libraries can be found [http://qt-project.org/downloads/ here]. We didn't test it since the 4.6.2 version works fine.''

Extract the file you just downloaded:

host$ tar -xvzf ''<DownloadFileName>''

You need to create a new make.conf. Run the following line to make a new mkspecs directory for the BeagleBoard Processor.

host$ cp -R ''<DownloadDirectory>''/mkspecs/qws/linux-arm-g++/ ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/

Edit the qmake.conf file found in ''<DownloadDirectory>''/mkspecs/qws/linux-DM3730-g++/ and overwrite it with the following lines.

<pre>
#
# qmake configuration for building with arm-linux-g++
#

include(../../common/g++.conf)
include(../../common/linux.conf)
include(../../common/qws.conf)

# modifications to g++.conf
#Toolchain

#Compiler Flags to take advantage of the ARM architecture
QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

QMAKE_CC = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/gcc
QMAKE_CXX = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++
QMAKE_LINK_SHLIB = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

# modifications to linux.conf
QMAKE_AR = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/ar cqs
QMAKE_OBJCOPY = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/objcopy
QMAKE_STRIP = /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/strip

load(qt_config)
</pre>

Now run the configure command (see this [http://processors.wiki.ti.com/index.php/Building_Qt website] for more details if needed):

For 32-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -xplatform qws/linux-DM3730-g++ -qtlibinfix E

For 64-bit Ubuntu:

host$ ./configure -opensource -confirm-license -prefix /opt/qt-arm -no-qt3support -embedded arm -little-endian -platform qws/linux-x86_64-g++ -xplatform qws/linux-DM3730-g++ -qtlibinfix E

Once this is complete you can run make and make install (make may take some hours):

host$ make
host$ sudo make install

3) Install and set up Qt Creator:

Go to http://qt-project.org/downloads to download Qt. Get the latest version of Qt for Linux/X11; be sure to get the appropriate 32bit or 64bit version. Once downloaded go to the download directory and execute the following using your download file name:

host$ chmod u+x ''<QtCreator.bin>''
host$ ./''<QtCreator.bin>''

''To '''Li Xia''': Qt Creator has commercial version on http://qt.nokia.com/downloads . I'm using it but I can only try it for 30 days. I just find the free version above but haven't tried it. Please try the free version and see if it works. If nothing's wrong, just simply remove this paragraph afterwards.''

Start Qt Creator. Go to: Tools > Options > Build & Run > Tool Chains, select Add -> GCC and insert the full compiler path below:

/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/bin/g++

Then go to: Tools > Options > Build & Run > Qt Versions, select Add and provide the following full path to qmake

/opt/qt-arm/bin/qmake

Press Apply and OK.

4. Setting up the BeagleBoard-xM

All of the Qt files that you need to move to the BeagleBoard can be found in the /opt/qt-arm/lib directory on your Linux Build System. Copy all the files out of your build system's /opt/qt-arm/lib directory and put those into the BeagleBoard-xM's /opt/qt-arm/lib directory. You can get the files to the Beagleboard by either networking, using a usb drive or plug the SD card into your Linux Build System.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Coming soon.

== Highlights ==

Coming soon.

== Theory of Operation ==

We are using the kinect as the sensor of our project. The provided algorithm of the kinect make it possible to recognize our gesture and motion. In this case, the gesture and motion can take the place of the mouse. Our project is running with the idea.

We can use QT to design our program and then cross-complie our project to the beagle-board. According to the cross-compiling of the sample project: Tracking-SDK, we have got a pretty good demo. Hence, it is possible for us to design an interesting gesture game on the QT platform and then run it on the beagle board with the kinect.

== Work Breakdown ==

* '''Previous Work Breakdown:'''
''' Yue Zhang '''
* Researched how to Burn the correct Image to the Beagle Board.
* Configure the Beagle Board to control the kinect.
''' Xinyu Cheng '''
* Researched how to configure the QT programming environment.
* Realize the cross-compiling on QT.
''' Xia Li '''
* Researched how to run the provided demo.
* How to speed up the demo.

== Future Work ==

Our future work is to design an interactive game which can be controlled through our gestures.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-05T08:23:31Z

Astroricks: /* Installation Instructions */

ECE497 Project: Kinect

2012-11-05T07:15:40Z

Astroricks: /* Installation Instructions */

ECE497 Project: Kinect

2012-11-05T06:04:55Z

Astroricks: /* Installation Instructions */

ECE497 Project: Kinect

2012-11-05T05:47:47Z

Astroricks: /* Installation Instructions */

ECE497 Project: Kinect

2012-11-05T05:43:18Z

Astroricks: /* Installation Instructions */

ECE497 Project: Kinect

2012-11-05T05:34:59Z

Astroricks: /* Installation Instructions */

ECE497 Project: Kinect

2012-11-05T05:18:20Z

Astroricks: /* Installation Instructions */

ECE497 Project: Kinect

2012-11-05T04:38:48Z

Astroricks:

ECE497 Project: Kinect

2012-11-05T04:38:19Z

Astroricks:

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang]] [[user:Xinyu1991|Xinyu Cheng]] [[user:Lix|Xia Li]]

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Give two sentence intro to the project.

Give two sentences telling what works.

Give two sentences telling what isn't working.

End with a two sentence conclusion.

The sentence count is approximate and only to give an idea of the expected length.

== Installation Instructions ==

Give step by step instructions on how to install your project on the SPEd2 image.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

== Highlights ==

Here is where you brag about what your project can do.

Include a [http://www.youtube.com/ YouTube] demo.

== Theory of Operation ==

Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.

== Work Breakdown ==

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

== Future Work ==

Suggest addition things that could be done with this project.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-05T04:37:51Z

Astroricks:

[[Category:ECE497 |Project]]

Team members: [user:Astroricks|Yue Zhang] [user:Xinyu1991|Xinyu Cheng] [user:Lix|Xia Li]

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Give two sentence intro to the project.

Give two sentences telling what works.

Give two sentences telling what isn't working.

End with a two sentence conclusion.

The sentence count is approximate and only to give an idea of the expected length.

== Installation Instructions ==

Give step by step instructions on how to install your project on the SPEd2 image.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

== Highlights ==

Here is where you brag about what your project can do.

Include a [http://www.youtube.com/ YouTube] demo.

== Theory of Operation ==

Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.

== Work Breakdown ==

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

== Future Work ==

Suggest addition things that could be done with this project.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

ECE497 Project: Kinect

2012-11-05T04:36:47Z

Astroricks: Created page with "Project Team members: [[user:Astroricks|Yue Zhang][user:Xinyu1991|Xinyu Cheng][user:Lix|Xia Li]] == Grading Template == I'm using the following template..."

[[Category:ECE497 |Project]]

Team members: [[user:Astroricks|Yue Zhang][user:Xinyu1991|Xinyu Cheng][user:Lix|Xia Li]]

== Grading Template ==
I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
00 Installation Instructions
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments:

Score: 00/100
</pre>

(Inline Comment)

== Executive Summary ==

Give two sentence intro to the project.

Give two sentences telling what works.

Give two sentences telling what isn't working.

End with a two sentence conclusion.

The sentence count is approximate and only to give an idea of the expected length.

== Installation Instructions ==

Give step by step instructions on how to install your project on the SPEd2 image.

* Include your [https://github.com/ github] path as a link like this: [https://github.com/MarkAYoder/gitLearn https://github.com/MarkAYoder/gitLearn].
* Include any additional packages installed via '''opkg'''.
* Include kernel mods.
* If there is extra hardware needed, include links to where it can be obtained.

== User Instructions ==

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

== Highlights ==

Here is where you brag about what your project can do.

Include a [http://www.youtube.com/ YouTube] demo.

== Theory of Operation ==

Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.

== Work Breakdown ==

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

== Future Work ==

Suggest addition things that could be done with this project.

== Conclusions ==

Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

{{YoderFoot}}

Adafruit: 2-Axis Thumb Joystick

2012-10-23T19:54:47Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Moravec
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

<pre style="color:red">
Yue
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 0 No git
Demo: 2
Total: 8
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|500px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

[[File:DOT MATRIX.JPG|500px]]

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

[[File:FROWN MATRIX.JPG|500px]] [[File:SMILE MATRIX.JPG|500px]]

We've reached our goal! Try to change the graphs and have fun!

The main codes are listed as below. And all the resources including the header files can be found on [https://github.com/Astroricks/Beagle-Project/tree/master/Miniproject02 Github:Astroricks].
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-23T19:54:00Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Moravec
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

<pre style="color:red">
Yue
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 0 No git
Demo: 2
Total: 8
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|500px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

[[File:DOT MATRIX.JPG|500px]]

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

[[File:FROWN MATRIX.JPG|500px]] [[File:SMILE MATRIX.JPG|500px]]

We've reached our goal! Try to change the graphs and have fun!

The main code are listed as below. And all the resources including the header files can be found on [https://github.com/Astroricks/Beagle-Project/tree/master/Miniproject02 Github:Astroricks].
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-17T23:26:19Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Moravec
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

<pre style="color:red">
Yue
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 0 No git
Demo: 2
Total: 8
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|500px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

[[File:DOT MATRIX.JPG|500px]]

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

[[File:FROWN MATRIX.JPG|500px]] [[File:SMILE MATRIX.JPG|500px]]

We've reached our goal! Try to change the graphs and have fun!

The main code are listed as below. And all the resources including the header files can be found [https://github.com/Astroricks/Beagle-Project/tree/master/Miniproject02 here].
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T06:27:33Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|500px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

[[File:DOT MATRIX.JPG|500px]]

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

[[File:FROWN MATRIX.JPG|500px]] [[File:SMILE MATRIX.JPG|500px]]

We've reached our goal! Try to change the graphs and have fun!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T06:26:06Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|500px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

[[File:DOT MATRIX.JPG]|500px]

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

[[File:FROWN MATRIX.JPG]|500px] [[File:SMILE MATRIX.JPG]|500px]

We've reached our goal! Try to change the graphs and have fun!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

File:SMILE MATRIX.JPG

2012-10-16T06:21:46Z

Astroricks: Smile face on the LED matrix.

Smile face on the LED matrix.

File:FROWN MATRIX.JPG

2012-10-16T06:18:03Z

Astroricks: Frown face on the LED matrix.

Frown face on the LED matrix.

File:DOT MATRIX.JPG

2012-10-16T06:14:08Z

Astroricks: A dot on the LED matrix.

A dot on the LED matrix.

Adafruit: 2-Axis Thumb Joystick

2012-10-16T06:11:13Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|600px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

We've reached our goal! Try to change the graphs and enjoy!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T05:56:36Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|400px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

We've reached our goal! Try to change the graphs and enjoy!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T05:56:17Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.

[[File:IMG wireup.JPG|400px]]

Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

We've reached our goal! Try to change the graphs and enjoy!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T05:55:41Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.
[[File:IMG wireup.JPG|200px]]
Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

We've reached our goal! Try to change the graphs and enjoy!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T05:54:24Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.
[[File:IMG wireup.JPG]]
Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

We've reached our goal! Try to change the graphs and enjoy!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T05:48:51Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.
[[File:IMG wireup.jpg]]
Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

We've reached our goal! Try to change the graphs and enjoy!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>

Adafruit: 2-Axis Thumb Joystick

2012-10-16T05:47:55Z

Astroricks: /* Control a 8x8 LED Matrix With The Joystick */

[[Category:ECE497]] [[Category:Adafruit]]

<pre style="color:red">
Overview: 2
Wiring: 2
Code: 2
git/Compiles with make: 2 gcc works
Demo: 2
Total: 10
Comments: Looks good.
</pre>

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kΩ pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

== Control a 8x8 LED Matrix With The Joystick ==

Now we have the joystick as an input, and we can do something interesting if there's an output part. This is a mini project about using the joysick to control a 8x8 LED matrix.

The details about the LED matrix can be found here: [https://www.adafruit.com/products/871 Mini 8x8 LED Matrix w/I2C - Yellow]
The LED matrix has an i2c port. Wire up the LED matrix to the Beagle Bone by attaching the Vdd to the 3.3V + bus, the GND to the - bus, SDA to SDA (pin 20), and SCLK to SCLK (pin 19). The joystick can be wired up as described above. Here is a picture of the hardware configuration.
[[File:IMG_wireup|thumb|Wire Up Picture]]
Our main goal is to create a bright dot on the LED matrix and use the joystick to move it.
<pre>
static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
pos = 0x80;

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}
</pre>
This is how we move the dot around: First, we create a bmp array whose first element is 0x80, which means only the dot on the right-down corner should be bright. 'analog_value_x' and 'analogy_value_y' are the two variables we set up to represent the voltage of x-axis and y-axis analog-in. 'pos' represents the position of the bright dot in the row. If 'analog_value_x' changes significantly and the bright dot does not reach the boundary of the 8x8 matrix, we should light up the dot next to it and turn off the dot itself.

<pre>
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
</pre>
For some reason the display is rotated one column, so after pre-unrotating the data, we can write the block data through the i2c bus. Thus, a dot can be lighten up on the matrix and can be moved as the way we want.

Next, we would like to make use of the button on the joystick. This is our objective: when pushing the button down, an interrupt is triggered and a frown face is presented on the LED matrix. Then if we move the dot across the face, it can be changed to a smile face.

According to the instructions on the joystick, the SEL shorts to ground when pressed. So the first important thing to do is to change gpio0_7 to pull-up mode. So that the interrupt can work correctly. Instructions about setting the interrupt can be found [http://elinux.org/EBC_Exercise_11_gpio_Polling_and_Interrupts here].

In the interrupt, we set the smile face as the 'hidden_bmp', the frown_face as the 'bright_bmp', and set up a 'trace_bmp' to record the LEDs that the dot has passed. The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
<pre>
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];
</pre>

We've reached our goal! Try to change the graphs and enjoy!

The main code are listed as below. And all the resources including the header files can be found here.
<pre>
/*****************************************************
Project Name: Joystick controlled 8x8 LED Matrix
Author: Yue Zhang
Date: 10/10/2012
*****************************************************/

#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <poll.h>
#include <signal.h> // Defines signal-handling functions (i.e. trap Ctrl-C)
#include "i2c-dev.h"
#include "i2cbusses.h"
#include "gpio.h"

/****************************************************************
* Constants
****************************************************************/

#define SYSFS_GPIO_DIR "/sys/class/gpio"
#define POLL_TIMEOUT (100) /* 0.1 seconds */
#define MAX_BUF 64

/****************************************************************
* Global variables
****************************************************************/
int keepgoing = 1; // Set to 0 when ctrl-c is pressed

/****************************************************************
* signal_handler
****************************************************************/
// Callback called when SIGINT is sent to the process (Ctrl-C)
void signal_handler(int sig)
{
printf( "Ctrl-C pressed, cleaning up and exiting..\n" );
keepgoing = 0;
}

/****************************************************************
* analog_in
****************************************************************/
int analog_in(char *ain)
{
FILE *fp;
char ainPath[MAX_BUF];
char ainVal[MAX_BUF];

snprintf(ainPath, sizeof ainPath, "/sys/devices/platform/omap/tsc/%s", ain);

if((fp = fopen(ainPath, "r")) == NULL){
printf("Can't open this pin, %s\n", ain);
return 1;
}

fgets(ainVal, MAX_BUF, fp);

fclose(fp);
return atoi(ainVal);
}

/****************************************************************
* Check
****************************************************************/
static void help(void) __attribute__ ((noreturn));

static void help(void)
{
fprintf(stderr, "Usage: my2cset (hardwired to bus 3, address 0x70)\n");
exit(1);
}

static int check_funcs(int file, int size)
{
unsigned long funcs;

/* check adapter functionality */
if (ioctl(file, I2C_FUNCS, &funcs) < 0) {
fprintf(stderr, "Error: Could not get the adapter "
"functionality matrix: %s\n", strerror(errno));
return -1;
}

switch (size) {
case I2C_SMBUS_BYTE:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus send byte");
return -1;
}
break;

case I2C_SMBUS_BYTE_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BYTE_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write byte");
return -1;
}
break;

case I2C_SMBUS_WORD_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_WORD_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus write word");
return -1;
}
break;

case I2C_SMBUS_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_BLOCK_DATA)) {
fprintf(stderr, MISSING_FUNC_FMT, "SMBus block write");
return -1;
}
break;
case I2C_SMBUS_I2C_BLOCK_DATA:
if (!(funcs & I2C_FUNC_SMBUS_WRITE_I2C_BLOCK)) {
fprintf(stderr, MISSING_FUNC_FMT, "I2C block write");
return -1;
}
break;
}

return 0;
}

/****************************************************************
* Main
****************************************************************/
int main(int argc, char *argv[])
{
struct pollfd fdset[1];
int nfds = 1;
int gpio_button_fd, ain_pin_x, ain_pin_y, timeout;
char *buf[MAX_BUF];
char ainx[MAX_BUF], ainy[MAX_BUF];
unsigned int gpio_button;
float analog_value_x = 0, analog_value_y = 0;
int res, i2cbus, address, size, file;
int value, daddress;
char filename[20];
int force = 0, readback = 1;
__u16 block[I2C_SMBUS_BLOCK_MAX], hidden_bmp[I2C_SMBUS_BLOCK_MAX], bright_bmp[I2C_SMBUS_BLOCK_MAX], trace_bmp[I2C_SMBUS_BLOCK_MAX];
int row = 0, pos = 0x80;
int i, n = 0;

static __u16 dot_bmp[] = {0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
static __u16 smile_bmp[] = {0x3C, 0x42, 0x95, 0xA1, 0xA1, 0x95, 0x42, 0x3C};
static __u16 frown_bmp[] = {0x3C, 0x42, 0xA5, 0x91, 0x91, 0xA5, 0x42, 0x3C};

// Set the signal callback for Ctrl-C
signal(SIGINT, signal_handler);

// Get the pin values
gpio_button = 7;
ain_pin_x = 6;
ain_pin_y = 4;

// Set gpio0_7 to be pullup
gpio_pullup();

// Set the gpio_button to be input and set its working pattern
gpio_export(gpio_button);
gpio_set_dir(gpio_button, 0);
gpio_set_edge(gpio_button, "falling"); // Can be rising, falling or both
gpio_button_fd = gpio_fd_open(gpio_button);

// Set up analog-in
snprintf(ainx, sizeof ainx, "ain%d", ain_pin_x);
snprintf(ainy, sizeof ainy, "ain%d", ain_pin_y);

// Set time out
timeout = POLL_TIMEOUT;

// Set up i2c
i2cbus = lookup_i2c_bus("3");
printf("i2cbus = %d\n", i2cbus);
if (i2cbus < 0)
help();

address = parse_i2c_address("0x70");
printf("address = 0x%2x\n", address);
if (address < 0)
help();

size = I2C_SMBUS_BYTE;

daddress = 0x21;
if (daddress < 0 || daddress > 0xff) {
fprintf(stderr, "Error: Data address invalid!\n");
help();
}

file = open_i2c_dev(i2cbus, filename, sizeof(filename), 0);
printf("file = %d\n", file);
if (file < 0
|| check_funcs(file, size)
|| set_slave_addr(file, address, force))
exit(1);

daddress = 0x21; // Start oscillator
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x81; // Display on, blinking off
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0xe7; // Full brightness
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

daddress = 0x00; // Start writing to address 0
printf("writing: 0x%02x\n", daddress);
res = i2c_smbus_write_byte(file, daddress);

while (keepgoing) {
memset((void*)fdset, 0, sizeof(fdset));

fdset[0].fd = gpio_button_fd;
fdset[0].events = POLLPRI;

analog_value_x = analog_in(ainx);
analog_value_y = analog_in(ainy);

poll(fdset, nfds, timeout);

if(analog_value_x >= 4000 && row < 7) {
row ++;
dot_bmp[row] = pos;
dot_bmp[row - 1] = 0x00;
}
if(analog_value_x <= 1000 && row > 0) {
row --;
dot_bmp[row] = pos;
dot_bmp[row + 1] = 0x00;
}
if(analog_value_y >= 4000 && pos < 0x80) {
pos = pos << 1;
dot_bmp[row] = pos;
}
if(analog_value_y <= 1000 && pos > 0x01) {
pos = pos >> 1;
dot_bmp[row] = pos;
}

// The LEDs we should light up is the LEDs in the bright_bmp that the dot hasn't passed, the LEDs in the hidden_bmp that the dot has already passed, and the dot itself.
trace_bmp[row] = trace_bmp[row] | dot_bmp[row];
for(i = 0; i < 8; i ++)
bright_bmp[i] = (bright_bmp[i] & ~trace_bmp[i]) | (hidden_bmp[i] & trace_bmp[i]) | dot_bmp[i];

// For some reason the display is rotated one column, so pre-unrotate the data.
for(i = 0; i < 8; i ++)
block[i] = (bright_bmp[i] & 0xfe) >>1 | (bright_bmp[i] & 0x01) << 7;

res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);

// Button interrupt
if (fdset[0].revents & POLLPRI) {
lseek(fdset[0].fd, 0, SEEK_SET); // Read from the start of the file
read(fdset[0].fd, buf, MAX_BUF);
switch(n){
case(0): // Initialize in the initial interrupt.
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = 0x00;
bright_bmp[i] = 0x00;
trace_bmp[i] = 0x00;
}
break;
default:
for(i = 0; i < 8; i ++)
block[i] = (frown_bmp[i]&0xfe) >>1 | (frown_bmp[i]&0x01) << 7;
res = i2c_smbus_write_i2c_block_data(file, daddress, 16, (__u8 *)block);
sleep(1);
for(i = 0; i < 8; i ++) {
hidden_bmp[i] = smile_bmp[i];
bright_bmp[i] = frown_bmp[i];
trace_bmp[i] = 0x00;
}
break;
}
n++;
}

fflush(stdout);
}

gpio_fd_close(gpio_button_fd);
return 0;

exit(0);
}
</pre>