Yes, I was able to get this working.  Here are the detailed instructions:

Building and Running the Camera Demo Application
OMAP3 WinCE BSP

Introduction

The WinCE BSP for the OMAP3530 platform includes a camera driver and corresponding camera demo application. This article outlines the steps required to build and run the demo.

Once built, the demo is a WinCE executable file CameraDshowApp.exe. This file simply needs to be executed on a running target. The method described in this article uses SD card boot so it’s best to place the demo executable on the SD card and once the EVM is booted, you can run the demo directly from the SD card.

As it ships at this time (BSP6.14.00), the steps needed to build the demo are not clear or well documented. The steps outlined in this document are the results of the efforts of one applications engineer who went through the process and jotted down the steps along the way, i.e. this document.

Build & Test Conditions

• Development PC
  • MS Windows XP SP2
  • MS Visual Studio 2005 with Platform Builder
  • MS Windows CE 6.00 R3
  • BSQUARE WinCE BSP 6.14.00
• Target Board
  • Mistral OMAP3530 EVM, Rev G
  • Onboard LCD display with touch-screen
  • SD card boot
  • Composite video input from camera

Location of Relevant Files

Following is a list of the relevant files and folders. It assumes WinCE is installed into the default location, i.e. %_WINCEROOT% is c:\WINCE600. These are being listed here just for reference.

• Camera Demo Application Note. This is the in the documentation folder of the BSP6.14.00 folder, depends on where you unzipped that to.
  
  OAK\6.14.00\Documentation\App Note - Video Capture Function with the TI OMAP3 EVM Platform.pdf
  
  
• BSP Platform Specific Build Options. This is where you set environment variables that impact the build process.
  
  c:\WINCE600\PLATFORM\TI_EVM_3530\ti_evm_3530.bat

• BSP Camera Driver. Location of the camera driver. You can view/edit/modify the source using the Solution Explorer.
  
  c:\WINCE600\PLATFORM\TI_EVM_3530\SRC\DRIVERS\CAMERA_MDC

• BSP Camera Demo Application Source.  This is the location of the BSP specific version of the demo application. This app started off as a clone of the Microsoft example and then modified to be BSP specific. Be sure to see the ReadMe.txt file located there.
  
  C:\WINCE600\PLATFORM\TI_EVM_3530\SampleApplications\VideoCapture

• Location of the original Microsoft version of the camera demo application.
  
  C:\WINCE600\PRIVATE\TEST\MULTIMEDIA\DIRECTX\DSHOW\CAMERA

• Location of the flat release directory. This is where the OS design output files and the demo application will reside after building.
  
  C:\WINCE600\OSDesigns\EVM_3530\EVM_3530\RelDir\TI_EVM_3530_ARMV4I_Release

• E2E forum post related to this topic.
  
  http://e2e.ti.com/support/embedded/f/353/p/52573/186425.aspx#186425

• Utility used to create a bootable SD card and copy the OS files onto it. (The base location could differ depending on where you unzipped the BSP package to).
  
  C:\WINCE600\bspsource_omapwince_06_14_00\OAK\6.14.00\Tools\SDCard_boot_utility\TI_SDCard_boot_utility_v1_0.exe

Summary of Steps

Below is a quick summary of the steps needed.

• Build the OS design using the specific build environment settings to enable the camera driver
• Create a bootable SD card image using the OS design
• Build the default Microsoft sample camera application, this is just to validate your WinCE install
• Copy the BSP specific camera sample application source over the original Microsoft source
• Build the BSP specific camera sample application
• Copy the camera sample application to your SD card
• Boot the EVM using the OS design on SD card
• Execute the sample camera application from the SD card

Step-by-Step Instructions

This section will walk you through step by step.

Build Your OS Design

1. Open your OS design solution in Visual Studio
   C:\WINCE600\OSDesigns\EVM_3530\EVM_3530.sln
   
   
