Yasemin YILMAZ

ActiveSync Error 608 After the Installation of Wi-Fi Driver on i.MX233 WinCE6.0 Device

Discussion created by Yasemin YILMAZ on Jun 27, 2011
Hi all,

Error 608 communication error has been thrown when i.MX233 Windows Embedded CE-based device is connected to desktop pc through Activesync over USB connection after wi-fi driver has been installed. I’ve observed the problems below:

1. Windows CE "Control Panel -> Network and Dial up Connections" has an available ‘USB’ named connection that is used for establishing ActiveSync USB connections. It's properties dialog box has COM1 and COM2 devices that are selectable RAS devices. But now this combo-box is empty.
2. Windows CE "Control Panel -> Network and Dial up Connections->Make a Connection" dialog box has the types of connections that could be created (Dial up Connection, Direct Connection, L2TP Connection, PPTP Connection) and all of them have enabled. But these check-boxes become disable after the installation of Wi-Fi driver. So “Make a Connection” has no functionality now.
3. ActiveSync over USB Serial connection terminates with error code 608.

I've examined the differences between pre and post installation of wi-fi driver in debug log files. And I've realized that it reports a problem related to loading ndis.dll during the system initialization. I wonder whether I can change the load order of wi-fi driver (rwlpsdio.dll). Is it possible? Maybe, the problem can be solved if asynmac.dll or pptp.dll are firstly loaded?

Wi-Fi driver has thrown an exception, but this error message does not cause a Wi-Fi connection problem. The device can connect to wireless networks successfully. But it makes unusable RAS devices (COM1 and COM2).

I've controlled the drivers loaded on the system under the key of HKEY_LOCAL_MACHINE\Drivers\Active. There is a sub-key of the NDIS (NDS0) module under this key before the installation of Wi-Fi driver but then the system does not create the sub-key for NDIS (NDS0) during system initialization after the installation of Wi-Fi driver. I suppose the cause is the exception throwing by wi-fi driver during system initialization. Is there a way to reload the NDIS (NDS0) driver?

*********************************************************************************************************************
The system initalization debug log after the installation of Wi-Fi driver is below (I've filtered the messages related to NDIS):
*********************************************************************************************************************

OSAXST1: >>> Loading Module 'ndis.dll' (0x829FFBA0) at address 0xC0A00000-0xC0A64000 in Process 'NK.EXE' (0x821FBAA0)
NDIS: RebindAdaptersOnResume = 0
NDIS: PcmciaNeedsMapToScrap = 0

OSAXST1: >>> Loading Module 'rwlpsdio.dll' (0x82A5B3E4) at address 0xD0A00000-0xD0A27000 in Process 'NK.EXE' (0x821FBAA0)
Kernel DLL 'rwlpsdio.dll' needs thread creation/deletion notification

==>NdisInitializeWrapper
<==NdisInitializeWrapper

==>NdisMRegisterMiniport: NdisWrapperHandle D0921A80
==>ndisRegisterMiniportDriver: NdisWrapperHandle D0921A80
<==ndisRegisterMiniportDriver: MiniBlock D0921AE0

NdisMRegisterMiniport: MiniBlock D0921AE0
<==NdisMRegisterMiniport: MiniBlock D0921AE0, Status 0

ndisMInitializeAdapter: Miniport D0921CA8, ==>ndisQueueMiniportOnDriver: Miniport D0921CA8, MiniBlock D0921AE0
<==ndisQueueMiniportOnDriver: Miniport D0921CA8, MiniBlock D0921AE0, rc 1

Exception 'Data Abort' (4): Thread-Id=00a30002(pth=83fa5a04), Proc-Id=00400002(pprc=821fbaa0) 'NK.EXE', VM-active=00400002(pprc=821fbaa0) 'NK.EXE'
PC=d0a01844(rwlpsdio.dll+0x00001844) RA=d0a01834(rwlpsdio.dll+0x00001834) SP=d029dac0, BVA=00000804
Exception 'Raised Exception' (-1): Thread-Id=00a30002(pth=83fa5a04), Proc-Id=00400002(pprc=821fbaa0) 'NK.EXE', VM-active=00400002(pprc=821fbaa0) 'NK.EXE'
PC=c01046c0(k.coredll.dll+0x000446c0) RA=8026f5c4(kernel.dll+0x0001a5c4) SP=d029d288, BVA=ffffffff
DEVICE!LaunchDevice: exception in Init for device 0xd09213e0
DEVICE!LaunchDevice: Init() failed for device 0xd09213e0
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix NDS, index 0, dll NDIS.Dll, context 0xd029e684
DeviceFolder::LoadDevice(Drivers\BuiltIn\NDIS) last 513 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\SDHC\BusPrefix) returned 2
DeviceFolder::LoadDevice(Drivers\BuiltIn\SDHC) last 46 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PXP\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'pxp.dll' (0x82A5BC9C) at address 0xC10E0000-0xC10EB000 in Process 'NK.EXE' (0x821FBAA0)
PXP_DllEntry: DLL_PROCESS_ATTACH lpvReserved(0x802a99dc)
++PXP_Init
++PxpClass::PxpInit
++PxpClass::PxpEnable
--PxpClass::PxpEnable
PxpClass::PxpInit: create PXP ISR thread success
PxpClass::PxpInit: Enabling pixel pipeline
--PxpClass::PxpInit
PXP_Init - hDev=0xd0922420
--PXP_Init

