Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
WLAN Driver on WinCE 6.0
41 views
Skip to first unread message
fredfromfrance
Dec 21, 2009, 10:09:02 AM12/21/09
to
Hi, i'm integrating a WiFi driver on a device based on Freescale iMx21 under
WindowsCE6.0. I've troubles with this driver, sometimes, the authentification
with a access point is ok, sometimes not. When it's KO, i've the following
error reports by the NDISUIO layer :
UIO:: >> Read time out or forced out.. <<
WindowsCE6.0. I've troubles with this driver, sometimes, the authentification
with a access point is ok, sometimes not. When it's KO, i've the following
error reports by the NDISUIO layer :
UIO:: >> Read time out or forced out.. <<
Someone have an idea ?
Thank you
Paul G. Tobey [ eMVP ]
Dec 21, 2009, 1:57:01 PM12/21/09
to
You're going to have to isolate something further, I bet, as to what the
actual problem with authentication is. The device is always in the same
location? There's no radio problem communicating with the AP? The signal
strength, when the connection works, is Excellent? The authentication type
is what? What other authentication types have you tried?
actual problem with authentication is. The device is always in the same
location? There's no radio problem communicating with the AP? The signal
strength, when the connection works, is Excellent? The authentication type
is what? What other authentication types have you tried?
Paul T.
fredfromfrance
Dec 28, 2009, 3:18:01 AM12/28/09
to
Thank you for your answer;.
No, there is not radio problem. I've a good experience in WLAN integration
and i know that the problem is due to the driver or the interface between the
driver and the NDIS layer. The authentication i use is PEAP with WPA-TKIP
key. It is the same thing if i use a WPA-preshared key.
No, there is not radio problem. I've a good experience in WLAN integration
and i know that the problem is due to the driver or the interface between the
driver and the NDIS layer. The authentication i use is PEAP with WPA-TKIP
key. It is the same thing if i use a WPA-preshared key.
Paul G. Tobey [ eMVP ]
Dec 29, 2009, 4:42:01 PM12/29/09
to
So, PEAP is not a great choice, since it requires that there be some sort of
server operational against which to verify your identity. WPA-PSK failing
suggests that there is some sort of real communications problem, but I would
still verify that your AP (this is what's doing the verification of the PSK,
yes?), doesn't have a log telling you that something is wrong when your
device connects.
server operational against which to verify your identity. WPA-PSK failing
suggests that there is some sort of real communications problem, but I would
still verify that your AP (this is what's doing the verification of the PSK,
yes?), doesn't have a log telling you that something is wrong when your
device connects.
It would also be worthwhile to verify WEP. I don't suppose that your card
or your driver for it has a means to adjust the MAC address, does it? That
wouldn't be an invalid address, by any chance? I've seen all sorts of odd
problems when an Ethernet address of an adapter was FFFFFFFFFFFF...
Since, generally, those authentication types work (assuming you included EAP
support), I'd guess that the driver is at fault, but have no idea where
inside the driver to look for a problem. The last time I checked, there
wasn't a good sample driver that supported WPA available from Microsoft. You
could check that, though.
Paul T.
fredfromfrance
Dec 30, 2009, 4:34:01 AM12/30/09
to
Thank you for your point of view.
I could have te same problem without using any security on the AP. So it's
not due to the fact that the driver doesn't support WPA mode.
The MAC address of my device is correct.
But i don't why but when the driver is loaded, ne NDISPWR level reports :
NDISPWR:: BIND notification for adapter [OWL221A1]
2 times.
With our old module, this log appears just on time. It strange, no ?
I could have te same problem without using any security on the AP. So it's
not due to the fact that the driver doesn't support WPA mode.
The MAC address of my device is correct.
But i don't why but when the driver is loaded, ne NDISPWR level reports :
NDISPWR:: BIND notification for adapter [OWL221A1]
2 times.
With our old module, this log appears just on time. It strange, no ?
Tjank you
Paul G. Tobey [ eMVP ]
Dec 31, 2009, 4:14:01 PM12/31/09
to
Microsoft didn't do a fabulous job of documenting exactly what network
drivers are supposed to do and when, so there are many minor differences from
one adapter's driver to another. That sounds like what you've got here, just
some situation where the driver is reporting a connection when (a) happens,
but also when (b) happens and sometimes the sequence is (a)..(b). The driver
could certainly be adjusted to report correctly, but I wouldn't assume that
this is the source of any problem. Just generally not connecting to the
access point at all, regardless of security, sounds like the driver is just
broken, is not the right driver for the hardware you are using, or that you
have some hardware characteristic that the device doesn't expect and isn't
handling correctly (could be bus timing, etc., etc.)
drivers are supposed to do and when, so there are many minor differences from
one adapter's driver to another. That sounds like what you've got here, just
some situation where the driver is reporting a connection when (a) happens,
but also when (b) happens and sometimes the sequence is (a)..(b). The driver
could certainly be adjusted to report correctly, but I wouldn't assume that
this is the source of any problem. Just generally not connecting to the
access point at all, regardless of security, sounds like the driver is just
broken, is not the right driver for the hardware you are using, or that you
have some hardware characteristic that the device doesn't expect and isn't
handling correctly (could be bus timing, etc., etc.)
0 new messages