Migrating from EDBG to KITL
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\E_to_k.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 | EDBG |
|---|---|
| KITLOutputDebugString | EdbgOutputDebugString |
| OEMKitlGetSecs | OEMEthGetSecs |
| KITLDebugZone | EdbgDebugZone |
| pKITLRegisterDfltClient | pEdbgRegisterDfltClient |
| pKITLSend | pEdbgSend |
| pKITLRecv | pEdbgRecv |
| pKITLInitializeInterrupt | pEdbgInitializeInterrupt |
| KITLRegisterDfltClient | EdbgRegisterDfltClient |
| KITLRegisterClient | EdbgRegisterClient |
| KITLDeRegisterClient | EdbgDeregisterClient |
| KITLSend | EdbgSend |
| KITLRecv | EdbgRecv |
| KITLSetDebug | EdbgSetDebug |
See Also
Kernel Independent Transport Layer | KITL Transport | Enabling KITL
Last updated on Wednesday, April 13, 2005
© 2005 Microsoft Corporation. All rights reserved.