Hello,

on WINCE 5.0 I have built a debug image, my Device connectivity is set
for ethernet, Debugger is KdStub,

I can download the image via ethernet but the debugger never switches to
Ethernet once the image loads. all my debug messages come out in my serial
port console and not via my etehrnet to the debug output window ? what am
I missing for the handoff ?

Thanks,

Joe W.

Re: kitl debug question by Valter

Valter
Thu Mar 20 08:20:03 PDT 2008

"Joe Welfeld" <jwelfeldnospam@datastrip.net> wrote in
news:OEI82zpiIHA.1164@TK2MSFTNGP02.phx.gbl:

> Hello,
>
> on WINCE 5.0 I have built a debug image, my Device
> connectivity is set for ethernet, Debugger is KdStub,
>
> I can download the image via ethernet but the debugger never
> switches to Ethernet once the image loads. all my debug
> messages come out in my serial port console and not via my
> etehrnet to the debug output window ? what am I missing for the
> handoff ?

Usually this happens when the device is not able to connect to PB.
This may be due to different reasons.
For example:
- the bootloader does not pass the right information to the
kernel/KITL, preventing it from using the ethernet adapter
- some firewall software or hardware closes or prevents the device-PB
connection.
Usually the beginning of serial output can provide some information
about the problem.

--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)

Re: kitl debug question by Silver

Silver
Thu Mar 20 09:35:38 PDT 2008

or IMGNOKITL is still set.

Re: kitl debug question by jack

jack
Fri Mar 21 03:59:11 PDT 2008

maybe you are using the kern.exe , you should use the kernkitl.exe

"Joe Welfeld" <jwelfeldnospam@datastrip.net> wrote:
> Hello,
>
> on WINCE 5.0 I have built a debug image, my Device connectivity is
> set for ethernet, Debugger is KdStub,
>
> I can download the image via ethernet but the debugger never switches
> to Ethernet once the image loads. all my debug messages come out in my
> serial port console and not via my etehrnet to the debug output window ?
> what am I missing for the handoff ?
>
> Thanks,
>
> Joe W.
>



Re: kitl debug question by Valter

Valter
Fri Mar 21 04:03:24 PDT 2008

"Silver" <moc.liamtoh@gnirrevliseht> wrote in news:OwnP1hqiIHA.4396
@TK2MSFTNGP04.phx.gbl:

> or IMGNOKITL is still set.
>

That's right, but the default configuration of a debug build should
include it.

--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)

Re: kitl debug question by Joe

Joe
Tue Mar 25 06:16:50 PDT 2008

just to follow up here,

I had previously installed QFE 916103 to support my Intel Ethernet card for
debug , but I had to copy the updated files into my BP's common.... Once I
did that it started to work.

Thanks All,

Joe W.


"jack toshi" <zhoumc@hotmail.com> wrote in message
news:u7rNmK0iIHA.4376@TK2MSFTNGP05.phx.gbl...
> maybe you are using the kern.exe , you should use the kernkitl.exe
>
> "Joe Welfeld" <jwelfeldnospam@datastrip.net> wrote:
>> Hello,
>>
>> on WINCE 5.0 I have built a debug image, my Device connectivity is
>> set for ethernet, Debugger is KdStub,
>>
>> I can download the image via ethernet but the debugger never switches
>> to Ethernet once the image loads. all my debug messages come out in my
>> serial port console and not via my etehrnet to the debug output window ?
>> what am I missing for the handoff ?
>>
>> Thanks,
>>
>> Joe W.
>>
>
>