Clone of BSP in wince

When it comes to wince, the BSP clone is actually a copy of the BSP, but it changes some of the information in the BSP. In the wince, the BSP cloning should be very simple, today to do a simple introduction.

I rarely use a BSP clone, do wince also have several years, used several times, the beginning is to learn to clone a few times, but there is no practical use. Later I work in an IC design company, the company opened a new arm chip, based on the company's old arm to improve the frequency, adding a number of new modules. This time I really used the BSP cloning, based on the company's old arm chip BSP, cloning a BSP, and then in the above for the new ARM chip development drive and new features.

Therefore, the BSP cloning should be a BSP development of the first step, when you have nothing, it is best to find a chip and your platform is similar to the existing BSP package, cloning, and then develop a new BSP on the above, this will save time. The reason everybody understands, the following introduction:

1. Based on WinCE6.0, first open VS2005, then select "Tools"-> "Platform Builder for CE 6.0" "Clone BSP", will pop up a clone BSP window.

2. In the pop-up window, we can see some information, in the "Source BSP" Select the current wince system has been supported BSP, select a and your platform similar to the BSP, that is cloned BSP, where we choose "Device emulator: ARMV4i ". Then in "Name", enter the first name as MYBSP, and in "Description" Enter the This is my BSP. Enter MYBSP in "Platform Directory", which is best aligned with the "Name" above. "Vendor" Enter My, "Version" Enter 1.0. Should be the following figure:

3. Finally click "Clone" on it, if fast, wait a few seconds will be completed. If successful, a dialog box will pop up telling you that the BSP has been cloned successfully.

Relatively simple, BSP has been cloned to complete. You can see a mybsp folder under "\wince600\platform\", which is the BSP that is cloned. Here's a brief description of what's Inside:

SOURCES.CMN: This file is a BSP sources total file, it will function in the BSP of all sources files, that is, the settings in this area will be used in all the BSP sources files.

Mybsp.bat: This is a batch file that mainly completes the settings for some of the default environment variables. He wants to have the same name as the folder, and this batch will run automatically when you create a project or open a project with that BSP.

Dirs: A directory file that indicates the folder to be compiled, typically pointing to the SRC folder.

Cebasecesysgen.bat: This batch will be called by Cesysgen.bat, mainly to set up some wince system-related SYSGEN_XXX environment variables. The script doesn't matter, and many of the BSP don't have the script.

Catalog folder: This folder contains the BSP's engineering files, called Mybsp.pbcxml. You can edit it directly using Notepad, and note that his name is consistent with the folder name, otherwise it cannot be identified.

Cesysgen folder: This folder contains a makefile file that filters the code and configuration files based on the settings of the environment variable.

Files folder: This folder contains the BSP and wince configuration files, including bib files, registry files, DB files, and so on.

Src folder: Is the BSP source code folder, which contains the BSP of all sources. These should include "Bootloader", "Drivers", "Inc", "OAL" and "Kitl" folders. Of course, different BSP, the name may be slightly different. "Bootloader" is the Bootloader of wince, generally refers to the eboot. "Drivers" contains all the drivers in the BSP. "Inc" is a header file folder. "OAL" contains the code for the OAL part of the wince. "Kitl" is a kilt code that implements network-based debugging.

This is the general introduction. It said a lot, in fact, is to introduce the BSP of the Clones, and BSP inside there are some things. Mention cloning, here in addition, in the WinCE6.0, not only the BSP can be cloned, wince some of the components can also be cloned. When we create a wince project, we can use some wince builds, but we want to change his source code, which is usually located under the public directory. Changing the source code in the public directory is not a good note, first of all, you change the source in the public directory needs to recompile the public directory, which will take a few hours, and then if the Microsoft patch updates the code you changed, then you may need to revise.