This document contains important information about Microsoft Windows CE 5.0 Mainstone BSP Update with the latest fixes and improvements.
System Requirements for Windows CE 5.0 Mainstone BSP Update
Known Issues for Windows CE 5.0 Mainstone BSP Update
Installing Windows CE 5.0 Mainstone BSP Update
Installation Issues for Windows CE 5.0 Mainstone BSP Update
Change List for Windows CE 5.0 Mainstone BSP Update
The Mainstone III BSP is based on the Mainstone II BSP with the addition of all hardware updates for the platform and C5 stepping support. The Mainstone BSP Update release is tested on Windows CE 5.0. However, you can install and build this release on any Windows CE 5.0-based installation.
The system requirements for Windows CE Platform Builder are as follows:
The system requirements for the Mainstone BSP Update are as follows:
The package containing Windows CE 5.0 Mainstone BSP Update will be placed in the following two directories during installation:
Installing the correct BSP package
Support for ARMV4I must be specified when you install Platform Builder
You must install the correct package for Windows CE 5.0 Mainstone BSP Update. The package for Windows Mobile Version 5.0 Mainstone BSP Update will not install correctly.
You must include support for ARMV4I microprocessors when you install Platform Builder. If you already installed Platform Builder and did not include this support, reinstall Platform Builder and include ARMV4I microprocessor support.
Note The ARMV4I is an ARMV4 build that supports interworking, which enables the ARMV4I to handle 32-bit code to and from 16-bit code jumps.
The ARMV4 kernel image is the same as the ARMV4I kernel image, except it does not support interworking.
After you select your choice of microprocessor support, all necessary tools and code binaries needed to support the processor architecture are installed.
Secure Digital (SD) bus driver can fail on Mainstone III
The SD driver may fail if the user repeatedly inserts and ejects a multimedia card (MMC) for an extended period of time, and if card ejections occur while it is in use. If a driver error occurs, the device must be rebooted to correct the problem.
When the CETK Notification Test is run, test case 17 and 18 might fail due to a bug in the notification subsystem. When CeRunAppAtTime is called with a non-null terminated string as its first parameter, the notification subsystem does not correctly handle the first parameter. Notification tests 10 and 11 call CeRunAppAtTime with a non-null terminated string, as a result of which test cases 17 and 18 may fail.
The Initial Program Loader (IPL) is programmed by default to always send its debug serial output to BTUART. If eboot changes this port to FFUART, the change will not propagate to the IPL. However, eboot will correctly use FFUART.
| Feature | Power Managed | Comments |
|---|---|---|
| OAL | Yes | Deep Sleep, OemIdle, Variable tick implemented |
| Display | Yes | D0/D4 support implemented |
| USB Host | Yes | Power callback supported |
| Keypad | Yes | Power callback supported |
| SD HC | Yes | Power callback supported |
| Serial | Yes | common serial pdd supports power callbacks |
| USB client | Yes | Power callback supported |
| Wavedev2 | Yes | Power callback supported |
| PCCard | No | |
| Touch | Yes | Power callback supported |
| Camera | Yes | D0/D3 support implemented |
| Backlight | Yes | D0/D4 support implemented |
© 2005 Microsoft Corporation.
All rights reserved.
© 2005 Microsoft Corporation. All rights reserved.