KITL Transport (Windows CE 5.0)
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.
Platform Manager uses the KITL transport to connect to the target device over the same channel that is used by the kernel debugger. KITL is an abstraction layer that makes the physical transport transparent to the tools.
By using KITL, you can define your own services to communicate between applications running on the development workstation and applications running the target device. For more information about KITL, see Kernel Independent Transport Layer.
To make a Platform Manager connection to a target device with the KITL transport, you must first configure the connection to the target device by using Platform Manager. For more information, see Configuring the Connection to a Target Device Using Platform Manager.
When you configure the KITL transport, you must choose a named connection. For information about creating a named connection, see Creating a Named Connection. You must also choose whether to turn on the keep-alive thread for the KITL transport. The keep-alive thread is a thread that Platform Manager uses to continuously send packets back and forth between the development workstation and target device to verify that the connection is active. The Check connection status check box controls the keep-alive thread.
You should turn off the keep-alive thread if the target device does not enable interrupts. For example, do not use the keep-alive thread with the following types of target devices:
- Any target device with polling-based KITL where interrupts are not enabled, such as the discontinued Intel SA1110/SA1111 (Assabet) development kit. With the Assabet hardware, even if you initialize the hardware with the Ethernet kernel transport, the connection is polling-based, which means both the KITLSend and KITLRecv functions block execution until data is sent or received. For more information about polling-based KITL, see Interrupt and Polled Transport.
- Any target device connected to the development workstation with the serial kernel transport. Over the serial connection, the KITLSend and KITLRecv functions block execution until data is sent or received. For information about establishing application connectivity over the serial kernel transport, see Connecting a Remote Tool Over the Serial Kernel Transport.
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.
See Also
Send Feedback on this topic to the authors