Tutorial: Building a Run-Time Image for a CEPC (Windows CE 5.0)
This guide helps you become familiar with Platform Builder and the new functionality of Windows CE. It provides a step-by-step tutorial for building and debugging a custom run-time image. The tutorial also shows you how to run the OS on a CEPC.
In this tutorial you build a run-time image for an Enterprise Web Pad, add a Hello World application to the run-time image, and then boot the run-time image on a CEPC.
This tutorial makes the following assumptions:
- You installed Platform Builder and Windows CE as described in the installation instructions
- You selected x86 as one of the CPUs to install on a CEPC that meets the following minimum system requirements.
- 64 MB RAM
Run-time images based on Debug configurations require at least 64 MB of RAM to run.
Run-time images based on Release configurations require at least 32 MB of RAM.
- A mouse
- An Ethernet card
Note Microsoft recommends that the CEPC Ethernet card be a NE2000 compatible network adapter. For information on additional configuration if the CEPC Ethernet card has a DMA-capable Ethernet controller, see article Q317432 at this Microsoft Web site.
- 64 MB RAM
- You are familiar with the terms defined in Terminology.
In this tutorial, which takes approximately 90 minutes to complete, you complete the following steps:
- Tutorial Step 1: Creating a Custom OS Design for a CEPC
- Tutorial Step 2: Building the Custom Run-Time Image for the CEPC
- Tutorial Step 3: Creating a Boot Floppy Disk for the CEPC
- Tutorial Step 4: Setting Up a Connection to the CEPC and Downloading the Run-Time Image
- Tutorial Step 5: Debugging the OS on the CEPC Using the Kernel Debugger
- Tutorial Step 6: Localizing the Run-Time Image for the CEPC
- Tutorial Step 7: Creating and Building an Application for the CEPC
- Tutorial Step 8: Running the Application on the CEPC
- Tutorial Step 9: Creating an SDK
For troubleshooting purposes, use a null modem cable to connect the COM1 port of the target CEPC to your development workstation and keep a Microsoft HyperTerminal window open and connected at 38400 baud and 8-N-1.
This allows you to see the debug information sent during boot, which is useful for troubleshooting. For more information, see Configuring HyperTerminal for BSPs.
Send Feedback on this topic to the authors