Configuring DMA Connectivity Settings for the Device Emulator (Windows Embedded CE 6.0)


This procedure explains how to configure DMA connectivity for the Device Emulator.

This procedure assumes that you have built a Device Emulator run-time image. For more information, see Creating a Device Emulator Image Using the OS Design Wizard.

When you configure connectivity settings for the Device Emulator, you must also configure the emulator properties. For more information, see Configuring Property Settings for the Device Emulator.

  1. From the Target menu, select Connectivity Options.

    This opens the Target Device Connectivity Options Dialog Boxdialog.

  2. Choose Kernel Service Map.

  3. In the Target Device field, select a target device.

    By default, Windows Embedded CE displays CE Device in the Target Device box. CE Device refers not to the currently connected target device, but to the BSP that was most recently booted from any instance of Platform Builder.

    To create and add a uniquely named connection to a target device, see Creating a Named Connection.

  4. In the Download box, select Device Emulator (DMA).

  5. On the Target Device Connectivity Options page, in the Transport box, select Device Emulator (DMA).

  6. In the Debugger box, select the debugger service you want to use.

    For the Platform Builder kernel debugger, select KdStub.

    - or -

    For hardware-assisted debugging, select the name of the eXDI driver installed by the hardware-assisted debugger you want to use.

  7. Choose Core Service Settings.

  8. In Download Image, select the download mode you prefer.

    • Only if image changed
    • Only on initial download
    • Never (jump to image only)

    For more information about the Download Image options, see Target Device Connectivity Options: Core Service Settings .

  9. In KITL Settings, select any of the following settings you want:

    • Enable KITL
    • Enable access to desktop files
    • Clear memory on soft reset
In the Device Emulator, Clear memory on soft reset behaves like a hard reset. That is, changes that were made to the registry or object store will not persist across the reset.

For more information about KITL Settings options, see Target Device Connectivity Options: Core Service Settings.

Community Additions