Kernel Independent Transport Layer (Windows CE 5.0)
The Kernel Independent Transport Layer (KITL) is designed to provide an easy way for you to support any debugging service. KITL separates the protocol of the communication service from the layer that communicates directly with the communication hardware. This reduces your involvement in creating a hardware transport layer that understands how to pass data to the device's communication hardware.
The hardware transport layer is then layered under KITL to keep KITL from needing to understand different types of communication hardware. For example, you could create both desktop and Windows CE device-side transport mechanisms.
On the desktop, the transport is a separate DLL that exports certain API functions that KITL relies on and is also registered in the system so KITL knows that it is a functional transport.
On the device, the transport is built into the OAL and therefore the kernel.
On the CE device, KITL relies on the transport to support a set of API level calls that are needed to support the debug services.
Note KITL over Ethernet or IP4 does not support the IP Security (IPSec) protocol. When a debugging network card is shared with a device such as Vmini, the IPSec connection with the development workstation hangs the KITL connection.
For more information on KITL, see the following topics:
- Adding KITL Initialization Code
- KITL Transport Communications
- Active and Passive KITL
- Interrupt and Polled Transport
- KITL Transport
For information about the KITL APIs you can use, see the following topics:
See Also
OEM Adaptation Layer | Ethernet Debugging Services | How to Use Platform Builder to Connect to Multiple Target Devices | Debugging and Testing
Send Feedback on this topic to the authors