NDIS Miniport driver initialization

Tutorials Win: Microsoft Windows Forum

Greetings,

I've got a SDIO-WLAN card for which I have a NDIS Miniport driver. I'm
using WinCE 5.0 and have built the driver properly in Platform
Builder, and it's part of the NK image that gets loaded on my device.

While running the Release version of my image I saw that the driver
wasn't fully initializing. I then built a Debug version of the image
and have the following relevant debug messages..

===
4294775509 PID:3f5078e TID:3f5076a 0x83f50528: >>> Loading module
irsir.dll at address 0x03E70000-0x03E82000 (RW data at
0x01FF4000-0x01FF4660)
4294775545 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisInitializeWrapper
4294775546 PID:3f5078e TID:3f5076a 0x83f50528:
<==NdisInitializeWrapper
4294775553 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisMRegisterMiniport: NdisWrapperHandle 00051CF0
4294775554 PID:3f5078e TID:3f5076a 0x83f50528:
==>ndisRegisterMiniportDriver: NdisWrapperHandle 00051CF0
4294775555 PID:3f5078e TID:3f5076a 0x83f50528:
<==ndisRegisterMiniportDriver: MiniBlock 00051D60
4294775556 PID:3f5078e TID:3f5076a 0x83f50528: NdisMRegisterMiniport:
MiniBlock 00051D60
4294775557 PID:3f5078e TID:3f5076a 0x83f50528:
<==NdisMRegisterMiniport: MiniBlock 00051D60, Status 0
4294775558 PID:3f5078e TID:3f5076a 0x83f50528:
4294775560 PID:3f5078e TID:3f5076a 0x83f50528: ndisMInitializeAdapter:
Miniport 00051F60,
4294775571 PID:3f5078e TID:3f5076a 0x83f50528:
==>ndisQueueMiniportOnDriver: Miniport 00051F60, MiniBlock 00051D60
4294775572 PID:3f5078e TID:3f5076a 0x83f50528:
<==ndisQueueMiniportOnDriver: Miniport 00051F60, MiniBlock 00051D60,
rc 1
4294775575 PID:3f5078e TID:3f5076a 0x83f50528: COM_Close: (0 handles)
total RX 0, total TX 0, dropped (mdd, pdd) 0,0
4294775576 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisMSetAttributesEx: Miniport 00051F60
4294775593 PID:3f5078e TID:3f5076a 0x83f50528: >>> Loading module
asyncmac.dll at address 0x03B00000-0x03B10000 (RW data at
0x01FC7000-0x01FC7988)
4294775629 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisInitializeWrapper
4294775630 PID:3f5078e TID:3f5076a 0x83f50528:
<==NdisInitializeWrapper
4294775631 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisMRegisterMiniport: NdisWrapperHandle 00052870
4294775632 PID:3f5078e TID:3f5076a 0x83f50528:
==>ndisRegisterMiniportDriver: NdisWrapperHandle 00052870
4294775633 PID:3f5078e TID:3f5076a 0x83f50528:
<==ndisRegisterMiniportDriver: MiniBlock 000528E0
4294775634 PID:3f5078e TID:3f5076a 0x83f50528: NdisMRegisterMiniport:
MiniBlock 000528E0
4294775635 PID:3f5078e TID:3f5076a 0x83f50528:
<==NdisMRegisterMiniport: MiniBlock 000528E0, Status 0
4294775636 PID:3f5078e TID:3f5076a 0x83f50528:
4294775638 PID:3f5078e TID:3f5076a 0x83f50528: ndisMInitializeAdapter:
Miniport 00052AF8,
4294775649 PID:3f5078e TID:3f5076a 0x83f50528:
==>ndisQueueMiniportOnDriver: Miniport 00052AF8, MiniBlock 000528E0
4294775650 PID:3f5078e TID:3f5076a 0x83f50528:
<==ndisQueueMiniportOnDriver: Miniport 00052AF8, MiniBlock 000528E0,
rc 1
4294775652 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisMSetAttributesEx: Miniport 00052AF8
4294775654 PID:3f5078e TID:3f5076a 0x83f50528: ASYNCMAC:MpQueryInfo:
OID 0x10116/Unknown OID not supported
4294775656 PID:3f5078e TID:3f5076a 0x83f50528: ASYNCMAC:MpQueryInfo:
OID 0xFD010100/Unknown OID not supported
===

