Building the Windows Embedded CE 6.0 development environment

Recently began to learn embedded, where the first to install Windows Embedded CE 6.0, which encountered a lot of problems, the computer system and related configuration will be affected during the installation process, so the author on the installation of the problem and the environment set up to introduce.

The first step is to install VS2K5 and install the vs2k5 SP1 patch (KB926601) after installation, otherwise platform Builder SP1 cannot be installed later.

The second step, installing Windows Embedded CE 6.0, is officially:
http://www.microsoft.com/downloads/details.aspx?familyid=7E286847-6E06-4A0C-8CAC-CA7D4C09CB56&displaylang= En
This article provides an offline installation of the file table (click to download), the File table to import thunderbolt can download a complete offline installation package, about 3.7G size. The installation interface for the CE6 is as follows:

The third step installs Windows Embedded CE 6.0 Platform Builder Service Pack 1, which is officially:
Http://www.microsoft.com/downloads/details.aspx?FamilyId=BF0DC0E3-8575-4860-A8E3-290ADF242678&displaylang=en. If the vs2k5 SP1 patch is not installed, the patch needs to be installed first.

After installing the above three steps, open the VS2K5, we can see installed products added a platform Builder for CE6.0, indicating that CE6 has been installed successfully, CE6 is installed in vs2k5 in add-on way.

The fourth step installs Microsoft Device Emulator 2.0, officially: http://www.microsoft.com/downloads/details.aspx? The familyid=dd567053-f231-4a64-a648-fea5e7061303&displaylang=en,2.0 version of the emulator is an upgrade to the 1.0 version of the default installation in Vs2k5.

The fifth step is to install Virtual machine Network Driver for Microsoft Device Emulator, which ensures that the emulator is running properly, and that if it is not installed, it will be a black screen after startup, and I have encountered this problem, The official: http://www.microsoft.com/downloads/details.aspx? 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, but here's a problem, VPC2007 can be in Windows xp/vista/windows The Server 2003 standard is installed on the enterprise and cannot be installed on enterprise, it can only install more advanced Virtual Server 2005. So be careful when choosing an operating system. Virtual PC 2007 is installed directly here because I am using Windows XP to operate the system.

The next step is to customize a Windows CE 6.0 system with the PB just installed, which can be loaded onto the Device emulator after the system has been customized so that we could develop and test the system. Open VS2K5, select Create a new installed OS design project template and go to the wizard page.

It is recommended to select device Emulator:armv4i in board support packages. This is a very important step, at the same time here to mention a point, the device simulator is ARM architecture, that is, the x86 architecture of the CE system can not be run on the simulator, this problem I have encountered, with cepc:x86 customized a system, compiled after the completion of attaching to the device simulator when reported error: Invalid or missing ROM image. But it doesn't matter if you choose the wrong choice, you can still modify these options after you've created the template.

PB provides a selection of design templates, I chose PDA Device----Mobile handheld, and then the next step to complete the creation, the final step of the creation will pop up a catalog Item notification dialog box, Click Acknolwlege OK to complete the creation. The topic of customizing Windows CE Systems is described in a future article. From the Vs2k5 menu, select Tools->device Emulator Manager to open the Device Emulator Management window, which lists all the virtual machines available now, such as Pocket PC 2003, Smartphone 2003, etc. But now that we can't find the Wince6_emu simulator, we're going to compile the custom-built system and build the SDK.

One thing to mention before compiling is to cancel kitl (no imgnokitl=1), which cannot be started in non-debug mode without canceling this option. Right-click the project name, select Properties, and in the build options, uncheck Enable KITL (no imgkitl=1). You can then compile and compile for a relatively long time, depending on how much you customize the functionality.

After the compilation is successful, a file named Nk.bin is generated in the reldir corresponding directory, which is the runtime image to use for the virtual machine, and the solution is to attach the compiled system to the device. Before you do this, make some settings for the connection properties. Open the Vs2k5 menu, select Target---Connectivity options, open the Target Device Connection Properties dialog box, target devices Select CE device, download and transport Select device Emulator (DMA), debugger select None. Other settings for the emulator's operating parameters, such as screen size, memory size, and so on, are set in this dialog box.

　　

After modifying the configuration click Apply and Close the window, select Target->attach device in VS2K5 to start attaching to the device, this time will be a few minutes, the Output window will show the added state, if the input window is stuck in a certain position, Emulator or a black screen, there may be a previous step in the configuration of the problem. You need to go back and check that when the simulator starts normally, you can see a Windows CE System Emulator window.

Next we create and install the SDK, which is designed to provide development support for target devices in vs2k5, such as class libraries, emulators, and so on. From the Vs2k5 menu, select the project, ADD New SDK to open the SDK Properties page. In Emulator, modify the configuration to device Emulator armv4i Debug, fill in the necessary information, click OK, then right-click the SDK that you just created in the Project window and select Compile. An MSI installation file is generated after compilation, located in the,sdks/<sdkname> directory under the Osdesign project folder. Close Vs2k5, and click Run this SDK and install.

After the installation is complete, open vs2k5, select Menu tools, Device Emulator Manager, open the Device Emulator Management window, we can see Wince6_emu has added the system we just created, right click on this project select Connect , the simulator window pops up and the CE system starts successfully.

This completes the entire process of customizing the CE6 operating system by PB, generating the SDK and installing it into the development environment. Once the installation is complete, we can develop debug-related applications on this custom CE6 platform.

Building the Windows Embedded CE 6.0 development environment