How to Separate the Kernel and OAL and Link KITL to the OAL
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
When migrating your board support package (BSP) to Windows Embedded CE 6.0, Microsoft strongly recommends that you adopt the Windows Embedded CE 6.0 BSP directory structure and remove the Kernel Independent Transport Layer (KITL) from the OEM adaptation layer (OAL) to encapsulate it in a separate DLL. However, this migration scenario is optional.
This how-to topic provides step-by-step instructions for migrating your BSP to Windows Embedded CE 6.0 without changing your directory structure or moving KITL into a separate DLL.
Hardware and Software Assumptions
- You are migrating your BSP from a previous version of Windows Embedded CE to Windows Embedded CE 6.0.
- Your reference OS is Windows Embedded CE 6.0.
- You have access and familiarity with Platform Builder and the build process. Platform Builder includes with it all the sources and libraries needed to support BSP migration.
- You are separating the kernel and the OAL, and then linking KITL to the OAL.
- You are not adopting the recommended BSP directory structure in Windows Embedded CE 6.0.
Use the following table to track your progress.
| Step | Topic |
|---|---|
1. Create and build Oal.exe and OalKitl.exe. |
|
2. Implement new KITL entry points in OalKitl.exe. |
|
3. Implement profiling support in the OAL. |
|
4. Update the boot loader sources file. |
See Also
Concepts
BSP Migration Guide
BSP Implementation Guide
Windows Embedded CE 6.0 BSP Directory Structure