Migrating from EDBG to KITL
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
Platform Manager now uses the Kernel Independent Transport Layer (KITL) transport for communication between the development workstation and the target device over any hardware for which the OEM supplies an appropriate transport.
The KITL Ethernet transport on the device reuses much of the Ethernet debug (EDBG) code. To map to the new KITL names, the header file %_WINCEROOT%\Public\Common\Oak\Inc\Halether.h has been included that maps the KITL functions to the EDBG functions.
The following table shows the functions from the header file and how they map.
KITL to EDBG Function Mapping
| KITL | EDBG |
|---|---|
KITLOutputDebugString |
EdbgOutputDebugString |
OEMKitlGetSecs |
OEMEthGetSecs |
KITLDebugZone |
EdbgDebugZone |
KITLRegisterDfltClient |
EdbgRegisterDfltClient |
KITLRegisterClient |
EdbgRegisterClient |
KITLDeRegisterClient |
EdbgDeregisterClient |
KITLSend |
EdbgSend |
KITLRecv |
EdbgRecv |
KITLSetDebug |
EdbgSetDebug |