Re: Debugger disconnected

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Most likely scenario (happened to me the same way...)

There are bootme messages coming out of the kernel when kitl initializes.
This causes Platform Builder to attempt to initiate another download, but
the device has already booted and isn't joining the process. So, PB
eventually times out and disconnects without realizing there is already a
kitl connection already happily up and running.

Two solutions
1 - The best solution is to find the offending code sending bootme packets,
and remove it. Why would it potentially be there in the first place? This
is the mechanism that causes the device to show up in the dialog box when
configuring the connection. Normally, the ethernet download process in the
bootloader sends these messages, and that's how you configure PB. If you
have a scenario where the image is being loaded some other way, the
bootloader isn't sending the messages, and it's tempting to put them in the
kernel just to make sure they exist somewhere.

2 - Configure PB to do something other than "Download Always" in the
connection settings. This way, it won't always attempt to download when it
sees the bootme messages, and thus won't time out part way through the debug
cycle.


--
Dean Ramsier - eMVP


"Piet" <pietdesomere@xxxxxxxxx> wrote in message
news:1124283602.635750.107380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> So.
>
> Platform Builder disconnects 45 seconds after OEMInit finishes.
> Debug/retail is same, OS image based on custom device or tiny kernel is
> same, and it doesn't matter if I keep the device in a breakpoint.
> Before disconnection debugging works perfectly, I see nothing out of
> order.
>
> Please shed a little bit of your combined wisdom on this as I have no
> idea what the condition would be for PB to break the connection.
>
> Naturally, I will give whatever extra information would be required,
> but frankly I have no idea where to look at this moment.
>
> Regards,
> Piet
>


.

Relevant Pages

  • Re: platform builder 4.2 debugger cannot connect to target
    ... Kernel Transport to Serial, ... to init KITL for Ethernet, not serial as it's doing now. ... I captured the serial port output during the download and boot up. ... Debugger could not initialize connection. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: problems with large files
    ... > althought my problem was there with 2.6.11.11 kernel as well. ... outgoing firewall slowing the connection? ... Do their internet connections have different upload/download speeds or ... For example A->B uses A's upload speed and B's download ...
    (comp.os.linux.networking)
  • connection problems with kernel 2.6
    ... Whenever I try to download the homepage with e.g. ... and then the connection is closed although ... Also, kernel 2.4.29 works perfectly. ... different computers at different locations. ...
    (comp.os.linux.networking)
  • Re: How does the CE device and dev workstation find each other on
    ... I can't get to the switches ... subnet mask is 255.255.255.0, so they are on the same subnet either ... BOOTME messages. ... Under "Download", entered 192.168.0.179. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: How does the CE device and dev workstation find each other on
    ... Yes, good call Paul. ... both device and workstation, plug in the ethernet cross-over, set staic IP's ... BOOTME messages. ... I'm trying to do my first download of a CE image to my ARTiGO, ...
    (microsoft.public.windowsce.platbuilder)