PRB: Target Does Not Boot After Download of Debug Version of Windows CE Operating System

• Microsoft Windows CE Platform Builder, version 2.11

SYMPTOMS

The target does not start after downloading the debug version of Nk.bin, using Ethernet or serial debug ports.

CAUSE

When you want to use the debug version of Nk.bin on a target, such as CEPC, you must run the debugger (Windbg) and put it in the Go state. You can run the debugger over either a serial port or an Ethernet connection: In the case of a serial port, the -g flag on Windbg.exe is set at invocation time, or Go, to be invoked manually at any time. The target then starts after this step.

In the case of an Ethernet port, just having the IDE up and the Shell.exe or Nk.exe files opened as the project isn't enough to start the target device. Windbg has to register with eshell before starting occurs. However, there is a limited window for it to register because eshell locks during initialization by the target and does not accept any more services like Windbg. So, Windbg has to have the -g flag in its invocation line before it is started, or you can invoke the Go command after Windbg is active. The latter must be done before download is complete and initialization starts. Otherwise, it Windbg gets locked out of eshell registration and the target does not start.

RESOLUTION

To work around this problem for serial port debugging, you can put the -g flag in the Windbg invocation line or use the Go command afterwards.

To work around the problem for Ethernet port debugging, you can use the Properties tab in the Windbg icon to set the -g flag at the end of the invocation line. Alternatively, after the invocation of Windbg but before downloading of image is completed, use a Go command on Windbg.

Additional query words:

Keywords : kbWinCE211 kbDSupport
Version : N\A:2.11
Platform : N\A
Issue type : kbprb