Debugging and Testing a Thin Client (Windows Embedded CE 6.0)

  • Article

1/5/2010

Generally, debugging a Windows Embedded CE powered thin client device requires that you build a thin client run-time image, download it to the standard development board or to the Windows Embedded CE computer-based hardware platform (CEPC), and then use the tools in Platform Builder for Windows Embedded CE 6.0 to debug the thin client operating system, modules, and any applications.

To use these tools, you must first establish a serial or Ethernet connection from your desktop workstation to the target device. For more information, see Ethernet Download Service.

If you are establishing a connection to a standard development board, your hardware supplier should have already tested and debugged the hardware. Similarly, your board support package (BSP) provider should have already tested and debugged the boot loader, OEM adaptation layer (OAL), and kernel. At this point, you should reserve debugging activities for the elements of your custom thin-client operating system (OS) design. For information about how to use the Remote Tools to debug software running on a remote device, see Remote Tools.

For information about getting started with building and downloading an image, see Getting Started with Developing a Thin Client.

For general information about how to debug, see Strategies for Debugging a Run-Time Image.

In This Section

  • Standard Development Board Design
    Describes a standard development board. This is a hardware development system with which you can develop and test your OS design by using a variety of processors and peripherals.

See Also

Concepts

Hardware-Assisted Debugging Considerations for a Thin Client

Other Resources

Developing a Thin Client