Kitl cannot connect

I am trying to get kitl working in order to debug my platform. I am
migrating from ce4.2 to 5.0.
The platform builder will download the image to the platform, but the
platform will not connect after the image starts. It appears to
attempt a connection, but fails at kwin32.c line 777. I followed this
to Kdinit, but I'm not sure why this fails.

Do any readers have suggestions on how to fix this, or where to look?

Here is the serial debug output:

T>Windows CE Firmware Init
T>Initialize timer used for delays in the HAL
T>Reset register indicates a cold boot
T>InitClock
T>Initialize driver globals area
T>Mask all peripheral interrupts
T>Firmware Init Done.
T>OEMInit End.
Booting Windows CE version 5.00 for (ARM)
&pTOC = 8820a25c, pTOC = 88f6c5dc, pTOC->ulRamFree = 89557000,
MemForPT = 000000
00

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 10917, Secondary pages: 0, Filesystem
pages = 1364

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 89558000, extension: 00003000, length: 02aa5000
Sp=ffffc7cc
ARMInit done.
Windows CE KernelInit
Updated eptr->e32_vsize to = 000aa000
Scheduling the first thread.
0x8bfff024: KernelInit2: pCurThread=8bfff024 hCurThread=0bfff266
hCurProc=0bfff0
02, KernelInit = 88227658
0x8bfff024: Detecting VFP...0x8bfff024: VFP Not Found!
0x8bfff024:
Updated eptr-
e32_vsize to = 00006000
0x8bfff024: Updated eptr->e32_vsize to = 00029000
0x8bfff024: Updated eptr->e32_vsize to = 00009000
0x8bfff024: Updated eptr->e32_vsize to = 00022000
0x8bfff024: ERROR: c:\macallan\private\winceos\coreos\nk\kernel
\kwin32.c line 777: 0x8bfff024: ConnectDebugger failed
0x8bfff024: first = 01f40000, last = 02000000, SharedDllBase =
032f0000

0x8bfe88c
8: CertMod.dll not found, using old OEM Trust Model
0x8bfe88c8: FileSystem Starting - starting with clean file system
0x8bfe88c8: IOCTL_HAL_INIT_RTC : attempted reset
0x8bfe88c8: FS: initializing ROM/RAM file system
0x8bfe88c8: SC_CreateAPIHandle: pvData == NULL
0x8bfe88c8: FS: Registering file system ROM, index 2, flags 0x00000031
0x8bfe88c8: FS: Mount complete (ROM, index 2, flags 0x00000031)
0x8bfe88c8: Succeeded on CheckFile

.

Relevant Pages

  • Re: [PATCH 1/4] Blackfin: arch patch for 2.6.18
    ... to the kernel from the mtd medium, ... architecture if that means that you have to leave holes like setup. ... You seem to have lots of these machine specfic header files in include/asm. ... probably be either 'subarchitecture' or 'platform' in your code. ...
    (Linux-Kernel)
  • Re: VMINI driver
    ... It talks about %_WINCEROOT%\<Hardware Platform ... I notice that common.bib seems to select either kernel, ... You need to load the VMINI driver through the registry. ... The file naming is not coherent among different BSPs and also the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [RFC] [PATCH] Device Tree on ARM platform
    ... platform bus binding, except in the data structures used. ... that have to be correct for the kernel to work. ... The main selling points of the device tree AFAICT are that some ... same NFS tree and the same kernel image. ...
    (Linux-Kernel)
  • Xscale PXA255 CE.NET 4.2: Getting OEMGetExtensionDRAM to work ?
    ... up to reflect this and the platform is stable using this 64Mb setup. ... The platform can be expanded with a further 64Mb of SDRAM. ... The kernel hangs very quickly with the following output: ... Booting kernel with clean memory configuration: ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [RFC] [PATCH] Device Tree on ARM platform
    ... This is a MPC5200 is the posterchild for device tree wreckage; ... an FPGA with all the devices instantiated in the FPGA fabric. ... changes from the kernel image. ...  abstraction for arbitrary hardware in the kernel: platform devices. ...
    (Linux-Kernel)
Loading