EBC Exercise 20 The Display SubSystem (DSS) - Revision history

Richarsm: /* video_thread.c */

2012-10-22T23:35:29Z

‎video_thread.c

2012-09-25T19:50:16Z

‎Part a - OSD Setup

2012-09-25T19:48:30Z

‎Part a - OSD Setup

2012-09-20T13:54:07Z

‎Part a - OSD Setup: Clean up for 2012

2012-07-18T21:40:05Z

2012-07-17T19:31:11Z

2012-05-31T14:09:20Z

‎Build and run

2012-05-31T14:08:29Z

‎osd_thread.c

2012-05-31T14:07:42Z

‎Part a - OSD Setup

2012-05-28T17:18:03Z

Added Header/Footer

@@ Line 104: / Line 104: @@
 '''video_thread_fxn()''' utilizes the following:
 ; video_input_setup()
-: these function is used to detect the video standard which the web cam is using and calculate the corresponding buffer size of a single video frame. It opens and configures the Linux V4L2 video capture driver. The driver uses driver-allocated (as opposed to user-allocated) buffers that are mmapped to the user space to store video frames. Advanced users can take a look in '''video_input.c''' to see the details.
+: This function is used to detect the video standard which the web cam is using and calculate the corresponding buffer size of a single video frame. It opens and configures the Linux V4L2 video capture driver. The driver uses driver-allocated (as opposed to user-allocated) buffers that are mmapped to the user space to store video frames. Advanced users can take a look in '''video_input.c''' to see the details.
 ; fopen()

@@ Line 45: / Line 45: @@
 When you are finished, save with '''File:Save'''. Then exit Gimp. The file should save as RGBA, that is red, green blue, alpha.  Where alpha is the transparency.  It DOES matter what you name the file because later, during the building process, this file is
-specifically copied to the target. This name also makes it easy to remember it’s a 640x80 Bitmap image in 24-bit RGBA.
+specifically copied to the target. This name also makes it easy to remember it’s a 640x480 Bitmap image in 24-bit RGBA.
 * Make sure your file is saved to your lab folder.
@@ Line 68: / Line 68: @@
 # Also  a call is made to '''video_osd_circframe()''' to initialize the OSD buffer with a circular semi-transparent (0x80 is 75% transparency) green frame (0x0000FF is blue, 0x00FF00 is green, 0xFF0000 is red).
-The application assumes the picture is supplied in a 640 x 80 32-bit ARGB (8-8-8-8) format, which should be the case if you followed the previous gimp instructions.
+The application assumes the picture is supplied in a 640 x 480 32-bit ARGB (8-8-8-8) format, which should be the case if you followed the previous gimp instructions.
 * Build and execute the application.

@@ Line 37: / Line 37: @@
 * Paint something for your OSD banner. You can create a simple graphic quickly using just three of the many tools.
 ** Before clicking any of the tools, you can choose a color first using the color box.
-** Start with the gradient tool to create a background. Select the tool, then click and drag the mouse over the 640x80 image area.
+** Start with the gradient tool to create a background. Select the tool, then click and drag the mouse over the 640x480 image area.
 ** Add text or paint something over the gradient with either of these tools, respectively.
 [[File:GimpTools.png | 500px]]

@@ Line 26: / Line 26: @@
 * Get the files from the git repository
- beagle$ '''git clone git@github.com:MarkAYoder/BeagleBoard-exercises.git exercises'''
+Make sure you have the most up to date versions.
-or if you've already git'ted them, make sure you have the most up to date versions.
+  beagle$ '''cd ~/exercises'''
   beagle$ '''cd exercises'''
   beagle$ '''git pull'''
-Either way
-* Change to the directory: VideoThru/lab07a_osd_setup
+* Change to the directory: videoThru/lab07a_osd_setup
 * Open the Gimp (open-source) paint program by typing “gimp Rose640x480a.bmp” in the terminal.
 * Edit the file to create a custom banner picture.

@@ Line 126: / Line 126: @@
 * Run the application
 Enter:
-  $ make
+  beagle$ '''make'''
-  $ ./videoThru_DEBUG.Beagle
+  beagle$ '''./videoThru_DEBUG.Beagle'''
 You will get a message from the application indicating that it has captured video
 frames. Check the following to ensure that the video has recorded properly:
-<pre>
-ls –lsa /tmp/video.raw
+ beagle$ '''ls –lsa /tmp/video.raw'''
-</pre>
 The file should be about 60 MB in size. The reason that the application only records 100 video frames is to keep from overflowing the /tmp directory.

@@ Line 72: / Line 72: @@
 * Build and execute the application.
-<pre>
-$ make debug
+ beagle$ '''make debug'''
-$ ./videoThru_DEBUG.Beagle
+ beagle$ '''./videoThru_DEBUG.Beagle'''
-</pre>
 What do you see?

@@ Line 1: / Line 1: @@
 [[Category:ECE497]]
 [[Category:EmbeddedBeagleClass]]
 This is a four part lab that explore the video system drivers. The labs demonstrate the Linux V4L2 and FBdev drivers as well as basic file I/O, through four small applications: on-screen display (OSD), video recorder, video player, and video loop-thru (video-capture copied to video-display). It's based on the materials used in TI's [http://processors.wiki.ti.com/index.php/OMAP%E2%84%A2/DaVinci%E2%84%A2_System_Integration_using_Linux_Workshop DaVinci System Integration using Linux Workshop].  The workshop is based on the DVEVM.  I've converted those materials to the BeagleBoard.
@@ Line 236: / Line 237: @@
 Once you have the video through working, demo your program to get credit.