Compartilhar via


How to Create a Run-Time Image with Multiple XIP Regions (Windows CE 5.0)

Send Feedback

Windows CE allows you to create multiple execute in place (XIP) regions in one single run-time image. XIP regions are areas where an application can execute code directly from read-only memory (ROM) rather than having to load it from random access memory (RAM).

With a multi-region run-time image, you have finer control over the run-time image layout, you can control region updates, and you can decide on a per-region basis how the OS will access that region when it pages its parts at run time.

Hardware and Software Requirements

This document makes the following assumptions:

To track your progress in the following table, select the check box next to each step.

  Step Topic
1. Create a base OS design for your run-time image with multiple XIP regions. Creating an OS Design for an Image with Multiple XIP Regions
2. Modify the Config.bib and Platform.bib binary image builder files to add settings and files that are required to build a run-time image with multiple XIP regions. Modifying the Binary Image Builder Files
3. Build the run-time image and open a workspace with multiple XIP regions from which you can download your run-time image to the CEPC. Building the Run-Time Image and Opening a Workspace with Multiple XIP Regions
4. Configure an Ethernet connection for downloading your run-time image to the CEPC.

In the Target Connectivity Options dialog box, under KITL Settings, clear the Enable access to desktop files checkbox.

Configuring an Ethernet Remote Connection
5. Download your run-time image to the CEPC. Downloading a Run-Time Image
6. Test your run-time image with multiple XIP regions by verifying that all of the modules that you have placed in a separate region load correctly. Testing the Run-Time Image with Multiple XIP mRegions

See Also

Multiple XIP Support | Multiple XIP Regions | RAM, ROM, and Mass Storage Comparison | Processes

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.