Wince6 USB camera (UVC) User Guide

From: http://hi.baidu.com/cahbb/blog/item/6d76093498fe0790a61e120e.html

After setting up the wince6 development environment, next we will test how to use the camera in wince6. I have collected a lot of information and learned a lot of useful things. Here I will record them to help others learn and use them later.

// --------- The following is the content of the Microsoft website

I have seen some questions about Windows Embedded ce DirectShow camera support. So in this article, I will show you how to make the Windows Embedded ce6.0 USB camera running properly on the ARM platform. In this example, we will use our Regulus platform.

Preparations:

• Ce 6.0's platform builder on Visual Studio 2005

• Ce 6.0 USB camera driver

• Regulus ARM development kit with Wince 6.0 R3 BSP. (http://www.e-consystems.com/regulus.asp)
• 3.2 mp usb camera (http://www.e-consystems.com/3mp_cameraboard_usb.asp)

Installation:

How to install Visual Studio and platform builder for ce6.0 is beyond the scope of this article. You can find an article on how to install the wince 6.0 platform builder on the Internet.

After the USB camera driver is installed, the source code of the driver will be automatically stored in the wince600 \ public \ thirdparty directory.

Compile the OS with a USB camera driver:

Create or open an existing osdesign in the Development Kit. Here I have generated a REGULUS-1_DEMO osdesign for our reguplus board.

Because this driver is based on directshow, we need to add the DirectShow filter to the OS image to make our drivers and applications work normally.

Select the following components from the catalog dialog box to add the installed USB camera driver to the OS image:

Is the DirectShow sysgen component:

After adding all the preceding sysgen components, select the following command from the vs2005 menu to compile osdesign:

Build-> advanced buildcommands-> clean sysgen

After compilation is complete, check Ce. bib and reginit. ini in the release directory to check whether the USB cam. dll setting item exists.

Application Compilation:

Now we have added the driver of the USB camera. Next let's test the driver with an application. We can find some DirectShow camera sample applications in the resources shared by WinCE (such as the Private directory. The source code of the camera application can be found in the following directory:

Wince600 \ private \ test \ multimedia \ DirectX \ dshow \ camera \ cameraapp

To generate an executable file for the application for compilation, perform the following steps:
• Select "Open release directory in build window" from the workspace build menu"
• Change the path to wince600 \ private \ test \ multimedia \ DirectX \ dshow \ common \ libs.
• Enter the 'Build-C' command '.
• After the compilation process in these paths is complete, change the path to wince600 \ private \ test \ multimedia \ DirectX \ dshow \ camera
• Enter the 'Build-C' command '.
• Compilation will be performed in these paths, but "Kato. lib" is not available at the end. • Transfer now to wince600 \ private \ test \ multimedia \ DirectX \ dshow \ camera \ cameraapp \

• Enter the 'Build-C' command'
• The application binary file "cameradshowapp.exe" will be generated in the osdesign release directory.
Download and execute:
After compiling the OS images with usbcam.dlland cameradshowapp.exe, we can download this image to the Development Board. After the download is completed and started, connect the USB camera to the USB host port of the Regulus Development Board.
When the program is connected to the device, we can run the program (cameradshowapp.exe) compiled before. This displays a list of optional filters used to generate a filter chart. If the camera driver is correctly loaded, the device name "cam1:" is displayed in this combo dialog box.

Select the desired filter and click OK. The camera preview function is run based on the size of the value supported by the camera, which is close to the value in the registry setting item "preferredwidth. You can check the registry file $ (_ winceroot) \ public \ thirdparty \ catalog \ usbcam \ driver \ usbcam. reg to determine the "preferredwidth" registry key.

Set the following registry items according to the output formats supported by webcam. My camera supports YUV non-compressed output, so my corresponding registry key is set:
[HKEY_LOCAL_MACHINE \ drivers \ USB \ clientdrivers \ video_class] "uncompressedsupport" = DWORD: 1 "m1_support" = DWORD: 0
Go to Tony embedded Forum, http://www.cevx.com/bbs/thread-38322-1-1.html

// ====== The above is the content of the Microsoft website

We recommend the best Website: http://www.msembed.com/, which can be used as a reference. Follow these steps to compile the wicne6 system with a USB camera driver. Error-variable "pci_bus_root" not defined. Remove this error. To go to the following directory:

Root drive letter: wince600 \ platform \ smdk6410 \ files \ platform. Reg is defined as follows:

# Define builtin_roothkey_local_machine \ drivers \ builtin
# Define pci_bus_root $ (builtin_root) \ PCI

Recompile the program and write the program to the Development Board. Then, plug in the camera, and you will not be prompted to enter the name of the USB settings. The driver is added. In the Windows directory of the Development Board, there is a test program, and I don't know how the system seems to come with it. Open and run the program and you will find that you can open the camera.

There is an episode in it. When compiling the camera program using the method described on the Internet, the source code for testing cannot be found. It is suggested that the installation of wince6 was not selected. I want to confirm that it is selected. Later, I installed wince6 with my colleague's installation file. This indicates that the wince6 installation package I am currently using does not have this source code. When using the repair and installation package, I purchased this disk from the development board manufacturer, prompting that the installation cannot be repaired. However, you can use the colleague's installation file to fix the installation. Again, this installation disk provided by the development board manufacturer has a small problem.