Illustration of how to clone using BSP clone of WinCE

Today we will talk about the BSP clone of wince, which is actually a BSP copy, but it only changes the information in some BSP. In wince, the cloning of BSP should be very simple. Today we will give a brief introduction.
I seldom use BSP cloning. I have been using wince for several years. I used it several times. I first tried it several times to learn how to clone it, but it has no practical use. Later, I worked in an IC design company. The company opened a new arm chip, which increased the frequency and added some new modules based on the company's old arm. At this time, I actually used BSP cloning. Based on the BSP of the company's old ARM chip, I cloned a BSP and developed the driver and new functions for the new ARM chip.

Therefore, BSP cloning should be the first step in BSP development. When you have nothing, you 'd better find an existing BSP package that is similar to your chip and platform for cloning, then develop a new BSP on the top, which will save time. Everyone understands the truth. The following is an introduction:

 

1. Based on wince6.0, first open vs2005, and then select "Tools"-> "platform builder for CE 6.0"-> "clone BSP". A clone BSP window is displayed.

 

2. in the pop-up window, we can see some information. In "Source BSP", select the BSP that is currently supported by the wince system and select a BSP that is similar to your platform, that is, the cloned BSP. Here we choose "device emulator: armv4i ". Then, in "name", enter the name mybsp, and in "Description", enter this is my BSP. Input mybsp in "platform directory". It is better to be consistent with "name" above ." Vendor "input my," version "Input 1.0. It should be like:

 
3. Click "clone". If it is fast, it will be completed in a few seconds. If yes, a dialog box will pop up to tell you that the BSP has been cloned successfully.

Simple. The BSP has been cloned. You can see a mybsp folder under "/wince600/platform/", which is the cloned BSP. The following briefly introduces some content:

 

Sources. CEN: this file is a total file of BSP's sources. It will act on all the sources files in BSP, that is, the settings here will be used in all the sources files in BSP.

 

Mybsp. BAT: This is a batch processing file, mainly used to set some default environment variables. The same name as the folder. When you create a project with the BSP or open the project, the batch processing will automatically run.

 

Dirs: directory file, indicating the folder to be compiled. It generally points to the SRC folder.

 

Cebasecesysgen. BAT: this batch is called by cesysgen. bat. It mainly sets the sysgen_xxx environment variables related to the wince system. It doesn't matter if this script does not exist. Many BSP do not have this script.

 

Catalog Folder: this folder contains the BSP project file named mybsp. pbcxml. You can use NotePad to edit it directly. Note that the name must be the same as the folder name, otherwise it cannot be recognized.

 

Cesysgen Folder: this folder contains a MAKEFILE file that filters out code and configuration files based on environment variable settings.

 

Files Folder: this folder contains BSP and wince configuration files, including bib files, registry files, and DB files.

 

SRC Folder: the source code folder of BSP, which contains all source code of BSP. These folders should include "bootloader", "drivers", "Inc", "oal", and "kitl. Of course, the names of different BSP may be slightly different ." "Bootloader" is the bootloader of wince, which generally refers to eboot ." Drivers contains all the drivers in BSP ." Inc is a header file folder ." OAL "contains the oal code in wince ." Kitl is a kilt code that implements network-based debugging.

 

This is a general introduction. I 've mentioned a lot above. In fact, I just introduced the cloning of BSP and what is in BSP. We will add that in wince6.0, not only BSP can be cloned, but some components in wince can also be cloned. After we create a wince project, we can use some wince components, but we want to modify its source code. Generally, these source codes are under the public directory. Changing the source code in the public directory is not a good concern. First, you need to re-compile the public directory to change the source code in the public directory. This will take several hours, next, if Microsoft updates your modified code, you may need to modify it again.

Therefore, in the wince project, if you want to change the source code of components under the public directory, cloning may be a better choice. Let's introduce it as follows:

1. if you already have a project, in the "catalog View" of your project, if you want to clone the module "device drivers"-> "USB function"-> "USB function client"-> "Mass Storage", right-click the module and the following window is displayed:

 

2. Select "clone catalog item" and a window will pop up, as shown below:

 

 

3. Select the component you want to clone and click "OK. After successful cloning, a dialog box is displayed.

After completing the preceding three steps, the clone of the component is completed. The cloned component is automatically copied to the directory of your project, switch to "Solution Explorer" in the IDE environment, and you will see the cloned component under "subprojects". The component already exists as a sub-project, the Code has also been copied to the project directory.

 

In the last few words, the cloning of BSP should be relatively simple, but sometimes errors may occur. The general error may be caused by a problem with the cloned BSP. Cloning components is used when you need to modify the source code under the public directory, and not all components can be cloned. If the components cannot be cloned, you need to manually modify it.

 

This article from: It Channel Network (http://www.itwis.com) detailed source reference:

Http://www.itwis.com/html/net/netother/20080908/2366.html