Configuring eXDI Hardware-Assisted Debugging (Windows Embedded CE 6.0)
1/5/2010
Platform Builder enables you to use eXDI hardware-assisted debugging to control the execution of a target device, and to examine and modify the state of the device.
If you install a third-party eXDI driver to add hardware-assisted debug support, Platform Builder activates the user interface elements that allow users to easily switch between different hardware-assisted solutions.
The user interface elements present the option to select hardware-assisted debugging in the Target Device Connectivity Options Dialog Box. This dialog lists the eXDI drivers installed in installation order; that is, the most recently installed driver appears first in the list of available drivers.
Although hardware-assisted debugging is less intrusive and requires no special software on the device to support debugging, hardware-assisted debugging requires access to the image file, nk.bin.
In addition, for a better debugging experience, hardware-assisted debugging requires access to the flat release directory that contains the binaries and compilation symbols that match the image you are debugging.
Note
To use eXDI hardware-assisted debugging with a hardware debug probe instead of KdStub, the Platform Builder kernel debugger, build the run-time image with both of the following environment variable settings:
- IMGNODEBUGGER=1 to remove debugger components from the kernel
- IMGHDSTUB=1 to enable OS awareness
To configure eXDI hardware-assisted debugging
Install the eXDI driver provided by the third-party probe or emulator vendor.
A new driver installation for a different probe overrides a previously installed driver.
From the Target menu, choose Connectivity Options.
In the Target Device Connectivity Options dialog, choose Kernel Service Map.
In the Debugger box, choose the name of the eXDI driver you want to use and choose OK.
The third-party probe vendor or emulator vendor defines the name of the eXDI driver.
These settings are associated with a named connection in the Core Connectivity Infrastructure. If you open a different OS design to use settings that you previously specified, you must choose the named connection that contains your settings, or specify the same settings in a different named connection.
The hardware debugger can communicate over any connection that the third-party driver supports. The driver might require settings in addition to settings required by Platform Builder.
See Also
Tasks
Using the eXDI Hardware-Assisted Debugger