Re: How to get USB / Ethernet (NIC) working on MS Windows CE 5.0 ?

Hi Luc & others :
I finally acquired the Wireless USR5421 (RNDIS-Class device).
However, when I plug in the USR5421 into the USB port of our product
running WinCE 5.0, I get the following errors : !OHCD: Td error
USB_DEVICE_NOT_RESPONDING_ERROR............................

Upon getting the device descriptor, it FAILS with the error USB device
NOT responding.

PB debug log :
----------------------

4294867844 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::InitiateGeneralTransfer
4294867846 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::GetDeviceDescriptor
4294867848 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::GetInitialDeviceDescriptor
4294867851 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::HandleConnectChange
4294867853 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD:
HcInterruptStatus = 0x00000046, HcInterruptEnable = 0x80000073
4294867855 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD: Writeback Done
4294867857 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::HandleWritebackDone paDoneHead = 520
4294867860 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: !OHCD: Td error
USB_DEVICE_NOT_RESPONDING_ERROR
4294867862 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: +OHCD::DeQueueTdList
4294867865 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: DeQueueTDList:
TD:2B1520, pTrans:2016C0 CC:5, paNext:0
4294867867 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: !OHCD: Dev 0 Endpoint
0 halted, TD error 0x5
4294867869 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::CompleteTransfer
4294867871 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: Ohcd: Warning, failed
to do initial config on new device (state 2 -
GettingInitialDescriptor). Retrying
4294867873 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD:Resetting root
hub port (status 0x103)
4294867875 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: -OHCD::DeQueueTdList
4294867877 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::HandleWritebackDone
4294867879 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD: RootHub Status
Change
4294867881 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::HandleConnectChange
4294867883 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::HandleConnectChange
4294867886 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD:
HcInterruptStatus = 0x00000044, HcInterruptEnable = 0x80000073
4294867888 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD: RootHub Status
Change
4294867890 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::HandleConnectChange
4294867904 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::GetInitialDeviceDescriptor
4294867906 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::GetDeviceDescriptor
4294867908 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
FreeSize = 4088 bytes; TotalSize = 4096 bytes
4294867910 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
Nodes Free = 0
4294867912 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
FreeSize = 4088 bytes; TotalSize = 4096 bytes
4294867914 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
Nodes Free = 0
4294867916 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : FreeMemory : VA
= 0x002B1800, PA = 0x00000800, flags = 0x00000000
4294867918 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD: FREE!!!!!! Block
at VA = 0x002B1800, PA = 0x00000800, flags = 0x00000000 was freed in
File: c:\wince500\platform\n40\drivers\usb\mdd_hcd\ohcd\ohcd.cpp, Line
#: 5236
4294867921 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
FreeSize = 2040 bytes; TotalSize = 2048 bytes
4294867923 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
Nodes Free = 0
4294867925 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : AllocateMemory
: VA = 0x002B1808, PA = 0x00000808, size = 8
4294867927 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
FreeSize = 2032 bytes; TotalSize = 2048 bytes
4294867929 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD : ValidateHeaps :
Nodes Free = 0
4294867931 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD: ALLOC!!!!! Block
at VA = 0x002B1808, PA = 0x00000808, size = 8 was allocated in File:
c:\wince500\platform\n40\drivers\usb\mdd_hcd\ohcd\ohcd.cpp, Line #:
5242
4294867934 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::InitiateGeneralTransfer
4294867936 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD:Control (DEV
201580): GET_DESCRIPTOR Val: 256, Idx: 0, Len: 8
4294867938 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD:TD 0x2B1520, IN
BP:808, len:8
4294867940 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::InitiateGeneralTransfer
4294867943 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::GetDeviceDescriptor
4294867945 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::GetInitialDeviceDescriptor
4294867948 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
-OHCD::HandleConnectChange
4294867950 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD:
HcInterruptStatus = 0x00000046, HcInterruptEnable = 0x80000073
4294867952 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: OHCD: Writeback Done
4294867954 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4:
+OHCD::HandleWritebackDone paDoneHead = 570
4294867956 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: !OHCD: Td error
USB_DEVICE_NOT_RESPONDING_ERROR
4294867958 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: +OHCD::DeQueueTdList
4294867960 PID:affb6a86 TID:6fd6327e 0x8fd5ecd4: DeQueueTDList:
TD:2B1570,

I would be very thankful if someone could clarify.

Thanks,
-DES

Luc Cool wrote:
Hi,

as voidcoder mentioned, it is not because a usb 2 ethernet uses the kawasaki
chipset that it is rndis compatible as well.

You mention the tests with the NETGEAR FA120. According to the internet,
that unit uses the ASIX chipset.

As I told already on this newsgroup, you can find drivers for windows CE 5.0
for their chipset.

Just, no version for the hitachi cpu group. (SH3 SH4) Maybe, if you contact
them, they can deliver you a CE driver for SH4. After all, it should just be
a recompilation with other CPU settings.
I tried to contact them and asked them for devices using their chipset. I
never got any response. I hope you have better luck.