These are for two other Miniport drivers that seem to load properly.
However, when my driver loads up, I see the called to
NdisMInitializeWrapper() being acknowledged and I also see the
NdisMRegisterMiniport() being acknowledged. But at this point in time
my InitializeHandler function should be getting called and I should
see an indication of this by the debug message:
"ndisMInitializeAdapter: Miniport XXXXXX" or something. But as you can
see, I don't have anything like that. From there the driver is
essentially ignored and the WinCE image fully loads with no WLAN
access.

Here's the log
===
4294775788 PID:3f5078e TID:3f5076a 0x83f50528: >>> Loading module
sdiowlan.dll at address 0x010E0000-0x011A5000
4294775790 PID:3f5078e TID:3f5076a 0x83f50528: MRVDRVND5:
DLL_PROCESS_ATTACH
4294775791 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] INIT - Enter
DriverEntry
4294775792 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] *** Driver
version 3.2 ***
4294775793 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] *** Built on
Jl1 071:21 1:21 ***
4294775793 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisInitializeWrapper
4294775794 PID:3f5078e TID:3f5076a 0x83f50528:
<==NdisInitializeWrapper
4294775795 PID:3f5078e TID:3f5076a 0x83f50528:
==>NdisMRegisterMiniport: NdisWrapperHandle 00053450
4294775796 PID:3f5078e TID:3f5076a 0x83f50528:
==>ndisRegisterMiniportDriver: NdisWrapperHandle 00053450
4294775798 PID:3f5078e TID:3f5076a 0x83f50528:
<==ndisRegisterMiniportDriver: MiniBlock 000534C0
4294775799 PID:3f5078e TID:3f5076a 0x83f50528: NdisMRegisterMiniport:
MiniBlock 000534C0
4294775799 PID:3f5078e TID:3f5076a 0x83f50528:
<==NdisMRegisterMiniport: MiniBlock 000534C0, Status 0
4294775800 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] <==
DriverEntry: register miniport success
===

Any ideas on how I can debug this???

Regards
Top

Re: NDIS Miniport driver initialization by Ashwin

Ashwin
Fri Jul 13 11:08:02 CDT 2007

