Partager via

eXDI Driver Requirements (Windows Embedded CE 6.0)

  • Article

1/5/2010

At a minimum, your driver, as an eXDI service, must be able to send instructions and receive data from your probe, and your probe must be able to communicate with the debugging target.

The eXDI service must implement the Core Connectivity Infrastructure for initialization, configuration, and connection. The service must expose any needed settings through service configuration, and save the settings by device in the Core Connectivity datastore.

eXDI provides a collection of helper elements that you can selectively add to your driver if you want to support the related functionality.

A sample driver is included under the installation directory at <Platform Builder installation path>\eXDI\Sampledriver.

Development Guidelines

The following list provides general guidelines to consider when developing an eXDI service.

  • The eXDI driver must allow multiple simultaneous clients.
  • Make sure your driver encapsulates its inner functionality.
  • Establish the driver as a service under ICcService, which provides connectivity support.
  • Provide the following breakpoint functionality:
    • Handle breakpoint instantiation details.
    • Monitor data breakpoints and code breakpoints.
  • Define any non-standard error values your probe driver requires, with associated descriptions.
  • Install and register the service with the Core Connectivity datastore.
    For more information about registering your service, see eXDI Driver Registration.
  • Implement your service as an in-process COM server.

eXDI Driver Elements

An eXDI driver consists of the following programming elements:

  • Driver handler
  • Probe handler
  • Connectivity management
  • eXDI helpers
    Provide additional functionalities that may not be available from a third-party probe or emulator through a reusable set of common code elements**.**
  • Client callback methods
    Provide notifications that allow clients to stay in sync with the target state, and with actions requested by other clients. IeXdi2ClientNotifyRunChg and IeXdi2ClientNotifyMemChg allow your driver to send eXDI information about the status of its target.

See Also

Concepts

Migrating from eXDI1
eXDI Driver Registration

Other Resources

eXDI Driver Development