eLinux.org - User contributions [en]

User:Routhcr

2010-05-21T03:53:37Z

Routhcr: /* Introduction */

[[Category:ECE597]]
= Introduction =
Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.
== Labs ==
Labs 1-7 are completed.

= Auto HUD Project =
[[ECE597: Auto HUD]]
*Created a index file generator which allowed for quicker training times, and multiple users to generate index files and pull them together.
*Trained Haarwavelet Cascades
*Created the camera interface and analyzing code.
*Worked with Gstreamer to get capture independent of X but to no luck so far.
*SEE PROJECT PAGE MOST DOCUMENTATION AND WORK WENT THERE

= Research on Random Topics =
*[[Executable and Linkable Format (ELF)]]
*[http://note.sonots.com/SciSoftware/haartraining.html | Haarwavelets]
*[http://opencv.willowgarage.com/wiki/ Opencv WIKI]

User:Routhcr

2010-05-21T03:52:27Z

Routhcr: /* Research on Random Topics */

[[Category:ECE597]]
= Introduction =
Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.
= Auto HUD Project =
[[ECE597: Auto HUD]]
*Created a index file generator which allowed for quicker training times, and multiple users to generate index files and pull them together.
*Trained Haarwavelet Cascades
*Created the camera interface and analyzing code.
*Worked with Gstreamer to get capture independent of X but to no luck so far.
*SEE PROJECT PAGE MOST DOCUMENTATION AND WORK WENT THERE

= Research on Random Topics =
*[[Executable and Linkable Format (ELF)]]
*[http://note.sonots.com/SciSoftware/haartraining.html | Haarwavelets]
*[http://opencv.willowgarage.com/wiki/ Opencv WIKI]

User:Routhcr

2010-05-21T03:50:48Z

Routhcr: /* Research on Random Topics */

User:Routhcr

2010-05-21T03:50:26Z

Routhcr: /* Research on Random Topics */

[[Category:ECE597]]
= Introduction =
Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.
= Auto HUD Project =
[[ECE597: Auto HUD]]
*Created a index file generator which allowed for quicker training times, and multiple users to generate index files and pull them together.
*Trained Haarwavelet Cascades
*Created the camera interface and analyzing code.
*Worked with Gstreamer to get capture independent of X but to no luck so far.
*SEE PROJECT PAGE MOST DOCUMENTATION AND WORK WENT THERE

= Research on Random Topics =
*[[Executable and Linkable Format (ELF)]]
*[[http://note.sonots.com/SciSoftware/haartraining.html | Haarwavelets]]

User:Routhcr

2010-05-21T03:49:40Z

Routhcr: /* Research on Random Topics */

[[Category:ECE597]]
= Introduction =
Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.
= Auto HUD Project =
[[ECE597: Auto HUD]]
*Created a index file generator which allowed for quicker training times, and multiple users to generate index files and pull them together.
*Trained Haarwavelet Cascades
*Created the camera interface and analyzing code.
*Worked with Gstreamer to get capture independent of X but to no luck so far.
*SEE PROJECT PAGE MOST DOCUMENTATION AND WORK WENT THERE

= Research on Random Topics =
*[[Executable and Linkable Format (ELF)]]
*[[http://note.sonots.com/SciSoftware/haartraining.html]]

User:Routhcr

2010-05-21T03:48:31Z

Routhcr: /* Auto HUD Project */

ECE597 Project Auto HUD

2010-05-21T03:46:32Z

Routhcr: /* OpenCV Haar Training */

[[category:ECE597]]

==Project Overview==
The goal of this project is to 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.

==Team Members==
[[user:routhcr | Chris Routh]]

[[user:collinjc | J. Cody Collins]]

[[user:jacksogc | Greg Jackson]]

Keqiong Xin

==Steps==
* Create Minimal Linux Image that can run OpenCV and run the display
* Determine hardware needed for the project
* Work on getting a camera functioning on the beagle board
* OpenCV running nativly on beagle with min config
* OpenCV working on video stream
* Projector working on Beagle
* Car integration (power)
* Algorithm development

==Installing OpenCV (Development Machine)==
This is a script that will install OpenCV on a debian-based development machine. The script will add the debian testing repositories and install OpenCV and its dependencies. The repositories are then removed to avoid conflicts with existing packages during regular updates.

<pre>
#!/bin/bash

echo "deb http://mirrors.kernel.org/debian/ testing main" > /tmp/opencv-temp.list
echo "deb-src http://mirrors.kernel.org/debian/ testing main" >> /tmp/opencv-temp.list
sudo mv /tmp/opencv-temp.list /etc/apt/sources.list.d/opencv-temp.list

sudo apt-get update
sudo apt-get install -y --allow-unauthenticated libcv4 libcv-dev libhighgui4 libhighgui-dev libcvaux4 libcvaux-dev

sudo rm -f /etc/apt/sources.list.d/opencv-temp.list

sudo apt-get update
</pre>

==Installing OpenCV on the Beagle==

Probably the easiest place to start is by using [http://www.angstrom-distribution.org/narcissus/ narcissus]. Choose beagleboard as the machine type and unstable for the release. In order for highgui to work (necessary for camera capture unless you are using GStreamer), you must build an image with X11 support. Therefore, choose X11 for the user environment. The choice for the X11 desktop environment is not critical, but it would be wise to choose something fairly lightweight, such as Enlightenment. It took several hours for Gnome to configure upon first boot. Once the filesystem has been extracted to a properly formatted SD card with an appropriate kernel on the boot partition (we tested this using 2.6.29), you should be able to boot. Upon boot, you will need to run opkg update. After this, you will need to run opkg install with the following packages:

* gcc
* gcc-dev
* binutils
* binutils-dev
* opencv
* opencv-dev
* g++

You should now be able to compile using:
<pre>
g++ signdetect.cpp -o signdetect -I /usr/include/opencv/ -L /usr/lib -lm -lcv -lhighgui -lcvaux
</pre>

==OpenCV Haar Training==
=== Gather Samples ===
Due to the large volume of sample data needed to create a effective Haar Cascade (about 1000 positive images) it is easier to gather video of a positive target and then break apart the video frame by frame and use the results as images. There are 2 two types of images, good and background. Both types of images are important in order for the cascade to be trained accurately.
=== Create Index File ===
There are two index files needing to be created in order for the system to train on the images, a background index file creating a list of filelocations, and a positive index file containing the positive file locations, the number of objects in the picture and the rectangular locations for the object.
==== Creating the Negative Index File ====
Use the following automated script from within the background images folder:
<pre>
#!/bin/bash

find ./*.jpg -maxdepth 2 -print > background.idx
find ./*.png -maxdepth 2 -print >> background.idx
find ./*.bmp -maxdepth 2 -print >> background.idx
find ./*.jpeg -maxdepth 2 -print >> background.idx
</pre>
==== Creating the Positive Index File ====
Use the following source code to create a training program that allows the user to click on the upper left and lower right of a object to select it and then press a key to return.
<pre>
////////////////////////////////////////////////////////////////////////
//
// Calibrate.cpp
// Date: 4/20/10
// Author: Christopher Routh
// This program brings up the necessary images and allows the user to
// select correct training spots for objects and generates a index file.
//
////////////////////////////////////////////////////////////////////////
#include <stdlib.h>
#include <stdio.h>
#include <math.h>
#include <cv.h>
#include <highgui.h>
#include <sys/types.h>
#include <dirent.h>
#include <errno.h>
#include <vector>
#include <string>
#include <iostream>
#include <fstream>

using namespace std;

static CvSize imageSize;
static CvPoint old_click_pt;
static CvPoint new_click_pt;
static std::vector<CvPoint> pointsClicked;

/*function... might want it in some class?*/
int getdir (std::string dir, std::vector<string> &files)
{
DIR *dp;
struct dirent *dirp;
if((dp = opendir(dir.c_str())) == NULL) {
std::cout << "Error(" << errno << ") opening " << dir << std::endl;
return errno;
}

while ((dirp = readdir(dp)) != NULL) {
files.push_back(string(dirp->d_name));
}
closedir(dp);
files.erase(files.begin(), files.begin()+2);
return 0;
}

// handle mouse clicks here
void mouse_callback(int event, int x, int y, int flags, void* obj)
{
if (event == CV_EVENT_LBUTTONDOWN)
{
cout << "(x,y) = (" << x << "," << y << ")" << endl;

// reset old_click_pt
old_click_pt.x = new_click_pt.x;
old_click_pt.y = new_click_pt.y;

// get new click point -- note the coordinate change in y
new_click_pt.x = x; // coming in from the window system
new_click_pt.y = imageSize.height-y; // window system and images have different y axes
pointsClicked.push_back(cvPoint(new_click_pt.x, new_click_pt.y));
}
}

int getCorrectObjectLocation(string file, vector<CvRect> &results)
{
IplImage* img = 0;
// load an image
cout << "Trying to load: " << file << endl;
img=cvLoadImage((file.insert(0, "./good/").c_str()));
if(!img){
printf("Could not load image file: %s\n",(file.insert(0, "./good/").c_str()));
exit(0);
}

// get the image data
int height = img->height;
int width = img->width;
int step = img->widthStep;
int channels = img->nChannels;
uchar* data = (uchar *)img->imageData;
printf("Processing a %dx%d image with %d channels\n",height,width,channels);

// create a window
cvNamedWindow("mainWin", CV_WINDOW_AUTOSIZE);

// show the image
cvShowImage("mainWin", img );

cvSetMouseCallback( "mainWin", mouse_callback );
// wait for a key
cvWaitKey(0);

int properClicks = pointsClicked.size() % 2;
if(properClicks != 0 || pointsClicked.size() == 0){

cout << "Improper Number of Points Clicked: " << pointsClicked.size() << " Selected" << endl;
return -1;

}else{

//Process new rectangles

for(unsigned int i = 0; i < pointsClicked.size(); i++){
cout << "Recieved Points X: " << pointsClicked.at(i).x << " Y: " << pointsClicked.at(i).y << endl;
}

for(unsigned int i = 0; i < pointsClicked.size(); i=i+2){
CvPoint topLeft = pointsClicked.at(i);
CvPoint bottomRight = pointsClicked.at(i+1);
results.push_back( cvRect(topLeft.x,abs(topLeft.y), (bottomRight.x - topLeft.x), abs((topLeft.y - bottomRight.y)) ) );
cout << "Rectangle Created --- X: " << topLeft.x << " Y: " << abs(topLeft.y) << " Width: " << (bottomRight.x - topLeft.x) << " Height: " << abs((topLeft.y - bottomRight.y)) << endl;
}

pointsClicked.clear();

}

// release the image
cvReleaseImage(&img );

return 0;
}

int main(int argc, char *argv[])
{
IplImage* img = 0;
int height,width,step,channels;
uchar *data;
int i,j,k;

string dir = string("./good/");
vector<string> files = vector<string>();
getdir(dir,files);
vector<CvRect> objectRects = vector<CvRect>();

ofstream vecFile;
vecFile.open ("./good/signs.idx");

for (unsigned int i = 0;i < files.size();i++) {
int success = getCorrectObjectLocation(files.at(i), objectRects);
if(success != 0){
i--;
pointsClicked.clear();
}else{

vecFile << "good/" << files.at(i) << " " << objectRects.size();

for(int j = 0; j < objectRects.size(); j++)
{
vecFile << " " << objectRects.at(j).x << " " << objectRects.at(j).y << " " << objectRects.at(j).width << " " << objectRects.at(j).height;
}

vecFile << endl;
objectRects.clear();

}
}

//Close the Vector File
vecFile.close();

cout << endl << endl << "****** INDEX FILE CREATED ******";
return 0;
}
</pre>
=== Generate Samples ===
Using the positive samples the creasamples cammand can apply transforms to the images and add them to the background images creating a wider range of images to train on. The syntax for this command is:
<pre>
Usage: ./createsamples
[-info <description_file_name>]
[-img <image_file_name>]
[-vec <vec_file_name>]
[-bg <background_file_name>]
[-num <number_of_samples = 1000>]
[-bgcolor <background_color = 0>]
[-inv] [-randinv] [-bgthresh <background_color_threshold = 80>]
[-maxidev <max_intensity_deviation = 40>]
[-maxxangle <max_x_rotation_angle = 1.100000>]
[-maxyangle <max_y_rotation_angle = 1.100000>]
[-maxzangle <max_z_rotation_angle = 0.500000>]
[-show [<scale = 4.000000>]]
[-w <sample_width = 24>]
[-h <sample_height = 24>]
</pre>
=== Run the Training Program ===
Commands differ based upon application and intended sample size, the command my group used was:
<pre>
opencv-haartraining -data signs_drivedata_rev1 -vec signs.vec -bg background.idx -nstages 20 -nsplits 2 -minhitrate 0.995 -maxfalsealarm .5 -npos 111 -nneg 2239 -w 40 -h 40 -nonsym -mem 512 -mode ALL
</pre>

==Display Buffer Mapping==
In order to get access to the display buffer on the beagle, you will need to run the following in U-Boot
<pre>
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait omapfb.mode=1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi omapfb.vram=0:10M,1:10M vram=20M
</pre>

Other sources have mentioned setting a value for mmcargs. However, we were not able to get it to work properly until the options were applied '''directly''' to the bootargs variable.

==Pico Projector Integration==
As of revision C4 of the Beagleboard there is no necessary configuration needed to display native resolution on the projector.

==Future Directions==
===GStreamer on the DSP===
There is a package available for the beagle called gst-dsp, which is a native GStreamer plug-in to give it access to the DSP. Along with gst-opamfb and the dsp-bridge driver, this should allow us to access the DSP directly and output video directly to the framebuffer. OpenCV can interact with GStreamer, so this appears to be a very promising direction for the project. See [http://felipec.wordpress.com/2009/10/13/new-project-gst-dsp-with-beagleboard-demo-image/ this article] for more information and a demonstration. That article also has a link to a minimal beagle image that provides a native framebuffer video player without requiring X.

ECE597 Project Auto HUD

2010-05-21T03:43:38Z

Routhcr: /* OpenCV Haar Training */

[[category:ECE597]]

==Project Overview==
The goal of this project is to 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.

==Team Members==
[[user:routhcr | Chris Routh]]

[[user:collinjc | J. Cody Collins]]

[[user:jacksogc | Greg Jackson]]

Keqiong Xin

==Steps==
* Create Minimal Linux Image that can run OpenCV and run the display
* Determine hardware needed for the project
* Work on getting a camera functioning on the beagle board
* OpenCV running nativly on beagle with min config
* OpenCV working on video stream
* Projector working on Beagle
* Car integration (power)
* Algorithm development

==Installing OpenCV (Development Machine)==
This is a script that will install OpenCV on a debian-based development machine. The script will add the debian testing repositories and install OpenCV and its dependencies. The repositories are then removed to avoid conflicts with existing packages during regular updates.

<pre>
#!/bin/bash

echo "deb http://mirrors.kernel.org/debian/ testing main" > /tmp/opencv-temp.list
echo "deb-src http://mirrors.kernel.org/debian/ testing main" >> /tmp/opencv-temp.list
sudo mv /tmp/opencv-temp.list /etc/apt/sources.list.d/opencv-temp.list

sudo apt-get update
sudo apt-get install -y --allow-unauthenticated libcv4 libcv-dev libhighgui4 libhighgui-dev libcvaux4 libcvaux-dev

sudo rm -f /etc/apt/sources.list.d/opencv-temp.list

sudo apt-get update
</pre>

==Installing OpenCV on the Beagle==

Probably the easiest place to start is by using [http://www.angstrom-distribution.org/narcissus/ narcissus]. Choose beagleboard as the machine type and unstable for the release. In order for highgui to work (necessary for camera capture unless you are using GStreamer), you must build an image with X11 support. Therefore, choose X11 for the user environment. The choice for the X11 desktop environment is not critical, but it would be wise to choose something fairly lightweight, such as Enlightenment. It took several hours for Gnome to configure upon first boot. Once the filesystem has been extracted to a properly formatted SD card with an appropriate kernel on the boot partition (we tested this using 2.6.29), you should be able to boot. Upon boot, you will need to run opkg update. After this, you will need to run opkg install with the following packages:

* gcc
* gcc-dev
* binutils
* binutils-dev
* opencv
* opencv-dev
* g++

You should now be able to compile using:
<pre>
g++ signdetect.cpp -o signdetect -I /usr/include/opencv/ -L /usr/lib -lm -lcv -lhighgui -lcvaux
</pre>

==OpenCV Haar Training==
=== Gather Samples ===
Due to the large volume of sample data needed to create a effective Haar Cascade (about 1000 positive images) it is easier to gather video of a positive target and then break apart the video frame by frame and use the results as images. There are 2 two types of images, good and background. Both types of images are important in order for the cascade to be trained accurately.
=== Create Index File ===
There are two index files needing to be created in order for the system to train on the images, a background index file creating a list of filelocations, and a positive index file containing the positive file locations, the number of objects in the picture and the rectangular locations for the object.
==== Creating the Negative Index File ====
Use the following automated script from within the background images folder:
<pre>
#!/bin/bash

find ./*.jpg -maxdepth 2 -print > background.idx
find ./*.png -maxdepth 2 -print >> background.idx
find ./*.bmp -maxdepth 2 -print >> background.idx
find ./*.jpeg -maxdepth 2 -print >> background.idx
</pre>
==== Creating the Positive Index File ====
Use the following source code to create a training program that allows the user to click on the upper left and lower right of a object to select it and then press a key to return.
<pre>
////////////////////////////////////////////////////////////////////////
//
// Calibrate.cpp
// Date: 4/20/10
// Author: Christopher Routh
// This program brings up the necessary images and allows the user to
// select correct training spots for objects and generates a index file.
//
////////////////////////////////////////////////////////////////////////
#include <stdlib.h>
#include <stdio.h>
#include <math.h>
#include <cv.h>
#include <highgui.h>
#include <sys/types.h>
#include <dirent.h>
#include <errno.h>
#include <vector>
#include <string>
#include <iostream>
#include <fstream>

using namespace std;

static CvSize imageSize;
static CvPoint old_click_pt;
static CvPoint new_click_pt;
static std::vector<CvPoint> pointsClicked;

/*function... might want it in some class?*/
int getdir (std::string dir, std::vector<string> &files)
{
DIR *dp;
struct dirent *dirp;
if((dp = opendir(dir.c_str())) == NULL) {
std::cout << "Error(" << errno << ") opening " << dir << std::endl;
return errno;
}

while ((dirp = readdir(dp)) != NULL) {
files.push_back(string(dirp->d_name));
}
closedir(dp);
files.erase(files.begin(), files.begin()+2);
return 0;
}

// handle mouse clicks here
void mouse_callback(int event, int x, int y, int flags, void* obj)
{
if (event == CV_EVENT_LBUTTONDOWN)
{
cout << "(x,y) = (" << x << "," << y << ")" << endl;

// reset old_click_pt
old_click_pt.x = new_click_pt.x;
old_click_pt.y = new_click_pt.y;

// get new click point -- note the coordinate change in y
new_click_pt.x = x; // coming in from the window system
new_click_pt.y = imageSize.height-y; // window system and images have different y axes
pointsClicked.push_back(cvPoint(new_click_pt.x, new_click_pt.y));
}
}

int getCorrectObjectLocation(string file, vector<CvRect> &results)
{
IplImage* img = 0;
// load an image
cout << "Trying to load: " << file << endl;
img=cvLoadImage((file.insert(0, "./good/").c_str()));
if(!img){
printf("Could not load image file: %s\n",(file.insert(0, "./good/").c_str()));
exit(0);
}

// get the image data
int height = img->height;
int width = img->width;
int step = img->widthStep;
int channels = img->nChannels;
uchar* data = (uchar *)img->imageData;
printf("Processing a %dx%d image with %d channels\n",height,width,channels);

// create a window
cvNamedWindow("mainWin", CV_WINDOW_AUTOSIZE);

// show the image
cvShowImage("mainWin", img );

cvSetMouseCallback( "mainWin", mouse_callback );
// wait for a key
cvWaitKey(0);

int properClicks = pointsClicked.size() % 2;
if(properClicks != 0 || pointsClicked.size() == 0){

cout << "Improper Number of Points Clicked: " << pointsClicked.size() << " Selected" << endl;
return -1;

}else{

//Process new rectangles

for(unsigned int i = 0; i < pointsClicked.size(); i++){
cout << "Recieved Points X: " << pointsClicked.at(i).x << " Y: " << pointsClicked.at(i).y << endl;
}

for(unsigned int i = 0; i < pointsClicked.size(); i=i+2){
CvPoint topLeft = pointsClicked.at(i);
CvPoint bottomRight = pointsClicked.at(i+1);
results.push_back( cvRect(topLeft.x,abs(topLeft.y), (bottomRight.x - topLeft.x), abs((topLeft.y - bottomRight.y)) ) );
cout << "Rectangle Created --- X: " << topLeft.x << " Y: " << abs(topLeft.y) << " Width: " << (bottomRight.x - topLeft.x) << " Height: " << abs((topLeft.y - bottomRight.y)) << endl;
}

pointsClicked.clear();

}

// release the image
cvReleaseImage(&img );

return 0;
}

int main(int argc, char *argv[])
{
IplImage* img = 0;
int height,width,step,channels;
uchar *data;
int i,j,k;

string dir = string("./good/");
vector<string> files = vector<string>();
getdir(dir,files);
vector<CvRect> objectRects = vector<CvRect>();

ofstream vecFile;
vecFile.open ("./good/signs.idx");

for (unsigned int i = 0;i < files.size();i++) {
int success = getCorrectObjectLocation(files.at(i), objectRects);
if(success != 0){
i--;
pointsClicked.clear();
}else{

vecFile << "good/" << files.at(i) << " " << objectRects.size();

for(int j = 0; j < objectRects.size(); j++)
{
vecFile << " " << objectRects.at(j).x << " " << objectRects.at(j).y << " " << objectRects.at(j).width << " " << objectRects.at(j).height;
}

vecFile << endl;
objectRects.clear();

}
}

//Close the Vector File
vecFile.close();

cout << endl << endl << "****** INDEX FILE CREATED ******";
return 0;
}
</pre>
=== Generate Samples ===
Using the positive samples the creasamples cammand can apply transforms to the images and add them to the background images creating a wider range of images to train on. The syntax for this command is:
<pre>
Usage: ./createsamples
[-info <description_file_name>]
[-img <image_file_name>]
[-vec <vec_file_name>]
[-bg <background_file_name>]
[-num <number_of_samples = 1000>]
[-bgcolor <background_color = 0>]
[-inv] [-randinv] [-bgthresh <background_color_threshold = 80>]
[-maxidev <max_intensity_deviation = 40>]
[-maxxangle <max_x_rotation_angle = 1.100000>]
[-maxyangle <max_y_rotation_angle = 1.100000>]
[-maxzangle <max_z_rotation_angle = 0.500000>]
[-show [<scale = 4.000000>]]
[-w <sample_width = 24>]
[-h <sample_height = 24>]
</pre>

==Display Buffer Mapping==
In order to get access to the display buffer on the beagle, you will need to run the following in U-Boot
<pre>
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait omapfb.mode=1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi omapfb.vram=0:10M,1:10M vram=20M
</pre>

Other sources have mentioned setting a value for mmcargs. However, we were not able to get it to work properly until the options were applied '''directly''' to the bootargs variable.

==Pico Projector Integration==
As of revision C4 of the Beagleboard there is no necessary configuration needed to display native resolution on the projector.

==Future Directions==
===GStreamer on the DSP===
There is a package available for the beagle called gst-dsp, which is a native GStreamer plug-in to give it access to the DSP. Along with gst-opamfb and the dsp-bridge driver, this should allow us to access the DSP directly and output video directly to the framebuffer. OpenCV can interact with GStreamer, so this appears to be a very promising direction for the project. See [http://felipec.wordpress.com/2009/10/13/new-project-gst-dsp-with-beagleboard-demo-image/ this article] for more information and a demonstration. That article also has a link to a minimal beagle image that provides a native framebuffer video player without requiring X.

ECE597 Project Auto HUD

2010-05-21T03:39:36Z

Routhcr: /* OpenCV Haar Training */

ECE597 Project Auto HUD

2010-05-21T03:34:12Z

Routhcr: /* OpenCV Haar Training */

ECE597 Project Auto HUD

2010-05-21T03:30:24Z

Routhcr: /* OpenCV Haar Training */

User:Routhcr

2010-05-21T03:22:03Z

Routhcr: /* Auto HUD Project */

[[Category:ECE597]]
= Introduction =
Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.
= Auto HUD Project =
*Created a index file generator which allowed for quicker training times, and multiple users to generate index files and pull them together.
*Trained Haarwavelet Cascades
*Created the camera interface and analyzing code.
*Worked with Gstreamer to get capture independent of X but to no luck so far.
*SEE PROJECT PAGE

= Research on Random Topics =
*[[Executable and Linkable Format (ELF)]]

User:Routhcr

2010-05-21T03:21:28Z

Routhcr: /* Auto HUD Project */

[[Category:ECE597]]
= Introduction =
Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.
= Auto HUD Project =
*Created a index file generator which allowed for quicker training times, and multiple users to generate index files and pull them together.
*Trained Haarwavelet Cascades
*Created the camera interface and analyzing code.
*Worked with Gstreamer to get capture independent of X but to no luck so far.

= Research on Random Topics =
*[[Executable and Linkable Format (ELF)]]

ECE597 Project Auto HUD

2010-05-19T18:10:18Z

Routhcr:

ECE597 Project Auto HUD

2010-04-20T20:14:48Z

Routhcr: moved ECE597: Auto HUD to ECE597 Project Auto HUD

Talk:ECE597 Project Auto HUD

2010-04-20T20:14:48Z

Routhcr: moved Talk:ECE597: Auto HUD to Talk:ECE597 Project Auto HUD

Assign dates and people to project tasks to create timeline

ECE597: Auto HUD

2010-04-20T20:14:48Z

Routhcr: moved ECE597: Auto HUD to ECE597 Project Auto HUD

#REDIRECT [[ECE597 Project Auto HUD]]

Talk:ECE597: Auto HUD

2010-04-20T20:14:48Z

Routhcr: moved Talk:ECE597: Auto HUD to Talk:ECE597 Project Auto HUD

#REDIRECT [[Talk:ECE597 Project Auto HUD]]

ECE597 Project Auto HUD

2010-04-20T20:13:47Z

Routhcr:

ECE597 BeagleBoard DSP Software Setup

2010-04-16T01:23:18Z

Routhcr: /* Rebuilding the DVSDK software for the target */

[[Category:ECE597]]

This is an adaptation of [http://wiki.davincidsp.com/index.php/GSG:_OMAP35x_DVEVM_Software_Setup GSG: OMAP35x_DVEVM Software Setup] for the BeagleBoard. Presently it's a work-in-progress. Follow the instructions and make corrections as you go. Change references to '''DVEVM''' to '''Beagle''' once you've tested a section and know it's correct. There are several links that pointed to pages on the original wiki. Fix them if you know how.

__TOC__

== Software Overview ==
To begin developing applications, you need to install the Beagle development environment. This section outlines the steps required to load the Beagle software onto the development host. You will need to download the files from the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page to get started.

The OMAP35x software approach provides interoperable, optimized, production-ready video and audio codecs that leverage DSP and integrated accelerators. These codecs are built into configurable frameworks, and are presented via published APIs within popular operating systems (such as Linux) for rapid software implementation.

The following software is provided in the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page.

* '''TI DVSDK Software.''' This includes demo applications, codec engine software, example codec servers, DVTB and DVSDK documentation. It contains the following files.
::* Getting Started Guide (this link)
::* DVSDK Product Release Notes
::* DVSDK Product Installer (dvsdk_#_##_##_##_Setup.bin)

* '''OMAP3525/OMAP3530 DVSDK Collaterals'''
::* Linux TSPA DSP Codec Server Installer (cs1omap3530_setupLinux_1_00_01-03.bin)
::* Linux TSPA DSP Codec Server Release Notes
::* Demonstration Multimedia Files-containing audio and video clips (data_dvsdk_#_##_##_##.tar.gz)
::* DVSDK OMAP3525/3530 Demo Overlay containing prebuilt DVSDK Binaries/Multimedia files. This should be added to an existing PSP file system (overlay_dvsdk_#_##_##_##.tar.gz)
::* Complete DVSDK file system including Pre-built DVSDK Binaries [overlay] and self starting DVSDK demos - suitable for NFS mount (nfs_dvsdk_#_##_##_##.tar.gz)
::* Complete DVSDK file system including Pre-built DVSDK Binaries [overlay] and self starting DVSDK demos - JFFS2 file system format [NAND flash] (rootfs_dvsdk_#_##_##_##.jffs2)
::* I don't know if these will work on the Beagle:
::** Prebuilt Kernel image for OMAP3525 and OMAP3530 default configuration (uImage-omap35x-evm.bin - Note that this is not a binary installer but needs to be renamed to uImage-omap35x-evm to use it for booting on OMAP3x EVM)
::** Prebuilt u-boot image for OMAP3525 and OMAP3530 default configuration (u-boot-omap35x-evm.bin)

* '''Linux Platform Support Package'''
::* PSP Release Notes
::* PSP User Guide
::* PSP Data Sheet
::* PSP Product Installer(AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.bin) - This installation file contains the linux source and binaries for OMAP35x platform and the necessary tools required for development on Linux for OMAP35x platform. This also contains the target file system

 

'''Command prompts in this guide'''

Commands are preceded by prompts that indicate the environment where the command is to be typed. For example:

;<tt>host $</tt> : Indicates command to be typed into the shell window of the host Linux workstation.
;<tt>Beagle #</tt> : Indicates commands to be typed into the U-Boot shell in a console window connected to the EVM board<nowiki>’</nowiki>s serial port. (see [http://wiki.davincidsp.com/index.php/GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program Setup Terminal Program] for EVM instructions. We need Beagle instructions).
;<tt>target $</tt> : Indicates commands to be typed into the Linux shell in the terminal window connected to the Beagle board's serial port.

 

'''NOTE: The document lists down various commands that needs to be executed on the target or on
the u-boot prompt for various operations required through out the document. Kindly note that a
direct copy and paste of these commands might result in insertion of lines for a single command.
Hence it would not work on the u-boot prompt or the target. Kindly ensure that you copy the long
commands into notepad, remove the line spaces between them and add a space wherever you
have removed the line spaces, before recopying and pasting it on the command prompts.'''
 

== '''Preparing to install''' ==

On a host system, copy the following .bin files from the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page to a temporary location with at least 2 GB free space. Since you can delete the installation files after installing the software, a directory like /tmp is recommended.

(I have copies of these that you can sftp from '''afs.rose-hulman.edu'''. They are in '''users/faculty/yoder/Public/beagle/downloads'''.)

*AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz
*dvsdk_#_##_##_##_Setup.bin
*xdctools_setuplinux_#_##_##.bin
*bios_setuplinux_#_##_##.bin
*TI-C6x-CGT-v#.#.##.#.bin
*cs1omap3530_setupLinux_#_##_##-##.bin
*overlay_dvsdk_#_##_##_##.tar.gz
*nfs_dvsdk_#_##_##_##.tar.gz
*rootfs_dvsdk_#_##_##_##.jffs2
*data_dvsdk_#_##_##_##.tar.gz

Ensure all the .bin files are set with executable permissions.
<pre>host $ chmod +x *.bin</pre>
 

== Installing the software ==

Installing the software used by the DVEVM involves performing the following steps:

*[[#Installing the Target Linux Software|Installing the Target Linux Software]]
*[[#Installing the DVSDK Software|Installing the DVSDK Software]]
*[[#Installing the A/V demo files|Installing the A/V demo files]]
*[[#Installing the toolchain|Installing the toolchain]]
*[[#Exporting a Shared File System for Target Access|Exporting a Shared File System for Target Access]]

 
=== Installing the Target Linux Software ===

This section explains how to install Linux for use on the target board.

Note that separate versions of Linux are used by the target and your host Linux workstation. The following Linux host operating systems have been used with the Beagle.

* Ubuntua 9.10, x86 32 bit

To install the Linux software, follow these steps:

<ol>
<li>Move AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz file (where ##.##.##.## is the current version number) from the temporary location that it was copied to your home directory.
<pre>host $ mv AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz /home/<useracct>
host $ cd
host $ tar xvzf AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz</pre>
<li>In future, all references in the document will assume that the user has installed the OMAP35x SDK using his user account and hence will refer to the OMAP35x SDK installation path as /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##</ol>
'''Note:''' The Linux Support Package (LSP) is a multi-platform LSP and is not configured for a particular platform. As shipped, this LSP cannot be used to build the demo or example applications. It must first be copied to a user area and configured/built for the Beagle. Please see the [[ECE597 BeagleBoard DSP Software Setup #Rebuilding_the_Linux_Kernel | Rebuilding the Linux Kernel]] section for instructions.
 

=== Installing the DVSDK Software ===

The TI DVSDK software includes demos, example software, Codec Engine components, DSP/BIOS Link, xDAIS and xDM header files, Local Power Manager Module, Framework Components and a contiguous memory allocator for Linux (CMEM). The DVSDK also contains the Digital Video Test Bench that enables testing the codecs and LSP with various configurations that are not possible with the Out of the Box demos.

'''Note:''' The installers for XDC, DSP/BIOS and Code Generation Tools (codegen) have a different default installation location. However, we strongly recommend that you change the default installation locations to place the components together (if you have not already installed the Linux versions of these components elsewhere). This simplifies the build setup steps.

To install the DVSDK software using the DVSDK Linux installer, follow these steps:

<ol>
<li>Log in using a user account. In the following steps, we refer to the home directory as "~".
<li>Execute the DVSDK installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./dvsdk_#_##_##_##_Setup.bin</pre>
The installer will start as a GUI application. Follow the instructions in the dialog boxes. You’ll be asked to agree to the End User License Agreement.
When you are prompted for an installation location, use the default installation location, that points to /home/<useracct>/dvsdk/dvsdk_#_##_##_##. This location will be used as the DVSDK installation folder through out this document.
<li>Execute the XDC installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./xdctools_setuplinux_#_##_##.bin</pre>
When you are prompted for an installation location, do not use the default installation location. Instead, install the software in the directory created in the previous step. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_##_##_##

NOTE: When prompted select '''Typical''' for the type of Setup.
<li>Execute the DSP/BIOS installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./bios_setuplinux_#_##_##.bin</pre>
When you are prompted for an installation location, do not use the default location. Instead, install the software in the directory created in step 2. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/bios_#_##_##_##
<li>Execute the Codec Server installer that you have previously downloaded from the DVSDK download page. For example:
<pre>host $ ./cs1omap3530_setupLinux_#_##_##-##.bin</pre>
When you are prompted for an installation location, install it in the location as specified or under the directory as created in step 2. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##_##
<li>Execute the Code Generation Tools installer that you previously downloaded from the DVSDK download page. The download link looked like TI-C6x-CGT-v#.#.##.#.bin; however the file you downloaded looked like ti_cgt_c6000_#.#.#_setup_linux_x86.bin. Run this file. For example:
<pre>host $ ./ti_cgt_c6000_#.#.#_setup_linux_x86.bin</pre>
When you are prompted for an installation location, install it in the location as specified or under the directory as created in step 2. If you are installing it under the DVSDK installation folder created in step 2, create a new folder under the dvsdk installation folder and then proceed to install. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##, where #_#_## is the version number.
<li>Remember to set the environment variable as directed by the installer. For example:
csh: (in the .cshrc file)
<pre>host $ setenv C6X_C_DIR /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/include:/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/lib</pre>
ksh or bash: (in the .bashrc file)
<pre>host $ export C6X_C_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/include:/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/lib</pre>
<li>You can now delete the .bin files that you loaded into the temporary directory.
</ol>
'''Note:''' You can uninstall these components by using the uninstall file in the respective installation directories. For example:
<pre>host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_#_#
host $ ./uninstall
</pre>
 

=== Installing the A/V demo files ===

'''These are very big, so I skipped them. --may'''

The TI DVSDK software installer, by itself does not contain the media files used by the demos. You can download the data files from DVSDK download page. Please use the steps mentioned below for extracting the media files into the desired location.

The Download page contains the Audio/Video files used by the demo. After following the instructions in the previous section, follow these instructions to install the A/V files:

<ol>
<li>Go to the DVSDK directory that you set up previously. For example
<pre>host $ cd ~/dvsdk/dvsdk_#_##_##_##/clips</pre>
<li>Copy the A/V data which you have downloaded from Download page to your DVSDK clips directory.For example:
<pre>host $ cp data_dvsdk_#_##_##_##.tar.gz .</pre>
<li>Extract the A/V data files. For example:
<pre>host $ tar -xvzf data_dvsdk_#_##_##_##.tar.gz</pre>
<li>Now you can delete the tar file from the clips folder.
</ol>

 

=== Installing the toolchain ===

This guide assumes use of the LITE version of the CodeSourcery toolchain.

==== Toolchain version to be used for DVSDK v3.01 ====
The toolchain used is ARM GNU/Linux EABI 2009q1. It can be downloaded from [http://www.codesourcery.com/sgpp/lite/arm/portal/package4571/public/arm-none-linux-gnueabi/arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 here]

[[Image:Codesourcery 2009q1.JPG|thumb|center|500px]]

To install the toolchain, follow the sequence below. These are to be executed on the Linux host platform.
<pre>
$ mkdir –p /home/<useracct>/toolchain
$ cp arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 /home/<useracct>/toolchain
$ cd /home/<useracct>/toolchain
$ tar -jxvf arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
$ rm arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
</pre>

=== I haven't tested these sections on use NFS ===

==== Exporting a Shared File System for Target Access ====

Although the board’s NAND flash contains a file system, during development it is more convenient to have the target board NFS mount a file system on a host Linux workstation. Once you test the application, you can store it on the board’s flash for a standalone demonstration.

Before the board can mount a target file system, you must export that target file system on the host Linux workstation. The file system uses an NFS (Network File System) server. The exported file system will contain the target file system and your executables.

To export the file system from your NFS server, perform the following steps. You only need to perform these steps once.

<ol>
<li>Log in with a user account on the host Linux workstation. (In the following steps, we refer to the home user directory as "~".)
<li>Perform the following commands to prepare a location for the OMAP35x EVM target file system.
<pre>host $ cd ~
host $ mkdir -p workdir/filesys
host $ cd workdir/filesys
</pre>
<li>Switch user to "root" on the host Linux workstation.
<pre>host $ su
password:
</pre>
There will be a prompt for entering the password as shown above. Type the root password, for getting the root permissions
<li>If you have already prepared a directory tree to use for the NFS root file-system (see Section [[#Rebuilding the NFS Image |Rebuilding the NFS Image]]) you can proceed to the next step. Otherwise, copy the prepared version(nfs_dvsdk_#_##_##_##.tar.gz) from the OMAP3530 DVSDK from the Download page to a new directory created in step 2. Perform the following commands.
'''Note:'''Un-tar the file with root permissions

<pre>$ cp /tmp/nfs_dvsdk_#_##_##_##.tar.gz .
$ tar –xvzf nfs_dvsdk_#_##_##_##.tar.gz
</pre>

<li>Make sure you can write into the opt folder in the file system by setting the permissions of the opt folder within the target file system with your user account. Perform the following command
<pre>host $ chown -R <useracct> /home/<useracct>/workdir/filesys/opt</pre>
Alternatively, if you want to have permissions to write or create folders within the target file system that you want to export as NFS, perform the following command
<pre>host $ chown -R <useracct> /home/<useracct>/workdir/filesys</pre>

<li>Make sure the NFS server is configured and functioning properly. Add the following line to the /etc/exports file of the server. Ensure you have root permission before editing this file.
<pre>/home/<useracct>/workdir/filesys *(rw,no_root_squash,no_all_squash,sync)</pre>

NOTE: On some systems you may wish to add the '''no_subtree_check''' option to avoid warnings like:
exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export <export listed here>.
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x

<li>Then issue the following command to notify the NFS server about the new exported directory.
<pre>
host $ /usr/sbin/exportfs –a
''' For Redhat Linux'''
host $ /sbin/service nfs restart
''' For Ubuntu'''
host $ /etc/init.d/nfs-kernel-server restart

</pre>

<li>Verify that the server firewall is turned off:
<pre>host $ /etc/init.d/iptables status</pre>
If the firewall is running, disable it:
<pre>host $ /etc/init.d/iptables stop</pre>
<li>Make sure you exit from having the root permissions after completing all the above steps
<pre>host $ exit</pre>
</ol>
 

==== Testing the shared file system ====

To test your NFS setup, follow these steps:
<ol>
<li>Get the IP address of your host Linux workstations as follows. Look for the IP address associated with the eth0 Ethernet port.
<pre>host $ /sbin/ifconfig</pre>

<li>Open a terminal emulation window to connect to the EVM board via RS-232 using the instructions in the [[GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program | Setup Terminal Program]] topic. If you have a Windows workstation, you can use HyperTerminal. If you have a Linux workstation, you might use Minicom. (You may need to turn on line wrap.)

<li>Power on the EVM board, and abort the automatic boot sequence by pressing a key in the console window. This gets you into the U-Boot prompt where you can configure how U-Boot will boot the Linux kernel.

<li>Set the following environment variables in the console window:
<pre>EVM # setenv nfshost <ip address of nfs host>
EVM # setenv rootpath <directory to mount></pre>
'''For DVSDK Releases from 3.00.00.36 upto and including 3.00.01.42, use the following bootargs:'''
<pre>EVM # setenv bootargs "console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=88M
omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y"</pre>
'''For DVSDK release 3.00.02.44, use the following bootargs:'''
<pre>EVM # setenv bootargs "console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=99M
mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y"</pre>

Note that the <tt>setenv bootargs</tt> command should be typed on a single line. Also note that you should avoid using the numeric keypad to enter numbers, as it can sometimes insert extra invisible characters. These environment variables must be typed in perfectly including capitals, if anything is typoed you will likely run into boot errors.

The ''<directory to mount>'' must match what you specified in Step 5 of the [[#Exporting a shared file system for target access| Exporting a shared file system for target access]] section. For example, <tt>/home/<user>/workdir/filesys</tt>.

'''Hints:''' If the kernel version stored in the NAND flash on the EVM is out of date you may wish to [[GSG:_OMAP35x_DVEVM_Additional_Procedures#Flashing_the_New_Linux_Kernel | flash the latest kernel image]] (using the uImage file in the /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##/images/kernel directory) or [[GSG:_OMAP35x_DVEVM_Additional_Procedures#Booting_via_TFTP_using_NFS_file_system | boot using TFTP]]

'''Hints:''' You may want to use the <tt>printenv</tt> command to print a list of your environment variables. You can also save these setenv commands in a .txt file from which you can paste them in the future.

<li>Save the environment so that you don't have to retype these commands every time you cycle power on the EVM board:
<pre>EVM # saveenv</pre>

<li>Boot the board using NFS:
<pre>EVM # boot</pre>

<li>You can now log in as "root" with no password required.

See the [[GSG:_OMAP35x DVEVM Additional Procedures#Alternate boot methods| Alternate boot methods]] section for information about booting with TFTP, NFS, or the board's NAND flash.
</ol>
 

=== Notes on using production codecs ===

As part of the OMAP35x DVSDK installation, you received a number of codecs:

* MPEG4 Simple Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* H.264 Base Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* MPEG2 Main Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* Sequential JPEG Decoder. This decoder is compliant with IIMGDEC1 Interface
* MPEG4 Simple Profile Encoder. This decoder is compliant with IVIDENC1 Interface
* H.264 Base Profile Encoder. This decoder is compliant with IVIDENC1 Interface
* JPEG Encoder. This encoder is compliant with IIMGENC1 Interface
* Advance Audio Codec (AAC) Decoder. This decoder supports both AAC-HE and AAC-LC configurations. It is compliant with IAUDDEC1 interface
* G.711 Speech Decoder. This decoder is compliant with ISPHDEC1 interface
* G.711 Speech Encoder. This encoder is compliant with ISPHENC1 interface

NOTE: Though the standalone codec server contain JPEG decode, the DVSDK decode demos do not support playback of JPEG streams. In order to evaluate these decoders, use Digital Video Test Bench (DVTB) which is included in the OMAP3530 DVSDK. The media files for MPEG2 MP and JPEG format streams are not available as part of the DVSDK installation, but they are available as part of data_dvsdk_#_##_##_##.tar.gz that can be downloaded from the OMAP software update site http://www.ti.com/omapsoftwareupdates
 

== Setting up the build/development environment ==
To set up the development and build environment, follow these steps:

<ol>
<li>Log in to your '''user''' account (and not as root) on the NFS host system.

<li>Add the /host/<useracct>/toolchain/<toolchain_version>/bin directory to your path. This is typically done by adding an additional line to your shell resource file (~/.bashrc). For the path given above, the line to add to your .bashrc file is:

<pre>export PATH=/home/<useracct>/toolchain/<toolchain_version>/bin:$PATH</pre>

This adds the CodeSourcery tools to your path and allows you to execute the tools using arm-none-linux-gnueabi-gcc (or other tools in the tool chain) from any directory.

<li>Remember to use the following command after modifying your .bashrc file. The source command essentially executes the .bashrc script so that the path you just added to it is added to your environment variables:

<pre>host $ source .bashrc</pre>

<li>You can test that the toolchain is installed correctly by starting a new shell and using the following command:
<pre>host $ arm-none-linux-gnueabi-gcc –v</pre>
When you execute this command, you will get an output like the one shown below.

<pre>Using built-in specs.
Target: arm-none-linux-gnueabi
Configured with: /scratch/sandra/lite/src/gcc-4.2/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --enable-shared --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion=Sourcery G++ Lite 2008q1-126 --with-bugurl=https://support.codesourcery.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/libc --enable-poison-system-directories --with-build-time-tools=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/bin
Thread model: posix
gcc version 4.2.3 (Sourcery G++ Lite 2008q1-126)
</pre>

</ol>
 
=== Writing a simple program and running it on the EVM ===
Make sure you have performed the steps in the [[#Exporting a shared file system for target access | Exporting a shared file system for target access ]] section and the [[#Setting up the build/development environment|Setting up the build/development environment]] section before continuing with the steps in this section.

Perform the following steps on the NFS host system as user (not as root):

<ol>
<li>
<pre>host $ mkdir –p ~/workdir/filesys/opt/hello</pre>

<li>
<pre>host $ cd ~/workdir/filesys/opt/hello</pre>

<li>Create a file called hello.c with the following contents:

<pre>#include <stdio.h>

int main() {
printf("Welcome to OMAP35x World!\n");
return 0;
}
</pre>

<li>Build the new C file:
<pre>host $ arm-none-linux-gnueabi-gcc hello.c -o hello</pre>

Perform the following steps on the target board. You may use either the target's console window (see [[GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program | Setup Terminal Program]]) or a telnet session.
</ol>
<ol>
<li>Move to the new directory on the target:

<pre>target $ cd /opt/hello</pre>

<li>Run the new executable:

<pre>./hello</pre>
</ol>

The output should be:

<pre>Welcome to OMAP35x World!</pre>
 

== Rebuilding the Software ==
This section describes how to rebuild pieces of the software delivery. Ensure that the toolchain setup and install has been completed (see [[#Installing the Toolchain|Installing the Toolchain]]).
 
=== Rebuilding U-boot ===
Rebuilding the U-boot is described in more detail in the LSP User’s Guide available at
AM35x-OMAP35x-PSP-SDK-##.##.##.##/docs/omap3530/UserGuide-##.##.##.##.pdf

Copy the U-Boot source archive from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/u-boot directory into your working directory

<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp /home/<useracct>/AM35x-OMAP35x-PSP-SDK-#.##.##.##/src/u-boot/u-boot-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the U-Boot source archive by performing the command given below.
<pre>host $ cd workdir/opt
host $ tar -zxvf u-boot-##.##.##.##.tar.gz
</pre>

To configure U-Boot for building, issue the following commands:
<pre>host $ cd uboot-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm distclean
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_config
</pre>

Once ready to build U-Boot, run the command:

<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm</pre>

The resulting U-Boot image named u-boot.bin will be in the current directory, ready to be loaded on the target.
 

=== Rebuilding the Linux Kernel ===
Rebuilding the kernel is described in more detail in the User’s Guide available at
AM35x-OMAP35x-PSP-SDK-##.##.##.##/docs/omap3530/UserGuide-##.##.##.##.pdf

Note that building the kernel requires using mkimage, a host side utility built by the u-boot makefile. If you have not already done so please build u-boot using the instructions in the [[ECE597 BeagleBoard DSP Software Setup #Rebuilding_U-boot | Rebuilding U-Boot section]]. You will need to build U-boot and place mkimage in your Path. A command like below can be used. If you are using a bash shell, kindly add the following in the .bashrc file in your user account.

<pre>export PATH=/<path_to_uboot>/tools:$PATH</pre>

Copy the Linux kernel source archive from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src directory into your working directory.
<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/kernel/linux-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the Linux kernel source archive by performing the commands given below.

<pre>host $ cd /home/<useracct>/workdir/opt
host $ tar -zxvf linux-##.##.##.##.tar.gz
</pre>

In order to prepare the kernel for building, follow these commands:

<pre>host $ cd linux-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_defconfig
</pre>

If you need to make changes to the default configuration, perform the following command.

<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm menuconfig</pre>

Once ready to build the kernel, run the following command
<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm uImage modules</pre>

The resulting kernel image uImage will be placed under arch/arm/boot and is ready to be loaded on the target.

Once the modules are built they must be installed on the target file system in order to be used. The following command will install the modules to the target file system and create the modules dependency file.

<pre>host $ su root
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- INSTALL_MOD_PATH=<target filesys dir> modules_install
</pre>

For example if you have been following the Getting Started Guide you should have created a target file system at /home/<useracct>/workdir/filesys. In the above command you should replace <target filesys dir> with /home/<useracct>/workdir/filesys.
 

=== Rebuilding the DVSDK software for the target ===
To place demo files in the /opt/dvsdk directory, you need to rebuild the DVSDK software. To do this, follow these steps:
<ol>
<li>If you have not already done so, rebuild the Linux kernel as described in the [[GSG:_OMAP35x_DVEVM_Software_Setup#Rebuilding_the_Linux_Kernel | Rebuilding the Linux Kernel]] section.

<li>Change directory to dvsdk_#_##_##_##.

<li>Edit the Rules.make file in the dvsdk_#_##_##_## directory.

<pre>host $ nano Rules.make</pre>

<li>Check the following directory definitions. If you installed components in the default locations, the directory definitions may already be correct, but you should verify them in any case.

<ul><li>Set PLATFORM to match your EVM board as follows (Note that this variable is case sensitive):

<pre>PLATFORM=omap3530</pre>

<li>Set DVSDK_INSTALL_DIR to the top-level DVSDK installation directory as follows, note that by default ${HOME} refers to your /home/<''useracct''> directory:

<pre>DVSDK_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##</pre>

<li>Modify the following variable as needed to match the location of XDCtools on your Linux host. We recommend that XDCtools be installed in the /home/<''useracct''>/dvsdk/dvsdk_#_##_##_## directory, but you may have installed it elsewhere.

<pre>XDC_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_##_##_##</pre>

<li>Make sure EXEC_DIR points to the opt directory on the NFS exported file system as follows. Refer [[#Exporting a Shared File System for Target Access|Exporting a Shared File System for Target Access]] for setting up the NFS exported file system.
<pre>EXEC_DIR=/home/<useracct>/workdir/filesys/opt/dvsdk/omap3530</pre>

<li>Make sure UBOOT_INSTALL_DIR is defined as follows so it points to where you copied the uboot source in the [[GSG:_OMAP35x_DVEVM_Software_Setup#Rebuilding_U-boot | Rebuilding U-Boot section]].

<pre>UBOOT_INSTALL_DIR=/home/<useracct>/workdir/opt/uboot-##.##.##.##</pre>

<li>Make sure LINUXKERNEL_INSTALL_DIR is defined as follows so it points to where you copied the Linux kernel tree in the Building a New Linux Kernel section.

<pre>LINUXKERNEL_INSTALL_DIR=/home/<useracct>/workdir/opt/linux-##.##.##.##</pre>

<li>Make sure OMAP3503_SDK_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>OMAP3503_SDK_INSTALL_DIR=/home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##</pre>

<li>Make sure CODEC_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>CODEC_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##</pre>
<li>Change the path of the CSTOOL_DIR to point to the location where you have installed the CodeSourcery tool-chain. (Refer [[#Installing the Toolchain|Installing the Toolchain]])

<pre>CSTOOL_DIR=/home/<useracct>/toolchain/<toolchain_version></pre>

<li>Make sure CODEGEN_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>CODEGEN_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##</pre>
<li>'''Note''' PSP_INSTALL_DIR donot need to be updated.They will be pointing to DVSDK installation directory.

<li>Check the path of all component installation directories to match the location where you want to point to. The default locations specified will choose the component versions as installed as part of the DVSDK installation

</ul>
<li>The top level DVSDK Makefile re-builds the kernel modules required by the DVSDK demonstration software (CMEM and LPM) and hence it is very important to at least perform the following commands (in case you have not performed the steps in [[#Rebuilding the Linux Kernel | Rebuilding the Linux Kernel]]), after extracting the Linux kernel source code in your work directory, whose path is provided in the top level DVSDK Rules.make. Refer section [[#Rebuilding the Linux Kernel | Rebuilding the Linux Kernel ]] for more details on “Rebuilding the Linux Kernel”.
<pre>host $ cd /home/<useracct>/workdir/opt/linux-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_defconfig
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm modules
</pre>
<li> Once the installation is complete please use the following commands to verify the paths set in Rules.make and components installed in DVSDK are proper.
<pre>host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##
host $ make check
host $ make info
</pre>

<li>While in the same directory that contains Rules.make, use the following commands to build the DVSDK demo applications and put the resulting binaries on the target file system specified by EXEC_DIR.
<pre>host $ make clean
host $ make all
host $ make install
</pre>
*'''Note :''' The '''make all''' command builds only the DVSDK demos, its dependent components and DVTB

<li>Additional commands for cleaning and building all the components are as mentioned below.
*'''Note :''' The PSP examples under AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/examples have to be extracted before using below commands
<pre>host $ make clobber
host $ make everything
</pre>
<li>For information on individually building the components please use the folowing command
*'''Note:'''Certain components have dependency on other components.So please make sure you have executed the '''make all''' command before proceeding for individual component build.
<pre>
host $ make help
</pre>
</ol>

'''NOTE:''' The dependencies for indivdual component builds are not addressed in the top level DVSDK Makefile. If you perform 'make clobber' or 'make clean' and then try building indivdual components like 'make dmai', the build will fail. Alternatively, if you perform 'make clobber' and then perform 'make everything', the build will go through. In addition to that, if you try cleaning the individual component and then build the same again, the build will go through. For example, after performing 'make everything', performing 'make dmai_clean' followed by 'make dmai' will work.
 

=== Rebuilding the DSP side server executables ===

The DSP side codec libraries are available under /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_## directory or if you have installed it in a different location specified by CODEC_INSTALL_DIR

The top level Makefile and the config.bld files are provided under the top level directory mentioned above. The codec binaries, header files as well as documents are RTSC packaged and available under /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##/packages/ti/sdo/codecs folder.

Ensure that the path settings for the DSP side code generation tools are set properly in the config.bld file

<pre>
C64P.rootDir = /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_# OR
C64P.rootDir=java.lang.System.getenv("CODEGEN_INSTALL_DIR");
cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##
host $ make clean
host $ make
</pre>

The rebuilt server executable can be found in the /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##/packages/ti/sdo/server/bin directory and is named cs.x64P.

The DSP side server executables can also be built from the DVSDK installation directory itself by following the below commands.

Ensure that DSP side code generation tools are set properly in the Rules.make in DVSDK installation directory

<pre>
CODEGEN_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##
</pre>

Re-building the Servers from DVSDK installation directory can be done using the following commands.

<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##
host $ make codecs_clean
host $ make codecs
host $ make install
</pre>
 
=== Rebuilding the Initial NAND X-loader ===

Copy the X-Loader source archive from OMAP35x-PSP-SDK-##.##.##.##/src/boot-strap directory into your working directory

<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp x-loader-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the X-Loader source archive by performing the following command.
<pre>
host $ cd /home/<useracct>/workdir/opt
host $ tar -zxvf x-loader-##.##.##.##.tar.gz
</pre>

Configure X-Loader for OMAP35x EVM target:
<pre>
host $ cd xloader-##.##.##.##
host $ make omap3evm_config
</pre>

To build X-Loader, run the command:
<pre>
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm
</pre>

The above command produces the x-load.bin file, but in order for the X-Loader to be loaded by the OMAP35x ROM bootloader, it needs to be signed with the signGP program from the AM35x-OMAP35x-PSP-SDK-##.##.##.##/host-tools/linux directory.

<pre>
host $ /home/<useracct>/AM35x-OMAP35x-PSP-SDK-#.##.##.##/host_tools/linux/signGP x-load.bin
</pre>

The resulting signed X-loader is named x-load.bin.ift and should be ready for the target.
For MMC/SD Card boot loading this file must be called MLO.

<pre>
host $ cp x-load.bin.ift MLO
</pre>
 
=== Rebuilding the Target-side UART Loader ===

Copy the UART loader dnld_util_target.tar.bz2 file from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/utils directory into your working directory.

<pre>
host $ cd ~
host $ mkdir –p workdir/opt
host $ cp dnld-util-target.tar.bz2 ~/workdir/opt/.
</pre>

Un-tar the UART loader by performing the following command.
<pre>
host $ tar -jxvf dnld_util_target.tar.bz2
host $ cd dnld_util_target
</pre>

Run the following command to build it.
<pre>
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm
</pre>

The resulting binary is called dnld_startup_omap3_evm.bin. This file is used with DownloadUtility.exe for UART peripheral boot.
 
=== Rebuilding the NFS Image ===

Kindly refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_NFS_Image]] (part of AM35x Getting Started Guide),for rebuilding NFS for AM35x SDK. This will contain different set of demos and sample applications.
The OMAP3535/OMAP3530 DVSDK installer has the script to (re)build the NFS image that includes the OMAP3525/OMAP3530 DVSDK demos under ~/dvsdk/dvsdk_#_##_##_##/targetfs folder.

In order to rebuild the NFS image with OMAP3530 DVSDK demos, make sure you have performed the steps in Section [[#GSG: _OMAP35x DVEVM Software Setup|OMAP35x DVEVM Software Setup]] and Section [[#Rebuilding the DVSDK Software for the target|Rebuilding the DVSDK Software for the target]].

'''NOTE:''' Also ensure that you have copied the overlay_dvsdk_#_##_##_##.tar.gz file to your /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs folder.

The following command removes the old the NFS tarball image:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_old_rootfs DVSDKVER=<your version number #_##_##_##>
</pre>

The following command will create the NFS tarball image:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make omap3530_dvsdk_nfs DVSDKVER=<your version number #_##_##_##>
</pre>

The following command will remove the NFS creation logs and the temporary NFS directory:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_nfs DVSDKVER=<your version number #_##_##_##>
</pre>
For any clarification about the procedure please perform the below command
<pre>host $ make –f targetfs_make help
</pre>

Executing above command requires the users to have sudo access. The linux host would prompt for the user password and the user needs to enter his password for the make to continue.
The user can make sure he has sudo access by including the following line in /etc/sudoers file.

<pre>
<useracct> ALL=(ALL) ALL</pre>

Executing above commands will create the new NFS file system with the DVSDK demo executables and all the media files required by the demonstrations.
You will see nfs_dvsdk_#_##_##_##.tar.gz created under the current folder ('''/home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs''').
 
=== Rebuilding the Full Ramdisk Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_Full_Ramdisk_Image]] (part of AM35x Getting Started Guide),for rebuilding full ramdisk image for AM35x SDK. This will contain different set of demos and sample applications.

The full ramdisk image cannot be built to include the OMAP3530 DVSDK demos as the ramdisk size requirement exceeds 40MB after the image is un-tarred and the bootargs given in step 5 in Section [[GSG:_OMAP35x DVEVM Additional Procedures#Running the Re-flash Procedure|Running the Re-flash Procedure]] will not work
 

=== Rebuilding the Minimal Ramdisk Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup]] (part of AM35x Getting Started Guide),for rebuilding minimal ramdisk image for AM35x SDK. The minimal ramdisk image does not contain any demos or examples.
 

=== Rebuilding the JFFS2 File-System Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_JFFS2_File-System_Image]] (part of AM35x Getting Started Guide),for rebuilding jffs2 image for AM35x SDK. This will contain different set of demos and sample applications.

The OMAP3525/OMAP3530 DVSDK installer has the pre-built JFFS2 root file system image that includes the OMAP3525/OMAP3530 DVSDK demos under ~/dvsdk/dvsdk_#_##_##_##/targetfs folder.

Check if the linux distribution on the host PC contains the mkfs.jffs2 utility. If not, download the binary from ftp://sources.redhat.com/pub/jffs2/mkfs.jffs2. Place this binary under /sbin directory in the Linux host development PC and ensure to include /sbin to the PATH environment variable in the .bashrc file.

In order to rebuild the JFFS2 root file system image with OMAP3530 DVSDK demos, make sure you have performed the steps in Section [[#GSG: _OMAP35x DVEVM Software Setup|OMAP35x DVEVM Software Setup]] and Section [[#Rebuilding the DVSDK Software for the target|Rebuilding the DVSDK Software for the target]]. Then, perform the following steps.

'''NOTE:''' Also ensure that you have copied the overlay_dvsdk_#_##_##_##.tar.gz file to your /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs folder.

Clean the old file system images:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_old_rootfs DVSDKVER=<your version number #_##_##_##>
</pre>

Create the JFFS2 Image (This requires building the NFS image to create the JFFS2 image from):
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make omap3530_dvsdk_jffs2 MKJFFS2=<your_jffs2_install_path> DVSDKVER=<your version number #_##_##_##>
</pre>

Clean up the temporary NFS file system directory:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_nfs DVSDKVER=<your version number #_##_##_##>
</pre>
For any clarification about the procedure please perform the below command
<pre>host $ make –f targetfs_make help
</pre>

Executing above commands requires the users to have sudo access. The linux host would prompt for the user password and the user needs to enter his password for the make to continue.

The user can make sure he has sudo access by including the following line in /etc/sudoers file.
<pre>
<useracct> ALL=(ALL) ALL</pre>

Executing above commands will create the new NFS and JFFS2 root file system with the DVSDK demo executables and all the media files required by the demonstrations.
You will see nfs_dvsdk_#_##_##_##.tar.gz and rootfs_dvsdk_#_##_##_##.jffs2 files created under the current folder ('''/home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs''').
 

== What's next? ==

The next chapter of this Getting Started Guide is [[GSG: OMAP35x DVEVM Additional Procedures]].

ECE597 BeagleBoard DSP Software Setup

2010-04-16T01:16:58Z

Routhcr:

[[Category:ECE597]]

This is an adaptation of [http://wiki.davincidsp.com/index.php/GSG:_OMAP35x_DVEVM_Software_Setup GSG: OMAP35x_DVEVM Software Setup] for the BeagleBoard. Presently it's a work-in-progress. Follow the instructions and make corrections as you go. Change references to '''DVEVM''' to '''Beagle''' once you've tested a section and know it's correct. There are several links that pointed to pages on the original wiki. Fix them if you know how.

__TOC__

== Software Overview ==
To begin developing applications, you need to install the Beagle development environment. This section outlines the steps required to load the Beagle software onto the development host. You will need to download the files from the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page to get started.

The OMAP35x software approach provides interoperable, optimized, production-ready video and audio codecs that leverage DSP and integrated accelerators. These codecs are built into configurable frameworks, and are presented via published APIs within popular operating systems (such as Linux) for rapid software implementation.

The following software is provided in the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page.

* '''TI DVSDK Software.''' This includes demo applications, codec engine software, example codec servers, DVTB and DVSDK documentation. It contains the following files.
::* Getting Started Guide (this link)
::* DVSDK Product Release Notes
::* DVSDK Product Installer (dvsdk_#_##_##_##_Setup.bin)

* '''OMAP3525/OMAP3530 DVSDK Collaterals'''
::* Linux TSPA DSP Codec Server Installer (cs1omap3530_setupLinux_1_00_01-03.bin)
::* Linux TSPA DSP Codec Server Release Notes
::* Demonstration Multimedia Files-containing audio and video clips (data_dvsdk_#_##_##_##.tar.gz)
::* DVSDK OMAP3525/3530 Demo Overlay containing prebuilt DVSDK Binaries/Multimedia files. This should be added to an existing PSP file system (overlay_dvsdk_#_##_##_##.tar.gz)
::* Complete DVSDK file system including Pre-built DVSDK Binaries [overlay] and self starting DVSDK demos - suitable for NFS mount (nfs_dvsdk_#_##_##_##.tar.gz)
::* Complete DVSDK file system including Pre-built DVSDK Binaries [overlay] and self starting DVSDK demos - JFFS2 file system format [NAND flash] (rootfs_dvsdk_#_##_##_##.jffs2)
::* I don't know if these will work on the Beagle:
::** Prebuilt Kernel image for OMAP3525 and OMAP3530 default configuration (uImage-omap35x-evm.bin - Note that this is not a binary installer but needs to be renamed to uImage-omap35x-evm to use it for booting on OMAP3x EVM)
::** Prebuilt u-boot image for OMAP3525 and OMAP3530 default configuration (u-boot-omap35x-evm.bin)

* '''Linux Platform Support Package'''
::* PSP Release Notes
::* PSP User Guide
::* PSP Data Sheet
::* PSP Product Installer(AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.bin) - This installation file contains the linux source and binaries for OMAP35x platform and the necessary tools required for development on Linux for OMAP35x platform. This also contains the target file system

 

'''Command prompts in this guide'''

Commands are preceded by prompts that indicate the environment where the command is to be typed. For example:

;<tt>host $</tt> : Indicates command to be typed into the shell window of the host Linux workstation.
;<tt>Beagle #</tt> : Indicates commands to be typed into the U-Boot shell in a console window connected to the EVM board<nowiki>’</nowiki>s serial port. (see [http://wiki.davincidsp.com/index.php/GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program Setup Terminal Program] for EVM instructions. We need Beagle instructions).
;<tt>target $</tt> : Indicates commands to be typed into the Linux shell in the terminal window connected to the Beagle board's serial port.

 

'''NOTE: The document lists down various commands that needs to be executed on the target or on
the u-boot prompt for various operations required through out the document. Kindly note that a
direct copy and paste of these commands might result in insertion of lines for a single command.
Hence it would not work on the u-boot prompt or the target. Kindly ensure that you copy the long
commands into notepad, remove the line spaces between them and add a space wherever you
have removed the line spaces, before recopying and pasting it on the command prompts.'''
 

== '''Preparing to install''' ==

On a host system, copy the following .bin files from the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page to a temporary location with at least 2 GB free space. Since you can delete the installation files after installing the software, a directory like /tmp is recommended.

(I have copies of these that you can sftp from '''afs.rose-hulman.edu'''. They are in '''users/faculty/yoder/Public/beagle/downloads'''.)

*AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz
*dvsdk_#_##_##_##_Setup.bin
*xdctools_setuplinux_#_##_##.bin
*bios_setuplinux_#_##_##.bin
*TI-C6x-CGT-v#.#.##.#.bin
*cs1omap3530_setupLinux_#_##_##-##.bin
*overlay_dvsdk_#_##_##_##.tar.gz
*nfs_dvsdk_#_##_##_##.tar.gz
*rootfs_dvsdk_#_##_##_##.jffs2
*data_dvsdk_#_##_##_##.tar.gz

Ensure all the .bin files are set with executable permissions.
<pre>host $ chmod +x *.bin</pre>
 

== Installing the software ==

Installing the software used by the DVEVM involves performing the following steps:

*[[#Installing the Target Linux Software|Installing the Target Linux Software]]
*[[#Installing the DVSDK Software|Installing the DVSDK Software]]
*[[#Installing the A/V demo files|Installing the A/V demo files]]
*[[#Installing the toolchain|Installing the toolchain]]
*[[#Exporting a Shared File System for Target Access|Exporting a Shared File System for Target Access]]

 
=== Installing the Target Linux Software ===

This section explains how to install Linux for use on the target board.

Note that separate versions of Linux are used by the target and your host Linux workstation. The following Linux host operating systems have been used with the Beagle.

* Ubuntua 9.10, x86 32 bit

To install the Linux software, follow these steps:

<ol>
<li>Move AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz file (where ##.##.##.## is the current version number) from the temporary location that it was copied to your home directory.
<pre>host $ mv AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz /home/<useracct>
host $ cd
host $ tar xvzf AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz</pre>
<li>In future, all references in the document will assume that the user has installed the OMAP35x SDK using his user account and hence will refer to the OMAP35x SDK installation path as /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##</ol>
'''Note:''' The Linux Support Package (LSP) is a multi-platform LSP and is not configured for a particular platform. As shipped, this LSP cannot be used to build the demo or example applications. It must first be copied to a user area and configured/built for the Beagle. Please see the [[ECE597 BeagleBoard DSP Software Setup #Rebuilding_the_Linux_Kernel | Rebuilding the Linux Kernel]] section for instructions.
 

=== Installing the DVSDK Software ===

The TI DVSDK software includes demos, example software, Codec Engine components, DSP/BIOS Link, xDAIS and xDM header files, Local Power Manager Module, Framework Components and a contiguous memory allocator for Linux (CMEM). The DVSDK also contains the Digital Video Test Bench that enables testing the codecs and LSP with various configurations that are not possible with the Out of the Box demos.

'''Note:''' The installers for XDC, DSP/BIOS and Code Generation Tools (codegen) have a different default installation location. However, we strongly recommend that you change the default installation locations to place the components together (if you have not already installed the Linux versions of these components elsewhere). This simplifies the build setup steps.

To install the DVSDK software using the DVSDK Linux installer, follow these steps:

<ol>
<li>Log in using a user account. In the following steps, we refer to the home directory as "~".
<li>Execute the DVSDK installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./dvsdk_#_##_##_##_Setup.bin</pre>
The installer will start as a GUI application. Follow the instructions in the dialog boxes. You’ll be asked to agree to the End User License Agreement.
When you are prompted for an installation location, use the default installation location, that points to /home/<useracct>/dvsdk/dvsdk_#_##_##_##. This location will be used as the DVSDK installation folder through out this document.
<li>Execute the XDC installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./xdctools_setuplinux_#_##_##.bin</pre>
When you are prompted for an installation location, do not use the default installation location. Instead, install the software in the directory created in the previous step. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_##_##_##

NOTE: When prompted select '''Typical''' for the type of Setup.
<li>Execute the DSP/BIOS installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./bios_setuplinux_#_##_##.bin</pre>
When you are prompted for an installation location, do not use the default location. Instead, install the software in the directory created in step 2. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/bios_#_##_##_##
<li>Execute the Codec Server installer that you have previously downloaded from the DVSDK download page. For example:
<pre>host $ ./cs1omap3530_setupLinux_#_##_##-##.bin</pre>
When you are prompted for an installation location, install it in the location as specified or under the directory as created in step 2. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##_##
<li>Execute the Code Generation Tools installer that you previously downloaded from the DVSDK download page. The download link looked like TI-C6x-CGT-v#.#.##.#.bin; however the file you downloaded looked like ti_cgt_c6000_#.#.#_setup_linux_x86.bin. Run this file. For example:
<pre>host $ ./ti_cgt_c6000_#.#.#_setup_linux_x86.bin</pre>
When you are prompted for an installation location, install it in the location as specified or under the directory as created in step 2. If you are installing it under the DVSDK installation folder created in step 2, create a new folder under the dvsdk installation folder and then proceed to install. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##, where #_#_## is the version number.
<li>Remember to set the environment variable as directed by the installer. For example:
csh: (in the .cshrc file)
<pre>host $ setenv C6X_C_DIR /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/include:/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/lib</pre>
ksh or bash: (in the .bashrc file)
<pre>host $ export C6X_C_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/include:/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/lib</pre>
<li>You can now delete the .bin files that you loaded into the temporary directory.
</ol>
'''Note:''' You can uninstall these components by using the uninstall file in the respective installation directories. For example:
<pre>host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_#_#
host $ ./uninstall
</pre>
 

=== Installing the A/V demo files ===

'''These are very big, so I skipped them. --may'''

The TI DVSDK software installer, by itself does not contain the media files used by the demos. You can download the data files from DVSDK download page. Please use the steps mentioned below for extracting the media files into the desired location.

The Download page contains the Audio/Video files used by the demo. After following the instructions in the previous section, follow these instructions to install the A/V files:

<ol>
<li>Go to the DVSDK directory that you set up previously. For example
<pre>host $ cd ~/dvsdk/dvsdk_#_##_##_##/clips</pre>
<li>Copy the A/V data which you have downloaded from Download page to your DVSDK clips directory.For example:
<pre>host $ cp data_dvsdk_#_##_##_##.tar.gz .</pre>
<li>Extract the A/V data files. For example:
<pre>host $ tar -xvzf data_dvsdk_#_##_##_##.tar.gz</pre>
<li>Now you can delete the tar file from the clips folder.
</ol>

 

=== Installing the toolchain ===

This guide assumes use of the LITE version of the CodeSourcery toolchain.

==== Toolchain version to be used for DVSDK v3.01 ====
The toolchain used is ARM GNU/Linux EABI 2009q1. It can be downloaded from [http://www.codesourcery.com/sgpp/lite/arm/portal/package4571/public/arm-none-linux-gnueabi/arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 here]

[[Image:Codesourcery 2009q1.JPG|thumb|center|500px]]

To install the toolchain, follow the sequence below. These are to be executed on the Linux host platform.
<pre>
$ mkdir –p /home/<useracct>/toolchain
$ cp arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 /home/<useracct>/toolchain
$ cd /home/<useracct>/toolchain
$ tar -jxvf arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
$ rm arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
</pre>

=== I haven't tested these sections on use NFS ===

==== Exporting a Shared File System for Target Access ====

Although the board’s NAND flash contains a file system, during development it is more convenient to have the target board NFS mount a file system on a host Linux workstation. Once you test the application, you can store it on the board’s flash for a standalone demonstration.

Before the board can mount a target file system, you must export that target file system on the host Linux workstation. The file system uses an NFS (Network File System) server. The exported file system will contain the target file system and your executables.

To export the file system from your NFS server, perform the following steps. You only need to perform these steps once.

<ol>
<li>Log in with a user account on the host Linux workstation. (In the following steps, we refer to the home user directory as "~".)
<li>Perform the following commands to prepare a location for the OMAP35x EVM target file system.
<pre>host $ cd ~
host $ mkdir -p workdir/filesys
host $ cd workdir/filesys
</pre>
<li>Switch user to "root" on the host Linux workstation.
<pre>host $ su
password:
</pre>
There will be a prompt for entering the password as shown above. Type the root password, for getting the root permissions
<li>If you have already prepared a directory tree to use for the NFS root file-system (see Section [[#Rebuilding the NFS Image |Rebuilding the NFS Image]]) you can proceed to the next step. Otherwise, copy the prepared version(nfs_dvsdk_#_##_##_##.tar.gz) from the OMAP3530 DVSDK from the Download page to a new directory created in step 2. Perform the following commands.
'''Note:'''Un-tar the file with root permissions

<pre>$ cp /tmp/nfs_dvsdk_#_##_##_##.tar.gz .
$ tar –xvzf nfs_dvsdk_#_##_##_##.tar.gz
</pre>

<li>Make sure you can write into the opt folder in the file system by setting the permissions of the opt folder within the target file system with your user account. Perform the following command
<pre>host $ chown -R <useracct> /home/<useracct>/workdir/filesys/opt</pre>
Alternatively, if you want to have permissions to write or create folders within the target file system that you want to export as NFS, perform the following command
<pre>host $ chown -R <useracct> /home/<useracct>/workdir/filesys</pre>

<li>Make sure the NFS server is configured and functioning properly. Add the following line to the /etc/exports file of the server. Ensure you have root permission before editing this file.
<pre>/home/<useracct>/workdir/filesys *(rw,no_root_squash,no_all_squash,sync)</pre>

NOTE: On some systems you may wish to add the '''no_subtree_check''' option to avoid warnings like:
exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export <export listed here>.
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x

<li>Then issue the following command to notify the NFS server about the new exported directory.
<pre>
host $ /usr/sbin/exportfs –a
''' For Redhat Linux'''
host $ /sbin/service nfs restart
''' For Ubuntu'''
host $ /etc/init.d/nfs-kernel-server restart

</pre>

<li>Verify that the server firewall is turned off:
<pre>host $ /etc/init.d/iptables status</pre>
If the firewall is running, disable it:
<pre>host $ /etc/init.d/iptables stop</pre>
<li>Make sure you exit from having the root permissions after completing all the above steps
<pre>host $ exit</pre>
</ol>
 

==== Testing the shared file system ====

To test your NFS setup, follow these steps:
<ol>
<li>Get the IP address of your host Linux workstations as follows. Look for the IP address associated with the eth0 Ethernet port.
<pre>host $ /sbin/ifconfig</pre>

<li>Open a terminal emulation window to connect to the EVM board via RS-232 using the instructions in the [[GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program | Setup Terminal Program]] topic. If you have a Windows workstation, you can use HyperTerminal. If you have a Linux workstation, you might use Minicom. (You may need to turn on line wrap.)

<li>Power on the EVM board, and abort the automatic boot sequence by pressing a key in the console window. This gets you into the U-Boot prompt where you can configure how U-Boot will boot the Linux kernel.

<li>Set the following environment variables in the console window:
<pre>EVM # setenv nfshost <ip address of nfs host>
EVM # setenv rootpath <directory to mount></pre>
'''For DVSDK Releases from 3.00.00.36 upto and including 3.00.01.42, use the following bootargs:'''
<pre>EVM # setenv bootargs "console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=88M
omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y"</pre>
'''For DVSDK release 3.00.02.44, use the following bootargs:'''
<pre>EVM # setenv bootargs "console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=99M
mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y"</pre>

Note that the <tt>setenv bootargs</tt> command should be typed on a single line. Also note that you should avoid using the numeric keypad to enter numbers, as it can sometimes insert extra invisible characters. These environment variables must be typed in perfectly including capitals, if anything is typoed you will likely run into boot errors.

The ''<directory to mount>'' must match what you specified in Step 5 of the [[#Exporting a shared file system for target access| Exporting a shared file system for target access]] section. For example, <tt>/home/<user>/workdir/filesys</tt>.

'''Hints:''' If the kernel version stored in the NAND flash on the EVM is out of date you may wish to [[GSG:_OMAP35x_DVEVM_Additional_Procedures#Flashing_the_New_Linux_Kernel | flash the latest kernel image]] (using the uImage file in the /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##/images/kernel directory) or [[GSG:_OMAP35x_DVEVM_Additional_Procedures#Booting_via_TFTP_using_NFS_file_system | boot using TFTP]]

'''Hints:''' You may want to use the <tt>printenv</tt> command to print a list of your environment variables. You can also save these setenv commands in a .txt file from which you can paste them in the future.

<li>Save the environment so that you don't have to retype these commands every time you cycle power on the EVM board:
<pre>EVM # saveenv</pre>

<li>Boot the board using NFS:
<pre>EVM # boot</pre>

<li>You can now log in as "root" with no password required.

See the [[GSG:_OMAP35x DVEVM Additional Procedures#Alternate boot methods| Alternate boot methods]] section for information about booting with TFTP, NFS, or the board's NAND flash.
</ol>
 

=== Notes on using production codecs ===

As part of the OMAP35x DVSDK installation, you received a number of codecs:

* MPEG4 Simple Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* H.264 Base Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* MPEG2 Main Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* Sequential JPEG Decoder. This decoder is compliant with IIMGDEC1 Interface
* MPEG4 Simple Profile Encoder. This decoder is compliant with IVIDENC1 Interface
* H.264 Base Profile Encoder. This decoder is compliant with IVIDENC1 Interface
* JPEG Encoder. This encoder is compliant with IIMGENC1 Interface
* Advance Audio Codec (AAC) Decoder. This decoder supports both AAC-HE and AAC-LC configurations. It is compliant with IAUDDEC1 interface
* G.711 Speech Decoder. This decoder is compliant with ISPHDEC1 interface
* G.711 Speech Encoder. This encoder is compliant with ISPHENC1 interface

NOTE: Though the standalone codec server contain JPEG decode, the DVSDK decode demos do not support playback of JPEG streams. In order to evaluate these decoders, use Digital Video Test Bench (DVTB) which is included in the OMAP3530 DVSDK. The media files for MPEG2 MP and JPEG format streams are not available as part of the DVSDK installation, but they are available as part of data_dvsdk_#_##_##_##.tar.gz that can be downloaded from the OMAP software update site http://www.ti.com/omapsoftwareupdates
 

== Setting up the build/development environment ==
To set up the development and build environment, follow these steps:

<ol>
<li>Log in to your '''user''' account (and not as root) on the NFS host system.

<li>Add the /host/<useracct>/toolchain/<toolchain_version>/bin directory to your path. This is typically done by adding an additional line to your shell resource file (~/.bashrc). For the path given above, the line to add to your .bashrc file is:

<pre>export PATH=/home/<useracct>/toolchain/<toolchain_version>/bin:$PATH</pre>

This adds the CodeSourcery tools to your path and allows you to execute the tools using arm-none-linux-gnueabi-gcc (or other tools in the tool chain) from any directory.

<li>Remember to use the following command after modifying your .bashrc file. The source command essentially executes the .bashrc script so that the path you just added to it is added to your environment variables:

<pre>host $ source .bashrc</pre>

<li>You can test that the toolchain is installed correctly by starting a new shell and using the following command:
<pre>host $ arm-none-linux-gnueabi-gcc –v</pre>
When you execute this command, you will get an output like the one shown below.

<pre>Using built-in specs.
Target: arm-none-linux-gnueabi
Configured with: /scratch/sandra/lite/src/gcc-4.2/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --enable-shared --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion=Sourcery G++ Lite 2008q1-126 --with-bugurl=https://support.codesourcery.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/libc --enable-poison-system-directories --with-build-time-tools=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/bin
Thread model: posix
gcc version 4.2.3 (Sourcery G++ Lite 2008q1-126)
</pre>

</ol>
 
=== Writing a simple program and running it on the EVM ===
Make sure you have performed the steps in the [[#Exporting a shared file system for target access | Exporting a shared file system for target access ]] section and the [[#Setting up the build/development environment|Setting up the build/development environment]] section before continuing with the steps in this section.

Perform the following steps on the NFS host system as user (not as root):

<ol>
<li>
<pre>host $ mkdir –p ~/workdir/filesys/opt/hello</pre>

<li>
<pre>host $ cd ~/workdir/filesys/opt/hello</pre>

<li>Create a file called hello.c with the following contents:

<pre>#include <stdio.h>

int main() {
printf("Welcome to OMAP35x World!\n");
return 0;
}
</pre>

<li>Build the new C file:
<pre>host $ arm-none-linux-gnueabi-gcc hello.c -o hello</pre>

Perform the following steps on the target board. You may use either the target's console window (see [[GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program | Setup Terminal Program]]) or a telnet session.
</ol>
<ol>
<li>Move to the new directory on the target:

<pre>target $ cd /opt/hello</pre>

<li>Run the new executable:

<pre>./hello</pre>
</ol>

The output should be:

<pre>Welcome to OMAP35x World!</pre>
 

== Rebuilding the Software ==
This section describes how to rebuild pieces of the software delivery. Ensure that the toolchain setup and install has been completed (see [[#Installing the Toolchain|Installing the Toolchain]]).
 
=== Rebuilding U-boot ===
Rebuilding the U-boot is described in more detail in the LSP User’s Guide available at
AM35x-OMAP35x-PSP-SDK-##.##.##.##/docs/omap3530/UserGuide-##.##.##.##.pdf

Copy the U-Boot source archive from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/u-boot directory into your working directory

<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp /home/<useracct>/AM35x-OMAP35x-PSP-SDK-#.##.##.##/src/u-boot/u-boot-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the U-Boot source archive by performing the command given below.
<pre>host $ cd workdir/opt
host $ tar -zxvf u-boot-##.##.##.##.tar.gz
</pre>

To configure U-Boot for building, issue the following commands:
<pre>host $ cd uboot-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm distclean
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_config
</pre>

Once ready to build U-Boot, run the command:

<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm</pre>

The resulting U-Boot image named u-boot.bin will be in the current directory, ready to be loaded on the target.
 

=== Rebuilding the Linux Kernel ===
Rebuilding the kernel is described in more detail in the User’s Guide available at
AM35x-OMAP35x-PSP-SDK-##.##.##.##/docs/omap3530/UserGuide-##.##.##.##.pdf

Note that building the kernel requires using mkimage, a host side utility built by the u-boot makefile. If you have not already done so please build u-boot using the instructions in the [[ECE597 BeagleBoard DSP Software Setup #Rebuilding_U-boot | Rebuilding U-Boot section]]. You will need to build U-boot and place mkimage in your Path. A command like below can be used. If you are using a bash shell, kindly add the following in the .bashrc file in your user account.

<pre>export PATH=/<path_to_uboot>/tools:$PATH</pre>

Copy the Linux kernel source archive from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src directory into your working directory.
<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/kernel/linux-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the Linux kernel source archive by performing the commands given below.

<pre>host $ cd /home/<useracct>/workdir/opt
host $ tar -zxvf linux-##.##.##.##.tar.gz
</pre>

In order to prepare the kernel for building, follow these commands:

<pre>host $ cd linux-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_defconfig
</pre>

If you need to make changes to the default configuration, perform the following command.

<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm menuconfig</pre>

Once ready to build the kernel, run the following command
<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm uImage modules</pre>

The resulting kernel image uImage will be placed under arch/arm/boot and is ready to be loaded on the target.

Once the modules are built they must be installed on the target file system in order to be used. The following command will install the modules to the target file system and create the modules dependency file.

<pre>host $ su root
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- INSTALL_MOD_PATH=<target filesys dir> modules_install
</pre>

For example if you have been following the Getting Started Guide you should have created a target file system at /home/<useracct>/workdir/filesys. In the above command you should replace <target filesys dir> with /home/<useracct>/workdir/filesys.
 

=== Rebuilding the DVSDK software for the target ===
To place demo files in the /opt/dvsdk directory, you need to rebuild the DVSDK software. To do this, follow these steps:
<ol>
<li>If you have not already done so, rebuild the Linux kernel as described in the [[GSG:_OMAP35x_DVEVM_Software_Setup#Rebuilding_the_Linux_Kernel | Rebuilding the Linux Kernel]] section.

<li>Change directory to dvsdk_#_##_##_##.

<li>Edit the Rules.make file in the dvsdk_#_##_##_## directory.

<pre>host $ vi Rules.make</pre>

<li>Check the following directory definitions. If you installed components in the default locations, the directory definitions may already be correct, but you should verify them in any case.

<ul><li>Set PLATFORM to match your EVM board as follows (Note that this variable is case sensitive):

<pre>PLATFORM=omap3530</pre>

<li>Set DVSDK_INSTALL_DIR to the top-level DVSDK installation directory as follows, note that by default ${HOME} refers to your /home/<''useracct''> directory:

<pre>DVSDK_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##</pre>

<li>Modify the following variable as needed to match the location of XDCtools on your Linux host. We recommend that XDCtools be installed in the /home/<''useracct''>/dvsdk/dvsdk_#_##_##_## directory, but you may have installed it elsewhere.

<pre>XDC_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_##_##_##</pre>

<li>Make sure EXEC_DIR points to the opt directory on the NFS exported file system as follows. Refer [[#Exporting a Shared File System for Target Access|Exporting a Shared File System for Target Access]] for setting up the NFS exported file system.
<pre>EXEC_DIR=/home/<useracct>/workdir/filesys/opt/dvsdk/omap3530</pre>

<li>Make sure UBOOT_INSTALL_DIR is defined as follows so it points to where you copied the uboot source in the [[GSG:_OMAP35x_DVEVM_Software_Setup#Rebuilding_U-boot | Rebuilding U-Boot section]].

<pre>UBOOT_INSTALL_DIR=/home/<useracct>/workdir/opt/uboot-##.##.##.##</pre>

<li>Make sure LINUXKERNEL_INSTALL_DIR is defined as follows so it points to where you copied the Linux kernel tree in the Building a New Linux Kernel section.

<pre>LINUXKERNEL_INSTALL_DIR=/home/<useracct>/workdir/opt/linux-##.##.##.##</pre>

<li>Make sure OMAP3503_SDK_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>OMAP3503_SDK_INSTALL_DIR=/home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##</pre>

<li>Make sure CODEC_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>CODEC_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##</pre>
<li>Change the path of the CSTOOL_DIR to point to the location where you have installed the CodeSourcery tool-chain. (Refer [[#Installing the Toolchain|Installing the Toolchain]])

<pre>CSTOOL_DIR=/home/<useracct>/toolchain/<toolchain_version></pre>

<li>Make sure CODEGEN_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>CODEGEN_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##</pre>
<li>'''Note''' PSP_INSTALL_DIR donot need to be updated.They will be pointing to DVSDK installation directory.

<li>Check the path of all component installation directories to match the location where you want to point to. The default locations specified will choose the component versions as installed as part of the DVSDK installation

</ul>
<li>The top level DVSDK Makefile re-builds the kernel modules required by the DVSDK demonstration software (CMEM and LPM) and hence it is very important to at least perform the following commands (in case you have not performed the steps in [[#Rebuilding the Linux Kernel | Rebuilding the Linux Kernel]]), after extracting the Linux kernel source code in your work directory, whose path is provided in the top level DVSDK Rules.make. Refer section [[#Rebuilding the Linux Kernel | Rebuilding the Linux Kernel ]] for more details on “Rebuilding the Linux Kernel”.
<pre>host $ cd /home/<useracct>/workdir/opt/linux-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_defconfig
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm modules
</pre>
<li> Once the installation is complete please use the following commands to verify the paths set in Rules.make and components installed in DVSDK are proper.
<pre>host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##
host $ make check
host $ make info
</pre>

<li>While in the same directory that contains Rules.make, use the following commands to build the DVSDK demo applications and put the resulting binaries on the target file system specified by EXEC_DIR.
<pre>host $ make clean
host $ make all
host $ make install
</pre>
*'''Note :''' The '''make all''' command builds only the DVSDK demos, its dependent components and DVTB

<li>Additional commands for cleaning and building all the components are as mentioned below.
*'''Note :''' The PSP examples under AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/examples have to be extracted before using below commands
<pre>host $ make clobber
host $ make everything
</pre>
<li>For information on individually building the components please use the folowing command
*'''Note:'''Certain components have dependency on other components.So please make sure you have executed the '''make all''' command before proceeding for individual component build.
<pre>
host $ make help
</pre>
</ol>

'''NOTE:''' The dependencies for indivdual component builds are not addressed in the top level DVSDK Makefile. If you perform 'make clobber' or 'make clean' and then try building indivdual components like 'make dmai', the build will fail. Alternatively, if you perform 'make clobber' and then perform 'make everything', the build will go through. In addition to that, if you try cleaning the individual component and then build the same again, the build will go through. For example, after performing 'make everything', performing 'make dmai_clean' followed by 'make dmai' will work.
 

=== Rebuilding the DSP side server executables ===

The DSP side codec libraries are available under /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_## directory or if you have installed it in a different location specified by CODEC_INSTALL_DIR

The top level Makefile and the config.bld files are provided under the top level directory mentioned above. The codec binaries, header files as well as documents are RTSC packaged and available under /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##/packages/ti/sdo/codecs folder.

Ensure that the path settings for the DSP side code generation tools are set properly in the config.bld file

<pre>
C64P.rootDir = /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_# OR
C64P.rootDir=java.lang.System.getenv("CODEGEN_INSTALL_DIR");
cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##
host $ make clean
host $ make
</pre>

The rebuilt server executable can be found in the /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##/packages/ti/sdo/server/bin directory and is named cs.x64P.

The DSP side server executables can also be built from the DVSDK installation directory itself by following the below commands.

Ensure that DSP side code generation tools are set properly in the Rules.make in DVSDK installation directory

<pre>
CODEGEN_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##
</pre>

Re-building the Servers from DVSDK installation directory can be done using the following commands.

<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##
host $ make codecs_clean
host $ make codecs
host $ make install
</pre>
 
=== Rebuilding the Initial NAND X-loader ===

Copy the X-Loader source archive from OMAP35x-PSP-SDK-##.##.##.##/src/boot-strap directory into your working directory

<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp x-loader-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the X-Loader source archive by performing the following command.
<pre>
host $ cd /home/<useracct>/workdir/opt
host $ tar -zxvf x-loader-##.##.##.##.tar.gz
</pre>

Configure X-Loader for OMAP35x EVM target:
<pre>
host $ cd xloader-##.##.##.##
host $ make omap3evm_config
</pre>

To build X-Loader, run the command:
<pre>
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm
</pre>

The above command produces the x-load.bin file, but in order for the X-Loader to be loaded by the OMAP35x ROM bootloader, it needs to be signed with the signGP program from the AM35x-OMAP35x-PSP-SDK-##.##.##.##/host-tools/linux directory.

<pre>
host $ /home/<useracct>/AM35x-OMAP35x-PSP-SDK-#.##.##.##/host_tools/linux/signGP x-load.bin
</pre>

The resulting signed X-loader is named x-load.bin.ift and should be ready for the target.
For MMC/SD Card boot loading this file must be called MLO.

<pre>
host $ cp x-load.bin.ift MLO
</pre>
 
=== Rebuilding the Target-side UART Loader ===

Copy the UART loader dnld_util_target.tar.bz2 file from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/utils directory into your working directory.

<pre>
host $ cd ~
host $ mkdir –p workdir/opt
host $ cp dnld-util-target.tar.bz2 ~/workdir/opt/.
</pre>

Un-tar the UART loader by performing the following command.
<pre>
host $ tar -jxvf dnld_util_target.tar.bz2
host $ cd dnld_util_target
</pre>

Run the following command to build it.
<pre>
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm
</pre>

The resulting binary is called dnld_startup_omap3_evm.bin. This file is used with DownloadUtility.exe for UART peripheral boot.
 
=== Rebuilding the NFS Image ===

Kindly refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_NFS_Image]] (part of AM35x Getting Started Guide),for rebuilding NFS for AM35x SDK. This will contain different set of demos and sample applications.
The OMAP3535/OMAP3530 DVSDK installer has the script to (re)build the NFS image that includes the OMAP3525/OMAP3530 DVSDK demos under ~/dvsdk/dvsdk_#_##_##_##/targetfs folder.

In order to rebuild the NFS image with OMAP3530 DVSDK demos, make sure you have performed the steps in Section [[#GSG: _OMAP35x DVEVM Software Setup|OMAP35x DVEVM Software Setup]] and Section [[#Rebuilding the DVSDK Software for the target|Rebuilding the DVSDK Software for the target]].

'''NOTE:''' Also ensure that you have copied the overlay_dvsdk_#_##_##_##.tar.gz file to your /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs folder.

The following command removes the old the NFS tarball image:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_old_rootfs DVSDKVER=<your version number #_##_##_##>
</pre>

The following command will create the NFS tarball image:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make omap3530_dvsdk_nfs DVSDKVER=<your version number #_##_##_##>
</pre>

The following command will remove the NFS creation logs and the temporary NFS directory:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_nfs DVSDKVER=<your version number #_##_##_##>
</pre>
For any clarification about the procedure please perform the below command
<pre>host $ make –f targetfs_make help
</pre>

Executing above command requires the users to have sudo access. The linux host would prompt for the user password and the user needs to enter his password for the make to continue.
The user can make sure he has sudo access by including the following line in /etc/sudoers file.

<pre>
<useracct> ALL=(ALL) ALL</pre>

Executing above commands will create the new NFS file system with the DVSDK demo executables and all the media files required by the demonstrations.
You will see nfs_dvsdk_#_##_##_##.tar.gz created under the current folder ('''/home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs''').
 
=== Rebuilding the Full Ramdisk Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_Full_Ramdisk_Image]] (part of AM35x Getting Started Guide),for rebuilding full ramdisk image for AM35x SDK. This will contain different set of demos and sample applications.

The full ramdisk image cannot be built to include the OMAP3530 DVSDK demos as the ramdisk size requirement exceeds 40MB after the image is un-tarred and the bootargs given in step 5 in Section [[GSG:_OMAP35x DVEVM Additional Procedures#Running the Re-flash Procedure|Running the Re-flash Procedure]] will not work
 

=== Rebuilding the Minimal Ramdisk Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup]] (part of AM35x Getting Started Guide),for rebuilding minimal ramdisk image for AM35x SDK. The minimal ramdisk image does not contain any demos or examples.
 

=== Rebuilding the JFFS2 File-System Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_JFFS2_File-System_Image]] (part of AM35x Getting Started Guide),for rebuilding jffs2 image for AM35x SDK. This will contain different set of demos and sample applications.

The OMAP3525/OMAP3530 DVSDK installer has the pre-built JFFS2 root file system image that includes the OMAP3525/OMAP3530 DVSDK demos under ~/dvsdk/dvsdk_#_##_##_##/targetfs folder.

Check if the linux distribution on the host PC contains the mkfs.jffs2 utility. If not, download the binary from ftp://sources.redhat.com/pub/jffs2/mkfs.jffs2. Place this binary under /sbin directory in the Linux host development PC and ensure to include /sbin to the PATH environment variable in the .bashrc file.

In order to rebuild the JFFS2 root file system image with OMAP3530 DVSDK demos, make sure you have performed the steps in Section [[#GSG: _OMAP35x DVEVM Software Setup|OMAP35x DVEVM Software Setup]] and Section [[#Rebuilding the DVSDK Software for the target|Rebuilding the DVSDK Software for the target]]. Then, perform the following steps.

'''NOTE:''' Also ensure that you have copied the overlay_dvsdk_#_##_##_##.tar.gz file to your /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs folder.

Clean the old file system images:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_old_rootfs DVSDKVER=<your version number #_##_##_##>
</pre>

Create the JFFS2 Image (This requires building the NFS image to create the JFFS2 image from):
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make omap3530_dvsdk_jffs2 MKJFFS2=<your_jffs2_install_path> DVSDKVER=<your version number #_##_##_##>
</pre>

Clean up the temporary NFS file system directory:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_nfs DVSDKVER=<your version number #_##_##_##>
</pre>
For any clarification about the procedure please perform the below command
<pre>host $ make –f targetfs_make help
</pre>

Executing above commands requires the users to have sudo access. The linux host would prompt for the user password and the user needs to enter his password for the make to continue.

The user can make sure he has sudo access by including the following line in /etc/sudoers file.
<pre>
<useracct> ALL=(ALL) ALL</pre>

Executing above commands will create the new NFS and JFFS2 root file system with the DVSDK demo executables and all the media files required by the demonstrations.
You will see nfs_dvsdk_#_##_##_##.tar.gz and rootfs_dvsdk_#_##_##_##.jffs2 files created under the current folder ('''/home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs''').
 

== What's next? ==

The next chapter of this Getting Started Guide is [[GSG: OMAP35x DVEVM Additional Procedures]].

ECE597 BeagleBoard DSP Software Setup

2010-04-16T01:06:47Z

Routhcr:

[[Category:ECE597]]

This is an adaptation of [http://wiki.davincidsp.com/index.php/GSG:_OMAP35x_DVEVM_Software_Setup GSG: OMAP35x_DVEVM Software Setup] for the BeagleBoard. Presently it's a work-in-progress. Follow the instructions and make corrections as you go. Change references to '''DVEVM''' to '''Beagle''' once you've tested a section and know it's correct. There are several links that pointed to pages on the original wiki. Fix them if you know how.

__TOC__

== Software Overview ==
To begin developing applications, you need to install the Beagle development environment. This section outlines the steps required to load the Beagle software onto the development host. You will need to download the files from the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page to get started.

The OMAP35x software approach provides interoperable, optimized, production-ready video and audio codecs that leverage DSP and integrated accelerators. These codecs are built into configurable frameworks, and are presented via published APIs within popular operating systems (such as Linux) for rapid software implementation.

The following software is provided in the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page.

* '''TI DVSDK Software.''' This includes demo applications, codec engine software, example codec servers, DVTB and DVSDK documentation. It contains the following files.
::* Getting Started Guide (this link)
::* DVSDK Product Release Notes
::* DVSDK Product Installer (dvsdk_#_##_##_##_Setup.bin)

* '''OMAP3525/OMAP3530 DVSDK Collaterals'''
::* Linux TSPA DSP Codec Server Installer (cs1omap3530_setupLinux_1_00_01-03.bin)
::* Linux TSPA DSP Codec Server Release Notes
::* Demonstration Multimedia Files-containing audio and video clips (data_dvsdk_#_##_##_##.tar.gz)
::* DVSDK OMAP3525/3530 Demo Overlay containing prebuilt DVSDK Binaries/Multimedia files. This should be added to an existing PSP file system (overlay_dvsdk_#_##_##_##.tar.gz)
::* Complete DVSDK file system including Pre-built DVSDK Binaries [overlay] and self starting DVSDK demos - suitable for NFS mount (nfs_dvsdk_#_##_##_##.tar.gz)
::* Complete DVSDK file system including Pre-built DVSDK Binaries [overlay] and self starting DVSDK demos - JFFS2 file system format [NAND flash] (rootfs_dvsdk_#_##_##_##.jffs2)
::* I don't know if these will work on the Beagle:
::** Prebuilt Kernel image for OMAP3525 and OMAP3530 default configuration (uImage-omap35x-evm.bin - Note that this is not a binary installer but needs to be renamed to uImage-omap35x-evm to use it for booting on OMAP3x EVM)
::** Prebuilt u-boot image for OMAP3525 and OMAP3530 default configuration (u-boot-omap35x-evm.bin)

* '''Linux Platform Support Package'''
::* PSP Release Notes
::* PSP User Guide
::* PSP Data Sheet
::* PSP Product Installer(AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.bin) - This installation file contains the linux source and binaries for OMAP35x platform and the necessary tools required for development on Linux for OMAP35x platform. This also contains the target file system

 

'''Command prompts in this guide'''

Commands are preceded by prompts that indicate the environment where the command is to be typed. For example:

;<tt>host $</tt> : Indicates command to be typed into the shell window of the host Linux workstation.
;<tt>Beagle #</tt> : Indicates commands to be typed into the U-Boot shell in a console window connected to the EVM board<nowiki>’</nowiki>s serial port. (see [http://wiki.davincidsp.com/index.php/GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program Setup Terminal Program] for EVM instructions. We need Beagle instructions).
;<tt>target $</tt> : Indicates commands to be typed into the Linux shell in the terminal window connected to the Beagle board's serial port.

 

'''NOTE: The document lists down various commands that needs to be executed on the target or on
the u-boot prompt for various operations required through out the document. Kindly note that a
direct copy and paste of these commands might result in insertion of lines for a single command.
Hence it would not work on the u-boot prompt or the target. Kindly ensure that you copy the long
commands into notepad, remove the line spaces between them and add a space wherever you
have removed the line spaces, before recopying and pasting it on the command prompts.'''
 

== '''Preparing to install''' ==

On a host system, copy the following .bin files from the [http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap.html Download] page to a temporary location with at least 2 GB free space. Since you can delete the installation files after installing the software, a directory like /tmp is recommended.

(I have copies of these that you can sftp from '''afs.rose-hulman.edu'''. They are in '''users/faculty/yoder/Public/beagle/downloads'''.)

*AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz
*dvsdk_#_##_##_##_Setup.bin
*xdctools_setuplinux_#_##_##.bin
*bios_setuplinux_#_##_##.bin
*TI-C6x-CGT-v#.#.##.#.bin
*cs1omap3530_setupLinux_#_##_##-##.bin
*overlay_dvsdk_#_##_##_##.tar.gz
*nfs_dvsdk_#_##_##_##.tar.gz
*rootfs_dvsdk_#_##_##_##.jffs2
*data_dvsdk_#_##_##_##.tar.gz

Ensure all the .bin files are set with executable permissions.
<pre>host $ chmod +x *.bin</pre>
 

== Installing the software ==

Installing the software used by the DVEVM involves performing the following steps:

*[[#Installing the Target Linux Software|Installing the Target Linux Software]]
*[[#Installing the DVSDK Software|Installing the DVSDK Software]]
*[[#Installing the A/V demo files|Installing the A/V demo files]]
*[[#Installing the toolchain|Installing the toolchain]]
*[[#Exporting a Shared File System for Target Access|Exporting a Shared File System for Target Access]]

 
=== Installing the Target Linux Software ===

This section explains how to install Linux for use on the target board.

Note that separate versions of Linux are used by the target and your host Linux workstation. The following Linux host operating systems have been used with the Beagle.

* Ubuntua 9.10, x86 32 bit

To install the Linux software, follow these steps:

<ol>
<li>Move AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz file (where ##.##.##.## is the current version number) from the temporary location that it was copied to your home directory.
<pre>host $ mv AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz /home/<useracct>
host $ cd
host $ tar xvzf AM35x-OMAP35x-PSP-SDK-setuplinux-##.##.##.##.tgz</pre>
<li>In future, all references in the document will assume that the user has installed the OMAP35x SDK using his user account and hence will refer to the OMAP35x SDK installation path as /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##</ol>
'''Note:''' The Linux Support Package (LSP) is a multi-platform LSP and is not configured for a particular platform. As shipped, this LSP cannot be used to build the demo or example applications. It must first be copied to a user area and configured/built for the Beagle. Please see the [[ECE597 BeagleBoard DSP Software Setup #Rebuilding_the_Linux_Kernel | Rebuilding the Linux Kernel]] section for instructions.
 

=== Installing the DVSDK Software ===

The TI DVSDK software includes demos, example software, Codec Engine components, DSP/BIOS Link, xDAIS and xDM header files, Local Power Manager Module, Framework Components and a contiguous memory allocator for Linux (CMEM). The DVSDK also contains the Digital Video Test Bench that enables testing the codecs and LSP with various configurations that are not possible with the Out of the Box demos.

'''Note:''' The installers for XDC, DSP/BIOS and Code Generation Tools (codegen) have a different default installation location. However, we strongly recommend that you change the default installation locations to place the components together (if you have not already installed the Linux versions of these components elsewhere). This simplifies the build setup steps.

To install the DVSDK software using the DVSDK Linux installer, follow these steps:

<ol>
<li>Log in using a user account. In the following steps, we refer to the home directory as "~".
<li>Execute the DVSDK installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./dvsdk_#_##_##_##_Setup.bin</pre>
The installer will start as a GUI application. Follow the instructions in the dialog boxes. You’ll be asked to agree to the End User License Agreement.
When you are prompted for an installation location, use the default installation location, that points to /home/<useracct>/dvsdk/dvsdk_#_##_##_##. This location will be used as the DVSDK installation folder through out this document.
<li>Execute the XDC installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./xdctools_setuplinux_#_##_##.bin</pre>
When you are prompted for an installation location, do not use the default installation location. Instead, install the software in the directory created in the previous step. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_##_##_##

NOTE: When prompted select '''Typical''' for the type of Setup.
<li>Execute the DSP/BIOS installer that you previously downloaded from the DVSDK download page. For example:
<pre>host $ ./bios_setuplinux_#_##_##.bin</pre>
When you are prompted for an installation location, do not use the default location. Instead, install the software in the directory created in step 2. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/bios_#_##_##_##
<li>Execute the Codec Server installer that you have previously downloaded from the DVSDK download page. For example:
<pre>host $ ./cs1omap3530_setupLinux_#_##_##-##.bin</pre>
When you are prompted for an installation location, install it in the location as specified or under the directory as created in step 2. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##_##
<li>Execute the Code Generation Tools installer that you previously downloaded from the DVSDK download page. The download link looked like TI-C6x-CGT-v#.#.##.#.bin; however the file you downloaded looked like ti_cgt_c6000_#.#.#_setup_linux_x86.bin. Run this file. For example:
<pre>host $ ./ti_cgt_c6000_#.#.#_setup_linux_x86.bin</pre>
When you are prompted for an installation location, install it in the location as specified or under the directory as created in step 2. If you are installing it under the DVSDK installation folder created in step 2, create a new folder under the dvsdk installation folder and then proceed to install. For example, /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##, where #_#_## is the version number.
<li>Remember to set the environment variable as directed by the installer. For example:
csh: (in the .cshrc file)
<pre>host $ setenv C6X_C_DIR /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/include:/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/lib</pre>
ksh or bash: (in the .bashrc file)
<pre>host $ export C6X_C_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/include:/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_#/lib</pre>
<li>You can now delete the .bin files that you loaded into the temporary directory.
</ol>
'''Note:''' You can uninstall these components by using the uninstall file in the respective installation directories. For example:
<pre>host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_#_#
host $ ./uninstall
</pre>
 

=== Installing the A/V demo files ===

'''These are very big, so I skipped them. --may'''

The TI DVSDK software installer, by itself does not contain the media files used by the demos. You can download the data files from DVSDK download page. Please use the steps mentioned below for extracting the media files into the desired location.

The Download page contains the Audio/Video files used by the demo. After following the instructions in the previous section, follow these instructions to install the A/V files:

<ol>
<li>Go to the DVSDK directory that you set up previously. For example
<pre>host $ cd ~/dvsdk/dvsdk_#_##_##_##/clips</pre>
<li>Copy the A/V data which you have downloaded from Download page to your DVSDK clips directory.For example:
<pre>host $ cp data_dvsdk_#_##_##_##.tar.gz .</pre>
<li>Extract the A/V data files. For example:
<pre>host $ tar -xvzf data_dvsdk_#_##_##_##.tar.gz</pre>
<li>Now you can delete the tar file from the clips folder.
</ol>

 

=== Installing the toolchain ===

This guide assumes use of the LITE version of the CodeSourcery toolchain.

==== Toolchain version to be used for DVSDK v3.01 ====
The toolchain used is ARM GNU/Linux EABI 2009q1. It can be downloaded from [http://www.codesourcery.com/sgpp/lite/arm/portal/package4571/public/arm-none-linux-gnueabi/arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 here]

[[Image:Codesourcery 2009q1.JPG|thumb|center|500px]]

To install the toolchain, follow the sequence below. These are to be executed on the Linux host platform.
<pre>
$ mkdir –p /home/<useracct>/toolchain
$ cp arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 /home/<useracct>/toolchain
$ cd /home/<useracct>/toolchain
$ tar -jxvf arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
$ rm arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
</pre>

=== I haven't tested these sections on use NFS ===

==== Exporting a Shared File System for Target Access ====

Although the board’s NAND flash contains a file system, during development it is more convenient to have the target board NFS mount a file system on a host Linux workstation. Once you test the application, you can store it on the board’s flash for a standalone demonstration.

Before the board can mount a target file system, you must export that target file system on the host Linux workstation. The file system uses an NFS (Network File System) server. The exported file system will contain the target file system and your executables.

To export the file system from your NFS server, perform the following steps. You only need to perform these steps once.

<ol>
<li>Log in with a user account on the host Linux workstation. (In the following steps, we refer to the home user directory as "~".)
<li>Perform the following commands to prepare a location for the OMAP35x EVM target file system.
<pre>host $ cd ~
host $ mkdir -p workdir/filesys
host $ cd workdir/filesys
</pre>
<li>Switch user to "root" on the host Linux workstation.
<pre>host $ su
password:
</pre>
There will be a prompt for entering the password as shown above. Type the root password, for getting the root permissions
<li>If you have already prepared a directory tree to use for the NFS root file-system (see Section [[#Rebuilding the NFS Image |Rebuilding the NFS Image]]) you can proceed to the next step. Otherwise, copy the prepared version(nfs_dvsdk_#_##_##_##.tar.gz) from the OMAP3530 DVSDK from the Download page to a new directory created in step 2. Perform the following commands.
'''Note:'''Un-tar the file with root permissions

<pre>$ cp /tmp/nfs_dvsdk_#_##_##_##.tar.gz .
$ tar –xvzf nfs_dvsdk_#_##_##_##.tar.gz
</pre>

<li>Make sure you can write into the opt folder in the file system by setting the permissions of the opt folder within the target file system with your user account. Perform the following command
<pre>host $ chown -R <useracct> /home/<useracct>/workdir/filesys/opt</pre>
Alternatively, if you want to have permissions to write or create folders within the target file system that you want to export as NFS, perform the following command
<pre>host $ chown -R <useracct> /home/<useracct>/workdir/filesys</pre>

<li>Make sure the NFS server is configured and functioning properly. Add the following line to the /etc/exports file of the server. Ensure you have root permission before editing this file.
<pre>/home/<useracct>/workdir/filesys *(rw,no_root_squash,no_all_squash,sync)</pre>

NOTE: On some systems you may wish to add the '''no_subtree_check''' option to avoid warnings like:
exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export <export listed here>.
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x

<li>Then issue the following command to notify the NFS server about the new exported directory.
<pre>
host $ /usr/sbin/exportfs –a
''' For Redhat Linux'''
host $ /sbin/service nfs restart
''' For Ubuntu'''
host $ /etc/init.d/nfs-kernel-server restart

</pre>

<li>Verify that the server firewall is turned off:
<pre>host $ /etc/init.d/iptables status</pre>
If the firewall is running, disable it:
<pre>host $ /etc/init.d/iptables stop</pre>
<li>Make sure you exit from having the root permissions after completing all the above steps
<pre>host $ exit</pre>
</ol>
 

==== Testing the shared file system ====

To test your NFS setup, follow these steps:
<ol>
<li>Get the IP address of your host Linux workstations as follows. Look for the IP address associated with the eth0 Ethernet port.
<pre>host $ /sbin/ifconfig</pre>

<li>Open a terminal emulation window to connect to the EVM board via RS-232 using the instructions in the [[GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program | Setup Terminal Program]] topic. If you have a Windows workstation, you can use HyperTerminal. If you have a Linux workstation, you might use Minicom. (You may need to turn on line wrap.)

<li>Power on the EVM board, and abort the automatic boot sequence by pressing a key in the console window. This gets you into the U-Boot prompt where you can configure how U-Boot will boot the Linux kernel.

<li>Set the following environment variables in the console window:
<pre>EVM # setenv nfshost <ip address of nfs host>
EVM # setenv rootpath <directory to mount></pre>
'''For DVSDK Releases from 3.00.00.36 upto and including 3.00.01.42, use the following bootargs:'''
<pre>EVM # setenv bootargs "console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=88M
omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y"</pre>
'''For DVSDK release 3.00.02.44, use the following bootargs:'''
<pre>EVM # setenv bootargs "console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=99M
mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y"</pre>

Note that the <tt>setenv bootargs</tt> command should be typed on a single line. Also note that you should avoid using the numeric keypad to enter numbers, as it can sometimes insert extra invisible characters. These environment variables must be typed in perfectly including capitals, if anything is typoed you will likely run into boot errors.

The ''<directory to mount>'' must match what you specified in Step 5 of the [[#Exporting a shared file system for target access| Exporting a shared file system for target access]] section. For example, <tt>/home/<user>/workdir/filesys</tt>.

'''Hints:''' If the kernel version stored in the NAND flash on the EVM is out of date you may wish to [[GSG:_OMAP35x_DVEVM_Additional_Procedures#Flashing_the_New_Linux_Kernel | flash the latest kernel image]] (using the uImage file in the /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##/images/kernel directory) or [[GSG:_OMAP35x_DVEVM_Additional_Procedures#Booting_via_TFTP_using_NFS_file_system | boot using TFTP]]

'''Hints:''' You may want to use the <tt>printenv</tt> command to print a list of your environment variables. You can also save these setenv commands in a .txt file from which you can paste them in the future.

<li>Save the environment so that you don't have to retype these commands every time you cycle power on the EVM board:
<pre>EVM # saveenv</pre>

<li>Boot the board using NFS:
<pre>EVM # boot</pre>

<li>You can now log in as "root" with no password required.

See the [[GSG:_OMAP35x DVEVM Additional Procedures#Alternate boot methods| Alternate boot methods]] section for information about booting with TFTP, NFS, or the board's NAND flash.
</ol>
 

=== Notes on using production codecs ===

As part of the OMAP35x DVSDK installation, you received a number of codecs:

* MPEG4 Simple Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* H.264 Base Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* MPEG2 Main Profile Decoder. This decoder is compliant with IVIDDEC2 Interface
* Sequential JPEG Decoder. This decoder is compliant with IIMGDEC1 Interface
* MPEG4 Simple Profile Encoder. This decoder is compliant with IVIDENC1 Interface
* H.264 Base Profile Encoder. This decoder is compliant with IVIDENC1 Interface
* JPEG Encoder. This encoder is compliant with IIMGENC1 Interface
* Advance Audio Codec (AAC) Decoder. This decoder supports both AAC-HE and AAC-LC configurations. It is compliant with IAUDDEC1 interface
* G.711 Speech Decoder. This decoder is compliant with ISPHDEC1 interface
* G.711 Speech Encoder. This encoder is compliant with ISPHENC1 interface

NOTE: Though the standalone codec server contain JPEG decode, the DVSDK decode demos do not support playback of JPEG streams. In order to evaluate these decoders, use Digital Video Test Bench (DVTB) which is included in the OMAP3530 DVSDK. The media files for MPEG2 MP and JPEG format streams are not available as part of the DVSDK installation, but they are available as part of data_dvsdk_#_##_##_##.tar.gz that can be downloaded from the OMAP software update site http://www.ti.com/omapsoftwareupdates
 

== Setting up the build/development environment ==
To set up the development and build environment, follow these steps:

<ol>
<li>Log in to your '''user''' account (and not as root) on the NFS host system.

<li>Add the /host/<useracct>/toolchain/<toolchain_version>/bin directory to your path. This is typically done by adding an additional line to your shell resource file (~/.bashrc). For the path given above, the line to add to your .bashrc file is:

<pre>export PATH=“/home/<useracct>/toolchain/<toolchain_version>/bin:$PATH”</pre>

This adds the CodeSourcery tools to your path and allows you to execute the tools using arm-none-linux-gnueabi-gcc (or other tools in the tool chain) from any directory.

<li>Remember to use the following command after modifying your .bashrc file. The source command essentially executes the .bashrc script so that the path you just added to it is added to your environment variables:

<pre>host $ source .bashrc</pre>

<li>You can test that the toolchain is installed correctly by starting a new shell and using the following command:
<pre>host $ arm-none-linux-gnueabi-gcc –v</pre>
When you execute this command, you will get an output like the one shown below.

<pre>Using built-in specs.
Target: arm-none-linux-gnueabi
Configured with: /scratch/sandra/lite/src/gcc-4.2/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --enable-shared --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion=Sourcery G++ Lite 2008q1-126 --with-bugurl=https://support.codesourcery.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/libc --enable-poison-system-directories --with-build-time-tools=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/sandra/lite/linux/install/arm-none-linux-gnueabi/bin
Thread model: posix
gcc version 4.2.3 (Sourcery G++ Lite 2008q1-126)
</pre>

</ol>
 
=== Writing a simple program and running it on the EVM ===
Make sure you have performed the steps in the [[#Exporting a shared file system for target access | Exporting a shared file system for target access ]] section and the [[#Setting up the build/development environment|Setting up the build/development environment]] section before continuing with the steps in this section.

Perform the following steps on the NFS host system as user (not as root):

<ol>
<li>
<pre>host $ mkdir –p ~/workdir/filesys/opt/hello</pre>

<li>
<pre>host $ cd ~/workdir/filesys/opt/hello</pre>

<li>Create a file called hello.c with the following contents:

<pre>#include <stdio.h>

int main() {
printf("Welcome to OMAP35x World!\n");
return 0;
}
</pre>

<li>Build the new C file:
<pre>host $ arm-none-linux-gnueabi-gcc hello.c -o hello</pre>

Perform the following steps on the target board. You may use either the target's console window (see [[GSG:_OMAP35x_DVEVM_Hardware_Setup#Setup_Terminal_Program | Setup Terminal Program]]) or a telnet session.
</ol>
<ol>
<li>Move to the new directory on the target:

<pre>target $ cd /opt/hello</pre>

<li>Run the new executable:

<pre>./hello</pre>
</ol>

The output should be:

<pre>Welcome to OMAP35x World!</pre>
 

== Rebuilding the Software ==
This section describes how to rebuild pieces of the software delivery. Ensure that the toolchain setup and install has been completed (see [[#Installing the Toolchain|Installing the Toolchain]]).
 
=== Rebuilding U-boot ===
Rebuilding the U-boot is described in more detail in the LSP User’s Guide available at
AM35x-OMAP35x-PSP-SDK-##.##.##.##/docs/omap3530/UserGuide-##.##.##.##.pdf

Copy the U-Boot source archive from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/u-boot directory into your working directory

<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp /home/<useracct>/AM35x-OMAP35x-PSP-SDK-#.##.##.##/src/u-boot/u-boot-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the U-Boot source archive by performing the command given below.
<pre>host $ cd workdir/opt
host $ tar -zxvf u-boot-##.##.##.##.tar.gz
</pre>

To configure U-Boot for building, issue the following commands:
<pre>host $ cd uboot-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm distclean
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_config
</pre>

Once ready to build U-Boot, run the command:

<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm</pre>

The resulting U-Boot image named u-boot.bin will be in the current directory, ready to be loaded on the target.
 

=== Rebuilding the Linux Kernel ===
Rebuilding the kernel is described in more detail in the User’s Guide available at
AM35x-OMAP35x-PSP-SDK-##.##.##.##/docs/omap3530/UserGuide-##.##.##.##.pdf

Note that building the kernel requires using mkimage, a host side utility built by the u-boot makefile. If you have not already done so please build u-boot using the instructions in the [[ECE597 BeagleBoard DSP Software Setup #Rebuilding_U-boot | Rebuilding U-Boot section]]. You will need to build U-boot and place mkimage in your Path. A command like below can be used. If you are using a bash shell, kindly add the following in the .bashrc file in your user account.

<pre>export PATH=/<path_to_uboot>/tools:$PATH</pre>

Copy the Linux kernel source archive from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src directory into your working directory.
<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp /home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/kernel/linux-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the Linux kernel source archive by performing the commands given below.

<pre>host $ cd /home/<useracct>/workdir/opt
host $ tar -zxvf linux-##.##.##.##.tar.gz
</pre>

In order to prepare the kernel for building, follow these commands:

<pre>host $ cd linux-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_defconfig
</pre>

If you need to make changes to the default configuration, perform the following command.

<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm menuconfig</pre>

Once ready to build the kernel, run the following command
<pre>host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm uImage modules</pre>

The resulting kernel image uImage will be placed under arch/arm/boot and is ready to be loaded on the target.

Once the modules are built they must be installed on the target file system in order to be used. The following command will install the modules to the target file system and create the modules dependency file.

<pre>host $ su root
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- INSTALL_MOD_PATH=<target filesys dir> modules_install
</pre>

For example if you have been following the Getting Started Guide you should have created a target file system at /home/<useracct>/workdir/filesys. In the above command you should replace <target filesys dir> with /home/<useracct>/workdir/filesys.
 

=== Rebuilding the DVSDK software for the target ===
To place demo files in the /opt/dvsdk directory, you need to rebuild the DVSDK software. To do this, follow these steps:
<ol>
<li>If you have not already done so, rebuild the Linux kernel as described in the [[GSG:_OMAP35x_DVEVM_Software_Setup#Rebuilding_the_Linux_Kernel | Rebuilding the Linux Kernel]] section.

<li>Change directory to dvsdk_#_##_##_##.

<li>Edit the Rules.make file in the dvsdk_#_##_##_## directory.

<pre>host $ vi Rules.make</pre>

<li>Check the following directory definitions. If you installed components in the default locations, the directory definitions may already be correct, but you should verify them in any case.

<ul><li>Set PLATFORM to match your EVM board as follows (Note that this variable is case sensitive):

<pre>PLATFORM=omap3530</pre>

<li>Set DVSDK_INSTALL_DIR to the top-level DVSDK installation directory as follows, note that by default ${HOME} refers to your /home/<''useracct''> directory:

<pre>DVSDK_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##</pre>

<li>Modify the following variable as needed to match the location of XDCtools on your Linux host. We recommend that XDCtools be installed in the /home/<''useracct''>/dvsdk/dvsdk_#_##_##_## directory, but you may have installed it elsewhere.

<pre>XDC_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/xdctools_#_##_##_##</pre>

<li>Make sure EXEC_DIR points to the opt directory on the NFS exported file system as follows. Refer [[#Exporting a Shared File System for Target Access|Exporting a Shared File System for Target Access]] for setting up the NFS exported file system.
<pre>EXEC_DIR=/home/<useracct>/workdir/filesys/opt/dvsdk/omap3530</pre>

<li>Make sure UBOOT_INSTALL_DIR is defined as follows so it points to where you copied the uboot source in the [[GSG:_OMAP35x_DVEVM_Software_Setup#Rebuilding_U-boot | Rebuilding U-Boot section]].

<pre>UBOOT_INSTALL_DIR=/home/<useracct>/workdir/opt/uboot-##.##.##.##</pre>

<li>Make sure LINUXKERNEL_INSTALL_DIR is defined as follows so it points to where you copied the Linux kernel tree in the Building a New Linux Kernel section.

<pre>LINUXKERNEL_INSTALL_DIR=/home/<useracct>/workdir/opt/linux-##.##.##.##</pre>

<li>Make sure OMAP3503_SDK_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>OMAP3503_SDK_INSTALL_DIR=/home/<useracct>/AM35x-OMAP35x-PSP-SDK-##.##.##.##</pre>

<li>Make sure CODEC_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>CODEC_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##</pre>
<li>Change the path of the CSTOOL_DIR to point to the location where you have installed the CodeSourcery tool-chain. (Refer [[#Installing the Toolchain|Installing the Toolchain]])

<pre>CSTOOL_DIR=/home/<useracct>/toolchain/<toolchain_version></pre>

<li>Make sure CODEGEN_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path).

<pre>CODEGEN_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##</pre>
<li>'''Note''' PSP_INSTALL_DIR donot need to be updated.They will be pointing to DVSDK installation directory.

<li>Check the path of all component installation directories to match the location where you want to point to. The default locations specified will choose the component versions as installed as part of the DVSDK installation

</ul>
<li>The top level DVSDK Makefile re-builds the kernel modules required by the DVSDK demonstration software (CMEM and LPM) and hence it is very important to at least perform the following commands (in case you have not performed the steps in [[#Rebuilding the Linux Kernel | Rebuilding the Linux Kernel]]), after extracting the Linux kernel source code in your work directory, whose path is provided in the top level DVSDK Rules.make. Refer section [[#Rebuilding the Linux Kernel | Rebuilding the Linux Kernel ]] for more details on “Rebuilding the Linux Kernel”.
<pre>host $ cd /home/<useracct>/workdir/opt/linux-##.##.##.##
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3_evm_defconfig
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm modules
</pre>
<li> Once the installation is complete please use the following commands to verify the paths set in Rules.make and components installed in DVSDK are proper.
<pre>host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##
host $ make check
host $ make info
</pre>

<li>While in the same directory that contains Rules.make, use the following commands to build the DVSDK demo applications and put the resulting binaries on the target file system specified by EXEC_DIR.
<pre>host $ make clean
host $ make all
host $ make install
</pre>
*'''Note :''' The '''make all''' command builds only the DVSDK demos, its dependent components and DVTB

<li>Additional commands for cleaning and building all the components are as mentioned below.
*'''Note :''' The PSP examples under AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/examples have to be extracted before using below commands
<pre>host $ make clobber
host $ make everything
</pre>
<li>For information on individually building the components please use the folowing command
*'''Note:'''Certain components have dependency on other components.So please make sure you have executed the '''make all''' command before proceeding for individual component build.
<pre>
host $ make help
</pre>
</ol>

'''NOTE:''' The dependencies for indivdual component builds are not addressed in the top level DVSDK Makefile. If you perform 'make clobber' or 'make clean' and then try building indivdual components like 'make dmai', the build will fail. Alternatively, if you perform 'make clobber' and then perform 'make everything', the build will go through. In addition to that, if you try cleaning the individual component and then build the same again, the build will go through. For example, after performing 'make everything', performing 'make dmai_clean' followed by 'make dmai' will work.
 

=== Rebuilding the DSP side server executables ===

The DSP side codec libraries are available under /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_## directory or if you have installed it in a different location specified by CODEC_INSTALL_DIR

The top level Makefile and the config.bld files are provided under the top level directory mentioned above. The codec binaries, header files as well as documents are RTSC packaged and available under /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##/packages/ti/sdo/codecs folder.

Ensure that the path settings for the DSP side code generation tools are set properly in the config.bld file

<pre>
C64P.rootDir = /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_# OR
C64P.rootDir=java.lang.System.getenv("CODEGEN_INSTALL_DIR");
cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##
host $ make clean
host $ make
</pre>

The rebuilt server executable can be found in the /home/<useracct>/dvsdk/dvsdk_#_##_##_##/cs1omap3530_#_##_##/packages/ti/sdo/server/bin directory and is named cs.x64P.

The DSP side server executables can also be built from the DVSDK installation directory itself by following the below commands.

Ensure that DSP side code generation tools are set properly in the Rules.make in DVSDK installation directory

<pre>
CODEGEN_INSTALL_DIR=/home/<useracct>/dvsdk/dvsdk_#_##_##_##/cg6x_#_#_##
</pre>

Re-building the Servers from DVSDK installation directory can be done using the following commands.

<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##
host $ make codecs_clean
host $ make codecs
host $ make install
</pre>
 
=== Rebuilding the Initial NAND X-loader ===

Copy the X-Loader source archive from OMAP35x-PSP-SDK-##.##.##.##/src/boot-strap directory into your working directory

<pre>host $ cd ~
host $ mkdir –p workdir/opt
host $ cp x-loader-##.##.##.##.tar.gz ~/workdir/opt/.
</pre>

Un-tar the X-Loader source archive by performing the following command.
<pre>
host $ cd /home/<useracct>/workdir/opt
host $ tar -zxvf x-loader-##.##.##.##.tar.gz
</pre>

Configure X-Loader for OMAP35x EVM target:
<pre>
host $ cd xloader-##.##.##.##
host $ make omap3evm_config
</pre>

To build X-Loader, run the command:
<pre>
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm
</pre>

The above command produces the x-load.bin file, but in order for the X-Loader to be loaded by the OMAP35x ROM bootloader, it needs to be signed with the signGP program from the AM35x-OMAP35x-PSP-SDK-##.##.##.##/host-tools/linux directory.

<pre>
host $ /home/<useracct>/AM35x-OMAP35x-PSP-SDK-#.##.##.##/host_tools/linux/signGP x-load.bin
</pre>

The resulting signed X-loader is named x-load.bin.ift and should be ready for the target.
For MMC/SD Card boot loading this file must be called MLO.

<pre>
host $ cp x-load.bin.ift MLO
</pre>
 
=== Rebuilding the Target-side UART Loader ===

Copy the UART loader dnld_util_target.tar.bz2 file from AM35x-OMAP35x-PSP-SDK-##.##.##.##/src/utils directory into your working directory.

<pre>
host $ cd ~
host $ mkdir –p workdir/opt
host $ cp dnld-util-target.tar.bz2 ~/workdir/opt/.
</pre>

Un-tar the UART loader by performing the following command.
<pre>
host $ tar -jxvf dnld_util_target.tar.bz2
host $ cd dnld_util_target
</pre>

Run the following command to build it.
<pre>
host $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm
</pre>

The resulting binary is called dnld_startup_omap3_evm.bin. This file is used with DownloadUtility.exe for UART peripheral boot.
 
=== Rebuilding the NFS Image ===

Kindly refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_NFS_Image]] (part of AM35x Getting Started Guide),for rebuilding NFS for AM35x SDK. This will contain different set of demos and sample applications.
The OMAP3535/OMAP3530 DVSDK installer has the script to (re)build the NFS image that includes the OMAP3525/OMAP3530 DVSDK demos under ~/dvsdk/dvsdk_#_##_##_##/targetfs folder.

In order to rebuild the NFS image with OMAP3530 DVSDK demos, make sure you have performed the steps in Section [[#GSG: _OMAP35x DVEVM Software Setup|OMAP35x DVEVM Software Setup]] and Section [[#Rebuilding the DVSDK Software for the target|Rebuilding the DVSDK Software for the target]].

'''NOTE:''' Also ensure that you have copied the overlay_dvsdk_#_##_##_##.tar.gz file to your /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs folder.

The following command removes the old the NFS tarball image:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_old_rootfs DVSDKVER=<your version number #_##_##_##>
</pre>

The following command will create the NFS tarball image:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make omap3530_dvsdk_nfs DVSDKVER=<your version number #_##_##_##>
</pre>

The following command will remove the NFS creation logs and the temporary NFS directory:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_nfs DVSDKVER=<your version number #_##_##_##>
</pre>
For any clarification about the procedure please perform the below command
<pre>host $ make –f targetfs_make help
</pre>

Executing above command requires the users to have sudo access. The linux host would prompt for the user password and the user needs to enter his password for the make to continue.
The user can make sure he has sudo access by including the following line in /etc/sudoers file.

<pre>
<useracct> ALL=(ALL) ALL</pre>

Executing above commands will create the new NFS file system with the DVSDK demo executables and all the media files required by the demonstrations.
You will see nfs_dvsdk_#_##_##_##.tar.gz created under the current folder ('''/home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs''').
 
=== Rebuilding the Full Ramdisk Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_Full_Ramdisk_Image]] (part of AM35x Getting Started Guide),for rebuilding full ramdisk image for AM35x SDK. This will contain different set of demos and sample applications.

The full ramdisk image cannot be built to include the OMAP3530 DVSDK demos as the ramdisk size requirement exceeds 40MB after the image is un-tarred and the bootargs given in step 5 in Section [[GSG:_OMAP35x DVEVM Additional Procedures#Running the Re-flash Procedure|Running the Re-flash Procedure]] will not work
 

=== Rebuilding the Minimal Ramdisk Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup]] (part of AM35x Getting Started Guide),for rebuilding minimal ramdisk image for AM35x SDK. The minimal ramdisk image does not contain any demos or examples.
 

=== Rebuilding the JFFS2 File-System Image ===

Refer to the [[GSG:_AM35x_EVM_Software_Setup#Rebuilding_the_JFFS2_File-System_Image]] (part of AM35x Getting Started Guide),for rebuilding jffs2 image for AM35x SDK. This will contain different set of demos and sample applications.

The OMAP3525/OMAP3530 DVSDK installer has the pre-built JFFS2 root file system image that includes the OMAP3525/OMAP3530 DVSDK demos under ~/dvsdk/dvsdk_#_##_##_##/targetfs folder.

Check if the linux distribution on the host PC contains the mkfs.jffs2 utility. If not, download the binary from ftp://sources.redhat.com/pub/jffs2/mkfs.jffs2. Place this binary under /sbin directory in the Linux host development PC and ensure to include /sbin to the PATH environment variable in the .bashrc file.

In order to rebuild the JFFS2 root file system image with OMAP3530 DVSDK demos, make sure you have performed the steps in Section [[#GSG: _OMAP35x DVEVM Software Setup|OMAP35x DVEVM Software Setup]] and Section [[#Rebuilding the DVSDK Software for the target|Rebuilding the DVSDK Software for the target]]. Then, perform the following steps.

'''NOTE:''' Also ensure that you have copied the overlay_dvsdk_#_##_##_##.tar.gz file to your /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs folder.

Clean the old file system images:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_old_rootfs DVSDKVER=<your version number #_##_##_##>
</pre>

Create the JFFS2 Image (This requires building the NFS image to create the JFFS2 image from):
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make omap3530_dvsdk_jffs2 MKJFFS2=<your_jffs2_install_path> DVSDKVER=<your version number #_##_##_##>
</pre>

Clean up the temporary NFS file system directory:
<pre>
host $ cd /home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs
host $ sudo make –f targetfs_make clean_nfs DVSDKVER=<your version number #_##_##_##>
</pre>
For any clarification about the procedure please perform the below command
<pre>host $ make –f targetfs_make help
</pre>

Executing above commands requires the users to have sudo access. The linux host would prompt for the user password and the user needs to enter his password for the make to continue.

The user can make sure he has sudo access by including the following line in /etc/sudoers file.
<pre>
<useracct> ALL=(ALL) ALL</pre>

Executing above commands will create the new NFS and JFFS2 root file system with the DVSDK demo executables and all the media files required by the demonstrations.
You will see nfs_dvsdk_#_##_##_##.tar.gz and rootfs_dvsdk_#_##_##_##.jffs2 files created under the current folder ('''/home/<useracct>/dvsdk/dvsdk_#_##_##_##/targetfs''').
 

== What's next? ==

The next chapter of this Getting Started Guide is [[GSG: OMAP35x DVEVM Additional Procedures]].

ECE597 Project Auto HUD

2010-03-23T01:05:57Z

Routhcr:

==Project Overview==
The goal of this project is to 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.

==Team Members==
[[user:routhcr | Chris Routh]]

[[user:collinjc | J. Cody Collins]]

Greg Jackson

Keqiong Xin

==Steps==
* Create Minimal Linux Image that can run OpenCV and run the display
* Work on getting a camera functioning on the beagle board
* OpenCV running nativly on beagle with min config
* OpenCV working on video stream
* Projector working on Beagle
* Car integration (power)
* Algorithm development

ECE497 Project Ideas

2010-03-23T00:27:17Z

Routhcr:

[[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 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.
|-
| Paul Morrison Steven Stark
| 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
| 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.
|}

Executable and Linkable Format (ELF)

2010-03-19T19:13:13Z

Routhcr: Created page with 'Category:ECE597 In computing, the '''Executable and Linkable Format''' ('''ELF''', formerly called '''Extensible Linking Format''') is a common standard file format for exec…'

[[Category:ECE597]]

In computing, the '''Executable and Linkable Format''' ('''ELF''', formerly called '''Extensible Linking Format''') is a common standard file format for executables, object code, shared libraries, and core dumps. First published in the System V application binary interface|Application Binary Interface specification,<ref>''[http://www.sco.com/developers/devspecs/gabi41.pdf System V Application Binary Interface]'' Edition 4.1 (1997-03-18)</ref> and later in the Tool Interface Standard,<ref>Tool Interface Standard (TIS) ''[http://refspecs.freestandards.org/elf/elf.pdf Executable and Linking Format (ELF) Specification] Version 1.2'' (May 1995)</ref> it was quickly accepted among different vendors of Unix systems. In 1999 it was chosen as the standard binary file format for Unix and Unix-like systems on x86 by the 86open project.

Unlike many proprietary executable file formats, ELF is very flexible and extensible, and it is not bound to any particular processor or Instruction set architecture|architecture. This has allowed it to be adopted by many different operating systems on many different platforms.

The ELF format has replaced older executable formats such as a.out and COFF in many Unix-like operating systems such as Linux, Solaris (operating system), IRIX, FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Syllable Desktop (operating system), and HP-UX (except for 32-bit PA-RISC programs which continue to use System Object Model (file format)). ELF has also seen some adoption in non-Unix operating systems, such as the Itanium version of OpenVMS, BeOS Revision 4 and later for x86 architecture (where it replaced the Portable Executable format; the PowerPC version stayed with Preferred Executable Format), and Haiku (operating system). The PlayStation Portable, PlayStation 2, PlayStation 3, Wii, Nintendo DS and GP2X consoles also use ELF. AmigaOS 4 and MorphOS also running on PowerPC machines, use ELF. On the Amiga platform the ELF executable has replaced the previous [[Amiga Hunk#Extended Hunk format|EHF]] (Extended Hunk Format) which was used on Amigas equipped with PPC processor expansion cards. The Symbian OS v9 uses E32Image<ref>''[http://wiki.forum.nokia.com/index.php/E32Image Symbian OS executable file format]''</ref> format that is based on ELF file format.

Most Sony Ericsson (for example, the Sony Ericsson W800, Sony Ericsson W610i, Sony Ericsson W300, etc.), some Siemens (SGOLD and SGOLD2 platforms: from Siemens C65 to S75 and BenQ-Siemens E71/BenQ-Siemens EL71) and Motorola (for example, the E398, Motorola SLVR L7, v360, Motorola_RAZR_V3#V3i and all phone LTE2 which has the patch applied) phones can run ELF files through the use of a Patch (computing) that adds Assembly Language to the main firmware (known as the ''ELFPack'', in the underground modding culture).

The ELF file format is also used as a generic object and executable format for binary images used with embedded processors{{Citation needed|date=June 2008}}.

== ELF file layout ==
[[Image:Elf-layout--en.png|link=http://en.wikipedia.org/wiki/File:Elf-layout--en.png|thumb|200px]]

Each ELF file is made up of one ELF header, followed by file data. The file data can include:

* Program header table, describing zero or more segments
* Section header table, describing zero or more sections
* Data referred to by entries in the program header table, or the section header table

The segments contain information that is necessary for runtime execution of the file, while sections contain important data for linking and relocation. Each byte in the entire file is taken by no more than one section at a time, but there can be orphan bytes, which are not covered by a section. In the normal case of a Unix executable one or more sections are enclosed in one segment.

==Tools==

*<code>readelf</code> is a Unix binary utility that displays information about one or more ELF files. A GNU General Public License implementation is provided by GNU Binutils.
*<code>elfdump</code> is a command for viewing ELF information in an elf file, available under Solaris and [[FreeBSD]].
*<code>[[objdump]]</code> provides a wide range of information about ELF files and other object formats. <code>objdump</code> uses the [[Binary File Descriptor library]] as a back-end to structure the ELF data.
*<code>file</code> is a Unix binary utility that displays information about the [[Instruction set architecture|architecture]] of ELF files.

==Specifications==

* Generic:
** ''[http://www.sco.com/developers/devspecs/gabi41.pdf System V Application Binary Interface]'' Edition 4.1 (1997-03-18)
** ''[http://www.sco.com/developers/gabi/latest/contents.html System V ABI Update]'' (October 2009)
** ''[http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf ELF-64 Object File Format]'' Version 1.5 Draft 2 (May 1998)
* AMD64:
** ''[http://www.x86-64.org/documentation/abi.pdf System V ABI, AMD64 Supplement]''
* ARM architecture:
** ''[http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044b/IHI0044B_aaelf.pdf ELF for the ARM Architecture]''
* IA32:
** ''[http://www.sco.com/developers/devspecs/abi386-4.pdf System V ABI, IA32 Supplement]''
* IA64:
** ''[http://refspecs.freestandards.org/IA64conventions.pdf Itanium Software Conventions and Runtime Guide]'' (September 2000)
* M32R:
** ''[http://www.linux-m32r.org/cmn/m32r/M32R-elf-abi.pdf M32R ELF ABI Supplement]'' Version 1.2 (2004-08-26)
* MIPS architecture:
** ''[http://www.sco.com/developers/devspecs/mipsabi.pdf System V ABI, MIPS RISC Processor Supplement]''
** ''[http://sources.redhat.com/ml/binutils/2003-06/msg00436.html MIPS EABI documentation]'' (2003-06-11)
* Motorola 6800:
** ''[http://www.uclibc.org/cgi-bin/viewcvs.cgi/trunk/docs/psABI-m8-16.pdf?rev=10808 Motorola 8 and 16 bit Embedded ABI]''
* PA-RISC:
* PowerPC:
** ''[http://refspecs.freestandards.org/elf/elfspec_ppc.pdf System V ABI, PPC Supplement]
** ''[http://ftp.twaren.net/Unix/Sourceware/binutils/ppc-docs/ppc-eabi-1995-01.pdf PowerPC Embedded Application Binary Interface] 32-Bit Implementation'' (1995-10-01)
** ''[http://www.linuxbase.org/spec/ELF/ppc64/PPC-elf64abi-1.9.html 64-bit PowerPC ELF Application Binary Interface Supplement]'' Version 1.9 (2004)
* SPARC:
** ''[http://www.sparc.org/standards/psABI3rd.pdf System V ABI, SPARC Supplement]''
* S/390:
** ''[http://www.linux-foundation.org/spec/ELF/zSeries/lzsabi0_s390/book1.html S/390 ELF ABI Supplement]
* zSeries:
** ''[http://www.linux-foundation.org/spec/ELF/zSeries/lzsabi0_zSeries.pdf zSeries ELF ABI Supplement]''
* Symbian OS 9:
** ''[http://wiki.forum.nokia.com/index.php/E32Image_file_format_on_Symbian_OS_9 E32Image file format on Symbian OS 9]''

File:Elf-layout--en.png

2010-03-19T19:03:49Z

Routhcr:

File:Elf-layout--en.svg

2010-03-19T19:00:45Z

Routhcr:

User:Routhcr

2010-03-19T18:40:52Z

Routhcr:

User:Routhcr

2010-03-18T01:41:11Z

Routhcr: Created page with 'Category:ECE597 = Introduction = Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.'

[[Category:ECE597]]
= Introduction =
Welcome to my user page, this is a work in progress but I plan for it to be the primary place to see my research and current projects.

ECE497 Project Ideas

2010-03-12T21:09:33Z

Routhcr:

[[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
| Fast Boot
| See [[BeagleBoard/GSoC/Ideas#Fast_Linux_boot]]
|}

EBC Exercise 22 Cross-Compiling

2010-03-11T20:04:40Z

Routhcr:

[[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.
| 2.5 hours
|-
| 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.
| ''pending''
|-
| 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.

ECE497 Editing a Wiki

2010-03-09T01:26:46Z

Routhcr:

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
|}

[[Category:ECE597]]