Difference between revisions of "ECE497 Lab10 gMake"

From eLinux.org
Jump to: navigation, search
m (Lab 10 - Using the OSS Driver)
m (Lab 11 - Using Video Drivers)
Line 65: Line 65:
== Lab 11 - Using Video Drivers ==
== Lab 11 - Using Video Drivers ==
Lab 11 is lab 6 on page 171 of '''DaVinci-OMAP_Workshop_v2.0.pdf'''.
Lab 11 is lab 7 on page 200 of '''DaVinci-OMAP_Workshop_v2.0.pdf'''.
=== Lab 11a - Writing to a Frame Buffer ===
=== Lab 11a - Writing to a Frame Buffer ===

Revision as of 10:39, 6 April 2011

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.

Note, the workshop calls these labs 6-8. I'm renumbering them to fit our numbering scheme, so the mapping is:

Our Lab Number TI Lab Number
9 5
10 6
11 7
12 8

Lab 09a - Instillation

  • Go to the class dfs site and get
    • DaVinci-OMAP_Workshop_v2.0.pdf
    • tto_workshop_labs_(v2.00).tar
    • makefile_profile.mak
  • 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). I've adapted them for the BeagleBoard.

Lab 09b - gMake

Lab 09 is lab 5 on pages 125-157 of DaVinci-OMAP_Workshop_v2.0.pdf. 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 get 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.

cd /home/user/CodeSourcery/Sourcery_G++_Lite/bin
ln -s arm-none-linux-gnueabi-gcc arm_v5t_le-gcc

Lab 10 - Using the OSS Driver

Lab 10 is Lab 6 is on pages 171-186 of DaVinci-OMAP_Workshop_v2.0.pdf. In doing this lab you will get audio from the line-in jack on the Beagle and sent it out the speaker jack.

  • Go to the class dfs site and get:
    • setpaths.mak
    • setpaths.sh
  • Move the setpaths files in the workshop directory to another location.
host $ cd workshop
host $ mv setpaths.sh setpaths.sh.orig
host $ mv setpaths.mak setpaths.mak.orig
  • Copy the setpaths files you got from DFS into the workshop directory. In Lab 10/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 11 - Using Video Drivers

Lab 11 is lab 7 on page 200 of DaVinci-OMAP_Workshop_v2.0.pdf.

Lab 11a - Writing to a Frame Buffer

Lab 11a 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 11b - Recording Video

Lab 11b 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.

Lab 11c - Video Playback

Lab 12 - Multithread