Boot Loader Migration (Windows CE 5.0)
A boot loader is generally used to place the operating system (OS) image into memory and then jump to the OS startup routine. In most cases, a boot loader from Microsoft® Windows® CE 3.0 and later will function correctly with no changes in Windows CE 5.0 to the existing boot loader code. For more information, see Developing a Boot Loader. However, to ensure that your boot loader runs correctly in Windows CE 5.0, consider the following recommendations:
Use the BLCOMMON infrastructure.
The boot loader common library, BLCOMMON, provides an infrastructure for all boot loaders. To minimize migration efforts, use the BLCOMMON infrastructure while developing a boot loader for your BSP. For information about the boot loader common interface, see BLCOMMON Code Library. For an example on how to use the BLCOMMON insfrastructure when developing a boot loader, see How to Develop a Boot Loader.
Update the binary image builder (.bib) files.
Verify that the existing boot loader .bib file is compatible with the Windows CE 5.0 BSP Config.bib file. For more information, see Binary Image Builder File.
Remove PCI Local Bus Specification (PCI) code.
If you are using the PCI bus driver, initialize only your PCI Kernel Independent Transport Layer (KITL) device, for example, your network interface card (NIC), and any intermediate PCI bridges. Leave all other PCI configuration to the PCI bus driver.
Enable virtual network miniport (VMINI).
See the Readme.txt file in the %_WINCEROOT%\Public\Common\Oak\Drivers\Ethdbg\Vmini directory for information.
Remove code to clear memory.
You do not have to implement code to force a clean OS boot in your boot loader. The KITL library provides routines to perform this operation.
See Also
BSP Migration | OAL Migration | Migrating a Board Support Package | How to Develop a Boot Loader | Debugging and Testing
Send Feedback on this topic to the authors