2. Set your high level build options as shown below. To bring up this dialog box, use the Project->EVM_3530 Properties menu. Make sure you select the Release configuration. Check the boxes to match the below screen shot.
   
   
   
   
   
3. Edit C:\WINCE600\PLATFORM\TI_EVM_3530\ti_evm_3530.bat to set appropriate build variables. The following list shows the appropriate variable settings. Some of these variables already exist so find them and make sure they are set accordingly. A couple of these don’t so you have to add them.
   1. set BSP_EVM2_VIDEO_CAPTURE=1
   2. set SYSGEN_DSHOW_ERRORS=1
   3. set SYSGEN_DSHOW_CAPTURE=1
   4. set BSP_NOCAMERA_MDC=
   5. set SYSGEN_OSTEST=1
   6. set BSP_NOCAMERA=1
   7. set BSP_NOVRFB=1
      
      
4. Make sure when you build your OS design you are set for Release build…
   
   
   
   
   
   
5. Clean the OS design using the menu Build->Clean Solution
6. Build the OS design using the menu Build->Build Solution
7. Go have a cup of coffee while it builds
8. Create a bootable SD card using the new OS design
   1. Launch TI_SDCard_boot_utility_v1_0.exe
   2. Select the MLO file from you flat release directory (click the … button)
      
      C:\WINCE600\OSDesigns\EVM_3530\EVM_3530\RelDir\TI_EVM_3530_ARMV4I_Release\MLO
      
      
      
   3. Now select the ebootsd.nb0 and NK.bin files from the same folder. HINT: when using the SD card utility, you have to select both the ebootsd.nb0  and NK.bin file at once, i.e. first select ebootsd.nb0 and then scroll over and find NK.bin and hold the CTRL-key and click NK.bin. Then hit open.
      
      C:\WINCE600\OSDesigns\EVM_3530\EVM_3530\RelDir\TI_EVM_3530_ARMV4I_Release\EBOOTSD.nb0
      
      C:\WINCE600\OSDesigns\EVM_3530\EVM_3530\RelDir\TI_EVM_3530_ARMV4I_Release\NK.bin
      
      
      
      
      
      
      
   4. Select Proceed, this will launch the Windows format utility. MAKE SURE YOUR SD CARD is SELECTED and format for FAT.
      
      
   5. Once the format completes, click OK and then the SD card utility will continue to copy the files. It also tags the boot sector as bootable.
      
      
9. Now you have a bootable SD card, it’s advisable to test this out before continuing.
   1. Place the SD card into the slot on the EVM
   2. Set the EVM dip switches (SW4) for SD card boot.
      
      
      
      
   3. Wait for it to boot, takes about a minute when booting from SD card. Since we disabled KITL when we built the OS design, the default EBOOT boot option will be NK.bin from SD card. If you have KITL enabled by default in your OS design then you’ll need to launch a terminal like teraterm connected to the EVM UART3 and tell eboot to boot from SD card.

Build the Sample Camera Application

1. Follow the directions from the forum post http://e2e.ti.com/support/embedded/f/353/p/52573/186425.aspx#186425
   
   The text of the custom directions are pasted below for reference. Skip steps I.1, I.2, and I.3 and start with I.4. Also, an additional step was added to correct a library reference error. After following these steps, copy the executable from the flat Release Directory to your SD card.
   
   

The CameraDshowApp.exe can be used to demonstrate the video capture

using the OMAP EVM MAIN BOARD REV D coupled with the MDC (Multimedia

Daughter Card) or with the OMAP EVM MAIN BOARD REV G (EVM2).

The EVM_3503_MDC (for EVM1+MDC) or EVM_3530 (for EVM2) sample OS configuration contain the OS components needed to run this application.

-------------------

Build Instructions:

-------------------

Please make sure to turn VRFB off in the ti_evm_3530.bat file ("set BSP_NOVRFB=1" and make a clean BSP build) when trying the Video capture application. The capture/preview that is part of Video Capture application does not handle the large stride needed for VRFB

