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

1/6/2010

Windows Embedded CE enables you to create multiple execute-in-place (XIP) regions in a single run-time image. XIP regions are areas in which an application can run code directly from ROM, rather than having to load it from 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 accesss that region when it pages its parts at run time.

Hardware and Software Requirements

This document makes the following assumptions:

You can track your progress in the following table.

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 Regions

See Also

Concepts

Multiple XIP Support
Multiple XIP Regions
Processes

Other Resources

RAM, ROM, and Mass Storage Comparison