Establishment of WinCE5.0 development environment

At present, the main development tools of WinCE5.0 are as follows: Platform Builder5.0, EVC4.0+SP4, Visual Studio2005. Where Platform Builder is used primarily for customizing the wince operating system, it can also be used to write drivers and applications. eVC as the name implies is the embedded version of the VC, which is mainly used to develop applications, of course, can also be used to write drivers. Visual Studio2005 is Microsoft's most developed tool. It can be used to customize the WinCE6.0 operating system, and it can also be used to develop applications and drivers.

Platform Builder5.0 installation process and precautions
1. The Setup program for Platform Builder5.0 is based on the. NET Framework 1.1, so you will need to install the. NET Framework 1.1 before installing Platform Builder, otherwise the Setup program will not run.

2. Platform Builder5.0 's installation file is about 2.55G, I recommend that you copy all the installation packages to a directory on your hard disk and install them. One is faster than using a CD-ROM installation, and two CD-ROM installations will cause you to insert the disc again, even if you are using a DVD disc and all the installation packages are in the same directory.

3. After the preparation is finished, you can begin to formally install Platform Builder.
To add here, Platform Builder requires a high level of configuration for the development host. At least 512MB of memory, of course, the total amount of space on the hard disk is at least 10G, where the remaining space of C drive is at least 6 g. Because Platform Builder's installation process is best configured by default, Platform Builder is best installed on the C drive. There is no way to install in the case of D or other disks can also be used (tested basically no problem). But if there is a problem in the later use process, it will be troublesome.
In addition, installing platform Builder on Windows Vista is not recommended. Once someone has installed, the results of the installation of the end of the time roll back, and then try again, still so. Half a day is a waste of time. Even if the installation is successful, I think it will be hard enough to compile. Generally recommended pure version of Windows XP Professional, and then install PB and other software, and in the installation of PB, turn off all security software, especially anti-virus software real-time monitoring. Because many files are created during the installation of PB, monitoring can cause the installation to become slower.

4. As with the general installer, run the Setup.exe program, start the installation, and select Install.

All the way to the dialog box as shown by default. Here you need to select the type of CPU you are using . The general selection is shown in the two figure below.

Next until the installation is successful.

We know that Microsoft's software is to be patched, PB is no exception. PB patches can be downloaded from the official website (http://msdn2.microsoft.com/zh-cn/embedded/aa731256 (en-us). aspx). Personal experience, patches do not seek the latest, can be used on the line. Because once hit the latest patch, compile the original project unexpectedly error, and then return to the line. It is generally recommended to install a 06 year patch. Patch installation is relatively simple, no longer repeat.

This completes the installation of the Platform Builder integrated development environment, and the methods for its use are described in subsequent documentation.

EVC4.0 installation process and precautions
1. The easiest way to install EVC is to completely install all components.

2. If you have insufficient hard disk space, you can select only the components you want in the options shown.

After you install the IDE for EVC , the SDK is installed automatically . When you are running out of hard disk space, you can install only the components you need. As shown in.

Nextuntil the installation is complete.

Finally install the EVC SP4 upgrade package, the installation process is relatively simple, also no longer repeat.

3. EVC You may experience some problems after the installation is complete. such as the simulator does not start up. The prompt dialog box appears as shown in each boot.

And it appears in Device Manager as shown in the following scenario:

The main reason for this is that Virtual pc/windows CE Emulator conflicts with physical Address extensions (PAE) . PAE is mainly to enable the system to use more than 4GB of memory, in general, basically no use, so directly disable PAE . Verify that PAE is working as shown, and if the physical Address extension is displayed, the PAE is started.

The way to disable PAE is to modify the contents of the boot. ini file (note the red part)

The contents of the original boot. ini file

[boot loader]

timeout=2

Default=multi (0) disk (0) rdisk (0) partition (1) WINDOWS

[Operating Systems]

multi (0) disk (0) rdisk (0) partition (1) windows= "Microsoft WINDOWS XP Professional"/noexecute=optin/fastdetect

Content of the modified boot. ini file

[boot loader]

timeout=2

Default=multi (0) disk (0) rdisk (0) partition (1) WINDOWS

[Operating Systems]

multi (0) disk (0) rdisk (0) partition (1) windows= "Microsoft WINDOWS XP Professional"/execute=optin/fastdetect

After the modification is complete, save and restart the machine will not be abnormal, the simulator can also start normally. At this point, the installation process and notes about EVC are complete.

Installation and precautions of VS2005
1. The easiest way to install VS2005 is to install it completely. However, this requires enough hard disk space. If your hard disk space is limited, select the components you want. The installation process is simple but slow, not an example.

2. When using VS2005, you often encounter problems with the inability to use the WinCE simulator. It is recommended to find the answers on the Microsoft official website. http://www.microsoft.com/downloads/details.aspx?FamilyID=474B03A6-E87D-455D-BC16-B8CF18EF39B4&displaylang=en)

Briefly, the VS2005 simulator is not the same as the simulator in eVC, the eVC Simulator is based on X86, and the VS2005 wince Simulator is a armv4i platform. So you need to download the dedicated BSP custom operating system from Microsoft's website and then export its SDK. Please refer to Microsoft documentation for more information on the specific process.

The development environment of wince is basically completed, including platform Builder, EVC (SP4) and VS2005. In the actual development process, also often use the synchronization tool Microsoft ACTIVESYNC 4.5, many sites are available to download, installation is very simple, no longer repeat.

Establishment of WinCE5.0 development environment