I.       Building the CameraDshowApp from Microsoft Shared Source

1.  Install Share Source from CE6 installation (if not done already). The default location is %_WINCEROOT%\private

2.  In your Visual Studio platform builder BSP project,select Project->EVM_3530 properties->Environment and enter a new environment variable SYSGEN_OSTEST and set the value to be 1.

3.  Do a clean build of your solution (this will create some OS test components that are needed by the test app)

START HERE

4.  Once this completes, click on Build->"Open Release directory in build window"

5.  cd %_WINCEROOT%\PRIVATE\TEST\MULTIMEDIA and run "build -c"

6.  This step may not proceed all the way and may give a failure but it does generate most of is needed for CameraDshowApp

7.  In the command window, "set DX_TST_ROOT=%_WINCEROOT%\PRIVATE\TEST\MULTIMEDIA\DIRECTX"

8.  cd %_WINCEROOT%\PRIVATE\TEST\MULTIMEDIA\DIRECTX\DSHOW and run "build"

9.  This build may also fail after a while but you should see CameraDshowApp.exe under your %_FLATRELEASEDIR%.

10. This is the app based on Microsoft shared source.

11. If you do not see the CameraDshowApp.exe following the steps above, please contact Microsoft support

II.      Building the CameraDshowApp for TI_EVM_3530 that is released as part of the BSP. (Depends on successful completion of the steps above)

1.  Replace the following sample camera app directories from Microsoft with the ones provided in the BSP (under TI_EVM_3530\SampleApplications\VideoCapture\Src). I would save off the originals in case you ever need to restore them

%_WINCEROOT%\PRIVATE\TEST\MULTIMEDIA\DIRECTX\DSHOW\CAMERA\FRAMEWORK

%_WINCEROOT%\PRIVATE\TEST\MULTIMEDIA\DIRECTX\DSHOW\CAMERA\CAMERAAPP

2.  cd %_WINCEROOT%\PRIVATE\TEST\MULTIMEDIA\DIRECTX\DSHOW\CAMERA\FRAMEWORK and run "build -c"

3.  cd %_WINCEROOT%\PRIVATE\TEST\MULTIMEDIA\DIRECTX\DSHOW\CAMERA\CAMERAAPP

4.  The next step to build the camera app doesn’t build properly as is, it has an incorrect path to a dependent libray file. So to fix this, you need to edit the sources file first to point to the correct library file.

Edit…
 C:\WINCE600\PRIVATE\TEST\MULTIMEDIA\DIRECTX\DSHOW\CAMERA\CAMERAAPP\sources

Change…

           $(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\CaptureFramework.lib \

To…

c:\WINCE600\OSDesigns\EVM_3530\EVM_3530\Wince600\TI_EVM_3530_ARMV4I\OAK\lib\ARMV4I\retail\CaptureFramework.lib \

5.  run "build -c"

6.  You should see the newly built CameraDshowApp.exe under the %_FLATRELEASEDIR% that you can load and execute

-------------

Known Issues:

-------------

This application requires a large amount of free RAM (~30 MB).

There is a large memory leak associated with using this application. To

work around this issue, reboot the EVM after running the application.

The application fails to operate under a retail build in some cases. To

work around this issue a debug build can be used.

Run the Sample Application

1. Make sure the sample application built properly from the above steps, check the timestamp to make sure it’s the one just built in case an old version was there.
   
   
2. Copy the resulting executable to your SD card
   
   %_FLATRELEASEDIR%\CameraDshowApp.exe
   
   
3. Boot the EVM using the SD card and execute the CameraDshowApp.exe file directly from the SD card.
   
   
4. Here’s some notes related to the application…
   1. When you first run it, it’s automatically in preview mode, i.e. capture to display loopback
   2. Make sure the correct input source is selected
   3. Do not click start, this is supposed to begin encoding the captured video to a file but it seems to lock up the app.
   4. Make sure to read the ReadMe.txt file in the sample app folder, it mentions a memory leak.