Lab 05 is on pages 125-157 of the DaVinci-OMAP_Workshop_v2.0.pdf file. Work through this lab. You'll learn how '''make''' works. Part C has an error in the solution, a workaround can be found [[User:Simonea|here]]. When you get to part D, compare my version of the make file ('''makefile_profile.mak.yoder''') to the one in the folder. The workshop assumes you have NFS setup to share files between the DVEVM and the host computer. Rather than share files, I've set up the makefile so use sftp and ssh to copy the executables to the Beagle when installing. If you can at the NFS working, great!, otherwise use my setup.

Lab 05 is on pages 125-157 of the DaVinci-OMAP_Workshop_v2.0.pdf file. Work through this lab. You'll learn how '''make''' works. Part C has an error in the solution, a workaround can be found [[User:Simonea|here]]. When you get to part D, compare my version of the make file ('''makefile_profile.mak.yoder''') to the one in the folder. The workshop assumes you have NFS setup to share files between the DVEVM and the host computer. Rather than share files, I've set up the makefile so use sftp and ssh to copy the executables to the Beagle when installing. If you can at the NFS working, great!, otherwise use my setup.

−

To get part '''d''' to compile correctly, you have to make sure all the path information is correct. Make sure to edit '''setpaths.sh, setpaths.mak, and makefile_profile.mak'''. Because Configuro is stubborn, you will still need to link 'arm_v5t_le-gcc' to 'arm-nonearm-none-linux-gnueabi-gcc' if it is to compile.

+

To get part '''d''' to compile correctly, you have to make sure all the path information is correct. Make sure to edit '''setpaths.sh, setpaths.mak, and makefile_profile.mak'''. Because Configuro is stubborn, you will still need to link 'arm_v5t_le-gcc' to 'arm-nonearm-none-linux-gnueabi-gcc' if it is to compile.

+

<pre>

+

cd /home/user/CodeSourcery/Sourcery_G++_Lite/bin

+

ln -s arm-none-linux-gnueabi-gcc arm_v5t_le_gcc

+

</pre>

== Lab 06, Using the OSS Driver ==

== Lab 06, Using the OSS Driver ==

Revision as of 14:22, 20 April 2010

Texas Instruments' Technical Tranining for students concerning the DaVinci/OMAP platforms including DM64xx, DM35x/36x, OMAP35x, OMAP-L1x, and AMx. Below are the details of the labs we'll be doing from the DaVinci workshop.

Untar the labs file on your Linux host. It will create two directories, workshop and solutions. You will find the materials needed to do the labs below in the workshop directory. The finished product for each lab can be found in the solutions directory. The directions in DaVanci-OMAP_Workshop file will tell you which directory to use for each lab.

These labs were originally done for the Digital Video Evaluation Module (DVEVM). We will be adapting them for the BeagleBoard as we go.

Lab 05, gMake

Lab 05 is on pages 125-157 of the DaVinci-OMAP_Workshop_v2.0.pdf file. Work through this lab. You'll learn how make works. Part C has an error in the solution, a workaround can be found here. When you get to part D, compare my version of the make file (makefile_profile.mak.yoder) to the one in the folder. The workshop assumes you have NFS setup to share files between the DVEVM and the host computer. Rather than share files, I've set up the makefile so use sftp and ssh to copy the executables to the Beagle when installing. If you can at the NFS working, great!, otherwise use my setup.

To get part d to compile correctly, you have to make sure all the path information is correct. Make sure to edit setpaths.sh, setpaths.mak, and makefile_profile.mak. Because Configuro is stubborn, you will still need to link 'arm_v5t_le-gcc' to 'arm-nonearm-none-linux-gnueabi-gcc' if it is to compile.

Copy the setpaths files you got from SharePoint into the workshop directory. In Lab 6 you will edit these files so they are correct.

You will still need the symbolic link from part 5, and make sure to update the file paths.

Lab 07, Using Video Drivers

Lab 07a - Writing to a Frame Buffer

Lab 07a almost works on the Beagle. You should be able to write to the frame buffer directly with a couple of changes. Here are some hints about what to change:

The path to the frame buffer /dev/fb... is different on the Beagle than in the code. Look on the Beagle and find the right path. Find the path in the code and change it.

The code assumes an attribute frame. I haven't found this on the Beagle, use #define's to remove the code that references the attribute frame.

Initially I commented out the code that draws the circular frame.

With these few changes your code should compile and when run it should display your picture on the Beagle. I was surprised to find it even worked through the VNC. I'm guessing X-windows just displays what's in the buffer.

Here's some things to try to see if you understand how the code works.

The code sets the background color to black. Make the background another color.

Try getting video_osd_circframe to work.

Lab 07b - Recording Video

Lab 07b almost works too. There are a couple of ioctl class that don't work with the web cam. Just #define them out. Don't run the app too long, it's writing to /tmp and you might fill it up.