Pbcxml Analysis of WinCE BSP Engineering documents

Each BSP has an engineering document, such as Mybsp.pbcxml, which describes the BSP information. Here is a description of the BSP Pbcxml file.

The approximate format of the file should be this:

<CatalogFile …>
<FileInformation ….>
….
</FileInformation>
<BSP …>
…
</BSP>
<Item …>
…
</Item>
<Item …>
…
</Item>
<Item …>
…
</Item>
<Item …>
…
</Item>
</CatalogFile>

In fact <CatalogFile>...</CatalogFile> is equivalent to a portal where bread contains all the contents of the WinCE BSP, which contains several sections, each of which is described separately below.

1. <FileInformation>...</FileInformation>: Here bread contains the basic information of BSP, such as the name of BSP, description, manufacturers and so on. Here is a template:

<FileInformation Id="FileInformation: VENDOR:CATALOGFILENAME ">
<Title>Title Name</Title>
<Description>BSP Description</Description>
<Vendor>Vendor Name</Vendor>
<OSVersion>WinCE Version</OSVersion>
<FileVersion>File Version</FileVersion>
</FileInformation>

Here is not too much to introduce, a look should be understood, the following for the actual BSP used in the description of the example:

<FileInformation Id="FileInformation:Cirrus Logic:EP94xx">
<Title>EP94xx</Title>
<Description>EP94xx BSP Catalog Items</Description>
<Vendor>Cirrus Logic</Vendor>
<OSVersion>6.00</OSVersion>
<FileVersion>1.0.0</FileVersion>
</FileInformation>

2. <BSP>...</BSP>: This item is generally followed by <FileInformation> to describe what components are in the current BSP, or what items are available. The specific template is as follows:

<Bsp Id="Bsp: VENDOR: BSPDIR: CPU">
<Title>BSP Title</Title>
<Description>BSP Description</Description>
<PlatformDirectory>Platform Directory</PlatformDirectory>
<CpuId>Cpu:CPU ID</CpuId>
<BspItemId>Item: VENDOR: VARIABLE</BspItemId>
<BspItemId>Item: VENDOR: VARIABLE</BspItemId>
…
</Bsp>

Here's what you need to explain:

Vendor: Name of the manufacturer, such as the BSP provided by Samsung, then it should be Samsung.

Bspdir: Refers to the path of the BSP under the "/platform" folder.

CPU: Refers to the CPU supported by the BSP, such as armv4i.

Module: Refers to the various modules in the BSP are compiled after the DLL or EXE generated by the name, such as Audio.dll, then this should be audio.

VARIABLE: Refers to the BSP and a module-related environment variables.

<title>...</title>: Refers to the title of a BSP

<description>...</description>: A description of a BSP

<platformdirectory>...</platformdirectory>: Refers to the path of the BSP under the "/platform" directory.

<cpuid>...</cpuid>: Refers to the supported CPUs, such as armv4i.

<bspitemid>...</bspitemid>: Refers to which modules are included in the BSP.

Note here that there are two ways to,<bspitemid>...</bspitemid> the following:

Method 1：<BspItemId>Item: VENDOR: VARIABLE</BspItemId>
Method 2：<BspItemId>Item: VENDOR: MODULE: BSPDIR</BspItemId>