regards,

Luc

"DES" <descasals@xxxxxxxxx> wrote in message
news:1163700245.201751.320850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi voidcoder, Luc Cool :
Your suggestions were very helpful.

I plugged in the NETGEAR FA120 into my desktop PC running Windows XP
and it is operational.
In Device Manager->Properties->Details, upon selecting 'Instance ID',
the following is displayed :
USB\VID-0846&PID-1040\5&9DA6B9A&0&2
I could not identify any Class or Interface information.

The above VID and PID are displayed in my Platform Builder 'Debug'
window upon plugging in the FA120 into the USB port of our WinCE
product running 5.0 (debug log attached) :

4294823168 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8:
+OHCD::CompleteTransfer
4294823170 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8:
OHCD::CompleteTransfer: pDev 0x219660, addr 1, config state:
7(SettingConfig)
4294823172 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8:
+OHCD::DoneInitialDeviceSetup, pDev:0x219660 addr:1
4294823173 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Dev.bLength =
0x12
4294823175 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Dev.bDescriptorType = 0x01
4294823177 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Dev.bcdUSB =
0x0200
4294823179 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Dev.bDeviceClass
= 0x02
4294823181 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Dev.bDeviceSubClass = 0x00
4294823183 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Dev.bDeviceProtocol = 0x00
4294823184 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Dev.bMaxPacketSize0 = 0x08
4294823186 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Dev.idVendor =
0x0846
4294823188 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Dev.idProduct =
0x1040
4294823189 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Dev.bcdDevice =
0x0001
4294823191 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Dev.iManufacturer = 0x01
4294823192 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Dev.iProduct =
0x02
4294823194 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Dev.iSerialNumber = 0x00
4294823196 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Dev.bNumConfigurations = 0x01
4294823197 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
CurrentConfiguration = 0x01
4294823199 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD: Config.bLength
= 0x09
4294823201 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Config.bDescriptorType = 0x02
4294823202 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Config.wTotalLength = 0x0027
4294823204 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Config.bNumInterfaces = 0x01
4294823206 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Config.bConfigurationValue = 0x01
4294823208 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Config.iConfiguration = 0x00
4294823210 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Config.bmAttributes = 0xA0
4294823212 PID:8ffb6b12 TID:4fd62fd2 0x8fd624d8: OHCD:
Config.MaxPower = 0x96

From the above log, the USB device (FA120) is recognized :
Dev.idVendor = 0x0846 (NETGEAR), Dev.idProduct = 0x1040 (FA120),
Dev.bDeviceClass = 0x02, Dev.bDeviceSubClass = 0x00,
Dev.bDeviceProtocol = 0x00

Why is Subclass = 0x00 and DeviceProtocol = 0x00 ?

As per your suggestion, as our product running WinCE is the USB Host
and the FA120 is the Remote NDIS device, I have deleted USB
Function->USB Function Clients->RNDIS Function Client from the OS
Design.

I verified Catalog->Core OS services->Communications Services and
Networking->Networking Local Area Network (LAN)->Wired Local Area
Network (802.3, 802.5)->All the paths for the drivers and RNDIS, NDIS
miniport drivers are listed.

I have removed the RNDIS related registry settings (which I had added
earlier) from platform.reg

I checked my WinCE500\PLATFORM\xx\xx.bat (xx=platform) and BSP_NORNDIS
is NOT defined.

I have verified my ................/SH4_Debug/ directory and I have ALL
the relevant .dlls :
rndisfn.dll, rndismp.dll, usb8023.dll, usbd.dll, usbdisk6.dll,
usbprn.dll, usbhid.dll, USBMSC.dll, USBModem.dll
I called Netgear and Linksys and both could NOT confirm that Netgear
EA101 and Linksys USB100T are RNDIS-compatible. Their on-line technical
specifications do not mention RNDIS at all!

If you are 100% sure that the RNDIS-compatibility is my root problem, I
shall buy EA101 and "try it out" as Luc has pointed out.

Thanks very much,
-Des


Luc Cool wrote:
Hi voidcoder,

i have to agree with you. One thing that comes in my mind is the
question
why people using chipsets in their devices might want to reinvent the
wheel?

The chipset is the only reference we have for the moment to assume that
a
USB 2 ethernet device "could be" rndis compatible. I recently contacted
US
robotics support to ask if their USR5423 was still RNDIS compatible and
got
the following answer:

We believe it still should be compatible , however the USR5421 is not
tested
on Windows CE and nor do we have the opportunity to test this.

The USR5423 has an Atheros chipset and if this is supported by Windows
CE
then it should work.

So, the chipset is different from the USR5421... and the chipset company
doesn't mention the word RNDIS once in their specifications....

This only leaves "trying things out" as a option. Posting the results in
this newsgroup might help against reinventions of the wheel.

But DES is looking for a wired device. So, USR is not in the game.

regards,

Luc


