Kernel Debugger Problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Clinton D. Britt (Britt_at_discussions.microsoft.com)
Date: 09/08/04 

Date: Wed, 8 Sep 2004 10:59:08 -0700

I am porting a platform from a pervious beta version of 5.0 to the release
vedrsion. My "beta" version's kernel debugging worked perfectly (well,
perfect for PB). The port to the release version has introduced a new problem
for me. It seems that I get a KITL connection, and all seems good until we
exit OEMInit(). At this time when the debugger attemps to attach, it reports
the following error in a dialog:

"OS image file can not be opened - it is either invalid or not accessable.
Non-recoverable error."

Has anyone seen this before? Is this caused by the fact that we add a
additional header to the beginning of the OS image and offset the jump
address to take this into account? Or is it due to the fact that the image
may be halted for some reason?

The only debug information output that is non-connection releated just
states that it finished OEMInit() and loaded the symbols for NK.exe. That's
it.

This is the debug output:

The Kernel Debugger is waiting to connect with target.
      0 PID:0 TID:0 -OALKitlStart(rc = 1)
      0 PID:0 TID:0 Reschedule increment=83300
      0 PID:0 TID:0 +RegisterKitl
      0 PID:0 TID:0 RegisterKitl: EtherIoAddr=0x1ae00, EtherIntrNumber=24
      0 PID:0 TID:0 RegisterKitl: bus=0, device=0, function=0
      0 PID:0 TID:0 RegisterKitl: bus=0, device=1, function=0
      0 PID:0 TID:0 RegisterKitl: bus=0, device=2, function=0
      0 PID:0 TID:0 RegisterKitl: bus=0, device=3, function=0
      0 PID:0 TID:0 RegisterKitl: bus=0, device=4, function=0
      0 PID:0 TID:0 RegisterKitl: bus=0, device=5, function=0
      0 PID:0 TID:0 RegisterKitl: bus=0, device=6, function=0
      0 PID:0 TID:0 RegisterEther: Found NIC on PCIbus (0/6/0),
VendorID=0x100B, DeviceID=0x20, BaseAddr=0x1AE00, IRQ=24
      0 PID:0 TID:0 RegisterEther: Found KITL NIC on PCIbus (0/6/0),
VendorID=0x100B, DeviceID=0x20, BaseAddr=0x1AE00, IRQ=24
      0 PID:0 TID:0 Irq=0x18, SysIntr=0x18
      0 PID:0 TID:0 -RegisterKitl
      0 PID:0 TID:0 Exiting OEMInit
Kernel debugger connected.
The Kernel Debugger connection has been established (Target CPU is MIPS).
Target name: CE Device
Probe name: KdStub
Binary Image should be loaded at 0x8000eeee / Data relocated at 0x8010eeee
Loaded symbols for
'D:\WINCE500\PBWORKSPACES\DEFAULT\RELDIR\MOZART_MIPSIV_FP_RELEASE\NK.EXE'

Anyone have any ideas??

Clinton D. Britt
Rockwell Automation

Relevant Pages

  • PB5.0 Target Connectivity - KDBG Service fails
    ... Service) attach fails for Mainstone III target, ... The Kernel Debugger is waiting to connect with target. ... PB 5.0) the Target Connectivity settings where I suspect the problem ... Receive Config message for service DBGMSG ...
    (microsoft.public.windowsce.platbuilder)
  • Re: PB5.0 Target Connectivity - KDBG Service fails
    ... > with PB 5.0 Target Connectivity: Kernel Debugger (host-side KDBG ... Receive Config message for service DBGMSG ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Unable to run clientside.exe
    ... Kernel debugger failed to connect with target. ... End s clientside /n=LAB1 /p=5555 ... 3.Now when I start CETK server, nothing happens,ie: no connection is established. ...
    (microsoft.public.windowsce.embedded)
  • WinDbg Command Line Prompt : Plz Help : Urgent Help Needed.
    ... I need to get something clarified regarding WinDbg command prompt. ... I have connected the host machine and the target machine usng a com ... SavRoam: initializing communications ... The above message shows that kernel debugger connection established. ...
    (microsoft.public.development.device.drivers)
  • Re: platform builder 4.2 debugger cannot connect to target
    ... Do you have the VMini network adapter in your image? ... I have a problem in starting the kernel debugger from platform builder ... I am using the ethernet for downloading and kernel transport. ... PC is running windows xp professional, and the target is running wince ...
    (microsoft.public.windowsce.platbuilder)