eXDI Driver Development (Windows Embedded CE 6.0)
1/5/2010
To enable eXDI hardware-assisted debugging with a probe, you must provide an eXDI service that users can install on a development workstation that also has Platform Builder installed.
The probe driver manages communication between the probe and all clients, including OSAccess and Platform Builder. The same driver can sometimes support multiple CPUs, even those from different CPU families at different runs.
The eXDI service can work solely with the debug support available on the hardware. For this reason, the hardware debugger can work even if the OS is not fully functional, or even if there is no OS on the target device. However, once an OS is running on the target device, the debugger can use the OS Access component to acquire Os-related information.
In This Section
- eXDI Driver Requirements
Provides an overview of the required elements of an eXDI service.
- Migrating from eXDI1
Describes how to use the legacy eXDI1 interfaces with an eXDI service.
- Using the eXDI2 Helpers
Provides key information about implementing the eXDI helper components.
- eXDI Driver Registration
Describes how to register the driver.
- eXDI Error Handling
Describes the standard error handling mechanisms for eXDI.
Related Sections
- Hardware-assisted Debugging
Provides descriptions of the benefits of hardware-assisted debugging, and describes how to use it.
- System Debugging
Describes the functionality of the Platform Builder kernel debugger.