*********************************************************************************************************************

*********************************************************************************************************************
The system initalization debug log before the installation of Wi-Fi driver is below:

*********************************************************************************************************************
OSAXST1: >>> Loading Module 'ndis.dll' (0x829FFBA0) at address 0xC0A00000-0xC0A64000 in Process 'NK.EXE' (0x821FBAA0)

NDIS: RebindAdaptersOnResume = 0
NDIS: PcmciaNeedsMapToScrap = 0

OSAXST1: >>> Loading Module 'rndisfn.dll' (0x82A5B024) at address 0xC0E00000-0xC0E1C000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: <<< Unloading Module 'rndisfn.dll' (0x82A5B024) at address 0xC0E00000-0xC0E1C000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: >>> Loading Module 'rndisfn.dll' (0x82A5B024) at address 0xC0E00000-0xC0E1C000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: <<< Unloading Module 'rndisfn.dll' (0x82A5B024) at address 0xC0E00000-0xC0E1C000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: >>> Loading Module 'vmini.dll' (0x82A5B024) at address 0xC0B80000-0xC0B8B000 in Process 'NK.EXE' (0x821FBAA0)
VBridge:: VB_INITIALIZED returns [0] VMini:: VBridge is not initialized! Bail out..
OSAXST1: <<< Unloading Module 'vmini.dll' (0x82A5B024) at address 0xC0B80000-0xC0B8B000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: >>> Loading Module 'asyncmac.dll' (0x82A5B024) at address 0xC06F0000-0xC0702000 in Process 'NK.EXE' (0x821FBAA0)

==>NdisInitializeWrapper
<==NdisInitializeWrapper

==>NdisMRegisterMiniport: NdisWrapperHandle D09219A0
==>ndisRegisterMiniportDriver: NdisWrapperHandle D09219A0
<==ndisRegisterMiniportDriver: MiniBlock D0921A00

NdisMRegisterMiniport: MiniBlock D0921A00
<==NdisMRegisterMiniport: MiniBlock D0921A00, Status 0

ndisMInitializeAdapter: Miniport D0921BC8, ==>ndisQueueMiniportOnDriver: Miniport D0921BC8, MiniBlock D0921A00
<==ndisQueueMiniportOnDriver: Miniport D0921BC8, MiniBlock D0921A00, rc 1

==>NdisMSetAttributesEx: Miniport D0921BC8
ASYNCMAC:MpQueryInfo: OID 0x10116/Unknown OID not supported
ASYNCMAC:MpQueryInfo: OID 0xFD010100/Unknown OID not supported
OSAXST1: >>> Loading Module 'pptp.dll' (0x82A5BF48) at address 0xC0710000-0xC074C000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: >>> Loading Module 'ws2k.dll' (0x82A5E0C0) at address 0xC0810000-0xC0837000 in Process 'NK.EXE' (0x821FBAA0)
==>NdisInitializeWrapper
<==NdisInitializeWrapper
==>NdisMRegisterMiniport: NdisWrapperHandle D0922580
==>ndisRegisterMiniportDriver: NdisWrapperHandle D0922580
<==ndisRegisterMiniportDriver: MiniBlock D09225C0
NdisMRegisterMiniport: MiniBlock D09225C0
<==NdisMRegisterMiniport: MiniBlock D09225C0, Status 0

