Updating the BSP for a New Build Environment

  • Article

The following steps show how to update your board support package (BSP) to support the new build and environment system in Windows CE .NET.

To update the BSP build environment for migration

  1. Adjust for new microprocessor names, as follows:

    • All the sources files for your BSP must be updated to use the new microprocessor names. For more information, see Microprocessor Changes.
    • Change Kernel\Hal\SHx to Kernel\Hal\SH.
    • Update the command line build window parameters to use the new CPU names.
    • Filter \platform and \public files based on CEModule variables.

  2. Adjust for new kernel names by updating the command line build window parameters.

  3. Use new BSP and BSP_NO environment variables.

    New BSP and BSP_NO variables make it easier to create and configure your BSP. In your platform batch file, set BSP_NO variables for any options your platform hardware does not support. For common drivers such as display, audio, and network, set positive BSP variables to choose defaults for each type of device. For example, set BSP_DISPLAY_PERM3 = 1 or BSP_WAVEDEV_TVIA5000 = 1. You should also set positive BSP variables in the BSP's Catalog feature (.cec) files, by using the DefaultDriver keyword. This keeps you from being prompted to choose the default each time you build a project based on the platform.

    In the case of a device such as a PCI bus, a number of drivers can be included in the image. For example, by setting all of the BSP_DISPLAY variables, the image detects and loads a driver for every supported display device.

  4. Set the BSP_DISPLAY flag.

    **Note   **The display drivers are located in the public drivers tree under %_WINCEROOT%\Public\Common\Oak\Drivers\Display. Display drivers are listed in Common.reg and Common.bib files.

  5. Modify platform Sysgens to optimize the build.

    Platform subdirectory (.dirs), registry editor (.reg), and binary image builder (.bib) files can now be filtered based on CE_MODULES variables. This means that unless an operating system (OS) feature is chosen that requires a platform device driver, for example, USB, that driver should not be built and should not be included in a .bib or .reg file. Adding conditionals to the .dirs, .reg, and .bib files does this. See the shipping platform files for more information.

See Also

Build Environment Changes | Migrating a BSP | Updating the Kernel, Debugger, and Profiler | Board Support Package Tools

Last updated on Wednesday, April 13, 2005

© 2005 Microsoft Corporation. All rights reserved.