Windows Embedded ce 6.0 development environment construction

I recently want to implement a serial communication on Windows CE.ProgramBecause we have never been involved in application development on Windows Embedded before, building a development environment has become the first challenge. This article will record and summarize the steps and problems encountered in the process of setting up the Windows Embedded ce 6.0 development environment, and hope to provide a reference for beginners of Windows Embedded Development.

My final development environment plan is Windows XP SP3 + Visual Studio 2005 SP1 + Windows Embedded ce 6.0. my current operating systems are Windows Server 2003, Visual Studio 2005 (hereinafter referred to as vs2k5) and Windows Embedded ce 6.0 (hereinafter referred to as ce6) can be directly installed on the server system, however, considering the need for device emulator debugging later, A necessary component of the simulator, virtual machine Network Driver for Microsoft device emulator, exists in virual PC 2007 (if it is not installed, the simulator starts a black screen ), however, virtual PC 2007 cannot be installed in the server operating system. Its alternative version is Virtual Server 2005 R2 SP1. . Therefore, in the server operating system, I used a Virtual Machine (the virtual machine uses Sun's virtualbox) to create a Windows XP SP3 Virtual Machine and set up the ce6 development environment on the virtual machine.

Step 1: Install vs2k5. After installation, install the vs2k5 SP1 Patch (kb926601). Otherwise, the following Platform builder SP1 cannot be installed.

Step 2: Install Windows Embedded ce 6.0. The official website is:
Http://www.microsoft.com/downloads/details.aspx? Familyid = 7e286847-6e06-4a0c-8cac-ca7d4c09cb56 & displaylang = en
The attachment in this article provides a file table for offline installation (click to download). You can import this file table to thunder to download the complete offline installation package, which is about GB in size. Shows the installation interface of ce6:

 

Step 3 install Windows Embedded ce 6.0 platform builder Service Pack 1. The official website is:
Http://www.microsoft.com/downloads/details.aspx? Familyid = BF0DC0E3-8575-4860-A8E3-290ADF242678 & displaylang = en. If you have not installed the vs2k5 SP1 Patch, install it first.

After completing the preceding three steps, open vs2k5. On the startup page, we can see that a platform builder for ce6.0 is added to installed products, indicating that ce6 has been successfully installed, ce6 is installed in vs2k5 using add-on.

 

Step 4 install Microsoft device emulator 2.0, official: http://www.microsoft.com/downloads/details.aspx? Familyid = dd567053-f231-4a64-a648-fea5e7061303 & displaylang = EN, version 2.0 simulators are upgraded to version 1.0 installed by default in vs2k5.

Step 5: Install the Virtual Machine Network Driver for Microsoft device emulator. This component ensures the normal operation of the simulator. If it is not installed, the simulator will be black after it is started, and I have encountered this problem, is: http://www.microsoft.com/downloads/details.aspx official? Familyid = dc8332d6-565f-4a57-be8c-1d4718d3af65 & displaylang = EN, this download has been turned off by Microsoft, it is recommended to download Microsoft Virtual PC 2007, the official: http://www.microsoft.com/downloads/details.aspx? Familyid = 04d26402-3199-48a3-afa2-2dc0b40a73b6 & displaylang = en, only more advanced Virtual Server 2005 can be installed on Enterprise. Therefore, pay attention to the selection of the operating system. Because I use Windows XP, virtual PC 2007 is directly installed here.

Next we will use the installed PB to create a Windows CE 6.0 system. After the system is customized, it can be loaded to the device simulator so that we can develop and test the system. Open vs2k5, select create a newly installed OS design project template, and enter the Wizard Page.

 

 

In board support packages, we recommend that you select device emulator: armv4i. This is an important step. At the same time, we should mention that the device simulator is based on the ARM architecture. That is to say, the CE system of the X86 architecture cannot run on the simulator, I have also encountered this problem. I have customized a system with cepc: x86, and reported an error when the system is attached to the device simulator after compilation: Invalid or missing ROM image. it does not matter if you select an error. You can modify these options after creating a template.

PB provides a series of optional design templates. I chose PDA device-> mobile handheld, and then the creation can be completed in one step, after the last step is confirmed, a catalog item notification dialog box is displayed. Click acknolwlege to complete the creation. Windows CE customization will be discussed in the futureArticle. In the vs2k5 menu, choose tools> device emulator manager to open the device simulator Management window, which lists all available virtual machines, such as Pocket PC 2003 and Smartphone 2003, however, we still cannot find the wince6_emu simulator. Next we will compile the customized system and generate the SDK.

 

Before compilation, we should mention canceling kitl (no imgnokitl = 1). If this option is not canceled, the simulator cannot be started in non-debug mode. Right-click the project name, select properties, and deselect "enable kitl (no imgkitl = 1)" In build options. Then you can compile it. The compilation time is relatively long, depending on the number of custom functions.

 

After compilation is successful, a directory named NK is generated under reldir. BIN file, which is the runtime image used by the Virtual Machine. After resolving this file, we need to attach the compiled system to the device. Before that, you must set the connection attributes. Open the vs2k5 menu, select target-> connectivity options, open the target device Connection Properties dialog box, select ce device for target device, select device emulator (DMA) for download and transport, and select none for debugger. Other settings for the simulator running parameters, such as screen size and memory size, must be set in this dialog box.

 

After the configuration is modified, click Apply and close the window. In vs2k5, select target-> attach device to start attaching to the device. This will take several minutes, and the added status will be displayed in the output window, if the output window is stuck in a certain position and the simulator is still black screen, it may be due to a configuration problem in the previous step. You need to check it. After the simulator starts normally, you can see a Windows CE system simulator window.

 

Next, we will create and install the SDK. The purpose of installing the SDK is to provide development support for the target device in vs2k5, such as class libraries and simulators. Select project> Add new SDK from the vs2k5 menu to open the SDK properties page. In emulator, modify configuration to device emulator armv4i debug, fill in necessary information, and click OK. In the project window, right-click the created SDK and select compile. After compilation, an MSI Installation File is generated, which is located in the osdesign project folder and in the sdks \ <sdkname> directory. Close vs2k5, and click Run SDK and install it.

After the installation is complete, open vs2k5, choose tools> device emulator manager, and open the device simulator Management window. We can see that the system we just created has been added under wince6_emu, right-click the project and select connect. The simulator window is displayed, and the CE system starts successfully.

So far, we have completed the step of customizing the ce6 operating system by Pb, generating the SDK, and installing it in the development environment. After the installation is complete, we can develop and debug related applications on this customized ce6 platform.

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/vvmao/archive/2009/03/13/3986222.aspx