Hi All,

Has anyone tried using Platform Builder Kernel debugger (kdstub)?

I have tried for quite some time but is still unable to connect Platform
Builder to my device for debugging. Platform Builder is always in 'The
Kernel Debugger is waiting to connect with target' status.

My device is connected via USB cable to the COM port and I have already
loaded the image to the device with other tools. My device has no Ethernet
port.

I understand that in order to use kdstub, I need to include Kernel Debugger
capability in the image. I am doing a release build but have undefined
IMGNODEBUGGER (i.e enable kernel debugger) and IMGNOKITL (i.e enable KITL).
However, I cannot find kdstub.dll in the release directory. What I have are
kd.dll, osaxst0.dll and osaxst1.dll. Is this the reason why Platfrom Builder
cannot connect to my device? If yes, how do I include kdstub.dll in the
image?

Also, may I know if it is a must to specify a transport in
'Target->Connectivity Option' before Platform Builder can connect to the
device? What if transport is set to 'NONE', can it still connect? I just
want to make sure if the problem can be from my serial KITL code.

Many tks,
Ada

Re: MIcrosoft Platform Builder by ctacke/>

ctacke/>
Wed Jan 11 07:19:04 CST 2006

You might try posting to the Platform Builder newsgroup.

-Chris


"my" <my@discussions.microsoft.com> wrote in message
news:0A880F07-26BF-45CA-BF49-85D690357062@microsoft.com...
> Hi All,
>
> Has anyone tried using Platform Builder Kernel debugger (kdstub)?
>
> I have tried for quite some time but is still unable to connect Platform
> Builder to my device for debugging. Platform Builder is always in 'The
> Kernel Debugger is waiting to connect with target' status.
>
> My device is connected via USB cable to the COM port and I have already
> loaded the image to the device with other tools. My device has no
> Ethernet
> port.
>
> I understand that in order to use kdstub, I need to include Kernel
> Debugger
> capability in the image. I am doing a release build but have undefined
> IMGNODEBUGGER (i.e enable kernel debugger) and IMGNOKITL (i.e enable
> KITL).
> However, I cannot find kdstub.dll in the release directory. What I have
> are
> kd.dll, osaxst0.dll and osaxst1.dll. Is this the reason why Platfrom
> Builder
> cannot connect to my device? If yes, how do I include kdstub.dll in the
> image?
>
> Also, may I know if it is a must to specify a transport in
> 'Target->Connectivity Option' before Platform Builder can connect to the
> device? What if transport is set to 'NONE', can it still connect? I just
> want to make sure if the problem can be from my serial KITL code.
>
> Many tks,
> Ada
>
>



Re: MIcrosoft Platform Builder by my

my
Wed Jan 11 19:15:02 CST 2006

Thank you Chris.

"<ctacke/>" wrote:

> You might try posting to the Platform Builder newsgroup.
>
> -Chris
>
>
> "my" <my@discussions.microsoft.com> wrote in message
> news:0A880F07-26BF-45CA-BF49-85D690357062@microsoft.com...
> > Hi All,
> >
> > Has anyone tried using Platform Builder Kernel debugger (kdstub)?
> >
> > I have tried for quite some time but is still unable to connect Platform
> > Builder to my device for debugging. Platform Builder is always in 'The
> > Kernel Debugger is waiting to connect with target' status.
> >
> > My device is connected via USB cable to the COM port and I have already
> > loaded the image to the device with other tools. My device has no
> > Ethernet
> > port.
> >
> > I understand that in order to use kdstub, I need to include Kernel
> > Debugger
> > capability in the image. I am doing a release build but have undefined
> > IMGNODEBUGGER (i.e enable kernel debugger) and IMGNOKITL (i.e enable
> > KITL).
> > However, I cannot find kdstub.dll in the release directory. What I have
> > are
> > kd.dll, osaxst0.dll and osaxst1.dll. Is this the reason why Platfrom
> > Builder
> > cannot connect to my device? If yes, how do I include kdstub.dll in the
> > image?
> >
> > Also, may I know if it is a must to specify a transport in
> > 'Target->Connectivity Option' before Platform Builder can connect to the
> > device? What if transport is set to 'NONE', can it still connect? I just
> > want to make sure if the problem can be from my serial KITL code.
> >
> > Many tks,
> > Ada
> >
> >
>
>
>