Difference between revisions of "ECE497 Lab12 The Display SubSystem (DSS)"

From eLinux.org
Jump to: navigation, search
(Lab 7a OSD Setup: Filled in details)
m
Line 3: Line 3:
 
This page explains, with examples, how the Display Subsystem (DSS) on the OMAP3530 on the BeagleBoard works.  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.
 
This page explains, with examples, how the Display Subsystem (DSS) on the OMAP3530 on the BeagleBoard works.  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.
  
Look [[ECE597_Installing_DSP_Development_Tools here]] for instructions on installing the development tools.
+
Look at [[ECE597 Installing DSP Development Tools]] for instructions on installing the development tools.
  
 
Here are my files for Lab 07 [[File:Workshop.Lab07.tar.gz]].  Lab 07 has four parts.  I have three working.
 
Here are my files for Lab 07 [[File:Workshop.Lab07.tar.gz]].  Lab 07 has four parts.  I have three working.
Line 17: Line 17:
 
== Lab 7a OSD Setup ==
 
== Lab 7a OSD Setup ==
  
This lab is a straight forward inspection lab.  Look at <code>video_thread.c</code> and <code>video_osd.c</code> and see how they work.
+
This lab is a straight forward inspection lab.  Look at <code>video_thread.c</code> and <code>video_osd.c</code> and see how they work.  The Beagle code differs from the original workshop code in the the OMAP3530 doesn't have an attribute frame.  All that code has been removed.
  
 
== Lab 7b Video Record ==
 
== Lab 7b Video Record ==
 +
 +
This is also a straight forward inspection lab.  Look at <code>video_thread.c</code> and <code>video_input.c</code> and see how they work.  Ditto on the attribute frame.
 +
 +
== Lab 7c Video Playback ==
 +
 +
Here we really depart from the workshop code.
 +
 +
== Lab 7d Video Loopthru ==

Revision as of 10:06, 17 May 2010


This page explains, with examples, how the Display Subsystem (DSS) on the OMAP3530 on the BeagleBoard works. It's based on the materials used in TI's DaVinci System Integration using Linux Workshop. The workshop is based on the DVEVM. I've converted those materials to the BeagleBoard.

Look at ECE597 Installing DSP Development Tools for instructions on installing the development tools.

Here are my files for Lab 07 File:Workshop.Lab07.tar.gz. Lab 07 has four parts. I have three working.

  1. OSD Setup (Take a bmp file, convert it to r16 format and display it on the GFX frame buffer (/dev/fb0).)
  2. Video Record (Read video from a web cam and store it in a file.)
  3. Video Playback (Read the file from above and display it on one of the video frame buffers (/dev/fb1).)
  4. Video Loopthru (Combine the previous two labs to read the live video and display it.)

I'll update this when I have the Video Loopthru lab working.

Here is a nice set of slides that explain the OMAP3530 DSS. I found a reference to it here. It's worth going through the slides before doing these labs.

Lab 7a OSD Setup

This lab is a straight forward inspection lab. Look at video_thread.c and video_osd.c and see how they work. The Beagle code differs from the original workshop code in the the OMAP3530 doesn't have an attribute frame. All that code has been removed.

Lab 7b Video Record

This is also a straight forward inspection lab. Look at video_thread.c and video_input.c and see how they work. Ditto on the attribute frame.

Lab 7c Video Playback

Here we really depart from the workshop code.

Lab 7d Video Loopthru