"voidcoder" <voidcoder@xxxxxxxxx> wrote in message
news:uRtq8qVCHHA.4224@xxxxxxxxxxxxxxxxxxxxxxx

As I understand, it is not really a rule. Even the chipset
is described as RNDIS compatible (what I think means that
the chipset manufacturer is providing ready to use RNDIS
enabled firmware or some sort of RNDIS SDK for their chipset),
the final adapter manufacturer may choice to not use this
feature in their device.


Luc Cool wrote:
Hi,

Thanks Voidcoder for the info about the US Robotics chipset.

As Paul explains, if the chipset is RNDIS compatible, it should work
with
the CE provided driver.

I searched the web, and found a list of adapters that are supposed
to
use
the Kawasaki chipset:

Kawasaki LSI KL5KUSB101B-based USB adapters:

3Com 3c19250
3Com 3c460 HomeConnect
AboCom Systems URE450 Ethernet
ADS Technologies USB-10BT
Aox USB101
Asante USB to Ethernet
ATen DSB-650C
ATen UC10T
Corega USB-T
D-Link DSB-650C
Entrega NET-USB-E45
I/O Data USB-ET/T
Jaton USB XpressNet
Kawasaki USB101
Kingston Ethernet
Linksys USB10T
Mobility Ethernet
Netgear EA101
Peracom USB
Portgear Ethernet
Portsmith Express Ethernet
Psion Dacom Gold Port Ethernet
Shark Pocket Adapter
Silicom U2E
SMC 2102USB
SMC 2104USB

it is kind of strange the Silicom U2E is in the list, while I am
sure it
should be the U2ES.

The list might be incomplete. However, it is a starting point.

regards.


"DES" <descasals@xxxxxxxxx> wrote in message
news:1163613215.233726.18710@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your response. Upon going thro' the tech. specs. for
USR5421, it listed 98SE / 2000 / ME / XP as the operating systems
supported. CE was not amomg them. Also, the connection protocol is
IEEE
802.11 (as it is Wireless). We have 802.3 (wired ethernet) driver.
Reg. U2ES, it is out of production as you had pointed out, however
I'm
researching U2ESC (the next generation product). I'm in the process
of
researching whether it supports WinCE.

Thanks,
DES

voidcoder wrote:
Is NETGEAR FA120 RNDIS class device? If not, why do you
try to use RNDIS driver for it?

You won't have much success with non RNDIS USB Ethernet
adapters, unless the manufacturer is providing CE drivers
for it.

Don't know any supported wired USB to Ethernet adapters,
but you may want to check wireless. There is a number of
RNDIS based USB WLAN adapters (like USR5421) supported
on CE. Anyway, Google is your friend.


DES wrote:
I need to get USB / Ethernet working on MS Windows CE 5.0.
Firstly, which device supports it ?
I was trying to use NETGEAR FA120. According to the tech. manual,
Win
CE is NOT supported.

We are using Windows CE ver. 5.0 in our product and I have been
trying
to get the RNDIS working; but have not been successful so far.
I have a NETGEAR Model FA120 USB / Ethernet adapter (NIC) plugged
into
the USB port of our product running WinCE 5.0.

Is NETGEAR FA120 supported on Windows CE ? Their spec. does not
list
Win CE (it lists 98, ME, 2000 and XP)

As soon as I plug in the NETGEAR NIC, I get the message
'Unidentified
USB Device' on my application console.
When I type the Driver name 'USB8023.DLL', I get the message :

4294860032 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: >>> Loading
module
rndismp.dll at address 0x03660000-0x03674000 (RW data at
0x01F6A000-0x01F6A894)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\RNDISMP.DLL'
4294860036 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: >>> Loading
module
usb8023.dll at address 0x03680000-0x03697000 (RW data at
0x01F6C000-0x01F6C5A7)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\USB8023.DLL'

4294861129 PID:4ffb6b3a TID:ac53bc2 0x8abe1400:
ParseUsbDescriptors
failed!
4294861132 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: Invalid Parameter

4294861134 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: RNDISMP:
DllUnload
called!
4294861137 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: <<< Unloading
module
usb8023.dll at address 0x03680000-0x03697000 (RW data at
0x01F6C000-0x01F6C5A7)
Unloaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\USB8023.DLL'
4294861141 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: <<< Unloading
module
rndismp.dll at address 0x03660000-0x03674000 (RW data at
0x01F6A000-0x01F6A894)
Unloaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\RNDISMP.DLL'
4294861204 PID:8fdedd56 TID:ac53bc2 0x8abe1400: DlgMgr:
FindDlgItem
id
1 returning NULL.

I believe RNDISMP.DLL and USB8023.DLL are part of WinCE 5.0. How
can
I
get it working so that the driver of the USB / Ethernet NIC
plugged
into the USB port is recognized ?
We do not have the source code for USB8023.DLL (part of Microsoft
library).

The USB port itself on our product works as plugging a USB flash
drive
works.





.

Relevant Pages