ndisMInitializeAdapter: Miniport D0922780, ==>ndisQueueMiniportOnDriver: Miniport D0922780, MiniBlock D09225C0
<==ndisQueueMiniportOnDriver: Miniport D0922780, MiniBlock D09225C0, rc 1
==>NdisMSetAttributesEx: Miniport D0922780
-MiniportQueryInformation C00000BB
OSAXST1: >>> Loading Module 'l2tp.dll' (0x82A5D21C) at address 0xC0750000-0xC077C000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: >>> Loading Module 'k.iphlpapi.dll' (0x82A5D378) at address 0xC07A0000-0xC07BD000 in Process 'NK.EXE' (0x821FBAA0)
==>NdisInitializeWrapper
<==NdisInitializeWrapper
==>NdisMRegisterMiniport: NdisWrapperHandle D09230E0
==>ndisRegisterMiniportDriver: NdisWrapperHandle D09230E0
<==ndisRegisterMiniportDriver: MiniBlock D0923140
NdisMRegisterMiniport: MiniBlock D0923140
<==NdisMRegisterMiniport: MiniBlock D0923140, Status 0

ndisMInitializeAdapter: Miniport D0923300, ==>ndisQueueMiniportOnDriver: Miniport D0923300, MiniBlock D0923140
<==ndisQueueMiniportOnDriver: Miniport D0923300, MiniBlock D0923140, rc 1
## LOOKASIDE INITIALIZE ## [40] bytes, depth [1]
## LOOKASIDE INITIALIZE ## [24] bytes, depth [1]
## LOOKASIDE INITIALIZE ## [64] bytes, depth [1]
## LOOKASIDE INITIALIZE ## [64] bytes, depth [1]
## LOOKASIDE INITIALIZE ## [32] bytes, depth [1]
## LOOKASIDE INITIALIZE ## [156] bytes, depth [1]
==>NdisMSetAttributesEx: Miniport D0923300
OSAXST1: >>> Loading Module 'veim.dll' (0x82A5C900) at address 0xC0D20000-0xC0D2D000 in Process 'NK.EXE' (0x821FBAA0)
OSAXST1: >>> Loading Module 'k.dhcpsrv.dll' (0x82A5CA5C) at address 0xC0D30000-0xC0D36000 in Process 'NK.EXE' (0x821FBAA0)
==>NdisInitializeWrapper
<==NdisInitializeWrapper
==>NdisIMRegisterLayeredMiniport: NdisWrapperHandle D0924020
==>ndisRegisterMiniportDriver: NdisWrapperHandle D0924020
<==ndisRegisterMiniportDriver: MiniBlock D0924060
<==NdisIMRegisterLayeredMiniport: MiniBlock D0924060, Status 0
NDIS:: CE_DeleteBusFriendlyNames() failed deleting [HKLM\Comm\BusFriendlyNames]
NDIS:: CeGetPowerCapabilitiesForPm(): Adapter [L2TP1] is not power manageable.
NDIS:: CeGetPowerCapabilitiesForPm(): Adapter [PPTP1] is not power manageable.
NDIS:: CeGetPowerCapabilitiesForPm(): Adapter [ASYNCMAC1] is not power manageable.
DeviceFolder::LoadDevice(Drivers\BuiltIn\NDIS) last 792 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\SDHC\BusPrefix) returned 2
DeviceFolder::LoadDevice(Drivers\BuiltIn\SDHC) last 8 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PXP\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'pxp.dll' (0x82A5CE70) at address 0xC10E0000-0xC10EB000 in Process 'NK.EXE' (0x821FBAA0)
PXP_DllEntry: DLL_PROCESS_ATTACH lpvReserved(0x802a99dc)
[NOTIFY] HandleSystemEvent 7 /ADD NDS0:

++PXP_Init
++PxpClass::PxpInit
++PxpClass::PxpEnable
--PxpClass::PxpEnable
PxpClass::PxpInit: create PXP ISR thread success
PxpClass::PxpInit: Enabling pixel pipeline
--PxpClass::PxpInit
PXP_Init - hDev=0xd0924580
--PXP_Init

Is there any way to overcome this problem?

Thanks a lot for your helps and your explanations,
Best regards,

Yasemin

Outcomes