Re: CE5 hangs in KitlInit

Tech-Archive recommends: Fix windows errors by optimizing your registry

Dean Ramsier wrote:
1) There is a flag in the PB Connectivity Options dialog, Core Service
Settings that can control whether Kitl connects in Active (wait for PB to
connect) or Passive (don't connect until a client requests it) mode. The
setting for this check box is passed to the bootloader as part of the
flags that come down at the end of a bootloader download.
Your bootloader can choose whether to honor this flag and pass it on to
the kernel for use in OEMInit.

Hmmm, I'm not sure I understand: do you mean that the flag is passed along
when writing the bootloader to flash or when I use PB with EBOOT to load a
kernel? I guess the latter is the case, because the former doesn't involve
PB at all.
FWIW, the bootloader I use is EBOOT from CE4.2(not CE5!) because I need to
still be able to boot CE4.2 images. I might upgrade at a later stage.

3) It's probably trying to connect, with nothing available to connect to.
If you have kitl enabled, make sure that PB and your device is configured
to handle the connection.

Okay, I found some code in OALKitlStart that tries to read an OAL_KITL_ARG
structure from the bootargs, but it always returns NULL because this
structure simply doesn't exist in the CE4.2 EBOOT arguments. It then used
the default flags that KITL is activated and DHCP used
(OAL_KITL_FLAGS_ENABLED and *_DHCP).
Now, I simply added OAL_KITL_FLAGS_PASSIVE to the flags, and now it boots.
However, now I have another problem: even when booting via PB, I don't get
the bootmessages - probably right so, because it says that the connection
is made on demand, i.e. when a debug break is triggered.

I now looked at the old bootloader's code, and I found in the BOOT_ARGS
structure the field ucEshellFlags which seems to have EDBG_FL_CLEANBOOT
when booting via CompactFlash.

It works now, though I'm not 100% sure I'm doing the right thing. Should
probably use the CE5 EBOOT...

thanks

Uli


.

Relevant Pages

  • Re: Connecting to device for debugging
    ... Before starting the CE kernel, the bootloader sets some parameters passed to ... Some of them refers to the ethernet settings that should be used ... The KITL connection is driven by 2 things: ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debug works, Release hangs
    ... I am certain I am building my image with KITL disabled. ... Does the bootloader need to disable KITL somehow? ... Are there Build Options I need to change between Debug and Release builds ... >> Hit space to enter configuration menu 5... ...
    (microsoft.public.windowsce.embedded)
  • Re: How to complete RNDIS on WinCE50?
    ... the bootloader basically just set up a configuration struct ... that kitl uses to configure itself from. ... Taking into account that kitl drivers don't rely much on os-specific ... might want to concider adding download support to the bootloader once ...
    (microsoft.public.windowsce.platbuilder)