¦ USB Downloads the run-time image over a Universal Serial Bus (USB) connection. There are no settings to configure.
¦ Image Update Updates the image in the device's flash memory. There are no settings to configure.
¦ None Select this option if you do not want to download or update the run-time image.
Transport Layer
After transferring the run-time image to the remote device, you can attach to the device if you enabled Kernel Independent Transport Layer (KITL) in the OS design. In general, the selected kernel transport service should match the download service that you selected in the Download list box. The Core Connectivity infrastructure supports the following transport layer options:
¦ Ethernet Communicates with the target device over an Ethernet connection. The connection uses the same settings as the download service.
¦ Serial Communicates with the target device over an RS232 connection. The connection uses the same settings as the download service.
¦ Device Emulator (DMA) Communicates with a device emulator through DMA.
¦ USB Communicates with the target device over a USB connection.
¦ None Disables communication with the target device.
Debugger Options
If you enabled support for one or more debuggers in the OS design, the debugger names will appear as options in the Debugger list box. By default, the following debugger options are available:
¦ Sample Device Emulator eXDI2 Driver This is a sample Extensible Resource Identifier (XRI) Data Interchange (XDI) driver included in Windows Embedded CE 6.0 R2. XDI is a standard hardware-debugging interface.
¦ KdStub This is the Kernel Debugger. KdStub stands for kernel debugger stub, which instructs Platform Builder and Visual Studio to use the software debugger.
¦ CE Dump File Reader If you added the Error Report Generator catalog item to your OS design, you can use this option for postmortem debugging.
¦ None Select this option if you do not want to use a debugger.
Attaching to a Device
Having configured the device connection, you are ready to transfer the run-time image to the target device or device emulator by using the Core Connectivity infrastructure. This is accomplished in Visual Studio 2005 by using the Attach Device command that is available on the Target menu. Even if you do not plan to use KITL or the Core Connectivity infrastructure for debugging, you must attach to the device so that Platform Builder can download the run-time image.
Following the image download, the start process commences, KITL becomes active if enabled on the target device, and you can use the Kernel Debugger to follow the start process, and debug operating system components and application processes. By using KITL, you can also exploit remote tools available in Visual Studio with Platform Builder on the Target menu, such as File Viewer to interact with the device's file system, Registry Editor to access the device's registry settings, Performance Monitor to analyze resource utilization and response times, and Kernel Tracker and other remote tools to view detailed information on the running system. You can find more information about system debugging in Chapter 4, 'Debugging and Testing the System.'
Lesson Summary
Windows Embedded CE supports run-time image deployment over a variety of device connections to accommodate hardware platforms with varying requirements and capabilities, including Ethernet connections, serial connections, DMA, and USB connections. For example, DMA is the right choice if you want to deploy CE 6.0 R2 on a Device Emulator. You only need to configure the communication parameters and you are ready to deploy Windows Embedded CE by clicking the Attach Device command on the Target menu in Visual Studio 2005 with Platform Builder.
To pass the certification exam, you must be familiar with the varioust ways to deploy a Windows Embedded CE run-time image. In particular, make sure you know how to deploy a run-time image for a Device Emulator.
Lab 2: Building and Deploying a Run-Time Image
In this lab, you build and deploy an OS design based on the Device Emulator BSP, analyze the build information in the Visual Studio Output window to identify the start of the various build phases, and then configure a connection to a target device in order to download the run-time image. To demonstrate how to customize a target device, you modify the Device Emulator configuration to support a larger screen resolution and to enable network communication. In a final step, you download the run-time image and attach to the target device with the Kernel Debugger, so you can examine the Windows Embedded CE start process in detail. To create the initial OS design in Visual Studio, follow the procedures outlined in Lab 1, 'Creating, Configuring, and Building an OS Design.'
To help you successfully master the procedures presented in this Lab, see the document 'Detailed Step- by-Step Instructions for Lab 2' in the companion material for this book.
Build a Run-Time Image for an OS Design
1. After completing Lab 1, select Sysgen under Advanced Build Commands on the Build menu in Visual Studio, as illustrated in Figure 2-8. Alternatively, you can select Build Solution under the Build menu, which will