On Jul 12, 3:52 pm, Ashwin Bihari <abih...@gmail.com> wrote:
> Greetings,
>
> I've got a SDIO-WLAN card for which I have a NDIS Miniport driver. I'm
> using WinCE 5.0 and have built the driver properly in Platform
> Builder, and it's part of the NK image that gets loaded on my device.
>
> While running the Release version of my image I saw that the driver
> wasn't fully initializing. I then built a Debug version of the image
> and have the following relevant debug messages..
>
> ===
> 4294775509 PID:3f5078e TID:3f5076a 0x83f50528: >>> Loading module
> irsir.dll at address 0x03E70000-0x03E82000 (RW data at
> 0x01FF4000-0x01FF4660)
> 4294775545 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisInitializeWrapper
> 4294775546 PID:3f5078e TID:3f5076a 0x83f50528:
> <==NdisInitializeWrapper
> 4294775553 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisMRegisterMiniport: NdisWrapperHandle 00051CF0
> 4294775554 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>ndisRegisterMiniportDriver: NdisWrapperHandle 00051CF0
> 4294775555 PID:3f5078e TID:3f5076a 0x83f50528:
> <==ndisRegisterMiniportDriver: MiniBlock 00051D60
> 4294775556 PID:3f5078e TID:3f5076a 0x83f50528: NdisMRegisterMiniport:
> MiniBlock 00051D60
> 4294775557 PID:3f5078e TID:3f5076a 0x83f50528:
> <==NdisMRegisterMiniport: MiniBlock 00051D60, Status 0
> 4294775558 PID:3f5078e TID:3f5076a 0x83f50528:
> 4294775560 PID:3f5078e TID:3f5076a 0x83f50528: ndisMInitializeAdapter:
> Miniport 00051F60,
> 4294775571 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>ndisQueueMiniportOnDriver: Miniport 00051F60, MiniBlock 00051D60
> 4294775572 PID:3f5078e TID:3f5076a 0x83f50528:
> <==ndisQueueMiniportOnDriver: Miniport 00051F60, MiniBlock 00051D60,
> rc 1
> 4294775575 PID:3f5078e TID:3f5076a 0x83f50528: COM_Close: (0 handles)
> total RX 0, total TX 0, dropped (mdd, pdd) 0,0
> 4294775576 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisMSetAttributesEx: Miniport 00051F60
> 4294775593 PID:3f5078e TID:3f5076a 0x83f50528: >>> Loading module
> asyncmac.dll at address 0x03B00000-0x03B10000 (RW data at
> 0x01FC7000-0x01FC7988)
> 4294775629 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisInitializeWrapper
> 4294775630 PID:3f5078e TID:3f5076a 0x83f50528:
> <==NdisInitializeWrapper
> 4294775631 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisMRegisterMiniport: NdisWrapperHandle 00052870
> 4294775632 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>ndisRegisterMiniportDriver: NdisWrapperHandle 00052870
> 4294775633 PID:3f5078e TID:3f5076a 0x83f50528:
> <==ndisRegisterMiniportDriver: MiniBlock 000528E0
> 4294775634 PID:3f5078e TID:3f5076a 0x83f50528: NdisMRegisterMiniport:
> MiniBlock 000528E0
> 4294775635 PID:3f5078e TID:3f5076a 0x83f50528:
> <==NdisMRegisterMiniport: MiniBlock 000528E0, Status 0
> 4294775636 PID:3f5078e TID:3f5076a 0x83f50528:
> 4294775638 PID:3f5078e TID:3f5076a 0x83f50528: ndisMInitializeAdapter:
> Miniport 00052AF8,
> 4294775649 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>ndisQueueMiniportOnDriver: Miniport 00052AF8, MiniBlock 000528E0
> 4294775650 PID:3f5078e TID:3f5076a 0x83f50528:
> <==ndisQueueMiniportOnDriver: Miniport 00052AF8, MiniBlock 000528E0,
> rc 1
> 4294775652 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisMSetAttributesEx: Miniport 00052AF8
> 4294775654 PID:3f5078e TID:3f5076a 0x83f50528: ASYNCMAC:MpQueryInfo:
> OID 0x10116/Unknown OID not supported
> 4294775656 PID:3f5078e TID:3f5076a 0x83f50528: ASYNCMAC:MpQueryInfo:
> OID 0xFD010100/Unknown OID not supported
> ===
>
> These are for two other Miniport drivers that seem to load properly.
> However, when my driver loads up, I see the called to
> NdisMInitializeWrapper() being acknowledged and I also see the
> NdisMRegisterMiniport() being acknowledged. But at this point in time
> my InitializeHandler function should be getting called and I should
> see an indication of this by the debug message:
> "ndisMInitializeAdapter: Miniport XXXXXX" or something. But as you can
> see, I don't have anything like that. From there the driver is
> essentially ignored and the WinCE image fully loads with no WLAN
> access.
>
> Here's the log
> ===
> 4294775788 PID:3f5078e TID:3f5076a 0x83f50528: >>> Loading module
> sdiowlan.dll at address 0x010E0000-0x011A5000
> 4294775790 PID:3f5078e TID:3f5076a 0x83f50528: MRVDRVND5:
> DLL_PROCESS_ATTACH
> 4294775791 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] INIT - Enter
> DriverEntry
> 4294775792 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] *** Driver
> version 3.2 ***
> 4294775793 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] *** Built on
> Jl1 071:21 1:21 ***
> 4294775793 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisInitializeWrapper
> 4294775794 PID:3f5078e TID:3f5076a 0x83f50528:
> <==NdisInitializeWrapper
> 4294775795 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>NdisMRegisterMiniport: NdisWrapperHandle 00053450
> 4294775796 PID:3f5078e TID:3f5076a 0x83f50528:
> ==>ndisRegisterMiniportDriver: NdisWrapperHandle 00053450
> 4294775798 PID:3f5078e TID:3f5076a 0x83f50528:
> <==ndisRegisterMiniportDriver: MiniBlock 000534C0
> 4294775799 PID:3f5078e TID:3f5076a 0x83f50528: NdisMRegisterMiniport:
> MiniBlock 000534C0
> 4294775799 PID:3f5078e TID:3f5076a 0x83f50528:
> <==NdisMRegisterMiniport: MiniBlock 000534C0, Status 0
> 4294775800 PID:3f5078e TID:3f5076a 0x83f50528: [SDIOWLAN] <==
> DriverEntry: register miniport success
> ===
>
> Any ideas on how I can debug this???
>
> Regards

Nevermind..the issue was that I was not including the necessary SD
Host Controller driver which actually detects the insertion of the
SDIO card and in turn makes the NDIS sub-system initialize and use the
MiniPort driver..

I'm all set..

Regards

Top