Adding KITL Initialization Code (Windows CE 5.0)
Kernel independent transport layer (KITL) support enables a debug communications channel with the development workstation through Platform Builder, and is essential for enabling kernel debugger support.
If the KITL connection occurs over an Ethernet connection, the Ethernet debug (EDBG) library used in the boot loader development process can be used. The EDBG library will be referenced and linked into the kernel executable. For more information about KITL, see Kernel Independent Transport Layer.
The following list shows the suggested tasks when adding KITL initialization code to the OEMInit function.
To add KITL initialization code
Initialize any PCI bridges and devices, and then enumerate, assign resources, and enable these.
Note This should only be done for the KITL network interface card (NIC) and for any bridges required by the KITL NIC.
Perform any other bus initialization required for the CPU in order to recognize the NIC.
Initialize KITL by calling the KitlInit function. You can copy most of the code by using Halkitl.c from another hardware platform. KitlInit must be called before any debug services can be started. For more information about KitlInit and enabling KITL, see Enabling KITL.
Implement the OEMKitlInit function, which searches for either KITL NIC, KITL serial, or parallel connections. For more information about implementing OEMKitlInit, see Implementing the OEMKitlInit Function.
OEMKitlInit performs the search by calling the OEMEthInit function, which in turn performs the same tasks as the OEMPreDownload function in the boot loader.
For more information about the tasks performed by OEMPreDownload, see Implementing the OEMPreDownload Function.
After implementing the OEMKitlInit function, include Kitl.lib and Kitleth.lib in your Platform\<Hardware Platform Name>\Src\Kernel\Kernkitl sources file.
After performing the above tasks, you can enable KITL polling.
See Also
How to Develop an OEM Adaptation Layer
Send Feedback on this topic to the authors