CeLog Data Collection Overview (Windows Embedded CE 6.0)
1/5/2010
CeLog tools not only allow you to control what data are collected, but also to control how that data is collected and where it is stored. CeLog can collect events in a log file, or transport them in real time to Kernel Tracker.
For information about starting CeLog Event Tracking, see Enabling CeLog Event Tracking in a Run-Time Image.
CeLog also allows you to log events in a variety of device configurations, such as with or without a Kernel Independent Transport Layer (KITL) connection to a development workstation. A KITL connection makes it possible to view the logged events as they occur, but a KITL connection is not required to collect event data in a log file.
CeLog event types are arranged into related groups called zones. By enabling and disabling the CeLog zones, you can control the event types that CeLog collects. For example, the zone CELZONE_THREAD contains all event types related to threads. When you enable CELZONE_THREAD, CeLog collects all thread events as they occur. For a complete list of pre-defined zones, see CeLog Zones.
For more information about the ways you can control the CeLog zone settings, see Filtering CeLog Events.
Once you have chosen the data you want to collect, you must choose the way you want the data to be collected. You can feed data dynamically to Remote Kernel Tracker, save the data to a file on the desktop workstation, or save the data on a target device. Even if you decide to use the data in real time from Remote Kernel Tracker, you can have Remote Kernel Tracker save the data in a file.
Although you do not need to build your run-time image in a specific way in order to collect CeLog data, some of the data types that CeLog collects are only available on profiling images. A profiling image is an image based on a special build of the Windows Embedded CE kernel that includes the kernel profiler and additional CeLog instrumentation.
Including the additional events of a profiling build can have a negative impact on performance. To avoid this performance impact, a non-profiling kernel does not log the events that have the largest effect on performance. For example, only the profiling build logs the interrupt events specified by the event identifier CELID_INTERRUPTS. Hence, to collect interrupt data with CeLog, you need to run a run-time image that includes the profiling build of the kernel. For a complete list of pre-defined CeLog events, see CeLog Event Identifiers.
See Also
Concepts
CeLog Tool Overview
CeLog Data Viewing