Cant reconnect... Connect Issues

Thanks for the help on my previous threads..

I am new to everything here so bare with me. I have a working platform and I am able to run the OS and the application on my target device with kernel debugging (I hit break points and everything succesfully). However, after stopping the debugger and then disconnecting, I cannot reconnect to the target device. Advice? Thanks for your help, in advance

Also, after I stop the debugger and disconnect can I edit my application code and expect the changes to be reflected on the target device

Is the same true with device drivers?

anonymous
Tue Feb 10 17:46:06 CST 2004

I actually can reconnect but I have to reset the target device and reload the image :-)

anonymous
Tue Feb 10 17:51:06 CST 2004

Let me add one more thing... when I click stop debugging I get a message telling me that I should disable the target side debugger component kdstub... well this may be the key right? How do I do that?

anonymous
Tue Feb 10 18:51:05 CST 2004

One more last thing, I tried turning off kernel debugging... but I still can't reconnect.

Geoff
Wed Feb 11 10:51:50 CST 2004

You can't connect to the same KITL connection twice in the same session - it
doesn't work. You were on the right lines with resetting the target device
then reconnecting.

KTIL is the transport that the kernel uses to communicate with the desktop.


What is it that you are trying to do?

--
Geoff Smith
eMVP
==

"nreader" <anonymous@discussions.microsoft.com> wrote in message
news:71DEC6E8-0923-4A41-97B7-B26D5D0870CF@microsoft.com...
> Thanks for the help on my previous threads...
>
> I am new to everything here so bare with me. I have a working platform and
I am able to run the OS and the application on my target device with kernel
debugging (I hit break points and everything succesfully). However, after
stopping the debugger and then disconnecting, I cannot reconnect to the
target device. Advice? Thanks for your help, in advance.
>
> Also, after I stop the debugger and disconnect can I edit my application
code and expect the changes to be reflected on the target device?
>
> Is the same true with device drivers?

anonymous
Wed Feb 11 11:46:07 CST 2004

Thanks Geoff. Now I wish I wouldn't have spent so long on that problem

Basically I was trying to speed up the debugging process.

Say... on my applications under user features the "build selected feature" is grayed out. Why would this be? They aren't core os, are they

I'm also working concurrently on a driver, which has this same issue..

is there a way for me not to have to build the whole os image every time I want load the image to the target device after I make a change to my driver or application
Thanks!

Steve
Wed Feb 11 12:49:28 CST 2004

Clarification, you can "stop debugging" and then re connect the debugger as
long as the underlying KITL connection is not terminated.

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com

Steve
Wed Feb 11 12:53:59 CST 2004

It is grayed out because you are debugging. It is possible to "stop
debugging" rebuild the driver and then run the debugger again as long as you
don't disconnect KITL That is the key difference between the Stop Debugging
command (menu or toolbar button) and the Disconnect. The disconnect will
shut down KITL while stopping debugging just stops the kernel debugger
letting you re-build something and re-start debugging again.

NOTE: there is a bug in the IDE that won't let you build most things while
KTIL is connected regardless of the kernel debugger. Search the newsgroups
for "CDBLD" (via google) to find a simple bat file to use with the "Open
Build Release" command. That command opens a command prompt window that you
can use to build the component you are working on even though the IDE won't
let you.


--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com