RE: CE5 Debugger Disconnect

From: J (J_at_discussions.microsoft.com)
Date: 10/28/04 

Date: Thu, 28 Oct 2004 12:15:08 -0700

Update

I've instrumented the code with lots of (serial) debug messages and noticed
that the device stops sending data across the link after the debug break has
been hit. It still receives data, but never makes any attempt to send
anything. It's not as if the adapter is unable to transmit, the kernel isn't
even trying.

Obviously, debug messages are no longer flowing since I'm at a breakpoint,
but I still think there is some kind of keep alive message that is probably
not making it.

Is there a change necessary in slightly higher level code that I missed on
the port from CE42 to CE5?

> I've got a problem where the CE5 debugger is disconnecting when it hits a
> breakpoint. It appears to be some kind of timeout mechanism that wasn't
> there in 4.2. This has only been observed with ethernet debugging
> (LAN91C111), serial debugging is working fine.
>
> If you continue from the breakpoint within a couple of seconds, it will not
> timeout. The ethernet debug code is the same as was used previously in 4.2,
> where it was working fine. Not using the PQOAL libraries, although I've been
> going through them to see if anything in supplied LAN91C111 libraries gives
> me any ideas...
>
> What's different in CE5, and suggestions on where I should look to resolve
> this problem?
>
>