Nicolas Besson - Microsoft Windows Embedded CE 6.0 Exam Preparation Kit

► Perform Mouse Driver Tests by Using the CETK<\/p> <\/div>

1. Open the Windows CE Test Kit application from the Start menu on your development computer (open the Windows Embedded CE 6.0 menu and click Windows Embedded CE Test Kit).<\/p>

2. In the Windows Embedded CE Test Kit window, open the Connection menu and click Start Client to establish a connection to the target device.<\/p>

3. Click Connect and select the device in the Connection Manager window.<\/p>

4. Verify that the workstation server application connects successfully to the device, deploys the required CETK binaries, detects available device drivers, and displays a list of all components in a hierarchical tree, as shown in Figure 4-16.<\/p>

5. Right-click the Windows CE Test Catalog node and click Deselect All Tests.<\/p>

6. Open each node in the list and select the Mouse Test check box.<\/p>

7. Open the Test menu and then clock on Start/Stop Test to perform a mouse test.<\/p>

8. On the target device perform the required mouse actions.<\/p>

9. Complete the test and then can access the test report by right-clicking the test entry and selecting View Results.<\/p>

10. Examine the results in the CETK parser and notice successful, skipped, and failed test procedures.<\/p>

Chapter Review<\/p> <\/div>

Platform Builder for Windows Embedded CE ships with a comprehensive set of debugging and testing tools to diagnose and eliminate root causes of errors, and validate the system in its final configuration prior to its release to production. The debugging tools integrate with Visual Studio and communicate over KITL connections with the target device. Alternatively, you can create a memory dump and use the CE Dump File Reader to debug the system in offline mode, which is particularly useful for postmortem debugging. The debugging environment is also extensible by means of eXDI drivers to perform hardware-assisted debugging beyond the capabilities of the standard Kernel Debugger.<\/p>

The Kernel Debugger is a hybrid debugger for kernel components and applications. Debugging starts automatically if you attach to a target device with KdStub and KITL enabled. You can use the Target Control window to start applications for debugging and perform advanced system tests based on CEDebugX commands. However, it is important to keep in mind that you cannot set breakpoints in interrupt handlers or OAL modules because at these levels, the kernel operates in single-thread mode and stops communicating with the development workstation if code execution halts. To debug interrupt handlers, use a hardware debugger or debug messages. The debug messages feature supports debug zones to control the information output without having the rebuild the run-time image. You can also use debug messages to debug the C-code portion of a boot loader, yet for the assembly code portion you must use a hardware debugger or an LED panel.<\/p>

KITL is also a requirement if you want to centralize system testing based on the CETK Test application, although it is also possible to run CETK tests in standalone mode. If you are developing a custom BSP for a target device, you can use the CETK to perform automated or semi-automated component tests based on custom Tux DLLs. Platform Builder includes a WCE TUX DLL template to create a skeleton Tux module that you can extend to meet your specific testing needs. You can integrate the custom Tux DLL in the CETK test application and run tests individually or as part of a larger test suite. Because all CETK tests use the same logging engine and log file format, you can use the same parser tool to analyze the results of default and user-defined tests.<\/p>