How to Migrate a Board Support Package to Windows CE .NET 4.2
If you are not creating a new board support package (BSP) for Windows CE .NET 4.2, and you want your BSP to be fully compatible with the features in Windows CE .NET 4.2, you must migrate or update your BSP from Windows CE .NET 4.0 or 4.1. In order to build your BSP correctly during the migration process, you must make specific changes to your BSP sources.
Note You do not need to make any changes or updates to the boot loader when you migrate your BSP from Windows CE .NET 4.0 or 4.1 to Windows CE .NET 4.2.
If you want to create a BSP for Windows CE .NET 4.2 from the beginning, see How to Create a Board Support Package.
To track your progress in the following table, select the check box next to each step.
|1. Update the OEM adaptation layer (OAL) by implementing the OEMCacheRangeFlush function to resolve references in the kernel.
You can implement the OEMCacheRangeFlush function by linking with the appropriate libraries, or by implementing a version that calls your existing FlushDCache, FlushICache, and ClearTLB functions.
|OEMCacheRangeFlush Function Implementation|
|2. Implement the SPI_GETPLATFORMVERSION IOCTL in the OAL.||Implementation of the SPI_GETPLATFORMVERSION IOCTL|
|3. Enlarge the page sizes for SH3 and SH4 kernels from 1 KB to 4 KB, and then rebuild any application or device driver binary builds with a 1-KB page size.
When you rebuild the binary builds, you enlarge the builds to a 4-KB page size. By performing this procedure, you ensure that the kernels load and run correctly on Windows CE .NET 4.2.
Note In previous versions of Windows CE, the default page size for SHx kernels was 1 KB. If you do not enlarge the page size, any binary builds with a 1-KB page size will not run on the current version of Windows CE.
|4. Update the battery driver and move an existing battery driver out of GWES.||Updating the Battery Driver for Windows CE .NET 4.2|
|5. Update the keyboard driver.
Select the appropriate topic, based on whether or not you want the keyboard driver to conform to the Layout Manager Interface.
For more information about the Layout Manager, see Layout Manager.
|How to Migrate a Keyboard Driver Without Conforming to the Layout Manager Interface|
Last updated on Wednesday, April 13, 2005
© 2005 Microsoft Corporation. All rights reserved.