In Windows Embedded CE 6.0, the kernel and OEM code are divided into the following three components:
1.Oal.exe
- This contains the startup code and the OEM adaptation layer (OAL) implementation.
- This component was previously named Kern.exe.
2.Kernel.dll
- This contains the OAL-independent kernel implementation.
3.Kitl.dll
- This contains the platform-specific KITL support.
Microsoft recommends that OEMs move KITL support out of the OAL and into Kitl.dll. All Microsoft sample board support packages (BSPs) will follow this model.
The goals for this design are to:
- Minimize OAL changes
- Clearly define the functions that the OAL can and cannot use
- Provide version information between components to provide forward compatibility
This model provides the following advantages:
- Allows Microsoft to update the kernel for retail devices without going through the OEM because the kernel is no longer dependent on the OAL.
- Simplifies the debugging process with an instrumented kernel. You only need to include a new instrumented Kernel.dll into the release directory and then re-make the run-time image.
- Provides OEMs with a binary-only version of the platform, which they can give to their customers.
- Makes loadable KITL possible. (I don`t understand)
- Enables all communication between the OEM code and the kernel to take place through well-defined interfaces.
BSP Migration Scenarios
- Scenario 1: Separate kernel, OAL, and KITL
- http://msdn2.microsoft.com/en-us/library/aa908403.aspx
- Scenario 2: Separate kernel and OAL(less effor)
- http://msdn2.microsoft.com/en-us/library/aa915383.aspx
Common.bib and the Make Run-Time Image (MakeImg) process require the following names:
- Oal.exe, use this to rename Kern.exe
- OalKitl.exe, use this to rename KernKitl.exe
沒有留言:
張貼留言