KITL Transport
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 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 transport operates over the same channel that is used by the kernel debugger.
By using KITL, you can define your own services to communicate between the development workstation and the target device.
To establish a connection to a target device that uses KITL transport
From the Target menu, select Remote Tools, and then select any remote tool.
If the Select a Windows CE Device dialog box appears, click Cancel.
From the Connection menu of the remote tool window, click Configure Windows CE Platform Manager.
From the Windows CE Platform Manager Configuration dialog box, expand the node for the devices that you want to configure.
Select the entry for your device, and then click Properties.
From the Device Properties dialog box in the Transport box, select KITL Transport for Windows CE, and then click Configure.
From the Configure Device Connection dialog box, select the Named connection that represents your target device.
To have Platform Manager continuously verify that the connection is active, check Check connection status check box to enable a keep-alive thread.
You should turn off the keep-alive thread if the target device does not enable interrupts.
Customize time-out and interval settings for the transport, and then click OK.
In the Startup Server box, select a startup server.
Choose OK.
After configuring the connection to the target device, connect to the target device. For more information, see Connecting to a Target Device with a Remote Tool.