Wince 4.2 Kernel debugger is waiting to connect with target

[santhi.ra...@gmail.com]

Hi all,
We are currently working on Wince 4.2. Please find below the issue
faced:
1. Previously when the debug build image nk.bin was downloaded to the
target, the debugger could connect to the target and we used to get
the debug messages on PB promptly without fail.

2. Now, with debug build, the PB debug window shows the following
message:
"Kernel debugger is waiting to connect with target"
and the screen goes blank. There are no debug messages on the screen!

But the target successfully boots up and the application also runs
fine.

Please let me know your views.

Thanks in advance,
Santhi Ramachandran

[Mike E.]

santhi.ra...@gmail.com wrote in news:1179725173.388322.327120
@b40g2000prd.googlegroups.com:

Hi Santhi,

have a look in you "Connectifty Options" I seems like that you have
changed some of your previous settings. To debug your kernel you need to
set "Download" and "Transport" to the interface that you are using on
your target (i.e. Ethernet). Also set "Debugger" to "KdStub" and you
should be able to connect to your target and debug. I guess that
"Transport" is set to "None" and then you kernel will be downloaded and
started directly without getting connected to Platform Builder.

Best regards,

Mike E.

--
Digi International Inc.
http://www.digi.com

[santhi.ra...@gmail.com]

On May 21, 1:25 pm, "Mike E." <m...@reterioja.com> wrote:
> santhi.ramachand...@gmail.com wrote in news:1179725173.388322.327120

> @b40g2000prd.googlegroups.com:
>
>
>
>
>
> > Hi all,
> > We are currently working on Wince 4.2. Please find below the issue
> > faced:
> > 1. Previously when the debug build image nk.bin was downloaded to the

> >target, thedebuggercouldconnectto thetargetand we used to get

> > the debug messages on PB promptly without fail.
>
> > 2. Now, with debug build, the PB debug window shows the following
> > message:
> > "Kerneldebuggeriswaitingtoconnectwithtarget"
> > and the screen goes blank. There are no debug messages on the screen!
>

> > But thetargetsuccessfully boots up and the application also runs

> > fine.
>
> > Please let me know your views.
>
> > Thanks in advance,
> > Santhi Ramachandran
>
> Hi Santhi,
>
> have a look in you "Connectifty Options" I seems like that you have

> changed some of your previous settings. To debug yourkernelyou need to

> set "Download" and "Transport" to the interface that you are using on

> yourtarget(i.e. Ethernet). Also set "Debugger" to "KdStub" and you
> should be able toconnectto yourtargetand debug. I guess that
> "Transport" is set to "None" and then youkernelwill be downloaded and

> started directly without getting connected to Platform Builder.
>
> Best regards,
>
> Mike E.
>
> --

> Digi International Inc.http://www.digi.com- Hide quoted text -
>
> - Show quoted text -

Hi Mike,

Thanks for that quick response. Yes, the "Download" and "Transport"
are both set to the interface that we are using on
our target(i.e. Ethernet).

How do we set "Debugger" to "KdStub"?

Please let me know your views.

Thanks,
Santhi Ramachandran

[Srini]

Pls verify

1) if your running debug / retail image with KITL enabled ? By default
for all debug builds it should be enabled.

2) Also verify, if you have terminated any CE processes before .. you
might hang up. Close PB and Make sure, all CE processes are closed and
re-run the PB and the debug image.

3) Under your Target Device Connectivity Options : Service
Configuration : Kernel Service Map

Select your Target Device, Download to Emulator, Transport as
Emulator, Debugger as KDStub

Under Core Service Settings - Set Download Image as Always, KITL
Settings as enable all checkboxes

Apply and Close.

Reverify the settings by opening the dialog again - PB has some
issues. Now, you are confirmed that you saved.

Launch debug image again.

-Srini

[Mike E.]

santhi.ra...@gmail.com wrote in news:1179809251.570372.250660
@x35g2000prf.googlegroups.com:

Hi Santhi,

sorry I mixed Wince V4.20 and V5.0. To get the Platform builder
connected to your target go to the Settings tab of the "Configure Remote
Connection" and check that "Connect To Device" is enabled.