I am porting an existing BSP to CE6 and have followed the migration guide
regarding the new Kernel/OAL/Kitl architecture. I have oal.exe and kitl.dll
built as well as the rest of the ROM image. I also have the bootloader
ported and functional.

After the image is downloaded to RAM via Ethernet the image is launched
successfully, but in OEMInit() the call to KITLIoctl (IOCTL_KITL_STARTUP,...)
is not invoking OEMKitlStartup() in kitl.dll and the system is hanging.

Thoughts as to why I am not seeing the entry into OEMKitlStartup()?? I have
debug tracing everywhere and am sure this is where the hang is occurring.

I have verified that the interrupts are being setup correctly, and as I
stated, this is a working BSP with CE 5.0, just want to upgrade to CE 6.0 for
the newer memory architecture.

Thanks.

RE: CE5 to CE6 port, Kitl Question by MattGoslineMSFT

MattGoslineMSFT
Mon May 05 11:36:01 PDT 2008


This can be caused if your KITL implementation is missing the KitlDllMain
entry point.

One of the things KitlDllMain does is to initialize the pfnKITLIoctl member
of the NKGLOBAL array. This variable must be setup correctly in order for
KitlIoctl to work properly.

KitlDllMain is provided for you in KitlCore.lib. Your sources file should
specify DLLENTRY=KitlDllMain in your KITL sources file.

http://msdn.microsoft.com/en-us/library/aa914525.aspx describes this in
detail.

Hope this helps,

Matt

--
This posting is provided AS IS with no warranties and confers no rights. --
Matt Gosline


"FoolBlah" wrote:

> I am porting an existing BSP to CE6 and have followed the migration guide
> regarding the new Kernel/OAL/Kitl architecture. I have oal.exe and kitl.dll
> built as well as the rest of the ROM image. I also have the bootloader
> ported and functional.
>
> After the image is downloaded to RAM via Ethernet the image is launched
> successfully, but in OEMInit() the call to KITLIoctl (IOCTL_KITL_STARTUP,...)
> is not invoking OEMKitlStartup() in kitl.dll and the system is hanging.
>
> Thoughts as to why I am not seeing the entry into OEMKitlStartup()?? I have
> debug tracing everywhere and am sure this is where the hang is occurring.
>
> I have verified that the interrupts are being setup correctly, and as I
> stated, this is a working BSP with CE 5.0, just want to upgrade to CE 6.0 for
> the newer memory architecture.
>
> Thanks.