LoadIntChainHandler returns NULL

Hi Everyone,

I have a problem and need your expertise.

I migrated USBOTG driver from MainstoneIII to our BSP based on PXA320 and
WinCE 6.0. When I run the OS with KITL and debugger enabled, the driver
works fine. But if I disable the KITL and debugger, LoadIntChainHandler(...)
returns NULL and the driver is unloaded.

The following are the related messages:
with KITL and debugger enabled:
LoadIntChainHandler ddi.szIsrDll = giisr.dll, ddi.szIsrHandler=ISRHandler,
ddi.dwIrq=0xb
22950 PID:400002 TID:d90002 RELFSD: Opening file giisr.dll from desktop
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\...\GIISR.DLL'
22981 PID:400002 TID:d90002 LoadIntChainHandler successed

with KITL and debugger disabled:
LoadIntChainHandler ddi.szIsrDll = giisr.dll, ddi.szIsrHandler=ISRHandler,
ddi.dwIrq=0xb
LoadIntChainHandler failed

I also copied registry settings for your reference:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\UsbOtg]

"Dll"="ms2_usbotg.dll"

"Prefix"="OTG"

"Order"=dword:10

"MemBase"=dword:40600000 ; UDC_BASE_U_VIRTUAL

"MemLen"=dword:1000 ; Needs at least 0xE04. Round up to 1 page.

"Irq"=dword:0b

"IsrDll"="giisr.dll"

"IsrHandler"="ISRHandler"

"HCDPortNumberOnOTG"=dword:2

"BusIoctl"=dword:2a0048

"InterfaceType"=dword:0

"IClass"=multi_sz:"{6F40791D-300E-44E4-BC38-E0E63CA8375C}=%b"

Thanks a lot,

James

James
Tue Jun 10 15:28:09 PDT 2008

I figured out the problem.

The giisr.dll is not included in the OS image. That's why it works when KITL
is enabled. The system will automatically search the "path" and load it from
the \Release folder. Without KITL\Release folder, giisr.dll cannot be found
and the OS failed to load it.

I added it in my BIB file and it works now.

Thanks,
James

"James" <dsljames.ca@gmail.com> wrote in message
news:OrnARa0yIHA.2384@TK2MSFTNGP02.phx.gbl...
> Hi Everyone,
>
> I have a problem and need your expertise.
>
> I migrated USBOTG driver from MainstoneIII to our BSP based on PXA320 and
> WinCE 6.0. When I run the OS with KITL and debugger enabled, the driver
> works fine. But if I disable the KITL and debugger,
> LoadIntChainHandler(...) returns NULL and the driver is unloaded.
>
> The following are the related messages:
> with KITL and debugger enabled:
> LoadIntChainHandler ddi.szIsrDll = giisr.dll, ddi.szIsrHandler=ISRHandler,
> ddi.dwIrq=0xb
> 22950 PID:400002 TID:d90002 RELFSD: Opening file giisr.dll from desktop
> PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\...\GIISR.DLL'
> 22981 PID:400002 TID:d90002 LoadIntChainHandler successed
>
> with KITL and debugger disabled:
> LoadIntChainHandler ddi.szIsrDll = giisr.dll, ddi.szIsrHandler=ISRHandler,
> ddi.dwIrq=0xb
> LoadIntChainHandler failed
>
> I also copied registry settings for your reference:
> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\UsbOtg]
>
> "Dll"="ms2_usbotg.dll"
>
> "Prefix"="OTG"
>
> "Order"=dword:10
>
> "MemBase"=dword:40600000 ; UDC_BASE_U_VIRTUAL
>
> "MemLen"=dword:1000 ; Needs at least 0xE04. Round up to 1 page.
>
> "Irq"=dword:0b
>
> "IsrDll"="giisr.dll"
>
> "IsrHandler"="ISRHandler"
>
> "HCDPortNumberOnOTG"=dword:2
>
> "BusIoctl"=dword:2a0048
>
> "InterfaceType"=dword:0
>
> "IClass"=multi_sz:"{6F40791D-300E-44E4-BC38-E0E63CA8375C}=%b"
>
> Thanks a lot,
>
> James
>
>