winCE5.0 6.0使用教程
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。
Windows CE 5.0软件安装过程
Windows CE 5.0软件安装过程首先，在安装Windows CE 5.0 之前我们要安装Microsoft .NET Framework 1.1，这是Microsoft制作的一个组件包。
如果不安装这个软件将无法安装Windows CE 5.0。
双击Microsof Windows CE 205.0.msi文件，如图。
会出现Welcome to Microsoft Windows CE 5.0的安装提示界面，如图。
点击“Install”，会出现如下界面。
Install准备后，出现如图界面。
点击“Next”后显示授权协议界面，选择“I accept the term in the licence agreement”如图。
单击“Next”，显示客户信息界面，键入用户信息，并输入产品密匙，如图。
单击“Next”，出现安装类型界面，选择“Custom（tool and OS）”安装类型，如图。
单击“Next”，如图显示的是目标文件夹对话框，单击“Change...”按钮，设置PlatformBuilder 5.0安装文件夹和Windows CE操作系统安装路径及文件夹。
注意：一般情况下，C盘为桌面操作系统，所以意见将Platform Builder和Windows CE 操作系统都安装到C盘外的其他逻辑盘，如D盘或E盘等，但无论安装到哪个驱动盘，都不可更改如下图所示的相对路径和路径名，否则将来在执行系统编译时会出现严重错误。
单击“Next”出现如下图的定制安装配置窗口，选择要安装的CPU类型。
建议安装Emulator、X86、ARMV4I和xScale处理器（这主要取决个人所使用的CPU体系），并选择安装“Windows CE 5.0 Test Kit”。
另外“Share Source for Windows CE 5.0”是微软开放的Windows CE 5.0的源代码，建议高级用户选择安装。
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模拟器使用教程
WinCE6.0模拟器使用教程在前些时日，我发表了一些列有关一体机的帖子。
回复中我承诺大家，给大家写一个关于如何使用模拟器的帖子。
恰好前几天发生点儿小状况，所以拖延到今天才写。
同时也庆祝我“一箭穿心”解禁复出。
我这里所说的模拟器其实并不是一个机器，而是一个软件平台。
是个虚拟的东西，看得见但摸不着。
所以，如果有人一听模拟器，以为是个机器。
呵呵，那就大错特错了。
导航仪本身其实就是一台微型电脑。
我们平时用的电脑有windows95~2003、windows XP以及现在挺火的windows7等操作系统。
而现在导航仪的操作系统一般为windowsCE5.0、windowsCE6.0及其他系统。
本贴以windows CE6.0操作系统为例展开如何使用的讲解。
以下文中windowsCE简称WinCE。
WinCE模拟器是一个不依赖于硬件可以运行WinCE的环境，它提供了一个虚拟的硬件平台，这样可以在上面测试一些应用程序。
在WinCE6.0中提供了针对于ARM的模拟器的支持，一般和底层硬件相关的程序是不能在模拟器上面调试的，但是有些界面程序和简单的应用程序，在WinCE模拟器上面调试还是很方便的。
如此以来，当我们下载一个新的导航程序及地图或者其他WinCE软件后，没必要先考到内存卡上，再插入导航仪中试用。
我们先可以上模拟器，如果模拟器运行正常，那上机后一般都能正常运行。
这样一来就避免了频繁拔插卡，对导航仪卡槽及卡造成损伤。
一、下载WinCE6.0模拟器。
这个很简单。
只要在百度搜索条中输入“WinCE6.0”，瞬间成片的结果就等你选择了。
随便选择一个下载就行。
安装版的也行，绿色版的也可。
下载后安装，文件夹如下图。
注意了：一定要安装在D盘！切记！！二、WinCE6.0模拟器的使用如下图中的三个批处理文件依次代表：4.3寸屏、7寸屏、及800*480高清屏。
根据自己的导航仪屏幕类型选择相应的批处理文件。
双击运行即可。
Wince6.0模拟器使用说明
Wince6.0模拟器【运行环境】:适用于Windows平台PC
【☆分辨率】:详见使用教程
【版本信息】:Wince6.0模拟器
【是否测试】:已测试
第一步：把软件下载解压后看到以下目录.
第二步：双击运行上图中的Skin_800X480.BAT，运行后得到下图.
第三步：点击上图中的文件－配置得到下图.
定．
第五步：运行上图中的我的设备，得到下图．
第六步：因为第二步和第三步的配置我的设置里面就会有个SDMMC盘．SDMMC就相当于你导航里面的一个SD卡或者说是导航仪的内置卡．双击打开SDMMCC．得到如下图
第七步：第二步和第三步设置的目录里面的要模拟的地图和程序了．再后面就不用说了吧，和导航仪一样的．．．
此软件优点运行速度比Wince模拟器5.0快，缺点就是每次模拟地图都要配置第二和第三步．
此教程为菜鸟级别学习，老鸟请漂过～～～。
WINCE5.0 6.0开发环境配置与SDK下载
WINCE5.0 6.0开发环境配置与SDK下载WinCE5.0 模拟器配置与SDK下载WinCE5.0中文模拟器SDK的安装过程不细说了，一路默认即可，下面主要介绍如何配置，使其能在VS2005中正常使用。
安装完成后，打开VS2005，点击菜单“工具”——“选项”——“设备工具”——“设备”，选择“Windows CE 5.0 ARMV4I Emulator”，点击“属性”按钮，如下图所示。
在弹出的对话框中，点击“仿真器选项”，如下图所示。
在弹出的对话框中，设置“Flash Memory File”和RAM Size如下图所示。
在Display下，设置显示属性，如下图所示，点击“OK”——“确定”——“确定”保存设置。
打开Device Emulator Manager，连接“Windows CE 5.0 ARMV4I Emulator”，启动模拟器。
如果需要保存文件及注册表设置，点击菜单“Flash”——“Save”即可，如下图所示。
该SDK的下载地址:/source/1846785/source/1846812WinCE6.0 模拟器配置与SDK下载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-B39 D-37BAF6B5B1DC&displaylang=en 430多兆，通吃所有版本。
WinCE6.0远程桌面的实现
WinCE支持远程桌面功能，可以在PC端访问目标设备的WinCE桌面。
这个功能在调试的时候很有用。
有些时候，你的目标板不带显示设备，这时你想访问目标板的WinCE系统感觉很不爽，毕竟习惯了桌面操作。
通过WinCE远程桌面，你可以在PC上面访问目标板的WinCE桌面并进行操作。
下面来介绍一下具体步骤：1. 选择支持WinCE远程桌面的组件：在WinCE的工程中选择”Core OS”->”CEBASE”->”Core OS Services”->”DebuggingTools”->”Remote Display Application”，如下图：在这里建议同时添加telnet组件，在”Core OS”->”CEBASE”->”Communication Services and Networking”->”Servers”->”Telnet Server”。
由于目标板可能没有任何输入输出设备，所以添加Telnet组件可以在系统启动以后，登陆Telnet来执行命令。
2. 配置远程桌面主机IP地址：打开WinCE工程的注册表文件project.reg，然后添加下面的内容。
[HKEY_LOCAL_MACHINE\SOFTWARE\CERDISP] "Hostname"="192.168.0.88"其中Hostname为PC机的IP地址，也可以是计算机名。
还可以同时添加Telnet注册表配置，如下：[HKEY_LOCAL_MACHINE\COMM\TELNETD]"IsEnabled "=dword:1"UseAuthentication"=dword:0该配置实现了无需身份验证，直接登录Telnet的功能。
3. 重新编译，下载运行WinCE：由于添加了新的WinCE组件，需要重新编译WinCE工程。
在WinCE5.0和WinCE6.0下 编译选项介绍
在WinCE5.0和WinCE6.0下编译选项介绍在WinCE5.0中，在Build OS菜单中，我们会看到不同的编译选项： Sysgen，Build and Sysgen和Build and Sysgen current BSP Sysgen：不用多说，当你在Catalog中添加或删除了新的item的时候，就用这个吧。
Build and Sysgen：当你更新了\public目录下的源代码的时候，你就需要用这个了。
一般比如在打patch以后，可能就需要进行Build and Sysgen了。
Build and Sysgen current BSP：当你只改变了你的BSP部分的代码，就可以用这个选项。
据说，当你改变了\platform目录下的代码，也可以用这个，具体没有试过。
在WinCE6.0中，在VS2005的Build菜单中，有一个Advanced Build Commands，其中有很多编译选项： Sysgen：相当于执行命令blddemo -q，一般第一次编译或者是改变了Catalog 中的item的时候，就用这个了。
Clean Sysgen：相当于执行命令blddemo clean -q，按照文档上的说明，当修改了%_WINCEROOT\Public\CEBASE\OAK\Misc\Cesysgen.bat的时候，或者改变了以SYSGEN，BSP为前缀的环境变量的时候，需要使用这个来编译。
在此我说一下我个人的经验，一般只有第一次创建完工程的时候，我会用Sysgen命令，以后只要是改变了SYSGEN为前缀的环境变量的设置或者是Catalog中的item，我就会使用Clean Sysgen，而改变了以BSP为前缀的环境变量要看具体情况，也不一定就要用Clean Sysgen。
继续... Build and Sysgen：相当于执行命令blddemo，当改变了\public目录下的代码，比如你打了WinCE的patch，你就需要用这个了。
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内存管理(CE5.0&CE6.0)
物理地址
虚拟内存模型（2）-CE5.0
FFFF FFFF
Kernel Space
Kernel Addresses: KPAGE, Trap Area, Others Unused
Total 4 GB Virtual Space 2 GB Kernel Space
User Space
Slots 63 – resources dll
Logical Memory (Heap, stack) Virtual Memory Physical Memory * Storage Device
Windows CE采用层次化的结构
内存结构（2）
物理内存
在内部或外部总线上可访问的实际的 RAM/ROM RAM分为对象存储区域（object store）和应 用程序内存区域（program memory）。 ROM中存放的内容可以是压缩的，也可以是 不压缩的（可本地执行--XIP，executed in place）。 Windows CE只能管理512MB的物理内存
WinCE 6的虚拟内存模型(5)
内核空间
低1G：静态虚拟地址 0xC0000000–0xC7FF FFFF： 内核加载的(XIP) DLL 0xC8000000–0xCFFFFFFF：文 件系统的对象存储区 0xD0000000–0xDFFFFFFF：内 核模式的程序执行区。如 GWES.DLL，系统DLL，内核驱 动等。 0xE0000000–0xEFFFFFFF：同 上。除了SH4架构的CPU。 0xF0000000–0xFFFFFFFF：捕 获系统调用，包含核心数据页。
FFFF FFFF
非常详细的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(…)单击确定，完成工程属性配置。
InsightPower Panel for WinCE 5.0 使用手册说明书
InsightPower Panel for WinCE 5.0使用手册InsightPower Panel目录第1章简介________________________________________________________3功能与特色___________________________________________________________3系统架构_____________________________________________________________3支持厂商_____________________________________________________________3第2章初始安装____________________________________________________4安装主程序___________________________________________________________4连接UPS通讯线________________________________________________________4第3章功能介绍____________________________________________________6 Main页面：___________________________________________________________6 UPS页面：___________________________________________________________6 Event页面：__________________________________________________________7 Data页面：___________________________________________________________7第4章组态设定____________________________________________________8 COM设定：___________________________________________________________8 Log设定：____________________________________________________________9 Other设定：__________________________________________________________92InsightPower Panel第1章简介功能与特色透过 RS485 与31部台达NT或T系列UPS通讯经由RS485可以连接高达31部UP ，监控其状态。
关于wince5、VS2005和wince6网盘下载的说明
WINCE5.0和WINCE6.0开发环境的安装程序下载说明一、WINCE5.0安装程序相关Wince5.0的platform builder5.0编译环境和EVC4.0安装程序已经压缩成一个文件包。
这个文件包分为四部分：Windows CE5.0.part1.rar、Windows CE5.0.part2.rar、Windows CE5.0.part3.rar、Windows CE5.0.part4.rar。
这四部分的下载地址分别为Windows CE5.0.part1.rar /file/e6krjb2fWindows CE5.0.part2.rar /file/e6krjoieWindows CE5.0.part3.rar /file/dnh9kd5cWindows CE5.0.part4.rar /file/clqoele3以Windows CE5.0.part1.rar为例，下载界面如下图：u蛋用户可选用优蛋专用下载通道，也可用电信或网通直接下载，115网盘也支持迅雷下载。
下载完四个压缩包后，如下图所示：解压时请确认下载下来的文件名要如上图所示中为1234四个部分，选中四个中任意一个文件右键解压即可，winrar会自动将这四个分卷解压成一个文件夹：具体安装过程请参考飞凌基础资料光盘中提供的手册。
二、VS2005和WINCE6的安装程序和补丁程序VS2005分卷压缩为5部分，每部分网盘下载地址为：VS2005.part1.rar /file/bhd0mo52VS2005.part2.rar /file/aq7accv0VS2005.part3.rar /file/aq7acrwuVS2005.part4.rar /file/aq7acc93VS2005.part5.rar /file/bhd0mchy解压完成后会生成VS2005文件夹，具体安装过程请参考飞凌基础资料光盘中提供的手册。
Wince6.0分为wince6.0—A和wince6.0—B两个文件夹，每个文件夹分卷压缩为4部分，共8部分，每部分网盘下载地址为：WinCE6.0-A.part1.rar /file/clqoe8i4WinCE6.0-A.part2.rar /file/clqoekolWinCE6.0-A.part3.rar /file/e6krjiz1WinCE6.0-A.part4.rar /file/clqoehqpWinCE6.0-B.part1.rar /file/aq7alhfvWinCE6.0-B.part2.rar /file/clqo54r3WinCE6.0-B.part3.rar /file/clqo5dynWinCE6.0-B.part4.rar /file/clqo5bqa解压完成后会生成wince6.0—A和wince6.0—B两个文件夹，如图所示：具体安装过程请参考飞凌基础资料光盘中提供的手册。
wince5.0安装及使用
wince5.0安装及使用2008-09-11 23:32为什么这么多人搜索WinCE，但我还是找不到有关WinCE的工作呢？wince5.0的操作系统比较特殊，因为我们不能获得它的具体的操作系统，而能获得的是它的集成开发环境，比如Platform builder.我们可以用这个开发工具，制作出一个操作系统映像，下载到目标机上。
或者我们可以用这个开发环境制作一个自己所需要的SDK,然后在具体的嵌入式软件开发环境中使用这个SDK.大多数情况下，我们是不需要自己定制SDK的，我们可以通过其他的手段，比如到微软的网站上下载对应wince版本的SDK,然后应用，这样做的好处是不涉及定制操作系统的过程，开发快速。
但缺点是已经定制好的操作系统不一定适合我们所有的需要。
如果定制一个操作系统的话，比较麻烦，具体做法呢，转载了别人的，供大家参考。
1、我们先来安装WinCE5的开发环境，也就是我们的Platform builder.安装的过程不用多说.2、我们看到，这个Platform Builder与WinCE4的基本相同，所以不用多解释，看到屏幕中间的那个"New Platform"了吗？点击它我们来新建一个平台。
.废话少说，我们来看几个关键的步骤。
在新建平台向导的第三步需要选择板支持包（BSP）的类型，这里要根据你的硬件平台进行选择，比如你使用AMD GEODE的板子，就可以选择这个，如果使用PC机做为目标平台就选用CEPC，当然也可以选择使用模拟器Emulator，使用模拟器的意思就是你的电脑既是开发机也是目标机。
在第四步中可以选择预定义的模板平台，比如你想做个企业终端就可以选择它，想做个网关就选网关模板，想做个机顶盒就选机顶盒模析，还有IP电话，手持式移动设备，瘦客户端等等，我就选了一个Internet Appliance来做一个基于Internet的应用。
后续的向导步骤都取默认，Finish。
windows CE.net 5.0 说明书
Windows 5.0 使用说明书第1章WinCE 5.0 for MagicARM2410特点 (1)1.1 Windows 5.0 for MagicARM2410提供的驱动程序 (1)1.2 Windows 5.0 for MagicARM2410优势 (1)1.3 配套教材 (2)1.4 推荐教材 (2)第2章Windows 5.0使用说明 (3)2.1 Windows 5.0功能演示 (3)2.1.1 Windows 5.0的启动 (3)2.1.2 USB键盘、鼠标的使用及Windows CE中的文件 (7)2.1.3 触摸屏校准 (8)2.1.4 以太网IP地址的修改、以太网功能的验证及WebServer功能 (9)2.1.5 系统设置与用户数据的保存 (11)2.1.6 播放mp3，mpeg多媒体文件 (12)2.1.7 Txt，Word，Excel，pdf，ppt，图片文件的浏览 (12)2.1.8 SD/MMC，CF卡，PCMCIA转CF卡，U盘的读写 (12)2.1.9 蓝牙USB适配器 (13)2.1.10 建立ActiveSync连接，从PC机传输数据到Windows 5.0 (14)2.1.11 蜂鸣器、步进电机、LED控制 (20)2.1.12 CAT1025 E2PROM的读写 (21)2.1.13 ZLG7290按键扫描及七段数据管显示 (21)2.1.14 ADC采样显示 (22)2.1.15 直流电机调速 (22)2.1.16 SD/MMC卡的读写 (22)2.1.17 GPRS拨打/接听电话，接收/发送短信，无线上网 (23)2.1.18 串口通信，以太网UDP、TCP通信，CAN总线通信 (25)第1章 WinCE 5.0 for MagicARM2410特点1.1 WinCE 5.0 for MagicARM2410提供的驱动程序MagicARM2410实验箱上运行的Windows CE操作系统为Windows 5.0，支持64MB的NANDFlash盘驱动，保证掉电后系统设置及用户数据不丢失，并且提供了丰富的外设驱动，包括：TFT 640 X 480液晶驱动程序触摸屏驱动程序S3C2410A USB Host驱动程序USB HID驱动程序(支持USB鼠标、USB键盘)USB大容量类驱动(支持U盘读写)USB蓝牙驱动(支持两个蓝牙设备之间的文件传输)USB Device驱动程序(支持与PC机Windows的ActiveSync连接，支持文件传输，应用程序在线调试，远程查看注册表等功能)支持GPRS拨打电话、收发短信、远程控制、无线上网CAN总线驱动10M/100M自适应以太网DM9000驱动(支持UDP、TCP/IP、WebServer)ZLG/FFS支持写平衡的NAND Flash驱动(NAND Flash在Widnows CE下表现为一个Flash Disk)串口UART0、UART1、UART2、RS485驱动程序SD/MMC卡驱动程序(支持SD/MMC卡的读写)PCMCIA驱动程序CF卡驱动程序(支持CF卡、PCMCIA转CF卡的读写)PCMCIA转UART卡驱动模数转换ADC驱动PWM驱动(支持直流电机调速、DAC输出)GPIO驱动(用于控制蜂鸣器、LED、步进电机)音频驱动(驱动2个扬声器、用于播放音乐)I2C主机驱动(可用于读写CAT1025的E2PROM或访问ZLG7290)单独按键KEY1驱动支持txt、Word、Excel、pdf、ppt、图片文件的浏览支持 mp3、mpeg多媒体文件的播放支持掉电系统设备和用户数据的保存1.2 WinCE 5.0 for MagicARM2410优势MagicARM2410教学实验开发平台支持的Windows 5.0与其他厂商支持的Windows CE相比较，其优势如表1.1所示。
实验一 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 的安装基本上是大同小异，个人感觉没有什么太大变化，都应该一次能安装成功的，这个过程让我熟悉了安装的过程。
Windows7上安装wince5.0 6.0及SDK模拟器
Windows Vista/Windows 7上安装wince5.0/6.0及SDK模拟器安装Windows CE 5.0/6.0及SDK模拟器在Windows Vista或Windows 7计算机上,该SDK由供应商提供将其安装在Windows Vista/Win7计算机上并安装了Visual Studio 2008。
虽然SDK出现在列表中与卸载的程序，但是VS2005或VS2008设备仿真器管理器中看不到也不能用。
1233 45直到完装完成。
打开VS2005/VS2008查看如下================================================在Windows Vista/Win 7 上装WinCE 6.0会出现如下问题：1、ToolsMsmCA(Error): Setup package issue or CoreCon DataStore corrupted: CDeviceSDKInstallShim Add/Remove failed. HR=0x8007005。
2、ToolsMsmCA(Error): Setup package issue or CoreCon DataStore corrupted: DeviceSDKInstComp Add/Remove failed. HR=0x8007005。
解决方法：在安装的时候采用管理员权限。
怪异的是，WinCE6.0的安装程序点击右键却没有“使用管理员权限”的菜单，这个也是微软的Bug了。
那怎么办呢，其实还是有办法的，我们用“管理员权限”打开cmd.exe，然后通过命令行的方式，使用Call安装执行程序就可以了。
网上还有其它错误问题的解决描述如下：如果你在安装window mobile 6 sdk时，出现如下烦人的错误：“To olMsmCA（Error）：Setup package issue or CoreCon DataStore corrupted:CDeviceSDKInstallShim Add/Remove failed.HR=0x80004005”.按如下方法应该可以解决此问题。
凯立德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拷入卡里，再在导航仪上设置导航路便可，如果遇到有端口和波特率和新导航的默认不一样，一般掌柜会在您拍下不久都会帮您设置好并发送给您的，您只要按说明放入相应的文件夹替换便可。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Windows ce6.0模拟器可用于车载导航系统(凯立德导航地图、道道通导航地图、城际通导航地图及其它Windows CE软件模拟测试)。
本次分享的是Wince6.0模拟器，喜欢折腾的朋友抓紧下载了！
Windows ce6.0模拟器使用方法：
1. 解压下载好的Windows ce6.0程序压缩包。
2. 运行文件夹内“连接加载.bat”注册Windows ce6.0。
3. 按需求运行文件夹内各分辨率“800x480.BAT”“7寸.bat”“
4.3寸.bat”运行文件，启动CE6.0模拟器。
480*272 4.3寸 CE6.0模拟器演示
480*234 7寸 CE6.0模拟器演示
800*480 CE6.0模拟器演示
windows ce6.0模拟器运行凯立德导航地图（其他导航系统运行方法一致）：
1、点击win CE6.0模拟器顶部文件选项>>>配置>>常规>>共享文件夹
2、点击共享文件夹"..."后，选择凯立德导航地图文件夹，选择完毕点击确定。
3、点击win CE6.0模拟器桌面上的“我的设备”图标。
4、打开“SDMMC”
5、打开“SDMMC”后，运行Navione.exe 运行凯立德导航系统。
windows ce6.0模拟器运行凯立德导航系统全屏设置：
1、单击windows ce6.0模拟器开始菜单>>>设置>>>任务栏和开始栏菜单
2、在任务栏和开始栏菜单属性>>>常规里勾选自动隐藏，点击OK，凯立德导航地图全屏显示了。
15.jpg(122.8 KB, 下载次数: 5)
下载附件
设置成功，凯立德导航地图全屏显示
2012-11-8 11:23 上传
Windows ce6.0模拟器下载：
下载地址：
本帖隐藏的内容
/share/link?shareid=104534&uk=2569674654。