QT210开发板WinCE6安装使用手册V1
qt-wince 安装开发及部署全解
Qt-WinCE 安装、开发及部署全解Qt-WinCE安装、开发及部署全解CTO技术网我要评论(0)一、Qt 嵌入式环境的搭建a) 首先，下载Qt的嵌入式开发包qt-embedded-wince-opensource-src-4.4opensourc embed 下载.0.zipb) 然后，下载VS2005。
c) 最后，下载一个嵌入式开发的SDK，如Windows Mobile5.0window mobil 下载Pocket PC SDK,可以在微软的官方网站上下载到！d) 还有一个是同步的软件Microsoft ActiveSync4.5中文简体版。
activesync microsoft 简体------------------------------------------安----装----------------------------------e) 首先安装VS2005，很简单，按照向导来，在自定2005 安装向导义安装中务必选择“智能设备开发”。
f) 关于Microsoft ActiveSync4.5的安装更是“straightforward”。
在此不再activesync microsoft 关于多说！g) 然后，安装Windows Mobile或是其它版本的SDK，可以用自windowmobil 或是定义的SDK!简单h) 比较麻烦的就是qt-embedded-wince的安装。
参照下面的步embed 下面参照骤：①、解压，将解压后的文件夹放到一个不含空格的路文件夹空格一个径中，如我的：f:\penguinx\qt_wince，qt_wince即为此文件夹。
然后设置penguinx 文件夹设置环境变量：右键“我的电脑”－>“属性”－>点“高级环境变量电脑”标签－>“环境变量”选项－>在"PATH"中添加路径“f:\penguinxpenguinx 环境路径\qt_wince \bin”。
wince6.0操作手册
Section 0 – 1:Clone a BSPCreate, Build, and Run a New OS DesignLearning ObjectivesCreate an OS Design using Visual StudioIdentify the catalog features included in the designExtend the standard design by adding catalog itemsBuild configuration for the run-time image and build a run-time imageRun the OS image on the target deviceEstimated time to complete this lab:45 minutesExercise 1: Clone BSPIn this exercise, you will use the Clone BSP tool in Visual Studio 2005 to create a copy of the existing Device Emulator Board Support Package (BSP). We can modify this copy instead of modifying the original that was delivered as a part of the Windows Embedded CE 6.0 tools. Clone the DeviceEmulator BSP1. Launch Microsoft Visual Studio 2005.Note If this is the first time Visual Studio is launched after installation the Choose Default Environment Setting dialog will be displayed. For the purposed of this course select Platform Builder Development Settings and select Start Visual Studio.2. Select the Tools | Platform Builder for CE6.0 | Clone BSP from the menu in VisualStudio to bring up the Clone BSP dialog box.3. In the Clone BSP dialog, drop down the Source Board Support Package and selectDevice Emulator: ARMV4I BSP for clone.Note If you are working with a hardware reference platform, select the BSP corresponding to your specific hardware.4. Type TrainingBSP in the Name field in the New Board Support Package Info area.5. Type a description for your new BSP in the Description field.6. Type TrainingBSP in the Platform Directory field.7. Type GeneriCo in the Vendor field.8. Type 1.0 in the Version field.9. Click the Clone Button. The Clone BSP tool will create a new Board Support Packagebased on the DeviceEmulator Board Support Package.10. Acknowledge the Clone BSP success message by selecting OK.11. Open the C:\WINCE600\PLATFORM\TrainingBSP\FILES folder using WindowsExplorer.Note The labs in this course refer to the default installation path for OS Build Tree, which is “C:\WINCE600”. If your path is something other than the default you will need to make theadjustment anytime the path is noted.12. Rename the deviceemulator-preri.bat file to trainingbsp-preri.bat.Note The previous step was necessary due to a bug in the Clone BSP tool. It is only necessary if the source BSP contains certain build related batch files in the FILES directory. This is notcommon, but is the case with the DeviceEmulator BSP. Failure to make the change will causea build error in a later step.The DeviceEmulator Board Support Package has now been cloned into a new Board Support Package called TrainingBSP. The TrainingBSP Board Support Package will be used in the remaining labs.Exercise 2: Create, build and run the OS designIn this exercise you will create an OS design, and then customize that design by adding components from the catalog and build the result. You will run the OS design on the Device Emulator.This OS design will be used in other labs and will be a suitable platform for running a variety of Windows CE applications.You will learn how to:Create an OS DesignSet up the build configuration for your OS run-time imageBuild an OS run-time imageRun the OS Design on the Device EmulatorCreate an OS design1. Select File | New | Project… from the Visual Studio menu.2. Select the Platform Builder for CE 6.0 project type in the New Projectdialog.3. Select OS Design under Visual Studio installed templates.4. Type TrainingOSDesign in the Name field. The solution name willdefault to TrainingOSDesign as well.5. Click OK. Visual Studio will launch the Windows Embedded CE6.0 OS Design Wizard.6. Click Next.7. In the list of available BSPs, select TrainingBSP: ARMV4I and click Next.8. From the list of available design templates, select PDA Device and clickNext.9. From the list of available design variants, select Mobile Handheld andclick Next. The Applications & Media configuration window willappear.10. Deselect .NET Compact Framework 2.0 and ActiveSync and clickNext. The Networking & Communications configuration window willappear.11. Deselect TCP/IPv6 Support.12. Deselect Personal Area Network (PAN). This will deselect Bluetoothand IrDA.13. Click Next, and then Finish to complete the Windows Embedded CE6.0 Design Wizard.Note The wizard creates the initial configuration for your OS design. We will have the opportunity to make further changes to the OS design after completing the wizard.14. Click Acknowledge on the Catalog Item Notification dialog.On completion, Visual Studio will display your OS design project. The SolutionExplorer tab should be active and show your new TrainingOSDesign project inyour TrainingOSDesign Solution.Inspect the OS Catalog15. Click on the Catalog Items View tab to display the Catalog.16. Click on the Filter drop down box in the upper left hand corner of theCatalog Items View. Observe the different filtering options. The filtercontrols the items that are displayed in the catalog. Ensure that AllCatalog Items in Catalog is selected.17. Observe the selection boxes and icons in the catalog by expanding thenodes. Selection boxes with a green check mark indicate an item thatwas specifically selected as a part of the OS design. Selection boxeswith a green square indicate an item that was brought in to the OSdesign as a dependency. Selection boxes that are not marked indicateitems that are not included in the OS design but are available to beadded.18. Locate a catalog item with a green square in its checkbox.19. Right click on the catalog item and choose Reasons for Inclusion ofItem. The Remove Dependent Catalog Item dialog box displays thecatalog items you selected that caused this catalog item to automatically be included in the OS design.20. Close the Remove Dependent Catalog Item dialog box.21. Expand the Core OS | CEBASE | Applications – End User | Active Syncnode in the catalog.22. Right click on either of the ActiveSync system cpl items (or double click)and select Display in Solution View. The view will change to theSolution Explorer tab. The subproject containing the ActiveSynccomponent is displayed.This is a great way to navigate the source code that is available as partof Windows Embedded CE 6.0.Add support for Internet Explorer 6.0 Sample Browser catalog item23. Select the Catalog Items View tab to display the OS design catalog.Note If the filtering option was not set to All Catalog Items in Catalog, you would not see catalog items that were not already included in the OS design.24. Enter the text Internet Explorer 6.0 Sample into the search text box tothe right of the filter button. Press Enter or click the green arrow. Thepath Core OS | CEBASE | Internet Client Services | Browser Application| Internet Explorer 6.0 for Windows Embedded CE – StandardComponents should be expanded.Note Depending on where you are currently located in the catalog, you may have to restart the search from the top.25. Select, to check, the Internet Explorer 6.0 Sample Browser catalogitem.Add support for managed code development to your OS design26. Enter the text ipconfig into the Search box and press Enter. TheNetwork Utilities (IpConfig, Ping, Route) will be highlighted.Note Again, depending on node selected when starting a search in the catalog, you may have to restart the search from the top.27. Add the Network Utilities to your design by selecting the component.28. Enter the text wceload into the Search box and press Enter. The CABFile Installer/Uninstaller component will be highlighted. This is due tothe fact that the SYSGEN name for the component is “wceload”.29. Add the Cab File Installer/Uninstaller utility to your OS design.30. Enter the text sysgen_dotnetv2_support into the Search box andpress Enter. The OS Dependencies for .NET Compact Framework2.0 component will be highlighted.31. Add the OS Dependencies for .NET Compact Framework 2.0 to yourOS design.Note There are two separate components in this category. Be sure you select the one that does NOT have the – Headless modifier in its description.Build the OS run-time image32. Select Build | Configuration Manager… from the Visual Studio menuto bring up the Configuration Manager dialog box.33. Select TrainingBSP ARMV4I Debug from the Active solutionconfiguration drop down box and then close the dialog box.34. Select the Solution Explorer view by selecting the Solution Explorertab.35. In the Solution Explorer window, right click on theTrainingOSDesign project (not the Solution node) and chooseProperties. This will launch the Property Pages dialog for your OSdesign.36. Expand the Configuration Properties tree and click on the BuildOptions node.37. Ensure the following build options are set:Enable eboot space in memoryEnable kernel debuggerEnable KITLEnable profiling38. Select OK39. Select Build | Build TrainingOSDesign from the Visual Studio menu.Note This will take several minutes to complete depending on the capabilities of your development system. The following steps for configuring connectivity may be accomplished while building.Configure connectivity options40. Select Target | Connectivity Options… from the Visual Studio menu.The Target Device Connectivity Options dialog will appear showingthe Kernel Service Map configuration for the CE Device namedconnection.41. Select Device Emulator (DMA) from the Download drop down box.42. Select Device Emulator (DMA) from the Transport drop down box.43. Select KdStub from the Debugger drop down box.Change the emulator configurationThe emulator has a number of configurable options. We will modify it to use a larger screen resolution and to enable network communications.44. Next to the Download drop down menu click Settings.45. Select the Display tab in the Emulator Properties dialog box.46. Change the Screen width to 640 pixels and the Screen height to 480pixels.47. Select the Network tab in the Emulator Properties dialog box.48. Check the box beside Enable NE2000…49. Click on OK50. Select Apply to save the new device configuration.51. Select Close to close the dialog box.Note The build must complete before moving on to the next step.Test your OS run time image on the Device Emulator52. Select Target | Attach Device from the Visual Studio menu.Visual Studio will start the Device Emulator with your OS run time image design. The download will take a short time to complete. You will be able to interact with the emulator and test the features of your new OS design. Congratulations, you have successfully built and run your first Windows Embedded CE 6.0 OS design!If you are continuing with the next Hands-On Lab, keep your emulator image running.Section 0 – 2:Static and Dynamic LibrariesObjectivesCreate simple static libraryLink the static library with a dynamic libraryLink the dynamic library with an executableEstimated time to complete this lab:45 minutesExercise 1: Create a static library (LIB)In this exercise you will create a static library with routines that you will later link to when you build a dynamic library and an executable.Note This exercise involves a bit of typing; if you perfer you may copy the text from the Student files. Create a static library subproject1. Select Project | Add New Subproject… from the Visual Studio menu.This will bring up the Windows CE Subproject Wizard.2. Select the WCE Static Library template.3. Set the Subproject name to Power_Status and click Next.4. Check the Precompiled header box.5. Click Finish.6. Configure the Power_Status subproject to be excluded from theimage and always build and link as debug. (In Solution ExplorerView, right click the TrainingOSDesign and select the Properties)Create files7. Right click on the Power_Status subproject in the Solution Explorerand select Add | New Item…8. Select the Code category, the C++ File (.cpp) template, and then typePower_ON_OFF in the name field.9. Click on Add to add the new file.10. Right click on the Power_Status subproject in the Solution Explorerand select Add | New Item…11. Select the Code category, the Header File (.h) template, and thentype Power_Status in the name field.12. Click on Add to add the new file.13. Using the Solution Explorer, locate the Power_ON_OFF.cpp file in thePower_Status subproject and open it.14. Add the following code to the Power_ON_OFF.cpp file:#include"stdafx.h"LPCTSTR g_StrOn = L"Power is on";LPCTSTR g_StrOff = L"Power is off";LPCTSTR PowerOn(){return g_StrOn;}LPCTSTR PowerOff(){return g_StrOff;}15. Save and close Power_ON_OFF.cpp.16. Expand the Include files node in the Power_Status subproject andopen stdafx.h17. Add an include for <windows.h> as follows:// TODO: reference additional headers your program requires here#include<windows.h>18. Save and close stdafx.h.19. Using the Solution Explorer, locate the Power_Status.h file in thePower_Status subproject and open it.20. Add the following to Power_Status.h:extern LPCTSTR PowerOff(void);extern LPCTSTR PowerOn(void);21. Save and close Power_Status.h.Build the library22. Right click the Power_Status subproject in the Solution Explorer andselect Build.Exercise 2 Create a dynamic library (DLL)In this exercise you will create a dynamic library that will link with the static library you created previously.Note This exercise involves a bit of typing; if you perfer you may copy the text from the Student files.Create the dynamic library subproject1. Select Project | Add New Subproject… from the Visual Studio menu.2. Select the WCE Dynamic-Link Library template.3. Set the Subproject name to ScanBarcode and click Next.4. Select A simple Windows Embedded CE DLL subproject and clickFinish.5. Configure the ScanBarcode subproject to be excluded from theimage and always build and link as debug.Edit source files for DLL project6. In the Solution Explorer, right-click on the ScanBarcode subproject,and then select Add | New Item…7. Select the Code category, the Header File (.h) template, and then typeScanBarcode in the name field.8. Using the Solution Explorer, open the ScanBarcode.h file from theScanBarcode subproject.9. Add the following code to the ScanBarcode.h file:#include<windows.h>EXTERN_C LPCTSTR ScanBarcode(void);EXTERN_C LPCTSTR ScanPowerOff(void);EXTERN_C LPCTSTR ScanPowerOn(void);10. Using the Solution Explorer, open the ScanBarcode.def file from theParameter files node in the ScanBarcode subproject.11. Add the following to the DEF file:LIBRARY ScanBarcodeEXPORTSScanPowerOffScanPowerOnScanBarcode12. Save and close ScanBarcode.def.13. Using the Solution Explorer, open the ScanBarcode.cpp file from theScanBarcode subproject.14. Add an include statement for Power_Status.h as follows:// ScanBarcode.cpp : Defines the entry point for the DLL application.//#include"stdafx.h"#include"Power_Status.h"BOOL APIENTRY DllMain( HANDLE hModule,DWORD ul_reason_for_call,LPVOID lpReserved){return TRUE;}15. Add the following code snippet to ScanBarcode.cpp after the inclusionof Power_Status.h.LPCTSTR g_StrScan = L"123456789ABC";EXTERN_C LPCTSTR ScanBarcode(void){return g_StrScan;}EXTERN_C LPCTSTR ScanPowerOn(void){return PowerOn();}EXTERN_C LPCTSTR ScanPowerOff(void){return PowerOff();}16. Save and close ScanBarcode.cpp.Link to static library17. Right click on the ScanBarcode subproject node in the SolutionExplorer, and then select Open. The ScanBarcode SOURCES filwill open.18. Locate the section of the file containing TARGETLIBS.19. Add a reference to the Power_Status.lib static library by modifying thissection as follows:TARGETLIBS= \$(_PROJECTROOT)\cesysgen\sdk\lib\$(_CPUINDPATH)\coredll.lib \$(PBWORKSPACEROOT)\Power_Status\obj\$(_CPUINDPATH)\Power_Status.lib \Note The trailing backslash characters on each line are line continuation characters. Ensure that there is no white space after them. Also, ensure that there is a blank line following the last line.20. Add the path to directory containing the Power_Status.h header file byadding the following to the bottom of the SOURCES file:INCLUDES= \$(PBWORKSPACEROOT)\Power_Status \Note Ensure that there is at least one blank line prior to the line containing the INCLUDES directive.This ensures that there are no line continuation characters prior to this statement that are still in effect.21. Save and close the SOURCES file.22. Right click on the ScanBarcode subproject in the Solution Explorerand select Properties.23. Select the C/C++ tab and observe the Include Directories entry.Notice that the directory you just added with the INCLUDES directivein the SOURCES file is listed here.24. Select the Link tab and observe the Additional Libraries entry.Notice that the library you just added with the TARGETLIBS directivein the SOURCES file is listed at the end of this line.Note The SOURCES file itself controls the build rules for the subproject. The graphical user interface shown here provides an alternate way to view and modify this file.25. Select Cancel to close this dialog without making any changes.Build the library26. Right click the ScanBarcode subproject in the Solution Explorer andselect Build.Exercise 3 Create an executable (EXE)In this exercise you will create an executable that uses functionality from the dynamic library you just created.Adding existing application subproject1. Copy the BarcodeDllTest subproject from the Student files to your OSdesign atC:\WINCE600\OSDesigns\TrainingOSDesign\TrainingOSDesign.2. Right click on the Subprojects node in the Solution Explorer and selectAdd Existing Subproject.3. Select the BarcodeDllTest.pbpxml file from the BarcodeDllTestfolder.4. Configure the BarcodeDllTest subproject to be excluded from theimage and always build and link as debug.Add reference to dll5. Right click on the BarcodeDllTest subproject in the Solution Explorerand select Open.6. Add the following to the bottom of the file:INCLUDES= \$(PBWORKSPACEROOT)\ScanBarcode \Note Ensure that there is a blank line preceding the INCLUDES directive. Ensure there is no whitespace after the trailing backslashes.7. Locate the TARGETLIBS directive and add a reference toScanBarcode.lib as follows:TARGETLIBS= \$(_PROJECTROOT)\cesysgen\sdk\lib\$(_CPUINDPATH)\coredll.lib \$(PBWORKSPACEROOT)\ScanBarcode\obj\$(_CPUINDPATH)\ScanBarcode.lib \Note Ensure that there is a blank line after the line containing ScanBarcode.lib. Ensure there is no white space after the trailing backslashes.8. Save and close the sources file.9. Right click on the BarcodeDllTest subproject and select Build.Run the BarcodeDllTest application10. Launch BarcodeDllTest.exe using Target | Run Programs from theVisual Studio menu.11. The BarcodeDllTest.exe application will present the following userinterface. You can exercise it by clicking on the various buttons.This simple application makes calls into the linked Scanbarcode.dll dynamic library, which includes functionality from the Power_Status.lib static library. You may wish to set breakpoints on functions in these modules and view the call stacks to see how they are eventually called from the application.Section 1:Integrating a Device DriverEstimated time to complete this lab: 30 minutesExercise 1: Integrate barcode scanner driver into BSPThe purpose of this exercise is to integrate a driver into the BSP. In this exercise you will Add the driver subdirectory containing the driver source code to the BSPAdd the appropriate bib entry to cause the driver to be included in the OS image Add the appropriate registry entries to cause the drive to be loaded at bootUpdate the BSP catalog file to support the new driverBuild a debug OS run-time image that we will use in future labsAdd driver source code to BSP directory1. Detach from the Emulator if connected.2. Copy the BARCODE directory from Student files to theC:\WINCE600\PLATFORM\TrainingBSP\SRC\DRIVERS directory.3. Double click the C:\WINCE600\PLATFORM\TrainingBSP\src\driversnode in the Solution Explorer. This will open the Dirs file.4. Add the following line to the end of the Dirs file directly after the# @CESYSGEN ENDIF CE_MODULES_DEVICE line:barcode \5. Save and close the Dirs file.Add Driver to image6. Open the platform.bib file in the Parameter Files node of theTrainingBSP in the Solution Explorer.7. Add the following lines near the top of platform.bib as the first entryin the MODULES section.IF BSP_BARCODEbarcode.dll $(_FLATRELEASEDIR)\barcode.dll NK SHK ENDIFWhen you are done, the top of the file should look similar to the following:;; Copyright (c) Microsoft Corporation. All rights reserved.;;; Use of this source code is subject to the terms of the Microsoft end-user; license agreement (EULA) under which you licensed this SOFTWARE PRODUCT.; If you did not accept the terms of the EULA, you are not authorized to use; this source code. For a copy of the EULA, please see the LICENSE.RTF on your; install media.;MODULES; Name Path Memory Type; -------------- ---------------------------------- -----------IF BSP_BARCODEbarcode.dll $(_FLATRELEASEDIR)\barcode.dll NK SHKENDIF; @CESYSGEN IF CE_MODULES_DISPLAYIF BSP_NODISPLAY !TrainingBSP_lcd.dll $(_FLATRELEASEDIR)\TrainingBSP_lcd.dll NK SHK; @CESYSGEN IF SHELLW_MODULES_GX; @XIPREGION IF MISC_TRAININGBSP_BIB8. Save and close the file.Add registry settings9. Open the file Platform.reg from the Parameter Files node of theTrainingBSP using the Solution Explorer.10. Right click on the [HKEY_LOCAL_MACHINE\Drivers\BuiltIn] keyand add a new key with the name Barcode.11. Add a String Value to the Barcode key with the name Dll and valueBarcode.dll.12. Add a String Value to the Barcode key with the name Prefix andvalue BAR.13. Save and close the file.Add driver to the catalog14. From the Visual Studio menu, select File | Open | File … and navigateto the C:\WINCE600\PLATFORM\TrainingBSP\CATALOG folder.15. Change the file mask to show Files of type: All Files (*.*)16. Open the TrainingBSP.pbcxml file.Note If no nodes are visible underneath Catalog in the Catalog Editor, click the Show All Catalog Files button.17. Expand the catalog tree to show the Device Drivers node.18. Right click on the Device Drivers node and select Add Catalog Item.The new item will be placed in the Third Party node.19. Set the Description field to Barcode Scanner.20. Set the Title field to Barcode Scanner.21. Set the Unique Id field to Item:GeneriCo:BarcodeScanner.22. Set the Additional Variables field to BSP_BARCODE.23. Set the Modules field to barcode.dll.24. Save and close the file.Add barcode scanner driver to image25. Switch to the Catalog Items View.26. Expand the TrainingBSP node under Third Party.Note Ensure that the Filter option is set to All Items in the Catalog. The Filter option is a drop down box in the upper right hand corner of the Catalog Items View.27. Select the Barcode Scanner item under Device Drivers. Refresh theCatalog View if necessary to see the Barcode Scanner.28. Select Build | Advanced Build Commands | Build Current BSPand Subprojects from the Visual Studio menu.Verify integration using Image Viewer29. Open the NK.bin file located in the flat release directory using VisualStudio. This will bring up the Run-Time Image Viewer.30. Click on the (All Files) node in the Image Explorer. This shows allfiles that are built into the OS run time image.31. Verify that barcode.dll is listed.32. Verify that the [HKLM\Drivers\BuiltIn\Barcode] key exists under theregistry node.33. Close the Image Viewer.Build debug OS image34. Select Build | Configuration Manager… using the Visual Studiomenu.35. Set the Active solution configuration to TrainingBSP ARMV4IDebug.36. Select Build | Build Solution using the Visual Studio menu. This willbuild a debug configuration that we will use in future labs.Section 2:Debugging the Scanner Device Driver ObjectivesUnderstand driver interaction with applicationUse kernel debugger to investigate call stackEstimated time to complete this lab: 30 minutesExercise 1 Application and Driver IntegrationIn this exercise you will add an application that communicates with the barcode scanner device driver. You will exercise the functionality of the driver and function call tree that results when the application calls into the driver.Add BarcodeTest1 application subproject to your OSDesign1. Copy the BarcodeTest1 folder from your Student files toC:\WINCE600\OSDesigns\TrainingOSDesign\TrainingOSDesign.2. Right click on the Subprojects node in the Solution Explorer and selectAdd Existing Subproject...3. Add the BarcodeTest1 subproject to your OS design.4. Configure the BarcodeTest1 subproject to be excluded from theimage and always build and link as debug.5. Right click on the BarcodeTest1 subproject in the Solution Explorerand select Build.Run test application on OS image6. Attach the emulator by selecting Target | Attach Device from the VisualStudio menu.Note This lab uses an updated version of the OS run time image. You will need to first detach from the existing emulator instance if it is still running.7. Open the BarcodeTest1.cpp file in the BarcodeTest1 subproject usingthe Solution Explorer.8. Set a breakpoint on the call to DeviceIoControl().9. Run the BarcodeTest1 application using Target | Run Programs…from the Visual Studio menu. The debugger will halt execution at thebreakpoint.10. Select Debug | Windows | Call Stack from the Visual Studio menu toshow the call stack. This window shows the sequence of calls thatresulted in the statement containing the breakpoint. You can doubleclick any of the calling functions to view the source code file containingeach function.Note The source code for the functions listed in this window is only available if you have installed the Shared Source. Only the disassembly view is available if the source code is not installed.11. Step through the application by pressing F10 through completion.Add additional functionality to test application and retest12. Locate the comment //Turn on power and add the following functioncall:Code:// Turn on powerDeviceIoControl(hBARPort, BARCODE_IOCTL_POWER_ON, NULL, 0, NULL,0, &dwNumBytesRead, NULL);13. Locate the comment //Check to make sure power is on and add thefollowing function call:Code:// Check to make sure power is onDeviceIoControl(hBARPort, BARCODE_IOCTL_QUERY_POWER_STATE,NULL,0, &dwResult, sizeof(DWORD), &dwNumBytesRead, NULL);_tprintf(_T("Power Status = %d.\n"),dwResult);14. Right click on the BarcodeTest1 subproject and select Build.15. Run the BarcodeTest1 application using Target | Run Programs…from the Visual Studio menu. The debugger will halt execution at thebreakpoint.16. Press F517. Observe debug messages in the Output window similar to thefollowing:Test BAR1: driver open/close.Barcode.DLL: +BAR_OpenBarcode.DLL: -BAR_OpenCreateFile returned a valid handle.Barcode.DLL: +BAR_IOControlBarcode.DLL: IOCTL - Set Power ManagementBarcode.DLL: -BAR_IOControl。
Wince6.0安装指南
实验四搭建WinCE 6.0 开发环境一．课时安排：4学时二．实验目的通过本实验掌握Windows CE 6.0 开发环境Platform Builder 的安装。
三．实验设备（1）硬件：PC机一台（2）软件Visual Studio 2005Windows CE 6.0安装软件四．实验内容安装VS2005安装MSDN（可选）安装Windows CE 6.0(Platform Builder for Windows CE 6.0)安装Windows CE 6.0 R2安装Windows CE 6.0 R3五．实验原理在Windows CE 6.0 之前，Windows CE 的开发环境都是当做一个独立的软件进行安装，安装成功之后用户可以看到一个名为Platform Builder for CE4.2/5.0 的工具，用户就直接使用这个IDE 来定制OS。
这种情况到Windows CE6.0 后做了较大改变，在安装Windows CE 6.0 之前必须安装VS2005，在顺利安装完VS2005 以及Windows CE 6.0 后，可看到对应的开发工具PlatformBuilder for Windows CE 6.0 当做一个插件集成到VS2005 的开发环境中。
本设备用到的Windows CE 6.0 R3 其实是Windows CE 6.0 的最新版本，这之前的版本号是Windows CE 6.0 R2。
通过以上知识点的了解就可以明白接下来安装开发环境各步骤先后顺序的关系。
六．实验步骤1.开发应用程序需安装软件及更新（软件列表见“WinCE 6.0下载列表”）Visual Studio 2005Visual Studio 2005 SP12.开发Windows Embedded CE 6.0操作系统需依次安装软件及更新开发WinCE 6.0系统，除按上面次序安装VS2005外，还需要按次序安装以下软件及补丁，由于安装路径对程序开发有一定的影响，为保持统一，减少不必要的麻烦，本文假定所有安装都是按照默认路径。
WinCE6.0搭建开发环境及模拟器
Windows Embedded CE 开发环境搭建过程1、先装Visual Studio 2005, 我拿到的是Professional Edition 英文版的。
需要使用虚拟光驱软件加载后再安装，公司目前存在的另一个以散装文件的方式提供的安装后无法安装升级，最后在编译和下载内核的时候会出现问题。
安装过程中最好别用DEFAULT安装，把组件CUSTOM一下，不然会花很多冤枉的磁盘空间。
WINCE600的Platform Builder不像WINCE500是独立的，而是作为VS2005的插件，以后建立和定制OS、编译调试全部在VS2005里完成。
在此之前如果你已经安装了的话，建议你将它卸载干净，等第一步和第二步都顺利完成之后再重新安装。
因为的PB是作为VS 的一个插件存在的。
2、安装Visual Studio 2005 Service Pack 1, 这是必须的装的， Release Note 里面提到SP1提供了Windows Embedded platform and tools support。
不同的VS2005版本(Standard / Professional / Tem Edition) 会对应到不同的下载上，不过目前这个版本可以同吃以上多种版本，官方命名为：，如果你的操作系统是Vista版本的话，你需要去微软的官方网站重新下载，因为这个版本只是针对XP操作系统升级的包。
安装升级包的时间比较长，需要耐心等待！3、安装MSDN，从VS2005的安装页里选择。
新版的MSDN界面功能看起来比较酷，但CE6的Product Documentation写得实在潦草，不少细节貌似没写清楚，所以这里建议选上CE5的产品文档留着以后作参考。
4、安装Windows Embedded CE 。
应用程序开发人员可以不装，可以利用CE6生成的SDK来工作；但是不装的话，恐怕无法在本地MSDN得到CE6的产品文档，另外还有PUBLIC目录下丰富的application sample code了。
WinCE6.0 SDK的安装及配置
WinCE6.0 SDK的安装及配置目录安装 (2)开发环境的配置 (2)1．MS Visual Studio 2005/2008开发及环境配置 (2)2．如何添加现有工程对guc_ce6_sdk平台的支持 (4)安装过程及需要注意的步骤如下：1．双击‘guc_ce6_sdk.msi’,启动SDK的安装。
2．在‘Choose Setup Type’页面，选择‘Custom’，并在组件列表中去掉Documents选项，如下图所示。
3．然后下一步，直到安装完成。
开发环境的配置1．MS Visual Studio 2005/2008开发及环境配置步骤如下：1．启动Visual Studio，新建Smart Device类型的工程（MFC或者是托管），如下图所示。
2．对于MFC类型的工程，在新建工程的Wizard过程中，需要选择开发平台，请添加guc_ce6_sdk平台，如下图所示：3．工程新建完成后，点击菜单‘Tools’–‘Options’，启动Visual Studio环境配置对话框。
切换到‘Projects and Solutions’—‘VC++ Directories’。
然后将guc_ce6_sdk平台的include和lib路径修改，如下图所示（红色部分是必选路径，具体路径跟您的安装路径相关）。
需要说明的是：1、这里的设置仅限于C++工程，其他工程不牵涉到这些配置。
2、这里的设置只需要配置一次，无须每个工程都重新配置。
3、如果按照上图的配置，编译时提示某些头文件错误或者系统函数找不到，请尝试在include files的选项中只保留红色标注的两个选项。
4．编译工程，成功生成。
2．如何添加现有工程对guc_ce6_sdk平台的支持在用Visual Studio 2005/2008开发MFC等应用时，如何添加现有工程对guc_ce6_sdk的支持呢？步骤如下：1．点击VisualStudio 的菜单‘Build’—‘Configuration Manager’启动配置管理器。
Wince6.0应用开发：一、平台搭建
Wince6.0应用开发：一、平台搭建由于需要参加一个比赛，于是就接触了WinCE6.0的应用开发，可是所看到的资料大部分都是关于WinCE6.0系统的开发，或者在系统之上的驱动开发。
像我这种只在WinCE6.0上利用厂商提供的类库进行应用开发的真实伤不起。
下面介绍开发环境：我的自己的系统是WIN7的系统其实假如你和我一样的话只开发应用的话，其实根本不需要按照网上那样下差不多4G的东西。
需要做的是，一、装个vs2008（记得包含智能设备开发这一项，vs2010是不支持智能设备开发的。
当然你也可以选择vs2005，这随便你。
vs2008对应的Wince上的.net compact framework3.5,而vs2005对应的是2.0），二、再装个WINCE6.0_CHS_SDK（这是个wince6.0的SDK软件开发包）三、安装一个Wince设备的同步软件。
四、（可选择）假如你想要让你的模拟器上网的话，你就吧Virtual Pc 2007安装上吧！详细的步骤：一、装个vs2008开发应用的话，比较快捷的无疑有c++以及c#，所以这就看你自己的需要的了，不过在安装的时候，记得选择上智能设备课编程技术这一项。
如下图这样第一步就完成了。
二、安装这个的目的是因为其提供了一个Win ce6.0的模拟器，之后只需要将写好的程序点击（开始执行不调试）或者（启动调试）都行，vs2008便会在模拟器上部署应用程序。
之后便可以执行了。
下载地址：《传送门》安装时的注意事项：1、安装的时候记得选择自定义2、然后如下图记得取消文档这一项，否则会出现安装失败的提醒。
三、同步软件的安装：Winxp:装的是Activesync 4.5 《传送门》Win7:装的是Windows mobile center 《传送门》补充：假如百度网盘的内容被取消了，给我留言，我会马上补充回来的四、Virtual Pc 2007安装后便能在wince模拟器中，做些设置便能上网了。
Wince6.0模拟器使用说明
Wince6.0模拟器【运行环境】:适用于Windows平台PC
【☆分辨率】:详见使用教程
【版本信息】:Wince6.0模拟器
【是否测试】:已测试
第一步：把软件下载解压后看到以下目录.
第二步：双击运行上图中的Skin_800X480.BAT，运行后得到下图.
第三步：点击上图中的文件－配置得到下图.
定．
第五步：运行上图中的我的设备，得到下图．
第六步：因为第二步和第三步的配置我的设置里面就会有个SDMMC盘．SDMMC就相当于你导航里面的一个SD卡或者说是导航仪的内置卡．双击打开SDMMCC．得到如下图
第七步：第二步和第三步设置的目录里面的要模拟的地图和程序了．再后面就不用说了吧，和导航仪一样的．．．
此软件优点运行速度比Wince模拟器5.0快，缺点就是每次模拟地图都要配置第二和第三步．
此教程为菜鸟级别学习，老鸟请漂过～～～。
Wince6开发环境搭建-yuge
Author：yuge Mail:nimengyu2@Wince6开发环境搭建-V1.0注意：以下软件和步骤均基于Microsoft Windows 7系统（旗舰版），如果在WindowsXP 系统上区别仅仅是不需要获取超级用户权限。
建议把安装软件复制到硬盘安装(ISO 光盘映象文件可借助虚拟光驱)，因为这样安装速度比较快。
整体的安装过程时间很长，需要做好心理准备。
Windows CE 6.0 的安装过程十分繁琐，并且对开发主机的要求比较高(否则会很慢)，我们建议用户特别是初学者务必按照我们介绍的步骤安装开发环境。
主机配置要求：CPU：双核，最好四核内存：DDR2 4GB或者DDR3硬盘空间：500GB安装所需的软件列表如下：Visual Studio 2005Visual Studio 2005 Service Pack 1(文件名：VS80sp1-KB926601-X86-ENU.exe或者VS80sp1-KB926601-X86-CHS.exe)Windows Embedded CE 6.0Windows Embedded CE 6.0 Platform Builder Service Pack 1Windows Embedded CE 6.0 R2Windows Embedded CE 6.0 R3注意如果安装的VS2005是中文版的，需要安装的pack也应该是中文版本的。
根据我这边实际的安装方法，我是按照中文版安装的，推荐安装中文版本。
以上列表顺序基本也说明了这些软件的安装顺序：先安装 Visual Studio 2005 及补丁，再安装 Windows CE 6.0及补丁，最后安装第三方软件。
说明：Windows CE 6.0所使用的 Platform Builder 和以往的 Windows CE 5.0/4.2 等均不同，它并不是独立的开发平台软件，而是作为 VS2005的一个插件来安装使用的，因此必须先安装 VS2005，以后所有的内核配置编译等开发都基于 VS2005 进行。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
QT210 WinCE6.0使用手册V1.0wjr@2012-09-21目录QT210 WinCE6.0使用手册V1.0 (1)wjr@ (1)2012-09-21 (1)目录 (2)1.QT210硬件/软件资源 (3)1.1 QT210 硬件资源介绍 (3)1.1.1 S5PV210处理器介绍 (3)1.1.2 QT210 硬件主要参数 (2)2. 安装开发环境 (4)2.1 安装VS2005开发环境 (6)2.2 安装VS2005 SP1升级包 (8)2.3 安装Platformbilud插件到VS2005 (9)2.4 安装PlatformBuild 6.0 SP1 (13)2.5 安装PlatformBuild6.0 R2升级包 (15)2.6 安装06/07/08年年补丁 (18)2.7 安装2009年补丁 (21)2.8 安装PlatformBiuld 6.0 R3升级包 (21)2.9 安装其它补丁 (24)2.10 Blend组件安装 (24)2.11 Word PDF View组件安装 (27)3.建立工程 (30)3.1 安装QT210 BSP (30)3.2 工程建立向导 (30)3.2.1 创建新工程 (31)3.2.2 设置工程名称及路径 (31)3.2.3 选择工程BSP (32)3.2.4 选择工程模板 (33)3.2.5 选择模板类型 (34)3.2.6 添加平台需要的应用 (34)3.2.7 添加网络应用 (35)3.3 快速建立工程方法 (38)4. 定制QT210 wince系统 (39)4.1 设置目标内核类型 (39)4.2 设置工程属性 (40)4.3.1 添加同步软件组件 (42)4.3.2 添加USB Host组件 (44)4.3.3 添加文件系统组件 (45)4.3.4 添加多媒体相关组件 (46)4.3.5 添加中文字库 (49)4.3.6 添加等Shell and User Interface组件 (50)4.3.7 选择设备驱动（Device Drivers） (51)5. 编译QT210 wince系统 (52)6. 烧写QT210 wince系统镜像 (54)6.1 配置QT210的启动模式 (54)6.2 QT210烧写使用说明 (55)6.2.1 QT210 烧写软件介绍 (55)6.2.2 QT210 烧写软件驱动安装 (55)6.2.3 QT210 烧写bootloader和NK详细过程 (61)1.QT210硬件/软件资源1.1 QT210 硬件资源介绍1.1.1 S5PV210处理器介绍●内核：ARM Cortex-A8 ARM V7指令集●主频：最大1GHZ●MIPI●两路SPI●一路AC97/IIS 接口，3 路PCM 接口●两路TOUCH接口，一般我们只用一路，其余可以做普通ADC ●12 路ADC 转换接口（其中包含八路用做触摸屏）●四路SDIO 接口，可以接SD卡，wifi等●最大支持1024*768 的TFT RGB 显示接口●一路OTG USB2.0 接口●一路USB HOST2.0 接口●双路CAMERA接口●支持NEON指令●支持MPEG-4/MPEG2、H.264/H263、VC-1、DivX●支持2D图形加速，最大支持8000×8000分辨率●支持3D图形加速（Power VR SGX540），支持OpenGl●支持SD/MMC/SDIO接口存储卡，最高支持32GB●支持JPEG硬件编解码，最大支持8192×8192分辨率●支持硬件加速（MFC）●四路UART，Uart2固定用作Uart Irom启动串口●支持HDMI，DVI ，支持SPDIF●支持LPDDR1/LPDDR2/DDR2，最大支持DDR2 1.5GB●支持MLC/SLC NAND FLASH●支持NOR FLASH●支持TV OUT 实时输出接口●支持ONENAND●支持ATA/CF●支持14*8 矩阵KEYPAD 接口S5PV210 更加详细的功能，请看下图：1.1.2 QT210 硬件主要参数●三星Cortex A8 处理器S5PV210（1GHz）●512M Bytes DDR2 内存（四片128M Bytes DDR2组成）●1G Bytes SLC nandflash（256M/512M bytes SLC nandflash 经过测试都已经支持，客户可以根据自己的需求定制）●集成声卡WM9713（兼容WM9714）●集成100M LAN9220 网卡●可以嵌入大部分对体积要求高的嵌入式设备●采用可以独立控制的DC/DC+LDO电源芯片，比BGA 为0.5mm 的PMIC有较大的贴片工艺可靠性以及成本优势●核心板总引脚数为240个，可以满足绝大部分客户需求●核心板可以工作在800M/1G HZ，功耗为2W1.2 QT210 软件资源说明2. 安装开发环境开发环境获取：1、按照本章介绍安装所需要的软件；2、直接下载已经安装好的虚拟机。
虚拟机下载地址：QT210CE6.part1.rar：/d/IEYJJWDXUVTDQT210CE6.part2.rar：/d/IHHPZKAEAUVCBSP源码包和工具：/d/IHRZOVHWJCYX虚拟机使用步骤，下载QT210CE6.part1.rar和QT210CE6.part2.rar这2个文件，放到至少有30G剩余空间的硬盘上，解压后得到一个QT210CE6的文件夹。
用Vmware打开虚拟机QT210CE6目录下的“Windows XP Professional.vmx”启动虚拟机电源虚拟机用的是6.5.3版本，下载地址：/d/IPPREKXOQOMY其他版本的虚拟机未测试，更高版本应该也能使用。
（下载了QT210CE6的虚拟机用户，请直接用Vmware打开虚拟机，所有软件已经安装完成,所有安装步骤可以省略，直接跳到第五章开始）如果是用户自行安装整个开发环境，请继续按照以下步骤进行。
Windows CE 6.0的编译环境都采用VS2005，因此如果要进行Windows CE的驱动程序开发，首先要安装VS2005 开发环境，开发环境安装时间较长，需要耐心按照步骤一步一步进行，不然开发环境没安装正确会引起编译出错，请耐心细心安装，无特别说明点击下一步即可。
Wince６.０开发安装环境微软提供的安装参考顺序如下：●Visual Studio 2005●Visual Studio 2005 Service Pack 1●Visual Studio 2005 Service Pack 1 Update for Windows Vista (if applicable)，XP不用安装，XP是最经典的的开发系统，强烈建议采用XP SP3系统环境。
●Windows Embedded CE 6.0 Platform Builder●Windows Embedded CE 6.0 SP1 (required if PB 6.0 Tools have been installed)●Windows Embedded CE 6.0 R2●WinCEPB60-061231-Product-Update-Rollup-Armv4I.msi●WinCEPB60-071231-Product-Update-Rollup-Armv4I.msi●WinCEPB60-081231-Product-Update-Rollup-Armv4I.msi●Windows Embedded CE 6.0 Monthly Update 2009 M1-M9●Windows Embedded CE 6.0 R3●WinCEPB60-R3-2009-Update-Rollup-Armv4I●Windows Embedded CE 6.0 Monthly Update 2009 M10-M12●Windows Embedded CE 6.0 Cumulative Product Update Rollup Package(through 12/31/2010)——这个不建议安装，因为2010年全年包打了之后会导致视频播放花屏●Windows Embedded CE 6.0 Monthly Update 2011●Other2.1 安装VS2005开发环境双击VS2005\VS2005TEAMSUITE\vs下的setup.exe点击下一步，建议新手默认安装路径，请确认默认安装路径（通常是C盘）拥有足够大的空间，VS2005和PB6.0 安装后的占据的空间大概是15G 左右，所以我们安装盘空间至少是30G 空间，为了方便保存数据，建议熟悉wince 开发环境以后，把VS2005 软件和VS2005 软件都安装到非系统盘里面去，即使电脑系统损坏，我们的BSP，我们的所有资料都还存在。
这里我选择D盘，保证我项目资料的数据安全。
选择好安装路径后，继续点击下一步，然后耐心等待，根据电脑的性能要15分钟到一个小时不等。
完成安装会有如下图出现，我们点击“完成”就可以结束VS2005安装。
2.2 安装VS2005 SP1升级包双击 VS80sp1-KB926604-X86-CHS.exe注意事项：●这里安装的VS2005是中文版，所以SP1也要对应中文版，如果VS2005是英文版，那么SP1也要去微软的网站下载英文版语言的，否则SP1无法安装成功。
●Wince的所有开发软件的补丁升级包都可以在网络上找到，请用户自行下载安装，如有困难，请联系我们。
确认安装安装时间较长，耐心等待,完成安装2.3 安装Platformbilud插件到VS2005双击 Windows Embedded CE 6.0.msi输入SN号接受许可协议S5pv210是ARM，这里选择ARMVI就可以了，其他不用选可以节省空间，如果喜欢看微软的源代码的，请把“Shared Source”也选上，我这里没选上，但是我建议大家选上。
点击 NEXT , Install。
正在安装过程，具体请看进度条提示。
完成安装2.4 安装PlatformBuild 6.0 SP1SP1安装，双击Windows Embedded CE 6.0 Platform Builder Service Pack 1.msi点击NEXT点击NEXT点击Install点击Fnish完成该部分安装2.5 安装PlatformBuild6.0 R2升级包双击Windows Embedded CE 6.0 R2.msi点击“NEXT”并接受“License Agreement”，并继续点击“NEXT”。