KITL
The kernel independent transport layer (KITL) provides a transport layer for the board under development to communicate with the Platform Builder on the development system. It is used by many Platform Builder tools such as kernel debugger, remote tools, debug message service, Target Control, remote file system (RELFSD), and so on. The Platform Builder debugger requires KITL to communicate with a target system. The target system needs to be configured and built for KITL. KITL can use a number of transports:
- Ethernet (most common)
- USB RNDIS
- Serial
- Custom
The two main functions for KITL are shown in Table 35-2.
TABLE 35-2: The Main KITL Functions
| FUNCTION | DESCRIPTION |
| OEMKitlInit | Fills the KITLTRANSPORT structure with appropriate function pointers. |
| OEMKitlIoctl | Handles platform-specific KITL I/O control calls. |
KITL is a separate component in the BSP from OAL. It can be removed from an image, especially one to be shipped. Common KITL code is located in:
$(_WINCEROOT)\platform\common\src\common\Kitl
When KITL and Kernel Debug are enabled, you can step through native code applications and drivers if they are built in Debug mode (but not through managed code). If the Release Directory File System (RELFSD) Catalog component (located under Storage Manager) is included in the operating system, applications and drivers not included in the image can be modified and rebuilt without stopping the operating system. RELFSD refers to the Release Directory, so any application and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access