Debug image and bootloaders

Hi,

We developped a boot loader on a Windows CE 4.2 device that allows us to
boot from a disc on chip or from the ethernet. It works perfectly in CE 4.2
and when we migrated to CE 5.0 I worked ok too. Now we try to migrate to CE
6.0.

The problem is this, I can download an image from Ethernet using our
bootloader but I can't connect to debug it. We enabled KITL and kernel
debugger in the image but it seams that Visual Studio 2005 start sending the
image and stop at some point (but only when we set debugger to kdstub, if we
set it to none the image is downloaded totally and executed correctly). Is
there something else to do to be able to connect with the debugger?

If it can help I receive trhough my KITLOutputDebugStrings the following
message when it stop sending data. According to my research proto 1 is ICMP
message so I suspect Visual Studio stopped listening or sendin messages.

!CheckUDP: Not UDP (proto = 0x00000001)

Any help on this is welcome.

Vinz
Tue Sep 25 12:50:07 CDT 2007

I found something interessting. In the KdStub Settings (in Target Device
Connectivity Options) there is an option that state Prompt on Error and I
think that if I change it my problem will go away, put the problem is that I
can't change it, if I set it to disable and press ok and apply it is put back
to enable.

Is there anyone else that saw this behavior?

"Vinz" wrote:

> Hi,
>
> We developped a boot loader on a Windows CE 4.2 device that allows us to
> boot from a disc on chip or from the ethernet. It works perfectly in CE 4.2
> and when we migrated to CE 5.0 I worked ok too. Now we try to migrate to CE
> 6.0.
>
> The problem is this, I can download an image from Ethernet using our
> bootloader but I can't connect to debug it. We enabled KITL and kernel
> debugger in the image but it seams that Visual Studio 2005 start sending the
> image and stop at some point (but only when we set debugger to kdstub, if we
> set it to none the image is downloaded totally and executed correctly). Is
> there something else to do to be able to connect with the debugger?
>
> If it can help I receive trhough my KITLOutputDebugStrings the following
> message when it stop sending data. According to my research proto 1 is ICMP
> message so I suspect Visual Studio stopped listening or sendin messages.
>
> !CheckUDP: Not UDP (proto = 0x00000001)
>
> Any help on this is welcome.