How to Debug a Run-Time Image on a CEPC (Windows CE 5.0)
When you run a Windows CE operating system (OS) on a CEPC, you can use the kernel debugger to debug the run-time image, if you include support for the debugger in the OS design. While creating an OS design, consider the ways in which you want to debug the run-time image. Prior to building the run-time image, you must complete certain preparatory steps to achieve the level of support that you want for debugging.
To track your progress in the following table, select the check box next to each step.
| Step | Topic | |
|---|---|---|
| 1. Open an existing OS design that uses the CEPC board support package (BSP), or create a new OS design and select the CEPC BSP. | Creating an OS Design | |
| 2. Familiarize yourself with the levels of debugging support in the configurations that Platform Builder provides by default with an OS design.
Choose a configuration that best fits the level of debugger support that you want for your run-time image. |
Levels of Debugging Support | |
| 3. If you chose a release configuration, add support for the kernel debugger to your configuration. | Using the Kernel Debugger with a Run-Time Image Built From a Release Configuration | |
| 4. To maximize debugging functionality, enable support for KITL in your OS design.
For more information about KITL, see Kernel Independent Transport Layer |
Supporting KITL in an OS Design | |
| 5. If you expect the size of your run-time image to exceed 32 megabytes (MB), enable support for a large run-time image in the settings for the configuration.
The status bar in the Platform Builder integrated development environment (IDE) shows the estimated size of the run-time image.
|
Enabling a Run-Time Image Size Larger Than 32 MB | |
| 6. Build your run-time image. | Building a Run-Time Image | |
| 7. If the CEPC uses an ISA-based Ethernet card, specify values for NET_IRQ and NET_IOBASE in the Autoexec.bat file on the boot floppy disk for the CEPC. | Editing the Autoexec.bat File for an x86 SDB | |
| 8. Configure the Microsoft® HyperTerminal accessory application to display the serial debug output from the CEPC. | Configuring HyperTerminal for BSPs | |
| 9. Configure a remote connection to the CEPC.
Choose the appropriate topic based on whether you have an Ethernet or a serial port connection between the development workstation and the CEPC. |
Configuring an Ethernet Remote Connection | |
| 10. Download the run-time image through the Ethernet or serial connection and boot the run-time image on the CEPC.
After the run-time image boots on the CEPC, the kernel debugger starts automatically, because you enabled kernel debugging in the settings for the configuration. |
Downloading a Run-Time Image | |
| 11. View debug information from the CEPC in the IDE.
When the debugger is available, a Debug menu and a Debug window appear in the IDE. When the debugger is running, the text [run] appears in the caption for the IDE. You can manually stop and start the debugger during the debugging process. |
Stopping Kernel Debugging | |
| 12. Configure Platform Manager to connect to the CEPC. | Configuring the Connection to a Target Device Using Platform Manager | |
| 13. Connect a remote tool to the CEPC.
For information about each remote tool that Microsoft provides, see Remote Tools. When the remote tool succeeds in connecting to a CEPC, the Connecting to device dialog box disappears, and information from the CEPC appears in the window for the remote tool. The type of information displayed differs for each remote tool. |
Connecting to a Target Device with a Remote Tool |
See Also
How-to Topics | Tools for Debugging and Testing | How to Connect to a Target Device for Debugging | How to Set up a CEPC
Send Feedback on this topic to the authors