Re: Device emulator debugging using VS2005 with PB for CE 6.0

Sorry - I misread your mail, and thought you wanted to do usermode app debugging using VS 2005. For kernel debugger in PB, you definitely wand "Enable KITL on device boot" checked.

The "Tools->Connectivity Options" dialog configures the PB side of debugging. You'll also need to make sure that the device side of debugging is enabled: in the Project->Properties dialog, make sure that "Enable KITL" is checked (and rebuild your emulator image if it is not).

You can also get a better idea of what is going on by changing the emulator's configuration a bit. In Target->Connectivity Options, there is a spot where you can change the settings that PB uses to launch the emulator (unfortunately, my PB is unhappy today and the dialog won't draw, so I can't give you the exact commands). But you'll get an "Emulator Properties" dialog with a "Peripherals" tab - check the "Create text console for serial port 1" option. That tells the emulator to direct debug output from the CE kernel to a Windows console window instead of to a virtual serial port. Hopefully that console window will have some useful messages for you.

Barry



"Srinimg@xxxxxxxxx" <Srinimgyahoocom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3F3F3DC3-8013-43E6-AB0D-1C4A2B4EEEB3@xxxxxxxxxxxxxxxx
Thanks Barry Bond for your Timely reply.

I am using Windows Embedded CE 6.0 Evaluation version with VS2005 IDE.

I used Tools->Connectivity Options-> (In Target Device Connectivity Options)
then Selected "Kernal Service Map"
Target Device : CE Device
Download : Device Emulator(DMA)
Transport : Device Emulator(DMA)
Debugger : KdStub
then selected "Core Service Settings"
Target Device : CE Device
Associated ren-time image: (specified nk.bin)
Download Image : Always is checked
KITL Settings : UNCHECKED "Enable KITL on device boot"
Remaining Items are CHECKED

My understanding is that you pointed out the above "KITL Settings".

After i build the Built the image, I made sure that the above settings are
in place.

Then hit F5 to debug, but it is showing "PB Debugger The Kernel Debugger is
waiting to connect with target." for long time, does not seem to be
connecting...

So please let me know what i am doing wrong.

Your timely help is very well appreciated.

NOTE:
1. Target->Attach Device launches the Emulator.
2. Also I see only emulators under Pocket PC 2003, Smartphone 2003, but not
under windows 5.0 & Platform Builder-Specific
Builder-Specific in the "Device Emulator Manager"

Thanks in advance
-Srini



"Barry Bond [MSFT]" wrote:

When you install the SDK you created with the emulator image, it should
create a new entry in VS2005 for the emulator image automatically. It will
have both bootstrap and transport set to DMA.

If you are using CE 6.0, then please be sure to disable KITL in your
image... KITL-over-DMA interferes with the VS2005 DMA bootstrap and
transport and will block VS from connecting.

Barry

"Srinimg@xxxxxxxxx" <Srinimgyahoocom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:F129527F-A2CA-480B-B8BF-21A40CCA9AB6@xxxxxxxxxxxxxxxx
> Hello All,
>
> I created a OS Design with "Device Emulator: ARMV4I". Could anyone
> please tell me Settings/Configurations to be done in VS2005
> (Target->Connectivity Options... OR using Device Emulator Manager)to > debug
> using the emulator?
>
> Thanks in advance
> -Srini
>
.

Relevant Pages

  • Re: Device emulator debugging using VS2005 with PB for CE 6.0
    ... Even after making sure the settings Build ... Could you please tell me what i should do to debug in the emulator? ... For kernel debugger in PB, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: custom OS emulator wont start
    ... it's working now once I uncheck "Enable KITL" option. ... always make sure the emulator isn't trying to connect to the debugger by ... building the image with no debugger IMGNODEBUGGER and no KITL IMGNOKITL ... The error message is: ...
    (microsoft.public.windowsce.embedded)
  • Re: Process.Start() in windows service on Windows Server 2003, problem
    ... What happens if you run ExtExp.exe under debugger? ... Change your Process.Start call to use these settings: ... > And I get no exceptions running it in remote debug mode. ... > I also made the extexp write to a log file the first thing it does.. ...
    (microsoft.public.platformsdk.security)
  • Re: Strange Debugger Problems
    ... > There are two ways to specify the engine: ... > if you try other settings?) ... > debug engine for the application when it is starting under debugger, ... > have this problem when attaching to it (if you choose "Native" in Attach to Process ...
    (microsoft.public.vc.debugger)
  • Working around a group policy
    ... There are probably messages posted already about how to override group ... scripts in Firefox, which has a nice debugger, and port them over. ... We also have a group policy in effect that hides the Advanced tab in ... Explorer/Disable changing Advanced page settings. ...
    (microsoft.public.windows.group_policy)