[Wince6.0] Windows Embedded ce 6.0 installation process, serial number and preliminary use)

Windows Embedded ce 6.0 installation process, serial number and preliminary use

1. Establishment of Windows Embedded ce 6.0 development environment

Development Environment: Windows XP SP3 + Visual Studio 2005 SP1 + Windows Embedded ce 6.0

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

1.2 install Windows Embedded ce 6.0. The official download address is:

Http://www.microsoft.com/downloa... & displaylang = en

Windows Embedded ce 6.0 and its serial number

Difficult to install

Program http://download.microsoft.com/do... dded % 20ce % 206.0.msi

Serial number:

Your 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

If the serial number is unavailable, apply for it by yourself.

Http://www.microsoft.com/windows/embedded/eval/trial.mspx

During installation, a file named data_1.cab is required. The file is as follows:

Http://download.microsoft.com/do... 50b862b2/data_1.cab

1.3 install Windows Embedded ce 6.0 platform builder Service Pack 1. The official website is:

Http://www.microsoft.com/downloa... & 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.

1.4 Microsoft device emulator 2.0, official: http://www.microsoft.com/downloa... & displaylang = EN, version 2.0 simulator is an upgrade to version 1.0 installed by default in vs2k5.

1.5 is to install Virtual Machine Network Driver for Microsoft device emulator. This component ensures the normal operation of the simulator. If it is not installed, it will be a black screen after the simulator is started, and I have encountered this problem, official: http://www.microsoft.com/downloa... & 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/downloa... & displaylang = EN, but there is a problem: vpc2007 can be installed on Windows XP/Vista/Windows Server 2003 standard, but cannot be installed on Enterprise, 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.

1.6 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 introduced in future articles. 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 sdks/<sdkname> directory under the osdesign project folder. 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.

2. Two Methods of program debugging

1. Install the wince simulator and debug it on the simulator.

1.1 select "chsint SDK for wince 6.0 emulator" for the target device in the vs2005 toolbar"

1.2 debug

2. Remote debugging, that is, remote debugging on the real development board

2.1 For the target device conmanclient2.exe in the vs2005toolbar, select "Windows CE device"

2.2 "C: /program files/common files/Microsoft shared/corecon/1.0/target/wce400/x86 "folder copies the following files to the target machine (with the settings of the wince operating system ): clientshutdown.exe,cmaccept.exe,conmanclient2.exe

2.3 run conmanclient2.exeon the target machine, and then run cmaccept.exe

2.4 debug