eLinux.org - User contributions [en]

User:Jesionaj

2010-09-29T20:12:35Z

Jesionaj: Blanked the page

ECE597 Project Adding Sense to Beagle

2010-05-20T14:50:06Z

Jesionaj: Adding completed work

Sensory aware applications are becoming more mainstream with the release of the Apple iPhone. This project would combine both hardware and software to add sensory awareness to beagle. First, additional modules such as GPS, 3-axis accelerometers, gyroscopes, temperature sensors, humidity sensors, pressure sensors, etc, would be added to Beagle to compliment the microphone input in order to allow sensing of the real world environment. Then software APIs would need to be layered on top to allow easy access to the sensory data for use by applications.

This project focuses on utilizing the ADXL345 using the [http://www.sparkfun.com/commerce/product_info.php?products_id=9045 breakout board from SparkFun.]

== Milestones ==
• Read data from I2C line -- Complete 
• Call our library from another C program -- Complete 
• Create clear documentation -- In progress

== Timeline ==
Week 3: Get accelerometer 
Week 4: Hook up sensor to the I2C; See what Beagleboard does automatically with I2C. 
Week 5: Learn how ARM I2C C functions work; Start coding. 
Week 6: Finish coding. 
Week 7: Do documentation. 
Week 8: If we are on time, start working on another I2C sensor. 
Week 9/10: Padding time.

== Code ==
[http://pastebin.com/ktdbMFpa ADXL345.c] -- Code to interact with ADXL345. 
[http://pastebin.com/9bBb9RJV ADXL345.h] -- Header file. 
[http://pastebin.com/CyfSu0PU demo.c] -- Demonstration program, requires ncurses. Make sure to run it with colors enabled. 
In order to properly link to ncurses, the compilation command should similar to <tt>arm-angstrom-linux-gnueabi-gcc demo.c adxl345.c -lncurses -o adxldemo</tt>.

=== Detail of ADXL345.c ===

According to i2c-tools, SMBus read does not work on the BeagleBoard. For that reason we are using plain I2C commands by reading from and writing to the file handle of the i2c-2 bus. One useful aspect of ADXL345.c is it provides a set of helper functions for working with I2C. For instance, reading from a register requires writing the address of that register before being able to read it. These functions simplify transfers so you do not have to keep calling the read and write commands, but rather call read_byte and pass it the desired register and a pointer to an unsigned char to store the data. Additionally, writing masked data is useful if you only want to change certain bits of the register, and a function is provided for that as well. The only downside is these do not support multibyte commands. 
Interfacing with the ADXL345 is based on the specifications in the [http://www.analog.com/static/imported-files/data_sheets/ADXL345.pdf ADXL345 datasheet.]

=== Working with ADXL345.c ===

Data collection is started by calling measure_mode(), which puts the ADXL into a process of continuous conversion. Data can then be read from the device using get_data_x (or _y, _z) and passing a pointer to a float. The function will return 0 if not successful (I believe this is a break in Linux convention, my apologies) and 1 if successful, along with the value of the acceleration in that direction in g's placed in the float. 
 
Additional functions are provided for going into low power mode, standby mode, and setting the measured g range.

== Team Members ==
[[user:jiangq | Qiang Jiang]] 
[[User:Jesionaj | Adam Jesionowski]]

[[category:ECE597]]

BeagleBrick

2010-05-20T08:17:39Z

Jesionaj: Typo

The BeagleBrick is a handheld software defined radio integrating the [[BeagleBoard]] with Angstrom Linux, SoftRock 6.3 transceiver, and an LCD touchscreen into an all-in-one radio unit. It's goal is to be an easy to use "iPad for hams."

= Current Status =
The project is currently in a transitional period. This page will document our progress on interfacing with hardware using the BeagleBoard and Linux. More information can be found [http://www.rarcpio.net/beaglebrick/ here].

= Preparing the OS =

== SD Card Setup ==
First, follow the [[BeagleBoardBeginners#SD_card_setup]] guide in formatting your SD card.

Next, on the first partition, copy these files in '''this order'''.
# MLO
# u-boot
# [http://mumon.us/beaglebrick/uImage.beaglebrick uImage]

== Kernel Source ==
We are working on the best way to distribute this, possibly in patch form.

== Root File System ==
The ext2 partition on the SD card contains the file system for Linux, where all your regular programs and data reside. There are three options for getting this:

# Our complete filesystem with FLDigi and hamlib configured [http://mumon.us/beaglebrick/beaglebrick.rootfs.tgz is available here].
# You can also compile a distribution remotely from [http://www.angstrom-distribution.org/narcissus/ the Angstrom site]. This has FLDigi, but you will need to add the BeagleBrick's hamlib module.
# Finally, you can create the rootfs yourself, by following [[ECE597_Installing_The_%C3%85ngstr%C3%B6m_Distribution]] This is much more involved than the previous two methods.

== Hamlib ==
Information on creating a [http://www.hamlib.org hamlib] module is forthcoming.

[[Category:ECE597]]
[[Category:BeagleBoard]]

BeagleBrick

2010-05-20T08:15:58Z

Jesionaj: The BeagleBrick is a ham application using the BeagleBoard

The BeagleBrick is a handheld software defined radio integrating the [[BeagleBoard]] with Angstrom Linux, SoftRock 6.3 transceiver, and an LCD touchscreen into an all-in-one radio unit. It's goal is to be an easy to use "iPad for hams."

= Current Status =
The project is currently in a transitional period. This page will document our progress on interfacing with hardware using the BeagleBoard and Linux. More information can be found [http://www.rarcpio.net/beaglebrick/ here].

= Preparing the OS =

== SD Card Setup ==
First, follow the [[BeagleBoardBeginners#SD_card_setup]] guide in formatting your SD card.

Next, on the first partition, copy these files in '''this order'''.
# MLO
# u-boot
# [http://mumon.us/beaglebrick/uImage.beaglebrick uImage]

== Kernel Source ==
We are working on the best way to distribute this, possibly in patch form.

== Root File System ==
The ext2 partition on the SD card contains the file system for Linux, where all your regular programs and data reside. There are three options for getting this:

# Our complete filesystem with FLDigi and hamlib configured [http://mumon.us/beaglebrick/beaglebrick.rootfs.tgz is available here].
# You can also compile a distribution remotely from [http://www.angstrom-distribution.org/narcissus/ the Angstrom site]. This has FLDigi, but you will need to add the BeagleBrick's hamlib module.
# Finally, you can create the rootfs yourself, by following [[ECE597_Installing_The_%C3%85ngstr%C3%B6m_Distribution]] This is much more involved than the previous two methods.

== Hamlib ==
Information on creating a [www.hamlib.org/ hamlib] module is forthcoming.

[[Category:ECE597]]
[[Category:BeagleBoard]]

Interfacing with I2C Devices

2010-05-05T02:58:16Z

Jesionaj: Added i2ctools and a short bit on cross compilation (more as a reminder than anything else)

This page is meant to provide some basic information about how to interface with [http://en.wikipedia.org/wiki/I%C2%B2C I²C] devices through the /dev/i2c interface. The I²C bus is commonly used to connect relatively low-speed sensors and other peripherals to equipment varying in complexity from a simple microcontroller to a full-on motherboard. I²C is extremely popular due to its ease-of-use and ability to control multiple peripherals while utilizing only two pins on the host controller. Although I2C has a variety of modes, this page will deal purely with communication between a Linux-based master and a slave peripheral for the time being.

= Code Examples =

Note: Examples shown on this page were developed based on a Texas Instruments [[BeagleBoard]] and some changes ''will'' be required depending on the system being utilized.

== Beagleboard I2C2 Enable ==

The TI BeagleBoard has 3 I2C buses available, which control a variety of on-board peripherals, including the DVI display driver and power sequencing. As bus 2 is by far the easiest to connect to due to its presence on the 0.1" spaced expansion header, it is assumed the user will be controlling that bus for the purposes of this example. However, by default bus 2 is disabled due to a lack of pull-up resistors on the board, so external pull-ups to 1.8V must be added and the kernel recompiled to enable i2c2. It is important to remember that this bus runs at 1.8V on the Beagleboard and that external level shifters will be required to interface with 3.3V or 5V devices.

See [[BeagleBoard#Linux_kernel]] and [[BeagleBoardLinuxKernel]] for details on how to recompile your Linux kernel. To enable i2c2 specifically during that process, enable the setting during the "make menuconfig" step.

I2C2 is pinned out as pins 23 (SDA) and 24 (SCL) on the expansion header.

== i2c-tools ==
[http://www.lm-sensors.org/wiki/I2CTools i2c-tools] is a set of I2C programs that make it easy to debug I2C devices without having to write any code. For example, with the BeagleBoard:
<pre>
$i2cdetect -r 2
</pre>
Will send out read byte commands on the /dev/i2c-2 line to probe for addresses, and return any devices found. This is useful for checking what devices are functioning properly. (Note: the -r flag may interfere with write-only devices, but the default probing method does not work on the Beagle.) [http://www.lm-sensors.org/wiki/man/i2cget i2cget] and [http://www.lm-sensors.org/wiki/man/i2cset i2cset] write and read to devices respectively.

== Basic Communication with the [http://elinux.org/Interfacing_with_I%C2%B2C_Devices#Code_Examples AD7991] [http://en.wikipedia.org/wiki/Analog-to-digital_converter ADC] ==

The AD7991 has four inputs as well as the ability to use one of the input pins as a reference voltage the other inputs are measured against. If that input is not used as the reference voltage, it uses the supply voltage as the reference voltage. The power on default configuration uses all 4 channels as inputs, so in this case no further configuration is necessary. Because the AD7991 is 12-bit device, its outputs ranges linearly from 0 to 4096 as the voltage ranges from 0 to the reference voltage.

There are multiple ways to communicate with I2C devices, including the writing of a full kernel driver. This adds significant extra complexity, however, as basic bus control can be accomplished with the open, ioctl, read, and write commands.

=== Opening the Bus ===

In order to communicate with an I2C peripheral with this simple structure, you must first open the bus for reading and writing like you would any file. A call to [http://en.wikipedia.org/wiki/Open_(system_call) open] must be used rather than fopen so that writes to the bus are not buffered. Open returns a new file descriptor (a non-negative integer) which can then be used to configure the bus. A typical reason for failure at this stage is a lack of permissions to access /dev/i2c-2. Adding the user to a group which has permissions to access the file will alleviate this problem, as will adjusting the file permissions to enable user access. Adding a [http://xgoat.com/wp/2008/01/29/i2c-device-udev-rule/ udev rule to set the i2c device group] is the most permanent solution.

<pre>
int file;
char *filename = "/dev/i2c-2";
if ((file = open(filename, O_RDWR)) < 0) {
/* ERROR HANDLING: you can check errno to see what went wrong */
perror("Failed to open the i2c bus");
exit(1);
}
</pre>

=== Initiating communication with the AD7991 ===

After successfully acquiring bus access, you must initiate communication with whatever peripheral you are attempting to utilize. I2C does this by sending out the seven bit address of the device followed by a read/write bit. The bit is set to 0 for writes and 1 for reads. This is another common failure point, as manufacturers tend to report the I2C address of the peripheral in a variety of ways. Some report the address as a seven bit number, meaning that the address must be shifted left by a bit and then have the r/w bit tacked onto the end. Others will provide it as an eight bit number and assume you will set the last bit accordingly. Although a few manufacturers actually say which method they use to describe the address, the vast majority do not, and the user may have to resort to testing via trial and error.

The AD7991 used for this example is the AD7991-1, which has an address reported by the datasheet as 0101001. To use this properly, zero pad the address on the left and store it as 0b00101001. The calls to read and write after the ioctl will automatically set the proper read and write bit when signaling the peripheral.

<pre>
int addr = 0b00101001; // The I2C address of the ADC

if (ioctl(file,I2C_SLAVE,addr) < 0) {
printf("Failed to acquire bus access and/or talk to slave.\n");
/* ERROR HANDLING; you can check errno to see what went wrong */
exit(1);
}
</pre>

=== Reading from the ADC ===

The read system call is used to obtain data from the I2C peripheral. Read requires a file handle, a buffer to store the data, and a number of bytes to read. Read will attempt to read the number of bytes specified and will return the actual number of bytes read, which can be used to detect errors.

The code in the else block below calculates the voltage present at the ADC pin assuming a 5 volt reference/supply voltage. The AD7991 samples a 12 bit value, which is read back as two eight bit values. Rather than waste the empty bits, two of them are also used to signal the channel data being sent. See page 21 of the datasheet for more details.

<pre>
char buf[10] = {0};
float data;
char channel;

for(int i = 0; i<4; i++) {
// Using I2C Read
if (read(file,buf,2) != 2) {
/* ERROR HANDLING: i2c transaction failed */
printf("Failed to read from the i2c bus.\n");
buffer = g_strerror(errno);
printf(buffer);
printf("\n\n");
} else {
data = (float)((buf[0] & 0b00001111)<<8)+buf[1];
data = data/4096*5;
channel = ((buf[0] & 0b00110000)>>4);
printf("Channel %02d Data: %04f\n",channel,data);
}
}
</pre>

=== Writing to the ADC ===

The write system call is used to obtain data from the I2C peripheral. Write requires a file handle, a buffer in which the data is stored, and a number of bytes to write. Write will attempt to write the number of bytes specified and will return the actual number of bytes written, which can be used to detect errors.

Some devices require an internal address to be sent prior to the data to specify the register on the external device to access. The AD7991 contains only one configuration register, and as such, does not require a internal register selection address to be sent to the device. For devices with more than one configuration register, the address of the register should be written first, followed by the data to be placed there. See the datasheet specific to the part for more details.

<pre>
//unsigned char reg = 0x10; // Device register to access
//buf[0] = reg;

buf[0] = 0b11110000;
if (write(file,buf,1) != 1) {
/* ERROR HANDLING: i2c transaction failed */
printf("Failed to write to the i2c bus.\n");
buffer = g_strerror(errno);
printf(buffer);
printf("\n\n");
}
</pre>

=== Detecting Errors ===

Errors on the I2C bus range from incorrect permissions and addressing to hardware errors that may simply not allow peripherals to respond. The errno interface is used to identify these errors using the glib function g_strerror. For simple usage, calling the function as above will work. See the glib api for more details.

=== Completed Code ===

<pre>
#include <glib.h>
#include <glib/gprintf.h>
#include <errno.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <linux/i2c-dev.h>
#include <sys/ioctl.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>

void
sensors_ADC_init(void) {
int file;
char filename[40];
const gchar *buffer;
int addr = 0b00101001; // The I2C address of the ADC

sprintf(filename,"/dev/i2c-2");
if ((file = open(filename,O_RDWR)) < 0) {
printf("Failed to open the bus.");
/* ERROR HANDLING; you can check errno to see what went wrong */
exit(1);
}

if (ioctl(file,I2C_SLAVE,addr) < 0) {
printf("Failed to acquire bus access and/or talk to slave.\n");
/* ERROR HANDLING; you can check errno to see what went wrong */
exit(1);
}

char buf[10] = {0};
float data;
char channel;

for(int i = 0; i<4; i++) {
// Using I2C Read
if (read(file,buf,2) != 2) {
/* ERROR HANDLING: i2c transaction failed */
printf("Failed to read from the i2c bus.\n");
buffer = g_strerror(errno);
printf(buffer);
printf("\n\n");
} else {
data = (float)((buf[0] & 0b00001111)<<8)+buf[1];
data = data/4096*5;
channel = ((buf[0] & 0b00110000)>>4);
printf("Channel %02d Data: %04f\n",channel,data);
}
}

//unsigned char reg = 0x10; // Device register to access
//buf[0] = reg;

buf[0] = 0b11110000;
if (write(file,buf,1) != 1) {
/* ERROR HANDLING: i2c transaction failed */
printf("Failed to write to the i2c bus.\n");
buffer = g_strerror(errno);
printf(buffer);
printf("\n\n");
}
}
</pre>

=== Cross Compilation ===

In order to compile the code and create a binary that can be run on the embedded system, you will need a cross compiler (e.g. [[ARMCompilers]]) on the host computer and added to the PATH.

For example, using the CodeSourcery ARM toolchain:
<pre>
$gcc CROSS-COMPILE=arm-none-linux-gnueabi ARCH=arm i2c_interface.c -o i2c_binary
</pre>
The resulting binary can then be moved to the embedded device and executed.

= Tested Devices =

* [http://www.analog.com/en/analog-to-digital-converters/ad-converters/ad7991/products/product.html AD7991 Quad Input ADC]
** Utilized with [http://www.acroname.com/robotics/parts/SharpGP2D12-15.pdf Sharp GP2D12 IR Range Sensors]
* [http://www.robot-electronics.co.uk/htm/srf08tech.shtml SRF08 Ultrasonic Range Sensors]
* [http://www.analog.com/static/imported-files/data_sheets/ADXL345.pdf ADXL345 3-axis Accelerometer]

= External Links =

* [http://en.wikipedia.org/wiki/I%C2%B2C Wikipedia I²C Page]
* [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/i2c/dev-interface Linux Kernel I2C Documentation]
* [http://linux.die.net/man/2/syscalls Standard Linux Syscalls]

[[Category:Robotics]]
[[Category:BeagleBoard]]
[[Category:ECE597]]

ECE597 Installing DSP Development Tools

2010-04-27T18:15:21Z

Jesionaj: Added creation of authorized_keys folder

[[Category:ECE597]]
[[Category:BeagleBoard]]

= Installing Software for the DSP =
Although TI's [http://wiki.davincidsp.com/index.php/GSG:_OMAP35x_DVEVM_Software_Setup GSG: OMAP35x DVEVM Software Setup] is targeting a different board (DVEVM, Digital Video EValuation Module) it looks like a good set of instructions for getting the Beagle set up for using the DSP. I've copied it locally so we can update it for the BeagleBoard ([[ECE597 BeagleBoard DSP Software Setup]]).

Follow the instructions at [[ECE597 BeagleBoard DSP Software Setup]] to install the Beagle DSP software. If you get stuck, look at the '''Old''' instructions below. These are the instructions I wrote before TI updated their site. They might help.

Once everything is installed, do the '''Authorizing ssh''' below. It will make developing software easier.

== Authorizing ssh ==

We'll be using '''ssh''' and '''sftp''' to move files to the Beagle and run them there. '''Makefile''' will be setup to automatically sftp files to the Beagle when <code>make install</code> is run. For this to work you need to set up authorization so you don't have to enter your password when using these commands. Here's how to do it:

* On your host computer run
<pre>
host $ ssh-keygen
host $ cd ~/.ssh
host $ sftp Beagle
put id_rsa.pub
exit
host $ ssh Beagle
</pre>
The first command creates an authorization key and places it in your .ssh directory. Remember the pass phrase you enter here. You'll use it below. The next two commands copy that key to your Beagle. The last command connects to your Beagle.
* On your Beagle run
<pre>
beagle $ mkdir ~/.ssh/authorized_keys
beagle $ cd ~/.ssh
beagle $ mv ../id_rsa.pub .
beagle $ cp id_rsa.pub authorized_keys
beagle $ exit
</pre>
Here we create a '''.ssh''' directory and copy the public key into it. The authorized_keys folder contains a list of all the machines that are authorized to connect to your Beagle without a password.
* Back on the host computer:
<pre>
host $ ssh Beagle
</pre>
This time you should see a window pop up. Enter your pass phrase from above. You should be logged into your Beagle. Log out and log in again. This time you should get access without having to enter your pass phrase.

[http://kimmo.suominen.com/docs/ssh/ Here] is move information on ssh authorization.

= Old =

Here's what you need to do to program the DSP side of the BeagleBoard. The first part is getting things installed. The second is moving things around and setting up ssh show you don't have to enter your password every time.

== Installing ==

To save download time I've put these files on the class SharePoint site. Look in the '''Shared Documents''' folder in '''Downloads'''.

=== Install OMAP35x SDK ===

First install the OMAP35x Software Developers Kit. Do this by:
* Go to [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html here]
* Click on [[File:Get_Software.png]]
* Scroll near the bottom to '''Linux Platform Support Package [PSP]'''. Below it you will see a link to '''OMAP35x-PSP-SDK-setuplinux-02.01.03.11.bin'''. Click and download it.
* Change to your download directory <code>cd ~/Downloads</code>.
* Make the downloaded file executable, <code>chmod +x OMAP35x-PSP-SDK-setuplinux-02.01.03.11.bin</code>
* Run it, <code>./OMAP35x-PSP-SDK-setuplinux-02.01.03.11.bin</code>.
[[File:OMAP35x_SDK_Install.png|300px]]
* Click '''Yes'''
[[File:OMAP35x_Setup.png|300px]]
* Click '''Next >'''
* Accept the terms.
[[File:OMAP35c_Location.png|300px]]
* Use the default location
* The install takes around 5 minutes. Continue clicking until it's installed.

=== Install Digital Video Software Development Kit [DVSDK] ===

The next step is the install the DVSDK.

* Go back to [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest/index_FDS.html here] and scroll down to '''Digital Video Software Development Kit [DVSDK]'''. Click on '''dvsdk_setuplinux_3_00_02_44.bin''' to download.
* Change to your download directory <code>cd ~/Downloads</code>.
* Make the downloaded file executable, <code>chmod 755 dvsdk_setuplinux_3_00_02_44.bin</code>
* Run it, <code>./dvsdk_setuplinux_3_00_02_44.bin</code>.
[[File:OMAP3530_DV_Install.png|300px]]
* Click '''Yes'''
[[File:OMAP3530_DV_Setup.png|300px]]
* Click '''Next >'''
* Accept the agreement.
[[File:OMAP3530_DV_Location.png|300px]]
* Keeping clicking until it's installed.

=== Install DVSDK Dependencies ===

The next step is the install the DVSDK Dependencies.

* Go back to [http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest/index_FDS.html here] and scroll down to '''DVSDK Dependencies'''. Click on '''xdctools_setuplinux_3_15_01_59.bin''' to download.
* Also download '''bios_setuplinux_5_33_06.bin''' and '''TI-C6x-CGT-v6.0.16.1.bin'''
* Change to your download directory <code>cd ~/Downloads</code>.
* Make the downloaded file executable, <code>chmod 755 xdctools_setuplinux_3_15_01_59.bin</code>
* Run it, <code>./xdctools_setuplinux_3_15_01_59.bin</code>.
* Pick you language (sorry, no Chinese)
[[File:XDCtools_Install.png|300px]]
* Click '''Yes'''
[[File:XDCtools_Setup.png|300px]]
* Click '''Next >'''
* Accept the agreement.
[[File:XDCtools_Location.png|300px]]
* Keeping clicking until it's installed. This will take longer than the previous installs.

* Repeat this process for '''bios_setuplinux_5_33_06.bin'''
[[File:DSP_BIOS_Setup.png|300px]]

* Again repeat for '''TI-C6x-CGT-v6.0.16.1.bin'''
[[File:C6x_Setup.png|300px]]
* Set the install path to '''/home/user/dvsdk_3_00_02_44/cg6x_6_0_16''' where '''user''' is your username.

=== Install the CodeSourcery Compiler ===

[http://www.elinux.org/ARMCompilers TI recommends] the 2009q1-203 version of the [http://www.codesourcery.com CodeSourcery] compiler.

* Get it [http://www.codesourcery.com/sgpp/lite/arm/portal/release858 here]
* Click on '''IA32 GNU/Linux Installer''' to download it
* Install as before
* After a while this will appear
[[File:Sourcery_Install.png|300px]]
* Click through, selecting '''Typical''' install
* Use the default install location
[[File:Sourcery_Path.png|300px]]
* Take the default shortcuts
* Click '''Install''' and wait awhile

Some addition useful information at be found here: [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Linux Digital Video Software Development Kit (DVSDK) for OMAP35x Processors]

== Post install setup ==

=== Move some things around ===

The TI workshop material that we are using have these files in slightly different locations. Let's move our files to match theirs.
<pre>
$ cd
$ mv bios_5_33_06/ dvsdk_3_00_02_44
$ mv xdctools_3_15_01_59/ dvsdk_3_00_02_44
$ mv OMAP35x-PSP-SDK-02.01.03.11 dvsdk_3_00_02_44
$ cd dvsdk_3_00_02_44
$ mv OMAP35x-PSP-SDK-02.01.03.11 PSP_02_01_03_11
</pre>

User:Jesionaj/Listings

2010-04-24T23:16:55Z

Jesionaj:

Listing 2-6
<pre>
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2009.11-rc1 (Jan 08 2010 - 21:19:52)

OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Board revision C1/C2/C3
Die ID #5ac400030000000004013f8901001001
Hit any key to stop autoboot: 0
OMAP3 beagleboard.org #
</pre>
Listing 4-3
<pre>
adam@melchoir linux-2.6.33.y]$ ls -l arch/arm/mach-omap2/
total 1.7M
-rw-r--r-- 1 adam users 5.1K Mar 12 00:59 board-2430sdp.c
-rw-r--r-- 1 adam users 17K Mar 12 00:59 board-3430sdp.c
-rwxr-xr-x 1 adam users 2.6K Mar 12 00:59 board-3630sdp.c
-rw-r--r-- 1 adam users 2.5K Mar 12 00:59 board-4430sdp.c
-rw-r--r-- 1 adam users 2.4K Mar 12 00:59 board-am3517evm.c
-rw-r--r-- 1 adam users 8.5K Mar 12 00:59 board-apollon.c
-rw-r--r-- 1 adam users 17K Mar 12 00:59 board-cm-t35.c
-rw-r--r-- 1 adam users 1.8K Mar 12 00:59 board-generic.c
-rw-r--r-- 1 adam users 9.2K Mar 12 00:59 board-h4.c
-rw-r--r-- 1 adam users 6.5K Mar 12 00:59 board-igep0020.c
-rw-r--r-- 1 adam users 9.1K Mar 12 00:59 board-ldp.c
-rw-r--r-- 1 adam users 3.4K Mar 12 00:59 board-n8x0.c
-rw-r--r-- 1 adam users 12K Mar 12 00:59 board-omap3beagle.c
-rw-r--r-- 1 adam users 12K Mar 12 00:59 board-omap3evm.c
-rw-r--r-- 1 adam users 11K Mar 12 00:59 board-omap3pandora.c
-rw-r--r-- 1 adam users 14K Mar 12 00:59 board-omap3touchbook.c
-rw-r--r-- 1 adam users 13K Mar 12 00:59 board-overo.c
-rw-r--r-- 1 adam users 2.6K Mar 12 00:59 board-rx51.c
-rw-r--r-- 1 adam users 19K Mar 12 00:59 board-rx51-peripherals.c
-rw-r--r-- 1 adam users 4.8K Mar 12 00:59 board-rx51-sdram.c
-rw-r--r-- 1 adam users 2.3K Mar 12 00:59 board-zoom2.c
-rw-r--r-- 1 adam users 1.6K Mar 12 00:59 board-zoom3.c
-rw-r--r-- 1 adam users 3.8K Mar 12 00:59 board-zoom-debugboard.c
-rwxr-xr-x 1 adam users 6.5K Mar 12 00:59 board-zoom-peripherals.c
-rw-r--r-- 1 adam users 16K Mar 12 00:59 clock2xxx.c
-rw-r--r-- 1 adam users 70K Mar 12 00:59 clock2xxx_data.c
-rw-r--r-- 1 adam users 1.5K Mar 12 00:59 clock2xxx.h
-rw-r--r-- 1 adam users 9.6K Mar 12 00:59 clock34xx.c
-rw-r--r-- 1 adam users 97K Mar 12 00:59 clock34xx_data.c
-rw-r--r-- 1 adam users 741 Mar 12 00:59 clock34xx.h
-rw-r--r-- 1 adam users 849 Mar 12 00:59 clock44xx.c
-rw-r--r-- 1 adam users 82K Mar 12 00:59 clock44xx_data.c
-rw-r--r-- 1 adam users 321 Mar 12 00:59 clock44xx.h
-rw-r--r-- 1 adam users 30K Mar 12 00:59 clock.c
-rw-r--r-- 1 adam users 1.2K Mar 12 00:59 clock_common_data.c
-rw-r--r-- 1 adam users 17K Mar 12 00:59 clockdomain.c
-rw-r--r-- 1 adam users 8.9K Mar 12 00:59 clockdomains.h
-rw-r--r-- 1 adam users 3.9K Mar 12 00:59 clock.h
-rw-r--r-- 1 adam users 29K Mar 12 00:59 cm44xx.h
-rw-r--r-- 1 adam users 1.4K Mar 12 00:59 cm4xxx.c
-rw-r--r-- 1 adam users 1.7K Mar 12 00:59 cm.c
-rw-r--r-- 1 adam users 4.3K Mar 12 00:59 cm.h
-rw-r--r-- 1 adam users 14K Mar 12 00:59 cm-regbits-24xx.h
-rw-r--r-- 1 adam users 26K Mar 12 00:59 cm-regbits-34xx.h
-rw-r--r-- 1 adam users 61K Mar 12 00:59 cm-regbits-44xx.h
-rw-r--r-- 1 adam users 15K Mar 12 00:59 control.c
-rw-r--r-- 1 adam users 9.6K Mar 12 00:59 cpuidle34xx.c
-rw-r--r-- 1 adam users 18K Mar 12 00:59 devices.c
-rw-r--r-- 1 adam users 14K Mar 12 00:59 dpll.c
-rw-r--r-- 1 adam users 1.5K Mar 12 00:59 emu.c
-rw-r--r-- 1 adam users 15K Mar 12 00:59 gpmc.c
-rw-r--r-- 1 adam users 9.2K Mar 12 00:59 gpmc-onenand.c
-rw-r--r-- 1 adam users 5.0K Mar 12 00:59 gpmc-smc91x.c
-rw-r--r-- 1 adam users 1.7K Mar 12 00:59 i2c.c
-rw-r--r-- 1 adam users 11K Mar 12 00:59 id.c
drwxr-xr-x 3 adam users 4.0K Mar 12 00:59 include/
-rw-r--r-- 1 adam users 7.7K Mar 12 00:59 io.c
-rw-r--r-- 1 adam users 7.8K Mar 12 00:59 iommu2.c
-rw-r--r-- 1 adam users 7.4K Mar 12 00:59 irq.c
-rw-r--r-- 1 adam users 3.9K Mar 12 00:59 Kconfig
</pre>

With [[User:Jiangq]]
== Chapter 4 ==

{|
! Number
! Page
! Caption
! Listing
|-
| 4-3
| 4-15
| Kernel Subdirectory
| <pre> qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 4_3
qiang@qiang-laptop:~/Desktop/linux-2.6$ ls -ls arch/arm/plat-omap/ | grep -v \\.o
total 432
12 -rw-r--r-- 1 qiang qiang 11124 2010-03-23 20:06 clock.c
12 -rw-r--r-- 1 qiang qiang 8521 2010-03-23 20:06 common.c
4 -rw-r--r-- 1 qiang qiang 4033 2010-03-23 20:06 cpu-omap.c
4 -rw-r--r-- 1 qiang qiang 2192 2010-03-23 20:06 debug-devices.c
8 -rw-r--r-- 1 qiang qiang 7170 2010-03-23 20:06 debug-leds.c
12 -rw-r--r-- 1 qiang qiang 10890 2010-03-23 20:06 devices.c
56 -rw-r--r-- 1 qiang qiang 52586 2010-03-23 20:06 dma.c
24 -rw-r--r-- 1 qiang qiang 22660 2010-03-23 20:06 dmtimer.c
12 -rw-r--r-- 1 qiang qiang 10055 2010-03-23 20:06 fb.c
64 -rw-r--r-- 1 qiang qiang 61308 2010-03-23 20:06 gpio.c
8 -rw-r--r-- 1 qiang qiang 5058 2010-03-23 20:06 i2c.c
4 drwxr-xr-x 3 qiang qiang 4096 2010-03-23 20:06 include
8 -rw-r--r-- 1 qiang qiang 6265 2010-03-23 20:06 io.c
24 -rw-r--r-- 1 qiang qiang 20765 2010-03-23 20:06 iommu.c
12 -rw-r--r-- 1 qiang qiang 9117 2010-03-23 20:06 iommu-debug.c
4 -rw-r--r-- 1 qiang qiang 2745 2010-03-23 20:06 iopgtable.h
20 -rw-r--r-- 1 qiang qiang 19320 2010-03-23 20:06 iovmm.c
8 -rw-r--r-- 1 qiang qiang 4819 2010-03-23 20:06 Kconfig
12 -rw-r--r-- 1 qiang qiang 8522 2010-03-23 20:06 mailbox.c
4 -rw-r--r-- 1 qiang qiang 882 2010-03-23 20:06 Makefile
44 -rw-r--r-- 1 qiang qiang 43730 2010-03-23 20:06 mcbsp.c
4 -rw-r--r-- 1 qiang qiang 2263 2010-03-23 20:06 mux.c
4 -rw-r--r-- 1 qiang qiang 2739 2010-03-23 20:06 ocpi.c
24 -rw-r--r-- 1 qiang qiang 21397 2010-03-23 20:06 omap_device.c
8 -rw-r--r-- 1 qiang qiang 7069 2010-03-23 20:06 omap-pm-noop.c
16 -rw-r--r-- 1 qiang qiang 12878 2010-03-23 20:06 sram.c
20 -rw-r--r-- 1 qiang qiang 18770 2010-03-23 20:06 usb.c

</pre>
|-
| 4-4
| 4-17
| Snippet from Linux 2.6.config
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 4_4
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y

</pre>

|-
| 4-6
| 4-22
| Makefile Targets
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 4_6
qiang@qiang-laptop:~/Desktop/linux-2.6$ make help
Cleaning targets:
clean - Remove most generated files but keep the config and
enough build support to build external modules
mrproper - Remove all generated files + config + various backup files
distclean - mrproper + remove editor backup and patch files

Configuration targets:
config - Update current config utilising a line-oriented program
menuconfig - Update current config utilising a menu based program
xconfig - Update current config utilising a QT based front-end
gconfig - Update current config utilising a GTK based front-end
oldconfig - Update current config utilising a provided .config as base
localmodconfig - Update current config disabling modules not loaded
localyesconfig - Update current config converting local mods to core
silentoldconfig - Same as oldconfig, but quietly, additionally update deps
randconfig - New config with random answer to all options
defconfig - New config with default answer to all options
allmodconfig - New config selecting modules when possible
allyesconfig - New config where all options are accepted with yes
allnoconfig - New config where all options are answered with no

Other generic targets:
all - Build all targets marked with [*]
* vmlinux - Build the bare kernel
* modules - Build all modules
modules_install - Install all modules to INSTALL_MOD_PATH (default: /)
firmware_install- Install all firmware to INSTALL_FW_PATH
(default: $(INSTALL_MOD_PATH)/lib/firmware)
dir/ - Build all files in dir and below
dir/file.[ois] - Build specified target only
dir/file.ko - Build module including final link
modules_prepare - Set up for building external modules
tags/TAGS - Generate tags file for editors
cscope - Generate cscope index
kernelrelease - Output the release version string
kernelversion - Output the version stored in Makefile
headers_install - Install sanitised kernel headers to INSTALL_HDR_PATH
(default: /home/qiang/Desktop/linux-2.6/usr)

Static analysers
checkstack - Generate a list of stack hogs
namespacecheck - Name space analysis on compiled kernel
versioncheck - Sanity check on version.h usage
includecheck - Check for duplicate included header files
export_report - List the usages of all exported symbols
headers_check - Sanity check on exported headers
headerdep - Detect inclusion cycles in headers

Kernel packaging:
rpm-pkg - Build both source and binary RPM kernel packages
binrpm-pkg - Build only the binary kernel package
deb-pkg - Build the kernel as an deb package
tar-pkg - Build the kernel as an uncompressed tarball
targz-pkg - Build the kernel as a gzip compressed tarball
tarbz2-pkg - Build the kernel as a bzip2 compressed tarball

Documentation targets:
Linux kernel internal documentation in different formats:
htmldocs - HTML
pdfdocs - PDF
psdocs - Postscript
xmldocs - XML DocBook
mandocs - man pages
installmandocs - install man pages generated by mandocs
cleandocs - clean all generated DocBook files

Architecture specific targets (x86):
* bzImage - Compressed kernel image (arch/x86/boot/bzImage)
install - Install kernel using
(your) ~/bin/installkernel or
(distribution) /sbin/installkernel or
install to $(INSTALL_PATH) and run lilo
fdimage - Create 1.4MB boot floppy image (arch/x86/boot/fdimage)
fdimage144 - Create 1.4MB boot floppy image (arch/x86/boot/fdimage)
fdimage288 - Create 2.8MB boot floppy image (arch/x86/boot/fdimage)
isoimage - Create a boot CD-ROM image (arch/x86/boot/image.iso)
bzdisk/fdimage*/isoimage also accept:
FDARGS="..." arguments for the booted kernel
FDINITRD=file initrd for the booted kernel

i386_defconfig - Build for i386
x86_64_defconfig - Build for x86_64

make V=0|1 [targets] 0 => quiet build (default), 1 => verbose build
make V=2 [targets] 2 => give reason for rebuild of target
make O=dir [targets] Locate all output files in "dir", including .config
make C=1 [targets] Check all c source with $CHECK (sparse by default)
make C=2 [targets] Force check of all c source with $CHECK

Execute "make" or "make all" to build all targets marked with [*]
For further info see the ./README file

</pre>

|-
| 4-10
| 4-32
| Customized .config File Snippet
| <pre>qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 4_10
# CONFIG_ARCH_PNX4008 is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_MSM is not set
# CONFIG_ARCH_SHMOBILE is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C2410 is not set
# CONFIG_ARCH_S3C64XX is not set
# CONFIG_ARCH_S5P6440 is not set
# CONFIG_ARCH_S5P6442 is not set
# CONFIG_ARCH_S5PC1XX is not set
# CONFIG_ARCH_S5PV210 is not set
# CONFIG_ARCH_SHARK is not set
# CONFIG_ARCH_LH7A40X is not set
# CONFIG_ARCH_U300 is not set
# CONFIG_ARCH_U8500 is not set
# CONFIG_ARCH_NOMADIK is not set
# CONFIG_ARCH_DAVINCI is not set
CONFIG_ARCH_OMAP=y

#
# TI OMAP Implementations
#
# CONFIG_ARCH_OMAP1 is not set
CONFIG_ARCH_OMAP2PLUS=y
# CONFIG_ARCH_OMAP2 is not set
# CONFIG_ARCH_OMAP3 is not set
# CONFIG_ARCH_OMAP4 is not set
</pre>

|-
| 4-11
| 4-33
| Makefile from .../arch/arm/mach-ixp4xx Kernel Subdirectory
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 4_11
qiang@qiang-laptop:~/Desktop/linux-2.6/arch/arm/plat-omap$ head -n 20 Makefile
#
# Makefile for the linux kernel.
#

# Common support
obj-y := common.o sram.o clock.o devices.o dma.o mux.o gpio.o \
usb.o fb.o io.o
obj-m :=
obj-n :=
obj- :=

# OCPI interconnect support for 1710, 1610 and 5912
obj-$(CONFIG_ARCH_OMAP16XX) += ocpi.o

# omap_device support (OMAP2+ only at the moment)
obj-$(CONFIG_ARCH_OMAP2) += omap_device.o
obj-$(CONFIG_ARCH_OMAP3) += omap_device.o

obj-$(CONFIG_OMAP_MCBSP) += mcbsp.o
obj-$(CONFIG_OMAP_IOMMU) += iommu.o iovmm.o
</pre>
|}

== Chapter 5 ==
{|
! Number
! Page
! Caption
! Listing
|-
| 5-2
| 5-5
| Assembly File piggy.s
| <pre> qiang@qiang-laptop:~/Desktop/linux-2.6/arch/arm/boot/compressed$ cat piggy.gzip.S
.section .piggydata,#alloc
.globl input_data
input_data:
.incbin "arch/arm/boot/compressed/piggy.gzip"
.globl input_data_end
input_data_end:

</pre>
|-
| 5-4
| 5-18
| Console Setup Code Snippet
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6/arch/arm/boot/compressed$ cat piggy.gzip.S
.section .piggydata,#alloc
.globl input_data
input_data:
.incbin "arch/arm/boot/compressed/piggy.gzip"
.globl input_data_end
input_data_end:

qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_4
/*
* Set up a list of consoles. Called from init/main.c
*/
static int __init console_setup(char *str)
{
char buf[sizeof(console_cmdline[0].name) + 4]; /* 4 for index */
char *s, *options, *brl_options = NULL;
int idx;

#ifdef CONFIG_A11Y_BRAILLE_CONSOLE
if (!memcmp(str, "brl,", 4)) {
brl_options = "";
str += 4;
} else if (!memcmp(str, "brl=", 4)) {
brl_options = str + 4;
str = strchr(brl_options, ',');
if (!str) {
printk(KERN_ERR "need port name after brl=\n");
return 1;
}
*(str++) = 0;

</pre>

|-
| 5-5
| 5-19
| Family of _setup Macro Definitions from init.h
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_5
/*
* Only for really core code. See moduleparam.h for the normal way.
*
* Force the alignment so the compiler doesn't space elements of the
* obs_kernel_param "array" too far apart in .init.setup.
*/
#define __setup_param(str, unique_id, fn, early) \
static const char __setup_str_##unique_id[] __initconst \
__aligned(1) = str; \
static struct obs_kernel_param __setup_##unique_id \
__used __section(.init.setup) \
__attribute__((aligned((sizeof(long))))) \
= { __setup_str_##unique_id, fn, early }

#define __setup(str, fn) \
__setup_param(str, fn, fn, 0)

</pre>

|-
| 5-6
| 5-20
| Kernel Command Line Processing
| <pre>qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_6
static int __init obsolete_checksetup(char *line)
{
struct obs_kernel_param *p;
int had_early_param = 0;

p = __setup_start;
do {
int n = strlen(p->str);
if (!strncmp(line, p->str, n)) {
if (p->early) {
/* Already done in parse_early_param?
* (Needs exact match on param part).
* Keep iterating, as we can have early
* params and __setups of same names 8( */
if (line[n] == '\0' || line[n] == '=')
had_early_param = 1;
} else if (!p->setup_func) {
printk(KERN_WARNING "Parameter %s is obsolete,"
" ignored\n", p->str);
return 1;
} else if (p->setup_func(line + n))
return 1;
}
p++;
} while (p < __setup_end);

return had_early_param;
}

</pre>

|-
| 5-7
| 5-23
| Example Initialization Routine
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_7
static void (*init_machine)(void) __initdata;

static int __init customize_machine(void)
{
/* customizes platform devices, or adds new ones */
if (init_machine)
init_machine();
return 0;
}
</pre>
|-
| 5-8
| 5-23
| initcall Family of Macros
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_8
#define __define_initcall(level,fn,id) \
static initcall_t __initcall_##fn##id __used \
__attribute__((__section__(".initcall" level ".init"))) = fn

/*
* Early initcalls run before initializing SMP.
*
* Only for built-in code, not modules.
*/
#define early_initcall(fn) __define_initcall("early",fn,early)

/*
* A "pure" initcall has no dependencies on anything else, and purely
* initializes variables that couldn't be statically initialized.
*
* This only exists for built-in code, not for modules.
*/
#define pure_initcall(fn) __define_initcall("0",fn,0)

#define core_initcall(fn) __define_initcall("1",fn,1)
#define core_initcall_sync(fn) __define_initcall("1s",fn,1s)
#define postcore_initcall(fn) __define_initcall("2",fn,2)
#define postcore_initcall_sync(fn) __define_initcall("2s",fn,2s)
#define arch_initcall(fn) __define_initcall("3",fn,3)
#define arch_initcall_sync(fn) __define_initcall("3s",fn,3s)
#define subsys_initcall(fn) __define_initcall("4",fn,4)
#define subsys_initcall_sync(fn) __define_initcall("4s",fn,4s)
</pre>
|-
| 5-9
| 5-26
| Creation of Kernel init Thread
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_9
static noinline void __init_refok rest_init(void)
__releases(kernel_lock)
{
int pid;

rcu_scheduler_starting();
kernel_thread(kernel_init, NULL, CLONE_FS | CLONE_SIGHAND);
numa_default_policy();
pid = kernel_thread(kthreadd, NULL, CLONE_FS | CLONE_FILES);
rcu_read_lock();
kthreadd_task = find_task_by_pid_ns(pid, &init_pid_ns);
rcu_read_unlock();
unlock_kernel();

/*
* The boot idle thread must execute schedule()
* at least once to get things moving:
*/
init_idle_bootup_task(current);
preempt_enable_no_resched();
schedule();
preempt_disable();

/* Call into cpu_idle with preempt disabled */
cpu_idle();
}

</pre>
|-
| 5-10
| 5-27
| Initialization via initcalls
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_10
extern initcall_t __initcall_start[], __initcall_end[], __early_initcall_end[];

static void __init do_initcalls(void)
{
initcall_t *fn;

for (fn = __early_initcall_end; fn < __initcall_end; fn++)
do_one_initcall(*fn);

/* Make sure there is no pending stuff from the initcall sequence */
flush_scheduled_work();
}
</pre>
|-
| 5-11
| 5-28
| Final Kernel Boot Steps from main.c
| <pre>
qiang@qiang-laptop:~/Desktop/linux-2.6$ cat 5_11
* makes it inline to init() and it becomes part of init.text section
*/
static noinline int init_post(void)
__releases(kernel_lock)
{
/* need to finish all async __init code before freeing the memory */
async_synchronize_full();
free_initmem();
unlock_kernel();
mark_rodata_ro();
system_state = SYSTEM_RUNNING;
numa_default_policy();

current->signal->flags |= SIGNAL_UNKILLABLE;

if (ramdisk_execute_command) {
run_init_process(ramdisk_execute_command);
printk(KERN_WARNING "Failed to execute %s\n",
ramdisk_execute_command);

</pre>
|}

[[Category:ECE597]]

ECE597 Project Adding Sense to Beagle

2010-03-25T02:11:00Z

Jesionaj: /* Timeline */

== Description of Project ==
Sensory aware applications are becoming more mainstream with the release of the Apple iPhone. This project would combine both HW and SW to add sensory awareness to beagle. First, additional modules such as GPS, 3-axis accelerometers, gyroscopes, temperature sensors, humidity sensors, pressure sensors, etc, would be added to Beagle to compliment the microphone input in order to allow sensing of the real world environment. Then software APIs would need to be layered on top to allow easy access to the sensory data for use by applications.

== Timeline ==
Week 3: Get accelerometer 
Week 4: Hook up sensor to the I2C; See what Beagleboard does automatically with I2C. 
Week 5: Learn how ARM I2C C functions work; Start coding. 
Week 6: Finish coding. 
Week 7: Do documentation. 
Week 8: If we are on time, start working on another I2C sensor. 
Week 9/10: Padding time.

== Milestones ==
• Read data from I2C line. 
• Call our library from another C program. 
• Create clear documentation.

ECE497 Project Ideas

2010-03-25T02:10:36Z

Jesionaj:

[[Category:ECE597]]
[[Category:BeagleBoard]]

== Sources for Project Ideas ==

Here are some links where you'll find ideas for your project.
* [http://wiki.omap.com/index.php/ETechDays_Community_Lightning_Talks ETechDays Community Lightning Talks], this is a one-day web-based conference where many project ideas are presented. One of our 2009-2010 senior design projects was found here.
* [http://beagleboard.org/project Official list of Beagle Projects], there are many Beagle specific projects listed here. Many are inactive. ''List your project here once it running.''
* [http://www.youtube.com/watch?v=Mk1xjbA-ISE Augmented Reality Project], here's an idea that I think we can do on the Beagle. Rather than using augmented reality glasses, I'd suggest we use a [http://focus.ti.com/dlpdmd/docs/dlpdiscovery.tsp?sectionId=60&tabId=2235 TI DLP pico projector]. [http://www.hitlabnz.org/wiki/EmbeddedAR Here's] AR running on the Beagle.
* [http://code.google.com/p/0xdroid/ Android], this is one of a couple of efforts to port [http://source.android.com/ Google's Android OS] to the Beagle.
* [[BeagleBoard/Ideas-2009]] Google summer code ideas 2009.

== Projects you would like to do ==
Edit this page to add projects you would like to do. If you aren't in the class, add ideas you would like to see done by class members.

{| border="1" cellspacing="0" cellpadding="5"
! Team Members
! Project Title
! Description
|-
| Mark A. Yoder
| [[ECE597 Google PowerMeter]]
| Google has a [http://www.google.com/powermeter project] to view and manage home electricity usage. This project would involve designing the hardware to measure the power usage and the Beagle software in interface with it. The Beagle would talk to the local home network via a wireless link and the home owner would configure the Beagle via a web page served on the Beagle.
|-
| Yannick Polius
| Audio MBox
| This project is mostly software, with the hardware element being the use of the dsp. The idea is to tie together three technologies: speech recognition, speech synthesis, and internet access in order to create an interface capable of orating information to the user based on a vocal command. The implementation I have in mind is to use the Pocket Sphinx speech recognition engine to first understand what the user wants through speech, such as "Rose-Hulman". Once the speech is translated, the software can execute a Wikipedia search to pull said item's page. Most of the important info is contained within the introductory paragraph, so the software will take only that chunk and feed it into the Flite speech synthesis engine. The end result is a simple machine with "mother box" like usability, that is, no interaction besides what is natural to the user (speaking) should be necessary to retrieve the information.
|-
| Paul Morrison Steven Stark
| [[ECE597 3D Chess | 3D Chess with Networking]]
| This project would simulate a hand-held chess game, and the game would allow two player games using two beagleboards over a network connection. The graphics would use the beagle's PowerVR SGX for hardware accelerated graphics by using OpenGL. In addition to 3D graphics and networking, a third portion of the project would be to optimize the boot time because a chess computer should start up quickly.
|-
| Tom Most David Baty Mark Jacobson
| [[ECE597: Sumo Robot|Sumo Robot]]
| The goal of this project is to create a robot capable of competing in the 3.0 kg weight class of a sumo competition ([http://www.youtube.com/watch?v=V3OR_sHrOJM an example]). This would have minor hardware and electronics elements, but would focus on communication with sensors using the BeagleBoard and the Linux kernel. At minimum, this involves sensors to detect the edge of the ring and the opposing robot. This would likely be implemented using Sharp IR rangefinders, a ultrasonic rangefinders, and ideally a camera. [http://circ.mtco.com/competitions/2010/rules/sumo Sumo rules].
|-
|Brian Embry Jessica Lipscomb Paul Banister
| [[ECE597 Network based MP3 player]]
| Network based mp3 player. The Beagle will be programmed using a custom, protocol for transferring files from a network based server (x86 pc) to a Beagle. Speakers will be attached to the Beagle, where the file will be played back. Possible extensions are a LCD for displaying id3 tag information, and buttons for user interaction (next track, previous track, etc.) on the GPIO interface.
|-
|[[user:routhcr | Chris Routh]] [[user:collinjc | J. Cody Collins]] Greg Jackson Keqiong Xin
| [[ECE597: Auto HUD]]
| Use the beagle board to run image recognition on a camera feed located inside a car, and then signaling to the driver via a pico projector various objects of interest.
|-
| Adam Jesionowski Qiang Jiang
| [[ECE597_Adding_Sense_to_Beagle|Adding Sense to Beagle]] (See [[BeagleBoard/GSoC/Ideas]])
| Sensory aware applications are becoming more mainstream with the release of the Apple iPhone. This project would combine both HW and SW to add sensory awareness to beagle. First, additional modules such as GPS, 3-axis accelerometers, Gyroscopes, Temperature Sensors, Humidity Sensors, Pressure Sensors, etc, would be added to beagle to compliment the microphone input in order to allow sensing of the real world environment. Then SW APIs would need to be layered on top to allow easy access to the sensory data for use by applications.
|-
| Mitch Garvin Matt Luke Elliot Simon Jian Li
| [[ECE597 Interactive Pong]]
| Run classic pong, projecting the screen and using a camera to track user's hands for input.
|}

ECE597 Project Adding Sense to Beagle

2010-03-25T02:09:49Z

Jesionaj: Created page with '== Description of Project == Sensory aware applications are becoming more mainstream with the release of the Apple iPhone. This project would combine both HW and SW to add sensor…'

== Description of Project ==
Sensory aware applications are becoming more mainstream with the release of the Apple iPhone. This project would combine both HW and SW to add sensory awareness to beagle. First, additional modules such as GPS, 3-axis accelerometers, gyroscopes, temperature sensors, humidity sensors, pressure sensors, etc, would be added to Beagle to compliment the microphone input in order to allow sensing of the real world environment. Then software APIs would need to be layered on top to allow easy access to the sensory data for use by applications.

== Timeline ==
Week 3: Get accelerometer
Week 4: Hook up sensor to the I2C; See what Beagleboard does automatically with I2C.
Week 5: Learn how ARM I2C C functions work; Start coding.
Week 6: Finish coding.
Week 7: Do documentation.
Week 8: If we are on time, start working on another I2C sensor.
Week 9/10: Padding time.

== Milestones ==
• Read data from I2C line. 
• Call our library from another C program. 
• Create clear documentation.

User:Jesionaj

2010-03-19T19:51:44Z

Jesionaj: Added link to listings

I'm Adam Jesionowski, soon to be ex-undergrad of Rose-Hulman. I'm a fan of Arch Linux and accidentally doing <tt>rm -Rf *</tt> on <tt>/</tt>

[[User:Jesionaj/Listings|My listings]]

[[Category:ECE597]]

User:Jesionaj/Listings

2010-03-19T19:50:56Z

Jesionaj: Created page.

EBC Exercise 22 Cross-Compiling

2010-03-18T22:14:16Z

Jesionaj: /* Step 7 - Building a complete Beagle demo image */ - adding link to tutorial

[[Category:ECE597]]
[[Category: BeagleBoard]]

This class is about developing software for embedded Linux. The [http://elinux.org/Main_Page eLinux site] is a good source for embedded Linux in general. There are many ongoing embedded efforts going on many platforms. Poke around the site a while to get a feel for what's happening.

We are going to use the [http://www.angstrom-distribution.org Ångström Distribution]. It's available many platforms. Look around the site, you may recognize some of them.

Instructions for building Ångström are given [http://www.angstrom-distribution.org/building-angstrom here]; however I'm going to present a Beagle-tuned version of those instructions on this page.

== Step 1 - get Open Embedded metadata ==

First install <code>git</code> by running the following on your host computer.
<pre>
sudo apt-get install git-core
</pre>

Then run the following to load the meta data.
<pre>
export OETREE="${HOME}/oe"
mkdir -p ${OETREE} && cd ${OETREE}
git clone git://git.openembedded.org/openembedded.git openembedded
cd openembedded
git checkout origin/stable/2009 -b stable/2009
</pre>
If <code>git://git.openembedded.org/openembedded.git</code> does not work, you can also try <code>http://repo.or.cz/r/openembedded.git</code>. 
The first git transfers some 336,000 object and takes about 18 minutes with the network running at 600 some KiB/s. Keep an eye on it, mine stopped about 23% in and I had to restart it. The second git takes almost no time.

Now run the following to update the metadata:
<pre>
cd ${OETREE}/openembedded
git pull
</pre>
You've created a directory called <code>oe</code>. Go explore around it to see what is there. Be sure to look in <code>oe/openembedded/recipes</code>. These folders contain instructions on where to get and how to build various things. Look in <code>recipes/linux</code>. Here are instructions for building various Linux kernels. We'll be using <code>linux-omap-2.6.*</code>. What's the highest version you can find?

== Step 2 - Installing bitbake and friends ==

bitbake is the workhorse that knows where to get everything and how to compile it. The following will install bitbake and additional programs that bitbake needs. This may take 5 minutes.
<pre>
sudo apt-get install bitbake
sudo apt-get install g++
sudo apt-get install help2man diffstat texi2html cvs texinfo subversion gawk
sudo apt-get autoremove
</pre>
If you are running Ubuntu you will have to also do the following:
<pre>
cd /bin
sudo mv sh sh.old
sudo ln -s bash sh
sudo sh -c "echo 0 > /proc/sys/vm/mmap_min_addr"
</pre>
Finally edit the file <code>/etc/sysctl.conf</code> using:
<pre>
sudo gedit /etc/sysctl.conf
</pre>
Add the following at the end and save.
<pre>
# This is for bitbake
vm.mmap_min_addr = 0
</pre>
Now you should be ready to run bitbake.

{{Give
|title=Psyco JIT compiler
|tip=bitbake suggest loading a compiler. Load and test the compiler. If it's worth using, write instructions.
}}
The Psyco Python JIT compiler should help speed up compilation times at the expense of memory use . It only works on 32-bit systems. To install, use
<pre>
sudo apt-get install python-psyco
</pre>

== Step 3 - Setting up for the BeagleBoard ==

Now let's setup <code>local.conf</code> for our needs:
<pre>
mkdir -p ${OETREE}/build/conf
cp ${OETREE}/openembedded/contrib/angstrom/local.conf ${OETREE}/build/conf/
</pre>
Open <code>${OETREE}/build/conf/local.conf</code> in your favourite editor and add the following to the end of the file.
<pre>
MACHINE ?= "beagleboard"
</pre>
Also, look at this block of lines:
<pre>
# Make use of SMP and fast disks
PARALLEL_MAKE = "-j4"
BB_NUMBER_THREADS = "4"
</pre>
Here you can tell it how many parallel threads to run. If you have several cores on your machine, make this number big. If you have only one core, you might be better performance setting it to 1. More details are [http://wiki.openembedded.org/index.php/Advanced_configuration here].
* PARALLEL_MAKE sets the number "gcc" threads (same as make -j4 at compile time
* BB_NUMBER_THREADS sets the number of bitbake threads, (one thread can be downloading, while another compiles)

To save you a lot of time, it is useful to disable locale generation for all but the one you need. Add this to local.conf
<pre>
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 en_GB.UTF-8 de_DE.UTF-8 fr_FR.UTF-8 pt_BR.UTF-8 es_ES.UTF-8 kn_IN.UTF-8 ml_IN.UTF-8 ta_IN.UTF-8"
</pre>

== Step 4 - Start building ==

We need to create a small script to setup the environment

<pre>
cd ${OETREE}
wget -c http://www.angstrom-distribution.org/files/source-me.txt
</pre>

*Take a second to read the script, and notice that it configures a download directory, a build directory, and a staging directory. Can you explain why ${PATH} is modified in this script?

Now we are almost ready for compiling
<pre>
#Go to the OpenEmbedded folder
cd ${OETREE}/openembedded

#Make sure it's up to date
git pull --rebase

#Set environment variables
cd ${OETREE}
source source-me.txt

#Start building
bitbake nano
</pre>

This will take a while. bitbake is installing everything that is needed to compile the system. This includes cross compilers, assemblers, source, everything. I started at 10am and ended around 5:30pm. It was running on just one of the two cores on my laptop. How long did it take on your machine? I notice that an additional 600M of disk space is being used.

{{Give
|title=Keep track of you running times and configurations.
|tip=We'll use this data to see what the best settings are.
}}

{| border="1" cellspacing="0" cellpadding="5"
|+ Initial <tt>bitbake nano</tt> runtime
! Processor
! Settings
! Run Time
|-
| Intel Pentium-M@2.0Ghz
| PARALLEL_MAKE = "-j1" BB_NUMBER_THREADS = "1" Psyco? Yes.
| 4.9 hours
|-
| Intel Atom N330@1.6Ghz
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "4" Psyco? No.
| 3.15 hours
|-
| Intel Core2Quad Q9300@2.5Ghz
| PARALLEL_MAKE = "-j5" BB_NUMBER_THREADS = "4" Psyco? No.
| 44 minutes
|-
| T2600@2.16 GHz
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "2" Psyco? Yes. All Locals
| 2.5 hours
|-
| T2600@2.16 GHz
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "4" Psyco? Yes. US Only
| 73 minutes
|-
| E8400@3.00 GHz
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "4" Psyco? No.
| All Locals 1.4 hours US only 43 Minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "4" Psyco? No.
| 56.08 minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j8" BB_NUMBER_THREADS = "8" Psyco? No.
| 57.83 minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "8" Psyco? No.
| 53.86 minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j7" BB_NUMBER_THREADS = "7" Psyco? No.
| 61.75 minutes
|-
| Core 2 Duo T7600@2.33GHz
| PARALLEL_MAKE = "-j1" BB_NUMBER_THREADS = "1" Psyco? No (64-bit).
| 2:10:04
|}

== Step 5 - Building a complete image ==

Up to this point all we have done is load all the infrastructure needed and compiled the simple '''nano''' text editor. We don't even have the kernel yet. Do the following to build a basic console image.
<pre>
bitbake console-image
</pre>
'''This bitbake took 7 hours and 15 minutes.''' There are now some 7,700 directories with 67,000 files in the <code>oe</code> directory. An additional 1.5G of disk space is in use.

How did I know to use '''console-image'''? I ran the following to find what images were out there:
<pre>
locate image | grep /oe/
</pre>
This found every file with '''image''' in the name it that also had '''/oe/''' in the path. From this I see that '''oe/openembedded/recipes/images''' has a bunch of files ending in '''-image'''. Take a look at '''console-image.bb''' and see what you can figure out.

== Step 6 - Loading your SD card ==

The output of the bitbake command will ultimately be found under the <code>$OE_HOME/angstrom-dev/deploy/glibc/images/beagleboard</code>. In there you can find at least two interesting files:
<pre>
console-image-beagleboard.tar.bz2
uImage-beagleboard.bin
</pre>
The console image represents a full and self-contained file system, *including* a kernel. The uImage-beagleboard.bin is a Linux kernel image suitable for loading by the U-boot bootloader.

* Rename '''uImage-beagleboard.bin''' as '''uImage''' and load on your SD as before ([[ECE597 Getting your Beagle running (precompiled)]]).
* Also load '''console-image-beagleboard.tar.bz2''' on the 2nd partition like you did before. Did you notice it untar's very quickly? Why?
* Boot and explore. What's there? What's missing?

Congratulations you've just build Linux from source. Try this:
<pre>
beagleboard login: root
root@beagleboard:~# cd /sys/class
root@beagleboard:/sys/class# ls -F
bdi/ hwmon/ misc/ scsi_generic/ usb_device/
block/ i2c-adapter/ mmc_host/ scsi_host/ usb_endpoint/
bluetooth/ i2c-dev/ mtd/ sound/ usb_host/
bmi/ ieee80211/ net/ spi_master/ usbmon/
display/ input/ regulator/ spidev/ vc/
firmware/ leds/ rtc/ thermal/ vtconsole/
gpio/ mdio_bus/ scsi_device/ tty/
graphics/ mem/ scsi_disk/ ubi/
</pre>
This is a list of low-level devices on the Beagle that you can access as files. Try:
<pre>
root@beagleboard:/sys/class# cd leds/
root@beagleboard:/sys/class/leds# ls -F
beagleboard::usr0@ beagleboard::usr1@
root@beagleboard:/sys/class/leds# cd beagleboard\:\:usr0
root@beagleboard:/sys/devices/platform/leds-gpio/leds/beagleboard::usr0# cat trigger
none nand-disk mmc0 mmc1 [heartbeat]
</pre>
This is a list of values you can assign to trigger. Notice LED0 is blinking on and off right now. Try:
<pre>
root@beagleboard:/sys/devices/platform/leds-gpio/leds/beagleboard::usr0# echo none > trigger
root@beagleboard:/sys/devices/platform/leds-gpio/leds/beagleboard::usr0# echo 1 > brightness
</pre>
What happens? Play around. [http://groups.google.com/group/beagleboard/msg/c623a16637625685?hl=en Here] are instructions on reading the '''USER''' switch. Try it. Can you make the LEDs blink in response to the button being pressed?

== Step 7 - Building a complete Beagle demo image ==

Now let's build the how demo we were running before. We'll do this via bitbake, but argument do we give it? Try looking in <code>oe/openembedded/recipes/images</code>, do you see a recipe that might work? Hint: It has beagle in the name. Here's what I tried.
<pre>
time bitbake beagle????-image
</pre>
Replace ???? with the recipe name you found. I added the '''time''' command so I could see how long it takes to run. My run took some 7.5 hours.

If you're having trouble with Gimp and/or gnumeric, consult [[ECE597 OpenEmbedded Issues and Problem_Solving]].

== Step 7.5 Building a complete unstable Beagle demo image ==
I did not have as much luck getting Ångström working in the stable OE branch, but I was able to make dev work. You should see that there are two branches available to to choose from.
<pre>
$ git branch
org.openembedded.dev
* stable/2009
$
</pre>

So switch to the .dev branch by saying

<pre>
$ git checkout org.openembedded.dev
$ git pull # may not be needed
</pre>

The OE dev branch '''does not''' ship with its own version of bitbake, so you will need to obtain bitbake from another source. Compiling from the OE dev branch seems to require an up-to-date version of bitbake. Install this by running

<pre>
$ cd ${OETREE}
$ wget http://download.berlios.de/bitbake/bitbake-1.8.18.tar.gz
$ tar -xvf bitbake-1.8.18.tar.gz
</pre>
This will download and unpack version 1.8.18 of bitbake. Currently, this version seems to work well with the OE dev branch. You must now edit the path that points to bitbake in the source-me.txt file so that it will point to the directory containing this version of bitbake. You should change the line containing

<pre>
PATH=${OETREE}/openembedded/bitbake/bin:${ORG_PATH}
</pre>
to the following:

<pre>
PATH=${OETREE}/bitbake-1.8.18/bin:${ORG_PATH}
</pre>
'''''NOTE''''': If you have modified the <code>GLIBC_GENERATE_LOCALES</code> setting in <code>${OETREE}/build/conf/local.conf</code> to contain only <code>en_US.UTF-8</code>, your build may fail due to missing required locales. You should have this set to <code>GLIBC_GENERATE_LOCALES = "en_US.UTF-8 en_GB.UTF-8 de_DE.UTF-8 fr_FR.UTF-8 pt_BR.UTF-8 es_ES.UTF-8 kn_IN.UTF-8 ml_IN.UTF-8 ta_IN.UTF-8"</code> for the build to be successful. If you local.conf file does not have a line containing <code>GLIBC_GENERATE_LOCALES</code>, your build still should be successful as it will, by default, include all available locales, including those mentioned above. Can you figure out where this list of locals came from?

We must now wipe out our stable build directory, as the two branches are not compatible. (Feel free to make a backup if you feel inclined).
<pre>
$ rm -rf ${OETREE}/angstrom-dev/
</pre>

Now you may follow the directions above by running
<pre>
$ time bitbake beagle????-image
</pre>

This will take a VERY long time, as it must recompile everything that was done previously. On my E8400 it took 10.4 hours to run with all locales, and 9.3 hours with only the ones I needed. It also used 17gb of space.

Once it has finished take a look in
<pre>
$ ls ${OETREE}/angstrom-dev/deploy/glibc/images/beagleboard
</pre>

You should recognize the files from when you previously installed Angstrom, if not re-read [[ECE597_Getting_your_Beagle_running_(precompiled)]]

The first boot of my beagle took a very long time...a few minutes (subsequent boots are faster), the beagle will hang on the below screen for a while, just let it go and it will continue.
<pre>
INIT: version 2.86 booting
Error. Cannot create canvas. Abort.
</pre>

I also saw a lot of these errors, again you can probably ignore them. (if you can figure out how to fix, post fix here)
<pre>
Cannot find fifo at /mnt/.splash/exquisite.
</pre>

ECE597 OpenEmbedded Issues and Problem Solving

2010-03-18T22:12:35Z

Jesionaj: For ECE597

== OpenEmbedded Issues ==

For the most part, looking at the error log will give you enough information to Google a result. In this particular case, while trying <tt>bitbake beagleboard-demo-image</tt>, I was getting errors that didn't give me much information from internet searches. The solution I decided on was to simply get rid of the Gimp and gnumeric packages. The following is the process I went through to figure out how to do just that.

== Removing Packages ==

From doing [[ECE597_Installing_The_Ångström_Distribution#Step_7_-_Building_a_complete_Beagle_demo_image|Step 7]] of the Beagle demo image tutorial, we know that <tt>beagleboard-demo-image.bb</tt> resides in <tt>${OETREE}/openembedded/recipes/images</tt>. That gives us a starting point for our search.

<pre>[adam@melchoir images]$ cat beagleboard-demo-image.bb
# Demo image for beagleboard

IMAGE_LINGUAS = "en-us"

XSERVER ?= "xserver-xorg \
xf86-input-evdev \
xf86-input-mouse \
xf86-video-fbdev \
xf86-input-keyboard \
"

ANGSTROM_EXTRA_INSTALL ?= ""

export IMAGE_BASENAME = "Beagleboard-demo-image"

DEPENDS = "task-base"
IMAGE_INSTALL = "\
${XSERVER} \
${ANGSTROM_EXTRA_INSTALL} \
task-beagleboard-demo \
"

IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"

#zap root password for release images</pre>
There's not much information here. One line that looks interesting is DEPENDS - since it needs that file, let's go take a look at that.

First we need to find it:
<pre>[adam@melchoir openembedded]$ find . -name *task-base*
./recipes/angstrom/angstrom-gpe-task-base.bb
./recipes/tasks/task-base.bb
</pre>
Alright, now let's take a look.
<pre>[adam@melchoir openembedded]$ nano recipes/tasks/task-base.bb
DESCRIPTION = "Merge machine and distro options to create a basic machine task/package"
PR = "r83"

inherit task

DEPENDS = "task-boot"
PROVIDES = "${PACKAGES}"
PACKAGES = ' \
task-base \
task-base-extended \
task-distro-base \
task-machine-base \
\
${@base_contains("MACHINE_FEATURES", "acpi", "task-base-acpi", "",d)} \
${@base_contains("MACHINE_FEATURES", "alsa", "task-base-alsa", "", d)} \
${@base_contains("MACHINE_FEATURES", "apm", "task-base-apm", "", d)} \
${@base_contains("MACHINE_FEATURES", "ext2", "task-base-ext2", "", d)} \
${@base_contains("MACHINE_FEATURES", "vfat", "task-base-vfat", "", d)} \
${@base_contains("MACHINE_FEATURES", "irda", "task-base-irda", "",d)} \
${@base_contains("MACHINE_FEATURES", "keyboard", "task-base-keyboard", "", d)} \
${@base_contains("MACHINE_FEATURES", "pci", "task-base-pci", "",d)} \
${@base_contains("MACHINE_FEATURES", "pcmcia", "task-base-pcmcia", "", d)} \
${@base_contains("MACHINE_FEATURES", "phone", "task-base-phone", "", d)} \
...
</pre>
A packages variable! That's much more interesting. There's a lot in this file, but doing a search for Gimp or gnumeric doesn't bring anything up. Looking back at <tt>beagleboard-demo-image.bb</tt> though, there's a similarly named file <tt>task-beagleboard-demo</tt>. Let's check <tt>recipes/tasks</tt> for it.
<pre>
[adam@melchoir tasks]$ ls | grep beagle
task-beagleboard-demo.bb
</pre>
Looks like it's in the same directory as task-base. Let's open it up.
<pre>
[adam@melchoir tasks]$ nano task-beagleboard-demo.bb
DESCRIPTION = "Task for Beagleboard-demo-image"

PR = "r7"

inherit task

ECONFIG ?= "places e-wm-config-angstrom e-wm-config-default"

RDEPENDS_${PN} = "\
task-proper-tools \
task-base-extended \
angstrom-x11-base-depends \
angstrom-gpe-task-base \
angstrom-gpe-task-settings \
angstrom-zeroconf-audio \
angstrom-led-config \
gimp \
gnumeric \
gpe-scap \
psplash \
mime-support e-wm ${ECONFIG} exhibit \
xterm xmms \
firefox midori \
swfdec-mozilla \
hicolor-icon-theme gnome-icon-theme \
jaaa nmap iperf gnuplot \
abiword \
powertop oprofile \
pidgin \
# irssi \
mplayer \
gnome-games \
rt73-firmware zd1211-firmware \
stalonetray \
synergy \
x11vnc angstrom-x11vnc-xinit \
angstrom-gnome-icon-theme-enable \
openssh-scp openssh-ssh \
picodlp-control \
connman-gnome \
"

# Install all kernel modules
RRECOMMENDS_${PN} += "kernel-modules"

PACKAGE_ARCH = "${MACHINE_ARCH}"
RRECOMMENDS_${PN}_append_armv7a = " omapfbplay"
</pre>
And there you can see Gimp and gnumeric. By commenting them out (adding a # in front, as in the case of irssi), the image will skip those packages, allowing the image to be built successfully.

ECE497 Project Ideas

2010-03-12T21:27:37Z

Jesionaj: Changing Project

[[Category:ECE597]]
[[Category:BeagleBoard]]

== Sources for Project Ideas ==

Here are some links where you'll find ideas for your project.
* [http://wiki.omap.com/index.php/ETechDays_Community_Lightning_Talks ETechDays Community Lightning Talks], this is a one-day web-based conference where many project ideas are presented. One of our 2009-2010 senior design projects was found here.
* [http://beagleboard.org/project Official list of Beagle Projects], there are many Beagle specific projects listed here. Many are inactive. ''List your project here once it running.''
* [http://www.youtube.com/watch?v=Mk1xjbA-ISE Augmented Reality Project], here's an idea that I think we can do on the Beagle. Rather than using augmented reality glasses, I'd suggest we use a [http://focus.ti.com/dlpdmd/docs/dlpdiscovery.tsp?sectionId=60&tabId=2235 TI DLP pico projector]. [http://www.hitlabnz.org/wiki/EmbeddedAR Here's] AR running on the Beagle.
* [http://code.google.com/p/0xdroid/ Android], this is one of a couple of efforts to port [http://source.android.com/ Google's Android OS] to the Beagle.
* [[BeagleBoard/Ideas-2009]] Google summer code ideas 2009.

== Projects you would like to do ==
Edit this page to add projects you would like to do. If you aren't in the class, add ideas you would like to see done by class members.

{|
! Team Names
! Project Title
! Description
|-
| Mark A. Yoder
| [[ECE597 Google PowerMeter]]
| Google has a [http://www.google.com/powermeter project] to view and manage home electricity usage. This project would involve designing the hardware to measure the power usage and the Beagle software in interface with it. The Beagle would talk to the local home network via a wireless link and the home owner would configure the Beagle via a web page served on the Beagle.
|-
| Yannick Polius Steven Stark Paul Morrison
| Audio MBox
| This project is mostly software, with the hardware element being the use of the dsp. The idea is to tie together three technologies: speech recognition, speech synthesis, and internet access in order to create an interface capable of orating information to the user based on a vocal command. The implementation I have in mind is to use the Pocket Sphinx speech recognition engine to first understand what the user wants through speech, such as "Rose-Hulman". Once the speech is translated, the software can execute a Wikipedia search to pull said item's page. Most of the important info is contained within the introductory paragraph, so the software will take only that chunk and feed it into the Flite speech synthesis engine. The end result is a simple machine with "mother box" like usability, that is, no interaction besides what is natural to the user (speaking) should be necessary to retrieve the information.
|-
| David Baty
| IRLP Node
| [http://www.irlp.net/ IRLP (Internet Radio Linking Project)] is an amateur radio project to allow the linking of repeaters across the world over the internet. It requires very little hardware, but due to an antiquated interface board and is typically run on old desktop hardware that uses significantly more power than a beagle board. All of the software already runs on Linux, but would require some porting. Interface hardware would also have to be designed, but if DTMF (dial tone) decoding is done in software, this external board would be very simple.
|-
| Tom Most
| Open Source Slingbox
| The [http://slingbox.com/ Slingbox] is a device that allows "place-shifting" of television through streaming. The idea is to create a similar device using the Beagle and a USB DTV tuner. It could implement a [[UPnP]] server and perform on-the-fly transcoding using [http://gstreamer.org/ GStreamer] (with [http://www.freedesktop.org/wiki/GstOpenMAX DSP] [[BeagleBoard/gst-openmax|acceleration]]). Hopefully [[UPnP#NAT_Traversal|UPnP NAT traversal]] could be used to automatically open a port for external access as well, enabling "place-shifting". [[DLNA Open Source Projects]] are relevant, particularly [http://live.gnome.org/Rygel Rygel].
|-
|Brian Embry Jessica Lipscomb Paul Banister
| [[ECE597: MythTV/DSP Pico Projector]]
| Have the Beagleboard act as a MythTV/portable video playback node. This may require work with the DSP acceleration of FFMPEG/Gstreamer. Additionally, interfacing with a Pico Projector to allow for portable media enjoyment. If MythTV support is not practical, simple localized video playback with DSP acceleration will be used.
|-
|Chris Routh [[user:collinjc | J. Cody Collins]] Greg Jackson Keqiong Xin
| [[ECE597: Auto HUD]]
| Use the beagle board to run image recognition on a camera feed located inside a car, and then signaling to the driver via a pico projector various objects of interest.
|-
| Adam Jesionowski Qiang Jiang
| Adding Sense to Beagle (See [[BeagleBoard/GSoC/Ideas]])
| Sensory aware applications are becoming more mainstream with the release of the Apple iPhone. This project would combine both HW and SW to add sensory awareness to beagle. First, additional modules such as GPS, 3-axis accelerometers, Gyroscopes, Temperature Sensors, Humidity Sensors, Pressure Sensors, etc, would be added to beagle to compliment the microphone input in order to allow sensing of the real world environment. Then SW APIs would need to be layered on top to allow easy access to the sensory data for use by applications.
|-
| Mitch Garvin Matt Luke Elliot Simon Jian Li
| [[ECE597 Interactive Pong]]
| Run classic pong, projecting the screen and using a camera to track user's hands for input.
|}

ECE497 Project Ideas

2010-03-12T20:49:17Z

Jesionaj: Forming possible team

[[Category:ECE597]]
[[Category:BeagleBoard]]

== Sources for Project Ideas ==

Here are some links where you'll find ideas for your project.
* [http://wiki.omap.com/index.php/ETechDays_Community_Lightning_Talks ETechDays Community Lightning Talks], this is a one-day web-based conference where many project ideas are presented. One of our 2009-2010 senior design projects was found here.
* [http://beagleboard.org/project Official list of Beagle Projects], there are many Beagle specific projects listed here. Many are inactive. ''List your project here once it running.''
* [http://www.youtube.com/watch?v=Mk1xjbA-ISE Augmented Reality Project], here's an idea that I think we can do on the Beagle. Rather than using augmented reality glasses, I'd suggest we use a [http://focus.ti.com/dlpdmd/docs/dlpdiscovery.tsp?sectionId=60&tabId=2235 TI DLP pico projector]. [http://www.hitlabnz.org/wiki/EmbeddedAR Here's] AR running on the Beagle.
* [http://code.google.com/p/0xdroid/ Android], this is one of a couple of efforts to port [http://source.android.com/ Google's Android OS] to the Beagle.
* [[BeagleBoard/Ideas-2009]] Google summer code ideas 2009.

== Projects you would like to do ==
Edit this page to add projects you would like to do. If you aren't in the class, add ideas you would like to see done by class members.

{|
! Team Name
! Project Title
! Description
|-
| Mark A. Yoder
| [[ECE597 Google PowerMeter]]
| Google has a [http://www.google.com/powermeter project] to view and manage home electricity usage. This project would involve designing the hardware to measure the power usage and the Beagle software in interface with it. The Beagle would talk to the local home network via a wireless link and the home owner would configure the Beagle via a web page served on the Beagle.
|-
| Yannick Polius
| Audio MBox
| This project is mostly software, with the hardware element being the use of the dsp. The idea is to tie together three technologies: speech recognition, speech synthesis, and internet access in order to create an interface capable of orating information to the user based on a vocal command. The implementation I have in mind is to use the Pocket Sphinx speech recognition engine to first understand what the user wants through speech, such as "Rose-Hulman". Once the speech is translated, the software can execute a Wikipedia search to pull said item's page. Most of the important info is contained within the introductory paragraph, so the software will take only that chunk and feed it into the Flite speech synthesis engine. The end result is a simple machine with "mother box" like usability, that is, no interaction besides what is natural to the user (speaking) should be necessary to retrieve the information.
|-
| David Baty
| IRLP Node
| [http://www.irlp.net/ IRLP (Internet Radio Linking Project)] is an amateur radio project to allow the linking of repeaters across the world over the internet. It requires very little hardware, but due to an antiquated interface board and is typically run on old desktop hardware that uses significantly more power than a beagle board. All of the software already runs on Linux, but would require some porting. Interface hardware would also have to be designed, but if DTMF (dial tone) decoding is done in software, this external board would be very simple.
|-
| Tom Most
| Open Source Slingbox
| The [http://slingbox.com/ Slingbox] is a device that allows "place-shifting" of television through streaming. The idea is to create a similar device using the Beagle and a USB DTV tuner. It could implement a [[UPnP]] server and perform on-the-fly transcoding using [http://gstreamer.org/ GStreamer] (with [http://www.freedesktop.org/wiki/GstOpenMAX DSP] [[BeagleBoard/gst-openmax|acceleration]]). Hopefully [[UPnP#NAT_Traversal|UPnP NAT traversal]] could be used to automatically open a port for external access as well, enabling "place-shifting". [[DLNA Open Source Projects]] are relevant, particularly [http://live.gnome.org/Rygel Rygel].
|-
| [[user:collinjc | J. Cody Collins]]
| BeagleBoard-Based Router
| This idea would involve writing software to perform the capabilities found in commercially available routers. The software could be written from scratch, or an existing project, such as [http://openwrt.org/ OpenWrt] could be ported to the BeagleBoard. Currently, some efforts are being made in porting OpenWrt to the BeagleBoard, but the number of contributers has been relatively small. These efforts could potentially result in a low-cost, open-source, OMAP3-based router.
|-
|Brian Embry Jessica Lipscomb Paul Banister
| MythTV/DSP Pico Projector
| Have the Beagleboard act as a MythTV/portable video playback node. This may require work with the DSP acceleration of FFMPEG/Gstreamer. Additionally, interfacing with a Pico Projector to allow for portable media enjoyment. If MythTV support is not practical, simple localized video playback with DSP acceleration will be used.
|-
| Adam Jesionowski
| Fast Boot
| See [[BeagleBoard/GSoC/Ideas#Fast_Linux_boot]]
|}

User:Jesionaj

2010-03-11T22:08:31Z

Jesionaj: Created page with 'I'm Adam Jesionowski, soon to be ex-undergrad of Rose-Hulman. I'm a fan of Arch Linux and accidentally doing <tt>rm -Rf *</tt> on <tt>/</tt> Category:ECE597'

I'm Adam Jesionowski, soon to be ex-undergrad of Rose-Hulman. I'm a fan of Arch Linux and accidentally doing <tt>rm -Rf *</tt> on <tt>/</tt>

[[Category:ECE597]]

EBC Exercise 22 Cross-Compiling

2010-03-11T21:50:03Z

Jesionaj: +times

[[Category:ECE597]]
[[Category: BeagleBoard]]

This class is about developing software for embedded Linux. The [http://elinux.org/Main_Page eLinux site] is a good source for embedded Linux in general. There are many ongoing embedded efforts going on many platforms. Poke around the site a while to get a feel for what's happening.

We are going to use the [http://www.angstrom-distribution.org Ångström Distribution]. It's available many platforms. Look around the site, you may recognize some of them.

Instructions for building Ångström are given [http://www.angstrom-distribution.org/building-angstrom here]; however I'm going to present a Beagle-tuned version of those instructions on this page.

== Step 1 - get Open Embedded metadata ==

First install <code>git</code> by running the following on your host computer.
<pre>
sudo apt-get install git-core
</pre>

Then run the following to load the meta data.
<pre>
export OETREE="${HOME}/oe"
mkdir -p ${OETREE} && cd ${OETREE}
git clone git://git.openembedded.org/openembedded.git openembedded
cd openembedded
git checkout origin/stable/2009 -b stable/2009
</pre>
If <code>git://git.openembedded.org/openembedded.git</code> does not work, you can also try <code>http://repo.or.cz/r/openembedded.git</code>. 
The first git transfers some 336,000 object and takes about 18 minutes with the network running at 600 some KiB/s. Keep an eye on it, mine stopped about 23% in and I had to restart it. The second git takes almost no time.

Now run the following to update the metadata:
<pre>
cd ${OETREE}/openembedded
git pull
</pre>
You've created a directory called <code>oe</code>. Go explore around it to see what is there. Be sure to look in <code>oe/openembedded/recipes</code>. These folders contain instructions on where to get and how to build various things. Look in <code>recipes/linux</code>. Here are instructions for building various Linux kernels. We'll be using <code>linux-omap-2.6.*</code>. What's the highest version you can find?

== Step 2 - Installing bitbake and friends ==

bitbake is the workhorse that knows where to get everything and how to compile it. The following will install bitbake and additional programs that bitbake needs. This may take 5 minutes.
<pre>
sudo apt-get install bitbake
sudo apt-get install g++
sudo apt-get install help2man diffstat texi2html cvs texinfo subversion gawk
sudo apt-get autoremove
</pre>
If you are running Ubuntu you will have to also do the following:
<pre>
cd /bin
sudo mv sh sh.old
sudo ln -s bash sh
sudo sh -c "echo 0 > /proc/sys/vm/mmap_min_addr"
</pre>
Finally edit the file <code>/etc/sysctl.conf</code> using:
<pre>
sudo gedit /etc/sysctl.conf
</pre>
Add the following at the end and save.
<pre>
# This is for bitbake
vm.mmap_min_addr = 0
</pre>
Now you should be ready to run bitbake.

{{Give
|title=Psyco JIT compiler
|tip=bitbake suggest loading a compiler. Load and test the compiler. If it's worth using, write instructions.
}}
The Psyco Python JIT compiler should help speed up compilation times at the expense of memory use . It only works on 32-bit systems. To install, use
<pre>
sudo apt-get install python-psyco
</pre>

== Step 3 - Setting up for the BeagleBoard ==

Now let's setup <code>local.conf</code> for our needs:
<pre>
mkdir -p ${OETREE}/build/conf
cp ${OETREE}/openembedded/contrib/angstrom/local.conf ${OETREE}/build/conf/
</pre>
Open <code>${OETREE}/build/conf/local.conf</code> in your favourite editor and add the following to the end of the file.
<pre>
MACHINE ?= "beagleboard"
</pre>
Also, look at this block of lines:
<pre>
# Make use of SMP and fast disks
PARALLEL_MAKE = "-j4"
BB_NUMBER_THREADS = "4"
</pre>
Here you can tell it how many parallel threads to run. If you have several cores on your machine, make this number big. If you have only one core, you might be better performance setting it to 1. More details are [http://wiki.openembedded.org/index.php/Advanced_configuration here].

To save you a lot of time, it is useful to disable locale generation for all but the one you need. Add this to local.conf
<pre>
GLIBC_GENERATE_LOCALES = "en_US.UTF-8"
</pre>

== Step 4 - Start building ==

We need a small script to setup the environment, so download [http://www.rose-hulman.edu/~yoder/eLinux/files/source-me.txt source-me.txt] to ${OETREE}.
<pre>
#Go to the OpenEmbedded folder
cd ${OETREE}/openembedded

#Make sure it's up to date
git pull --rebase

#Set environment variables
cd ${OETREE}
source source-me.txt

#Start building
bitbake nano
</pre>

This will take a while. bitbake is installing everything that is needed to compile the system. This includes cross compilers, assemblers, source, everything. I started at 10am and ended around 5:30pm. It was running on just one of the two cores on my laptop. How long did it take on your machine? I notice that an additional 600M of disk space is being used.

{{Give
|title=Keep track of you running times and configurations.
|tip=We'll use this data to see what the best settings are.
}}

{| border="1" cellspacing="0" cellpadding="5"
|+ Initial <tt>bitbake nano</tt> runtime
! Processor
! Settings
! Run Time
|-
| T2600@2.16 GHz
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "2" Psyco? Yes. All Locals
| 2.5 hours
|-
| T2600@2.16 GHz
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "4" Psyco? Yes. US Only
| 73 minutes
|-
| E8400@3.00 GHz
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "4" Psyco? No.
| All Locals 1.4 hours US only 43 Minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "4" Psyco? No.
| 56.08 minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j8" BB_NUMBER_THREADS = "8" Psyco? No.
| 57.83 minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j4" BB_NUMBER_THREADS = "8" Psyco? No.
| 53.86 minutes
|-
| E5410@2.33 GHz (×2)
| PARALLEL_MAKE = "-j7" BB_NUMBER_THREADS = "7" Psyco? No.
| 61.75 minutes
|-
| T7600@2.33GHz (×2)
| PARALLEL_MAKE = "-j1" BB_NUMBER_THREADS = "1" Psyco? No (64-bit).
| 5412.14user 1446.15system 2:10:04elapsed 87%CPU (0avgtext+0avgdata 0maxresident)k 559896inputs+16591944outputs (2435major+323453596minor)pagefaults 0swaps
|}

== Step 5 - Building a complete image ==

Up to this point all we have done is load all the infrastructure needed and compiled the simple '''nano''' text editor. We don't even have the kernel yet. Do the following to build a basic console image.
<pre>
bitbake console-image
</pre>
'''This bitbake took 7 hours and 15 minutes.''' There are now some 7,700 directories with 67,000 files in the <code>oe</code> directory. An additional 1.5G of disk space is in use.

How did I know to use '''console-image'''? I ran the following to find what images were out there:
<pre>
locate image | grep /oe/
</pre>
This found every file with '''image''' in the name it that also had '''/oe/''' in the path. From this I see that '''oe/openembedded/recipes/images''' has a bunch of files ending in '''-image'''. Take a look at '''console-image.bb''' and see what you can figure out.

== Step 6 - Loading your SD card ==

The output of the bitbake command will ultimately be found under the <code>$OE_HOME/angstrom-dev/deploy/glibc/images/beagleboard</code>. In there you can find at least two interesting files:
<pre>
console-image-beagleboard.tar.bz2
uImage-beagleboard.bin
</pre>
The console image represents a full and self-contained file system, *including* a kernel. The uImage-beagleboard.bin is a Linux kernel image suitable for loading by the U-boot bootloader.

* Rename '''uImage-beagleboard.bin''' as '''uImage''' and load on your SD as before ([[Getting your Beagle running]]).
* Also load '''console-image-beagleboard.tar.bz2''' on the 2nd partition like you did before. Did you notice it untar's very quickly? Why?
* Boot and explore. What's there? What's missing?

Congratulations you've just build Linux from source. Try this:
<pre>
beagleboard login: root
root@beagleboard:~# cd /sys/class
root@beagleboard:/sys/class# ls -F
bdi/ hwmon/ misc/ scsi_generic/ usb_device/
block/ i2c-adapter/ mmc_host/ scsi_host/ usb_endpoint/
bluetooth/ i2c-dev/ mtd/ sound/ usb_host/
bmi/ ieee80211/ net/ spi_master/ usbmon/
display/ input/ regulator/ spidev/ vc/
firmware/ leds/ rtc/ thermal/ vtconsole/
gpio/ mdio_bus/ scsi_device/ tty/
graphics/ mem/ scsi_disk/ ubi/
</pre>
This is a list of low-level devices on the Beagle that you can access as files. Try:
<pre>
root@beagleboard:/sys/class# cd leds/
root@beagleboard:/sys/class/leds# ls -F
beagleboard::usr0@ beagleboard::usr1@
root@beagleboard:/sys/class/leds# cd beagleboard\:\:usr0
root@beagleboard:/sys/devices/platform/leds-gpio/leds/beagleboard::usr0# cat trigger
none nand-disk mmc0 mmc1 [heartbeat]
</pre>
This is a list of values you can assign to trigger. Notice LED0 is blinking on and off right now. Try:
<pre>
root@beagleboard:/sys/devices/platform/leds-gpio/leds/beagleboard::usr0# echo none > trigger
root@beagleboard:/sys/devices/platform/leds-gpio/leds/beagleboard::usr0# echo 1 > brightness
</pre>
What happens? Play around. [http://groups.google.com/group/beagleboard/msg/c623a16637625685?hl=en Here] are instructions on reading the '''USER''' switch. Try it. Can you make the LEDs blink in response to the button being pressed?

== Step 7 - Building a complete Beagle demo image ==

Now let's build the how demo we were running before. We'll do this via bitbake, but argument do we give it? Try looking in <code>oe/openembedded/recipes/images</code>, do you see a recipe that might work? Hint: It has beagle in the name. Here's what I tried.
<pre>
time bitbake beagle????-image
</pre>
Replace ???? with the recipe name you found. I added the '''time''' command so I could see how long it takes to run. My run took some 7.5 hours.

EBC Exercise 22 Cross-Compiling

2010-03-11T19:31:13Z

Jesionaj: Moved stuff to make slightly more sense

EBC Exercise 22 Cross-Compiling

2010-03-10T15:17:29Z

Jesionaj:

EBC Exercise 22 Cross-Compiling

2010-03-10T14:53:51Z

Jesionaj: Psyco info + bitbake table

EBC Exercise 22 Cross-Compiling

2010-03-10T12:19:03Z

Jesionaj: Mirror

Category:ECE597

2010-03-09T23:21:08Z

Jesionaj: Creating category page.

This category contains the relevant pages for the [[ECE597_-_32-bit_Embedded_Linux,_Rose-Hulman|ECE597]] course.

ECE497 Editing a Wiki

2010-03-09T11:20:26Z

Jesionaj:

Here is a wiki you can practice editing. Before you can edit it you will have to create an login. Pick something that will make it easy for me to identify you as part of my class. Then just add your name and date on the end of the table.

You can get help here: [[Help:Contents]].

{|
! Name
! Date
|-
| Mark A. Yoder
| 2-Mar-2010
|-
| Elliot Simon
| 8-Mar-2010
|-
| Mitch Garvin
| 8-Mar-2010
|-
| J. Cody Collins
| 8-Mar-2010
|-
| Steven Stark
| 8-Mar-2010
|-
| Brian Embry
| 8-Mar-2010
|-
| Qiang Jiang
| 8-Mar-2010
|-
| Jessica Lipscomb
| 8-Mar-2010
|-
| Chris Routh
| 8-Mar-2010
|-
| Paul Morrison
| 8-Mar-2010
|-
| David Baty
| 8-Mar-2010
|-
| Adam Jesionowski
| 9-Mar-2010
|}

[[Category:ECE597]]