WinCE6.0R3安装顺序说明
wince6.0_开发环境搭建
Window CE6.0开发平台搭建详解2011年08月29日Windows CE6.0的开发无非两大方面：操作系统开发和应用程序开发，操作系统开发包括系统的定制，驱动开发和其他需要完成的底层工作。
应用程序开发主要是与实际应用结合紧密的程序开发。
要搭建这样的开发环境，至少要包括两部分，一个是硬件平台，一个是软件平台，在Windows CE6.0的开发中，微软公司把这些开发软件集成到了vs2005中。
Windows CE6.0开发环境需要安装的软件比较多、比较大，至少要10GB的空间，而且有着严格的安装顺序要求，一旦其中某一个环节出错，都会导致软件运行出现故障，为确保安装顺利，请仔细阅读本文，按照步骤一步一步进行安装。
一、所需安装软件1、Visual Studio 20052、Visual Studio 2005 Service Pack 13、MSDN4、platform builder for Windows Embedded CE6.05、Windows Embedded CE 6.0 Platform Builder Service Pack 16、Windows mobile 6的sdk二、所用磁盘空间在安装之前，请检查电脑的磁盘空间，VS2005和Windows Embedded CE6.0均是比较大的软件，要占硬盘好10G多的空间，建议不要装在C盘，但是我装Windows Embedded CE6.0的时候，发现不能更改安装路径，没办法，只能把Windows Embedded CE6.0装在C盘。
三、安装顺序1.安装Visual Studio 2005最好选择自定义安装方式，把不用的一些组件都删掉，这样会节省不少的磁盘空间。
WINCE6.0的Platform Builder不像WINCE5.0是独立的，而是作为VS2005的插件，以后建立和定制OS、编译调试全部在VS2005里完成。
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。
wince软件安装介绍
• 下载官网地址： /enus/download/details.aspx?id=5553
• 3、MSDN • 本部分可以不装，步骤省略。
• 4、WINCE6.0 • 即Windows Embedded CE 6.0 Platform Builder • 序列号： Your product key(s) for installation are: * Windows Embedded CE 6.0 (plugin for Visual Studio 2005): H8RQR-MMKRP-XFRFC-9HKGJ-82R6J * If you are also evaluating Visual Studio 2005, Visual Studio 2005 Professional Edition Trial: M3C9X-9K3Q9-DC8PX-B3YR3-BKQR8 如果上面的序列号不可用，请自己去申请 /windows/embedded/eval/trial. mspx
• 用以解决，没有选中ATL时，下一 步生成osdesign1时的错误：fatal error U1073: don‘t know how to make （定制wince操作系统并模 拟运行）
• 该错误需要在 \WINCE600\build.log中查看到。 (学会查看日志，跟踪错误的方法)
• 取消enable kitl(no imgnokil=1),否则可能造 成黑屏。
• • • •
10、WINCE6.0 Updates Packages 本部分必须要安装（我暂且没有安装）。 本部分的所有更新补丁可在微软官网的下载中心进行下载， 必须先安装Windows Embedded CE 6.0 Cumulative Product Update Rollup Package (through 12/31/2010) • 然后安装Windows Embedded CE 6.0 Monthly Update 每个月份更新补丁，每个月份补丁安装要按照顺序 • /enus/embedded/aa731256.aspx • /downloads/en/NoResults.aspx ?displaylang=enUS&freetext=Windows+Embedded+CE+6.0+Monthly+U pdate
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
如何安装WinCE6.0 [转]嵌入式Wince 2010-02-27 13:46:56 阅读654 评论0 字号：大中小订阅最近要做一个Windows CE系统上的串行通讯程序，因为在此之前并没有接触过有关Windows嵌入式方面的应用开发，所以搭建开发环境成了摆在面前的第一道难题。
本文将记录并总结我搭建Windows Embedded CE 6.0开发环境的步骤和过程中碰到的问题，希望给同为Windows嵌入式开发初学者的朋友们提供一个参考。
我最终确定的开发环境方案为：Windows XP SP3 + Visual Studio 2005 SP1 + Windows Embedded CE 6.0. 我目前的操作系统是Windows Server 2003, Visual Studio 2005 （以下简称VS2k5）和Windows Embedded CE 6.0（以下简称CE6）都可以直接在server系统上安装，但是考虑到后期要用模拟器(Device emulator)进行调试，而使用模拟器有一个必要的组件Virtual Machine Network Driver for Microsoft Device Emulator是存在于Virual PC 2007中（不安装的话模拟器启动黑屏），但是Virtual PC 2007不能安装在Server操作系统中，其替代版本为Virtual Server 2005 R2 SP1。
因此我在Server操作系统中用虚拟机（虚拟机采用了Sun的VirtualBox）创建了一个Windows XP SP3的虚拟机，在该虚拟机上搭建CE6开发环境。
第一步，安装VS2k5，安装完成后要安装VS2k5 SP1补丁（KB926601），否则后面的PlatformBuilder SP1无法安装。
第二步，安装Windows Embedded CE 6.0，官方下载地址为：/downloads/details.aspx?familyid=7E286847-6E06-4A0C-8CAC-CA7D4C09CB56&displaylang=enYour product key(s) for installation are:* Windows Embedded CE 6.0 (plug-in for Visual Studio 2005):H8RQR-MMKRP-XFRFC-9HKGJ-82R6J* If you are also evaluating Visual Studio 2005, Visual Studio 2005 Professional Edition Trial:M3C9X-9K3Q9-DC8PX-B3YR3-BKQR8* Other recommended downloads:Visual Studio 2005 Service Pack 1 Beta本文附件中提供一个离线安装的文件表（点击下载），把该文件表导入迅雷可以下载完整的离线安装包，大概有3.7G大小。
旗舰版Win7搭建WinCE6.0环境以及第一个Hello Windows CE程序
旗舰版Win7建立WinCE6.0环境Windows CE 6.0所使用的Platform Builder 和以往的Windows CE 5.0/4.2等均不同，它并不是独立的开发平台软件，而是作为VS2005的一个插件来安装使用的，因此必须先安装VS2005，以后所有的内核配置编译等开发都基于VS2005进行。
在安装WinCE6.0之前要先安装VS2005以及Vs2005的相关补丁，而所装操作系统（XP、Win7）和VS2005版本不同（中文版、英文版），所需的补丁也有所不同。
下面就罗列出不同操作系统和不同版本VS2005所需的补丁。
安装软件列表如下，以下排列顺序也是安装顺序。
安装这些软件大概占用14G硬盘空间，以下软件皆可在网上下载到。
软件列表1.Visual Studio 20052.Visual Studio 2005 Service Pack 1若安装的是英文版VS2005，则需要安装的补丁的文件名为：VS80sp1-KB926601-X86-ENU.exe；若安装的是中文版VS2005，则需要安装的补丁的文件名为：VS80sp1-KB926604-X86-CHS.exe3.Visual Studio 2005 Service Pack 1 Update for Windows Vista若使用的是WindowsXP，则不用安装此项。
若使用的是Windows7，则需要安装此补丁。
若安装的是英文版VS2005，则需要安装的补丁的文件名为：VS80sp1-KB932232-X86-ENU.exe；若安装的是中文版VS2005，则需要安装的补丁的文件名为：VS80sp1-KB932230-X86-CHS.exe4.Visual Studio 2005 Service Pack 1 ATL Security Update若使用的是XP系统，则不必安装该补丁。
文件名：VS80sp1-KB971090-X86-INTL.exe ATL是ActiveX Template Library 的缩写，它是一套C++模板库5.Windows Embedded CE6.06.Windows Embedded CE 6.0 Platform Builder Service Pack 17.Windows Embedded CE 6.0 R28.Windows Embedded CE 6.0 R39.安装模拟器Microsoft Device Emulator 2.0 -- Standalone Release10.CHSEmu.msi这个文件是我从网上下载到的别人创建的SDK，如果你自己创建自定义SDK不成功，或者不想自己创建一个SDK的话，直接安装这个SDK就可以了。
凯立德WINCE6.0导航安装说明
车载及PD机导航安装步骤（CE版）普清机首先把卡里的资料备份进电脑保存好，以防升级不成功时恢复原样。
然后删除旧卡的上资料。
2、不要改动卡名，每种导航仪都有自己命名卡名的方法，以防找不到卡的现象，如果是新卡请改成和旧卡一样的卡名。
3、下载好后右击压缩包解压至当前文件夹得到一个NaviOne文件夹。
4、把NaviOne文件夹拷到卡里，把卡插回导航仪。
5、打开导航仪进入设置查看GPS路径是不是：卡名\Navione\NaviOne.exe,不是请修改。
有的机器路径可能在文件管理的里面修改，也有的在导航路径修改，掌柜不可能知道所有机器路径设置，请自行找。
6、进入导航点功能—系统—往下翻找到GPS卫星天线点击——点搜索——稍等点确定，这里主要是让导航仪自己找到端口和波特率。
这一步一定要做，不做可能找不到卫星。
800*480的机器可能要修改一个文件才行。
7、把导航仪拿空旷的地方进行首次定位。
看到卫星信号指示条下面有数字说明已找到卫星，稍等即可定位。
注意：没办法知道自己屏幕分辨率、端口、波特率的，请向掌柜要一个名为GPS.EXE的文件，把GPS.EXE放卡里，把卡插回PD或车载机里，然后从机里点系统设置—找程序路径点击—找到GPS.EXE，再回机里的点应用程序—GPS.EXE就会检测到自己屏幕分辨率、端口、波特率（报错不用管它），请记下来哦，这此是修改导航的设置要用的。
有的朋友反映我的导航安装后出现了很多喜字，恭喜您中头奖了，这是一些品牌机为了不让客户在外面安装导航软件而设的一个小把戏。
您只要告诉掌柜您的分辨率，就会给您发回一个小文件替换上即可解决。
高清机下载后解压，把解压后的文件夹NaviOne拷入卡里，再在导航仪上设置导航路便可，如果遇到有端口和波特率和新导航的默认不一样，一般掌柜会在您拍下不久都会帮您设置好并发送给您的，您只要按说明放入相应的文件夹替换便可。
Wince6.0模拟器使用说明
Wince6.0模拟器【运行环境】:适用于Windows平台PC
【☆分辨率】:详见使用教程
【版本信息】:Wince6.0模拟器
【是否测试】:已测试
第一步：把软件下载解压后看到以下目录.
第二步：双击运行上图中的Skin_800X480.BAT，运行后得到下图.
第三步：点击上图中的文件－配置得到下图.
定．
第五步：运行上图中的我的设备，得到下图．
第六步：因为第二步和第三步的配置我的设置里面就会有个SDMMC盘．SDMMC就相当于你导航里面的一个SD卡或者说是导航仪的内置卡．双击打开SDMMCC．得到如下图
第七步：第二步和第三步设置的目录里面的要模拟的地图和程序了．再后面就不用说了吧，和导航仪一样的．．．
此软件优点运行速度比Wince模拟器5.0快，缺点就是每次模拟地图都要配置第二和第三步．
此教程为菜鸟级别学习，老鸟请漂过～～～。
wince6.0安装说明和对此过程出现的BUG的解决办法
本文说明：从WINCE6.0的安装到使用，花费时间最大的是在下载需要安装的软件和修复各种运行时的BUG错误一.WINCE6.0开发环境建立：主要对WINCE6.0的开发环境需要的软件，硬盘空间，安装步骤等进行了说明二.安装WINCE6.0过程和使用WINCE6.0时遇到的问题及解决办法一.WinCE6.0开发环境建立（1）需要安装的软件及安装包大小（下面提到的软件安装包都已在公司文件服务器平台组public目录下的win CE6.0文件夹中进行备份）1、Visual Studio 2005 2.6G2、Visual Studio 2005 Service Pack 1 430M3、MSDN（可选）4、Windows Embedded CE6.0 3.67G5、Windows Embedded CE 6.0 Platform Builder Service Pack 1 56.3M6、WINCE6.0R2 1.9G7、WINCE6.0R3 1.14G8、Microsoft Device Emulator 2.09、Virtual Machine Network Driver for Microsoft Device Emulator10、WINCE6.0 Updates Packages（2011）大于1.4G本文基于Windows XP SP3操作系统环境，以上10项除第3项外，其他的都必须安装，并且必须安装顺序安装。
软件下载及遇到问题：a.VS2005客户端需要在第三方网站下载，目前微软官方网站上提供的安装包的安装程序是不能启动的，通过微软官网下载只会浪费时间。
b.VS2005 SP1补丁包也可通过第三方网站下载。
c.WINCE6.0客户端+SP1+R2+R3安装包，微软提供了相应的下载器下载这几个部分的安装包，但使用这些下载器的下载速度可能会让你不耐烦，建议找一个第三方网站直接下载这些客户端的离线安装包，我找到的唯一一个地址为：/id/2793687d.用于运行WINCE6.0的OS镜像的模拟器Emulator2.0可以在微软官网下载，但其VirtualMachine Network Driver for Microsoft Device Emulator微软官网已经关闭此安装程序的下载，需要寻找第三方网站进行下载。
Windows CE 6.0 安装顺序 - 操作系统
Windows CE 6.0 安装顺序- 操作系统1、先装Visual Studio 2005, 我拿到的是Professional Edition。
最好别用DEFAULT安装，把组件CUSTOM一下，不然会花很多冤枉的磁盘空间。
WINCE600的Platform Builder不像WINCE500是独立的，而是作为VS2005的插件，以后建立和定制OS、编译调试全部在VS2005里完成2、安装Visual Studio 2005 Service Pack 1, 发布的地址/zh-cn/vstudio/bb265237.aspx 这是必须的装的，Release Note里面提到SP1提供了Windows Embedded 6.0 platform and tools support。
不同的VS2005版本(Standard / Professional / Tem Edition) 会对应到不同的下载上，不过简单点就用这个下载/downloads/details.aspx?familyid =BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displayl ang=en 430多兆，通吃所有版本。
3、可选，安装Visual Studio 2005 Service Pack 1 Update for Windows Vista。
发布和下载网址/downloads/details.aspx?FamilyI D=90e2942d-3ad1-4873-a2ee-4acc0aace5b6&displaylang =en在SP1的基础上增加对VISTA的支持。
注意一定要先装SP1，再装这个，在System Requirements里强调了Required Software: licensed copy of a Visual Studio 2005 and Visual Studio 2005 Service Pack 1. 我当时以为这个包含了上面SP1，浪费了不少时间4、安装MSDN，从VS2005的安装页里选择。
WindowsCE6.0安装顺序-操作系统
WindowsCE6.0安装顺序-操作系统1、先装Visual Studio 2005, 我拿到的是Professional Edition。
最好别⽤DEFAULT安装，把组件CUSTOM⼀下，不然会花很多冤枉的磁盘空间。
WINCE600的Platform Builder不像WINCE500是独⽴的，⽽是作为VS2005的插件，以后建⽴和定制OS、编译调试全部在VS2005⾥完成4、安装MSDN，从VS2005的安装页⾥选择。
新版的MSDN界⾯功能看起来⽐较酷，但CE6的Product Documentation写得实在潦草，不少细节貌似没写清楚，所以这⾥建议选上CE5的产品⽂档留着以后作参考。
5、安装Windows Embedded CE 6.0。
应⽤开发⼈员可以不装，在后⽂会提到可以利⽤CE6⽣成的SDK来⼯作；但是不装的话，恐怕⽆法在本地MSDN得到CE6的产品⽂档，另外还有PUBLIC ⽬录下丰富的application sample code了。
⼏个注意点：(1) 在下图这步才可以改路径。
点选组件后，然后点下⾯的Browse。
这⾥不像WINCE500安装时有专门的⼀步来改路径。
害我狂点next/back⼏圈才找到。
(2) CE6没有专门的⼀个Emualtor(x86)选项了, 我以为是包含在x86⾥⾯, 后来发现x86部分我⽩装了。
WINCE600和VS2005的模拟器可以直接跑ARM指令，他们管这个叫ARMulator ( 貌似LINUX 上先有这个东西, MS抄⼈家的? )。
这导致了CE5 的基于x86的Emulator⽆法在VS2005上跑起来，得⽤个很绕路并且不太好⽤的⽅法，等我⽤顺了再写⽂章出来。
(2) 注意磁盘空间，我选装了ARMV4I和X86两个，⽤掉6.5G，⽐WINCE500还要⼤些。
--------------------------------如果BSP开发⼈员不打算⽤模拟器的话，装到这步就⾏了。
ARM9 WinCE6.0 mifare读卡器 技术说明
建立开发环境1，安装ADS1.2（可以不安装，直接使用编译好的文件）2，安装HJTAG1.0（必须安装）3，安装VS2005及WINCE6.0 R3（定制系统及应用软件开发必须安装）3.1，安装顺序：VS20053.2，VS80sp1-KB926601-X86-ENU.msp3.3，CE6(必须安装在分区的根目录)3.4，Windows Embedded CE 6.0 Platform Builder Service Pack 1.msi3.5，CE6 R23.6，CE6 R34，安装EVC4及EVC SP4（可以不安装，提供的EVC4代码可以转到VS2005下）4，PROTEL 99SE（原理图及PCB查看）5，其他工具及软件：JTAG烧写小板，DNW软件，JTAG并口驱动，USB下载驱动编译说明：1，ADS BIOS程序编译1.1，将程序拷贝到磁盘的根目录，并且路径不包含中文及空格1.2，进入工程目录，双击扩展名为MCP的ADS工程文件即可打开该工程1.3，使用键盘上的Ctrl+-组合键清除原来的编译信息1.4，编译（Make）2，WINCE6的编译2.1，复制BSP(MINI2440文件夹)到CE6安装目录下，路径：($):\WINCE600\PLATFORM\MINI24402.2，复制工程文件夹到（$）:\WINCE600\OSDesigns\Mini24402.3，打开（$）:\WINCE600\OSDesigns\Mini2440\Mini2440.sln2.4，如果需要定制特性，请打开Catalog Items View进行定制2.5，生成解决方案程序固化说明：1，连接计算机并口到JTAG烧写小板；连接JTAG烧写板与系统板的J7；连接串口及USB从口；打开电源2，打开HJTAG程序，并从Init->Init Script菜单载入配置文件：FriendlyARMM2440.his3，在Settings->USB/LPT Selection菜单下选择：LPT4，在Settings->LPT Jtag Setting下做如下设置：4.1，J tag Selection：User Defined4.2，T CK Control：MAX/14.3，U ser Defined Pin Assignment：TMS(PIN4),TCK(PIN2),TDI(PIN3),TDO(PIN11),nTRST(NOTAP RST),Nsrst(NO SYS RST)5，使用Control->Detect Target命令查看是否连接正常（正常需显示：ARM9,0x00324090D,这表明已经检测到CPU）6，使用菜单：Flasher->Start H-Flasher打开烧写程序H-Flasher7，在H-Flasher->Load选择S3C2440+K9F2G08.hfc配置文件8，在程序左边选择：4 Programming9，设置Type:Plain Binary Format10，Dst Addr:Block-0000 page-000011，Src File:（用右边的路径选择按钮浏览到：YLP2440_MON.BIN12，点击按钮：Program,将看到编程迅速完成13，打开DNW.exe，并选择Serial Port->Connect14，系统板上电，此时DNW窗口内有BIOS的启动信息15，键盘上按下任意键，将出现BIOS的菜单16，选择【0】Downoad & Run(在键盘上输入0)17，在第一次使用时PC将会提示找到新硬件，此时可直接运行：FriendlyARM USB Download Driver Setup_20090421.exe安装需要驱动；安装完成后DNW程序的右上角提示:USB:OK18，使用USB Port->Transmit菜单，选择编译好的NK.NB0文件并打开19，下载完成后系统将自动运行WINCE（此操作中没有将系统固化到FLASH，如果断电将丢失所有数据）20，测试系统各个接口及软件功能21，系统固化：使用H-FLASHER将STEPLDR.NB1烧写到NAND的：Block-0000 page-0000;Eboot.Nb0烧写到：Block-0004 page-000022，在DNW中将空格键按下，系统上电，将在DNW中显示EBOOT的菜单0-W23，选择B)Mark Bad Block at Reserved Block命令将系统STEPLDR.NB1和EBOOT的分区保护起来24，选择9)Format Boot Media for BinFS命令将NAND格式化为WINCE需要的格式25，选择U)Download image now(USE USB)26，选择DNW->USB Port->Transmit选择需要固化的WINCE系统文件NK.BIN并打开27，等待下载完成及烧写结束后系统自动启动到WINCE28，系统固化完成，断电后重启将自动启动WINCE系统系统及驱动介绍：1，WINCE6操作系统设置运行频率：400Mhz；总线频率：100Mhz；LCD:TS35ND5B（TFT-16BIT模式），分辨率320X240；刷新频率60HZ；串口：支持3个串口；无调试串口模式USB：USB主从驱动；以太网：CS8900 10M网卡驱动;SD卡：测试过8G卡键盘：键值分布图，其中上、下、左、右需要长按键GPIO驱动：设备名称GIO，请使用下面的DeviceIoControl来控制输出信号：ARM的串口3输出至连接器J5：#define UART_TO_CONNECT 1//VD16=0,LCDVF2=1,LCDVF0=1LCDVF2为0时，ARM的串口3输出至智能卡#define UART_TO_SAMCARD 2 //VD16=1,LCDVF2=0,LCDVF0=1LCDVF0为0时，ARM的串口3输出至键盘（读卡器）#define UART_TO_CARDREADER 3 //VD16=1,LCDVF2=1,LCDVF0=0LCDVF1为SAM卡的复位信号(#define SET_RESET_SAM_CARD 4 //SET RST #define CLR_RESET_SAM_CARD 5 //CLEAR RST)VD0=0,VD8=1时，SAM卡将可以向ARM发送数据#define SEND_TO_SAMCARD 6 //ARM SEND DATA TO SAMCARD,VD0=1,VD8=0VD0=1,VD8=0时，ARM将可以向SAM卡发送数据#define RECV_FROM_SAMCARD 7 //READ DATA FROM SAMCARD,VD0=0,VD8=1GPB1为0时，蜂鸣器不叫(该功能由于被三极管倒相，软件中的ON实为OFF)#define BEEPER_ON 8 //BEEPER ON #define BEEPER_OFF 9 //BEEPER OFFnRTS0,nCTS0连接至键盘板nRTS0用于控制键盘上LED灯的亮（1）灭（0）#define SET_KEYBOARD_LED 10 //nRTS0=1#define CLR_KEYBOARD_LED 11 //nRTS0=0#define SET_KEYBOARD_IO 12 //nCTS0=1#define CLR_KEYBOARD_IO 13 //nCTS0=0VD1,VD9,VD17,VD18分别对应：黄、蓝、红、绿四个LED的亮（0）灭（1）#define SET_YELLOW_LED 14 //VD1=0#define CLR_YELLOW_LED 15 //VD1=1#define SET_BLUE_LED 16 //VD9=0#define CLR_BLUE_LED 17 //VD9=1#define SET_RED_LED 18 //VD17=0#define CLR_RED_LED 19 //VD17=1#define SET_GREEN_LED 20 //VD18=0#define CLR_GREEN_LED 21 //VD18=1输入信号：返回值及该信号的高低，#define READ_INPUT_IO 22 //READ USB_EN已经编译WINCE软件特性：.NET Compact Framwork 3.5,CAB File Installer/Uninstaller,Activesync,Active Template Library(ATL),C Libraries and Runtimes,Compent Services(COM and DCOM),Message Queuing(MSMQ),Object Exchange Protocol(OBEX),SQL Compact,String Safe Utility Functions,XML Core Services and Document Object Model(DOM), NDIS User-mode I/O Protocol Driver,TCP/IP,WinSock Support,Dial Up Networking(RAS/PPP),Telephony API(TAPI 2.0),FTP Server,Telnet Server,Web Server(HTTPD),USB KEYBOARD/MOUSE/STORAGE support, Authentication Services(SSPI),Credential Mangager,Cryptography Services(Cortificates(CryptoAPI 2.0))上述特性请自行验证。
Windows CE 6.0入门详解(环境搭建系统开发起步)教学文稿
W i n d o w s C E 6.0入门详解(环境搭建系统开发起步)Windows CE 6.0入门详解（环境搭建内核配置和应用开发起步）武汉众嵌科技有限公司修订历史记录A - 增加M - 修订D - 删除一、安装开发环境 (5)A)按下列顺序安装所需软件 (5)B)安装说明 (5)C)装中可能出现的问题及解决方法 (6)二、WINDOWS CE 内核定制 (8)A)基W INDOWS CE产品开发流程大致分为以下几个阶段 (8)1. 硬件设计 (8)2. 选定BSP (8)3. 获得驱动程序 (8)4. 剪裁系统内核 (8)5. 导出SDK (9)B)详细制作流程 (9)1. 新建立一个OS Design工程 (9)2. 建立工程 (10)3. 配置工程 (11)C)配置内核 (13)1. 选择应用程序（Applications-End User） (13)2. Applications and Services Development (13)3. 选择系统核心服务（Core OS Services） (14)4. Communication Services and Networking (15)5. 设备管理（Device Management） (15)6. File System and Data Store (16)7. 选择字体（Fonts）： (16)8. 国际化支持（International） (16)9. Internet Client Services (17)10. Graphics and Multimedia Technologies (17)11. Shell and User Interface (17)D)生成系统镜像 (17)E)生成SDK (18)F)安装A CTIVE S YNC 并配置 (18)G)配置模拟器并生成程序 (18)H)配置模拟器 (19)I)应用开发 (21)一、安装开发环境a) 按下列顺序安装所需软件1.Visual studio 20052.Visual studio 2005 server pack 13.Visual studio 2005 service pack 1 update for Windows vista/74.Windows Embedded CE 6.0 (Windows Embedded CE 6.0.iso)5.Windows Embedded CE6.0 service pack 16.Windows Embedded CE 6.0 R27.Windows Embedded CE 6.0 R38.Windows Embedded CE cumulate product update rolluppackage through(12/31/2010)9.VS_emulator.exe(模拟器)b) 安装说明我的系统是Windows 7 旗舰版所以存在一个权限问题我以这样的方式安装所有的程序：c) 装中可能出现的问题及解决方法报错信息：1. ToolsMsmCA(Error): Setup package issue or CoreConDataStore corrupted: DeviceSDKInstComp Add/Remove failed.HR=0x8007005。
非常详细的WINCE6.0模拟器使用说明
第一种方法，下载安装中文wince6.0模拟器SDK，直接运行即可。
①/detail/sunrain_hjb/563215下载模拟器②下载安装ActiveSync。
连接后显示：与PC机连接：就在wince6里面“开始->设置->网络和拨号连接-》新建连接->我的连接,选项：直接连接->下一步：选择设备 Serial Over DMA-》点完成，回到控制面板-》pc连接-》更改连接-》我的连接，然后插入底座就可以正常连接了。
插入底座：如图，cradle插入设备，更改PC端ActiveSync设置，连接DMA选项。
打开移动设备，即可把文件放入模拟器wince的文件夹中进行测试。
或者打开编写的工程，F5启动调试，即可在模拟器的wince6.0中进行测试。
大功告成！第二种方法，自己创建模拟器文件。
网上下载安装Microsoft Device Emulator 2.0，Virtual Machine Network Driver for Microsoft Device Emulator。
两个文件都不大。
1.新建工程及配置属性1.1创建的工程是基于模拟器的工程，按照WinCE的工程向导，一步步走下去，需要注意的几个点是：1. Available BSPs选择Device Emulator:ARMV4I，2. Design Templates选择 PDA Device，3. Variants选择Mobile Handled；当然，组建的添加和删除也是根据功能需求来进行。
1.2.建立工程完成之后，选择工程类型为Release，1.3配置工程属性会弹出本工程相应的对话框，分别对Configuration Properties下的现象进行配置，对General的配置：（在编译的时候选择Release模式，这样编译的速度会快很多，，而且生成的NK.bin内核文件相对比较小，方便bootload）对Locale的配置如下：（首先进行Clear all，之后选择中文（中国）或英语（美国））对Build Uptions的配置如下：勾去Enable KITL(…)单击确定，完成工程属性配置。
Windows CE 6.0入门详解(环境搭建系统开发起步)
Windows CE 6.0入门详解（环境搭建内核配置和应用开发起步）武汉众嵌科技有限公司修订历史记录一、安装开发环境 (3)A)按下列顺序安装所需软件 (3)B)安装说明 (3)C)装中可能出现的问题及解决方法 (4)二、WINDOWS CE 内核定制 (5)A)基W INDOWS CE产品开发流程大致分为以下几个阶段 (5)1.硬件设计 (5)2.选定BSP (5)3.获得驱动程序 (5)4.剪裁系统内核 (5)5.导出SDK (6)B)详细制作流程 (6)1.新建立一个OS Design工程 (6)2.建立工程 (7)3.配置工程 (8)C)配置内核 (10)1.选择应用程序（Applications-End User） (10)2.Applications and Services Development (10)3.选择系统核心服务（Core OS Services） (11)munication Services and Networking (12)5.设备管理（Device Management） (12)6.and Data Store (13)7.选择字体（Fonts）： (13)8.国际化支持（International） (13)9.Internet Client Services (14)10.Graphics and Multimedia Technologies (14)11.Shell and User Interface (15)D)生成系统镜像 (15)E)生成SDK (16)F)安装A CTIVE S YNC 并配置 (16)G)配置模拟器并生成程序 (16)H)配置模拟器 (17)I)应用开发 (19)一、安装开发环境a) 按下列顺序安装所需软件1.Visual studio 20052.Visual studio 2005 server pack 13.Visual studio 2005 service pack 1 update for Windows vista/74.Windows Embedded CE 6.0 (Windows Embedded CE6.0.iso)5.Windows Embedded CE6.0 service pack 16.Windows Embedded CE 6.0 R27.Windows Embedded CE 6.0 R38.Windows Embedded CE cumulate product update rolluppackage through(12/31/2010)9.VS_emulator.exe(模拟器)b) 安装说明我的系统是Windows 7 旗舰版所以存在一个权限问题我以这样的方式安装所有的程序：c) 装中可能出现的问题及解决方法报错信息：1. ToolsMsmCA(Error): Setup package issue or CoreConDataStore corrupted: DeviceSDKInstComp Add/Remove failed.HR=0x8007005。
组态王在wince工业平板电脑的安装使用方法
WINCE工业控制计算机运行系统的软、硬件环境● 硬件■ Intel x86或x86兼容CPU以与ARM系列CPU，主频200MHz以上■ 64MB RAM■ 32MB 存储空间，支持Doc（Disk On Chip）、DOM（Disk On Module）或者CF卡（COMPACT FLASH）■ 10Mbps Base-T标准网卡■ 支持VGA的显示卡● 软件■ 中文版Windows （CE4.0）或更高■ 支持注册表信息永久保存功能安装运行系统安装组态王嵌入版运行系统：第一步：将安装有组态王嵌入版开发系统的PC机和嵌入式系统连接在同一个局域网的同一个网段中。
(如果采用网线直接将PC机和嵌入式系统设备连接的话，需要使用交叉网线)。
第二步：上电启动预先安装在系统上的WinCE系统，设置WinCE上的网络和拨号连接，给这个设备分配一个IP地址。
第三步：在PC机建立一个共享目录（名称最好用英文或者拼音，否则可能显示乱码）；将组态王嵌入版安装目录下的ARMV4文件夹或者CEX86文件夹(根据嵌入式机器的CPU类型来确定)下的KV_FTP_ERVER.EXE拷贝到您PC机的共享目录下。
第四步：在嵌入式机器的WinCE中，在资源浏览器的地址栏中输入PC机的UNC地址，如PC机机器名为aaa，则输入\\aaa。
找到KV_FTP_SERVER.EXE所在的共享目录。
注意：第三步和第四步也可以使用U盘将KV_FTP_SERVER.EXE程序拷贝到嵌入式设备的存储器上。
第五步：拷贝KV_FTP_SERVER.EXE到嵌入式系统的存储器上，比如DiskOnChip，Flash 等，然后启动KV_FTP_SERVER.EXE第六步：点击主菜单中“工具\远程部署操作”，弹出远程部署操作对话框如图1.15所示：在远程站点处输入嵌入式设备的IP地址，点击“连接”，连接成功后状态提示为：“连接服务器：操作成功”；如果提示：“连接服务器：连接主机失败”，请检查嵌入式设备和PC机网络连接是否正确或IP地址设置是否正确。
实验一 WinCE开发环境安装及使用
实验一WinCE6.0的开发环境安装及使用
一、实验目的
1、学会使用WinCE操作系统的最基本开发工具和开发方法
2、认识和熟悉定制WinCE6.0内核的工具PlatformBuilder
3、了解嵌入式开发的基本思想和开发过程
二、实验内容
学习安装并使用WinCE的开发工具，并通过PlatformBuilder进行WinCE 6.0内核的定制vs2005。
三、预备知识
WinCE 6.0的基本知识，WinCE6.0的内核的特点及定制过程。
四、实验设备及工具
硬件：PC一台P3以上。
软件：PC操作系统Windows XP, WinCE6.0安装程序，VS2005或VS2008.
五、实验步骤
1、Visual Studio 2008的安装
第一步：打开vs2008文件，安装之前如图1所示。
图1 打开vs2008安装之前的界面
第二步：打开setup.exe安装的应用程序，弹出的安装对话框，选择第一项，如图2所示。
图2 安装对话框的效果图
第三步：加载vs2008程序所需组件的效果图，如图3、4、5所示。
图3、4、5 加载程序所需的全部组件
2、Windows CE 6.0内核的定制
（1）
（2）
（3）
（4）。
六、实验总结
Vs2005和vs2008 的安装基本上是大同小异，个人感觉没有什么太大变化，都应该一次能安装成功的，这个过程让我熟悉了安装的过程。
粤嵌嵌入式实验室-WinCE6.0升级指导
W i nd ndoo ws Embedded CE 6.0R3升级指导广州粤嵌通信科技股份有限公司目录第一章、WinCE6.0R3新增特性介绍 (3)第二章、必须软件 (3)第三章、安装R3及选项软件 (3)3.1升级WinCE6.0R3前，请仔细阅读当前目录下的 (3)3.2安装WinCE6.02009Monthly Updates (3)3.3安装WinCE6.0R3 (4)3.4安装Expression Blend2Trial (8)3.5安装Office and PDF Viewers (13)3.6安装QQ Messenger Client (17)3.7下载地址 (21)第四章、R3特性选项 (22)4.1Silverlight for Windows Embedded (22)4.2Internet Explorer Embedded (23)4.3Adobe Flash Lite (24)4.4Touch and Gesture (25)4.5Connection Manager (26)4.6Microsoft Office and PDF Viewers (27)4.7Tencent Mobile QQ (28)第五章、WinCE R3功能使用 (29)5.1Tencent QQ (29)5.2PowerPoint Viewer (30)5.3Word Viewer (30)5.4Excel Viewer (31)5.5JETCET PDF (31)5.6Adobe Flash Lite (32)第六章、WinCE6.0R3OS完整定制过程 (33)6.1新建WinCE6.0工程 (33)6.2设置工程属性 (43)6.3添加组件 (47)6.4编译工程 (60)1Microsoft Visual Studio 20052Visual Studio 2005Service Pack 13Windows Embedded CE 6.04Windows Embedded CE 6.0Platform Builder Service Pack 15Windows Embedded CE 6.0R26WinCE 6.0Updates ：WinCEPB60-081231-Product-Update-Rollup-Armv4I.msi第一章、WinCE6.0R3新增特性介绍Silverlight for Windows Embedded在Windows Embedded CE 中引入了Silerlight的强大功能，从而能够建立丰富多彩的应用程序和程序界面Internet Explorer EmbeddedInternet explorer 平移和缩放功能以及可自定义界面，可优化设备上的浏览体验Adobe Flash Lite 新增的浏览器插件，Touch and Gesture 新增的插件引擎，可实现自然输入功能和手势动画Connection Manager 基础设施技术，可管理设备上的多个网络接口Microsoft Office and PDF Viewers应用程序，可在设备上呈现Microsoft Word 、PowerPoint ，Excel and Adobe PDF 内容QQ Messenger腾讯QQ ，设备上的客户端程序，可链接到常用的即时消息传递服务第二章、必须软件请确保您的PC 已经正确安装了如下软件：以下软件安装的详细步骤，请按照《VS2005_WinCE6.0安装指导PDF》进行第三章、安装R3及选项软件需要安装件12009Monthly updates：WinCEPB60-090131-2009M01-Armv4I~WinCEPB60-090228-2009M08-Armv4I.msi2WinCE6.0R33Expression Blend2Trial4Office and PDF Viewers5QQ Messenger Client3.1升级WinCE6.0R3前，请仔细阅读当前目录下的Windows Embedded CE6.0R3ReleaseNotes.htm Windows Embedded CE6.0R3License.rtf Windows Embedded CE6.0R3Install Guide.htm3.2安装WinCE6.02009Monthly UpdatesWinCEPB60-090131-2009M01-Armv4I.msiWinCEPB60-090228-2009M02-Armv4I.msiWinCEPB60-090228-2009M03-Armv4I.msiWinCEPB60-090228-2009M04-Armv4I.msiWinCEPB60-090131-2009M05-Armv4I.msiWinCEPB60-090228-2009M06-Armv4I.msiWinCEPB60-090228-2009M07-Armv4I.msiWinCEPB60-090228-2009M08-Armv4I.msi如果在安装R2的时候已经装过Monthly Updates，则这里不需要再安装。
S3C2410下WinCE6.0的启动过程详解
S3C2410下WinCE6.0的启动过程详解通过前两篇文章的介绍，我们已经知道NBOOT用来引导EBOOT，继而EBOOT加载并引导WinCE操作系统(NK)。
那么，WinCE6.0的启动过程又是怎样的呢？本文基于S3C2410的平台做一个详细的分析。
需要说明的是，WinCE6.0的整个启动过程对于同一类型的MCU来说大同小异，如S3C2410和PXA270同属ARM平台的MCU，所以他们的启动过程是类似的，可以说唯一的不同就在OAL处，而WinCE操作系统的启动正是从OAL开始的。
OAL（OEM Adaptation Layer）即OEM适配层，它的主要作用是在移植WinCE到新的硬件平台时减少操作系统的修改，通俗的说就是为WinCE 操作系统抹平MCU的差异，使其能很方便的在不同MCU上运行。
所以，OAL 包括了和系统硬件通讯的最底层代码。
内核则通过OAL跟硬件进行交互。
逻辑上，OAL是介于CE内核和设备硬件之间的一个代码层，是一个抽象的概念。
物理上，OAL和其他一些库一起链接成可执行文件，在WinCE6.0中对应的文件是OAL.exe，这是OAL的客观存在。
WinCE6.0中的OAL跟先前的OAL比，是有一些变化的，它从内核中分离出来成为OAL.exe，而内核则变成了Kernel.dll。
这样做的好处是可以单独升级OAL。
但整体的OAL结构并没有改变，OEM函数保持一致，OAL和Kernel的接口由共享结构NKGLOBAL实现。
这一部分的具体内容下一篇再做介绍。
下图所示为WinCE6.0的OAL设计。
在移植WinCE到新的硬件平台时，创建OAL是最复杂的任务之一。
一般来说，最简单的方法是拷贝一个跟新的硬件平台类似的且成熟的OAL，然后根据硬件的不同进行修改，使其满足目标硬件的特定要求。
这里不展开说明，回头再单独整理。
从EBOOT到OAL.exe的跳转是从OEMLaunch（）开始的，函数OEMLaunch（）中调用Launch（dwPhysLaunchAddr），它的实现代码如下：CodeLEAF_ENTRY Launchldr r2, = PhysicalStartldr r3, = (VIR_RAM_START - PHY_RAM_START)sub r2, r2, r3mov r1, #0x0070 ; Disable MMUmcr p15, 0, r1, c1, c0, 0nopmov pc, r2 ; Jump to PStartnop; MMU & caches now disabled.PhysicalStartmov r2, #0mcr p15, 0, r2, c8, c7, 0 ; Flush the TLBmov pc, r0 ; Jump to program we are launchin g.函数Launch（）的参数为物理地址，因为在跳转之前已将MMU关闭。