|
|
Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/14/2008 1:10 AM
post16549
|
Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi,
I am trying to get a Linksys WUSB54GC-AS USB Wireless adapter working which I believe should have a Ralink RT2501USB
chipset.
I can start the devnp-rum.so driver successfully using the command:
#io-pkt-v6-hc -v -d rum
The resulting slog is as follows:
----------------------------------------------------
Time Sev Major Minor Args
Jan 01 00:21:57 5 14 0 tcpip starting
Jan 01 00:21:57 3 14 0 Unable to attach to pci server: No such file or directory
Jan 01 00:21:57 3 14 0 Using pseudo random generator. See "random" option
Jan 01 00:21:57 5 14 0 initializing IPsec... done
Jan 01 00:21:57 5 14 0 IPsec: Initialized Security Association Processing.
Jan 01 00:21:57 5 14 0 USB device vendor 0x13b1, device 0x20 matched.
Jan 01 00:21:57 5 14 0 rum0 at pci0 dev 0 function 0rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:
2
1:29:de:ff:9e
Jan 01 00:21:57 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:21:57 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 01 00:21:57 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps
48Mb
ps 54Mbps
----------------------------------------------------
However once I set the interface status to up (using the command: ifconfig rum0 up), I get the following errors in slog:
----------------------------------------------------
Time Sev Major Minor Args
Nov 08 23:08:25 6 816493 1862 ite MAC register: NOMEM
Mar 22 22:57:57 2 204858 1782 544501614 1953265005 1920409705 543519849 541278541 1768383858 1919251571 1330520122
5
064013 799325 14 1448 812479858 1868767290 543452277 544501614 1953265005 1701978217 1293968481 1914716993 1936287589
980
575604 1297042976 19781 799357 14 1448 812479858 1868767290 543452277 544501614 1953265005 1920409705 543519849
541278541
1768383858 1919251571 1330520122 5064013 799421 14 1448 812479858 1868767290 543452277 544501614 1953265005 1701978217
1
293968481 1914716993 1936287589 980575604 1297042976 19781 799453 14 1448 812479858 1868767290 543452277 544501614
195326
5005 1920409705 543519849 541278541 1768383858 1919251571 1330520122 5064013 799517 14 1448 812479858 1868767290
54345227
7 544501614 1953265005 1701978217 1293968481 1914716993 1936287589 980575604 1297042976 19781 799549 14 1448 812479858
18
68767290 543452277 544501614 1953265005 1920409705 543519849 541278541 1768383858 1919251571 1330520122 5064013 799613
14
1448 812479858 1868767290 543452277 544501614 1953265005 1701978217 1293968481
Jan 27 06:06:44 1 616293 1846 1297042976 19781 799645 14 1448 812479858 1868767290 543452277 544501614 1953265005
19
20409705 543519849 541278541 1768383858 1919251571 1330520122 5064013 799709 14 1448 812479858 1868767290 543452277
54450
1614 1953265005 1701978217 1293968481 1914716993 1936287589 980575604 1297042976 19781
Jan 01 00:24:08 5 14 0 rum0: could not multi write MAC register: NOMEM
Jan 01 00:24:08 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:24:10 5 14 0 rum0: timeout waiting for BBP/RF to wakeup
Jan 01 00:24:10 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:24:10 5 14 0 rum0: could not multi write MAC register: NOMEM
----------------------------------------------------
Running USB, the device is detected as follows:
----------------------------------------------------
Device Address : 2
Upstream Host Controller : 0
Upstream Device Address : 1
Upstream Port : 4
Upstream Port Speed : Full
Vendor : 0x13b1 (Cisco-Linksys)
Product : 0x0020 (Compact Wireless-G USB Adapter)
Device Release : r0.01
USB Spec Release : v2.00
Serial Number : N/A
Class : 0x00 (Independent per...
View Full Message
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/14/2008 11:40 AM
post16585
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Although the device designation (WUSB-54GC-AS) is different from mine
(WUSB-54GC), the USB vendor and device appear to be the same, so it
should be working (I've tested it here and it works fine).
Is this on x86? Have you already stopped io-pkt-v4-hc which was
launched on boot?
The driver code is here
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev/u
sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
Here's where the failure appears to be occuring (in usb_do_request):
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy1001
&view=markup
So it looks like usbd_alloc is failing to allocate memory.
Are you operating in a very low memory situation ("pidin in" should
help)?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Friday, November 14, 2008 1:10 AM
To: general-networking
Subject: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi,
I am trying to get a Linksys WUSB54GC-AS USB Wireless adapter working
which I believe should have a Ralink RT2501USB chipset.
I can start the devnp-rum.so driver successfully using the command:
#io-pkt-v6-hc -v -d rum
The resulting slog is as follows:
----------------------------------------------------
Time Sev Major Minor Args
Jan 01 00:21:57 5 14 0 tcpip starting
Jan 01 00:21:57 3 14 0 Unable to attach to pci server: No such
file or directory
Jan 01 00:21:57 3 14 0 Using pseudo random generator. See
"random" option
Jan 01 00:21:57 5 14 0 initializing IPsec... done
Jan 01 00:21:57 5 14 0 IPsec: Initialized Security Association
Processing.
Jan 01 00:21:57 5 14 0 USB device vendor 0x13b1, device 0x20
matched.
Jan 01 00:21:57 5 14 0 rum0 at pci0 dev 0 function 0rum0:
MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:2
1:29:de:ff:9e
Jan 01 00:21:57 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:21:57 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps
11Mbps
Jan 01 00:21:57 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps
11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mb
ps 54Mbps
----------------------------------------------------
However once I set the interface status to up (using the command:
ifconfig rum0 up), I get the following errors in slog:
----------------------------------------------------
Time Sev Major Minor Args
Nov 08 23:08:25 6 816493 1862 ite MAC register: NOMEM
Mar 22 22:57:57 2 204858 1782 544501614 1953265005 1920409705
543519849 541278541 1768383858 1919251571 1330520122 5
064013 799325 14 1448 812479858 1868767290 543452277 544501614
1953265005 1701978217 1293968481 1914716993 1936287589 980
575604 1297042976 19781 799357 14 1448 812479858 1868767290 543452277
544501614 1953265005 1920409705 543519849 541278541
1768383858 1919251571 1330520122 5064013 799421 14 1448 812479858
1868767290 543452277 544501614 1953265005 1701978217 1
293968481 1914716993 1936287589 980575604 1297042976 19781 799453 14
1448 812479858 1868767290 543452277 544501614 195326
5005 1920409705 543519849 541278541 1768383858 1919251571 1330520122
5064013 799517 14 1448 812479858 1868767290 54345227
7 544501614 1953265005 1701978217 1293968481 1914716993 1936287589
980575604 1297042976 19781 799549 14 1448 812479858 18 68767290
543452277 544501614 1953265005 1920409705 543519849 541278541 1768383858
1919251571 1330520122 5064013 799613 14
1448 812479858 1868767290 543452277 544501614 1953265005 1701978217
1293968481
Jan 27 06:06:44 1 616293 1846 1297042976 19781 799645 14 1448
812479858 1868767290 543452277 544501614 1953265005 19
20409705 543519849 541278541 1768383858 1919251571 1330520122 5064013
799709 14 1448 812479858 1868767290 543452277 54450
1614 1953265005...
View Full Message
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/16/2008 6:48 PM
post16626
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert,
Thanks for the quick reply!
The system it is running on is an ARM-le device (Freescale i.MX31 ADS board).
Yes I stopped the instance of io-pkt-v4-hc loaded during bootup first.
In terms of memory, pidin in gives the following output:
CPU:ARM Release:6.4.0 FreeMem:106Mb/128Mb BootTime:Jan 01 00:00:00 UTC 1970
Processor1: 1091023716 arm1136 532MHz FPU
I would assume this is enough memory for the device?
> Although the device designation (WUSB-54GC-AS) is different from mine
> (WUSB-54GC), the USB vendor and device appear to be the same, so it
> should be working (I've tested it here and it works fine).
>
> Is this on x86? Have you already stopped io-pkt-v4-hc which was
> launched on boot?
>
> The driver code is here
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev/u
> sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
>
> Here's where the failure appears to be occuring (in usb_do_request):
>
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy1001
> &view=markup
>
>
> So it looks like usbd_alloc is failing to allocate memory.
>
> Are you operating in a very low memory situation ("pidin in" should
> help)?
>
> Robert.
>
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 4:56 PM
post16701
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That should be plenty.... Hmmmm.... I seem to remember that ARM is
somewhat strange when it comes to how much memory a process can use at
one time, but I seem to remember that we have had people using the
Linksys dongle on an ARM platform...
What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
running?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Sunday, November 16, 2008 6:48 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert,
Thanks for the quick reply!
The system it is running on is an ARM-le device (Freescale i.MX31 ADS
board).
Yes I stopped the instance of io-pkt-v4-hc loaded during bootup first.
In terms of memory, pidin in gives the following output:
CPU:ARM Release:6.4.0 FreeMem:106Mb/128Mb BootTime:Jan 01 00:00:00 UTC
1970
Processor1: 1091023716 arm1136 532MHz FPU
I would assume this is enough memory for the device?
> Although the device designation (WUSB-54GC-AS) is different from mine
> (WUSB-54GC), the USB vendor and device appear to be the same, so it
> should be working (I've tested it here and it works fine).
>
> Is this on x86? Have you already stopped io-pkt-v4-hc which was
> launched on boot?
>
> The driver code is here
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev
> /u
> sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
>
> Here's where the failure appears to be occuring (in usb_do_request):
>
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib
> /l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy10
> 01
> &view=markup
>
>
> So it looks like usbd_alloc is failing to allocate memory.
>
> Are you operating in a very low memory situation ("pidin in" should
> help)?
>
> Robert.
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16626
|
|
|
|
|
|
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 4:58 PM
post16702
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
Which procnto are you running? I think the imx31 can run procnto-v6 which would eliminate the 32Mb problem..
Robert Craig wrote:
> That should be plenty.... Hmmmm.... I seem to remember that ARM is
> somewhat strange when it comes to how much memory a process can use at
> one time, but I seem to remember that we have had people using the
> Linksys dongle on an ARM platform...
>
> What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
> running?
>
>
> Robert.
>
> -----Original Message-----
> From: Radek Pesina [mailto:community-noreply@qnx.com]
> Sent: Sunday, November 16, 2008 6:48 PM
> To: general-networking
> Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
> chipset)
>
> Hi Robert,
>
> Thanks for the quick reply!
>
> The system it is running on is an ARM-le device (Freescale i.MX31 ADS
> board).
>
> Yes I stopped the instance of io-pkt-v4-hc loaded during bootup first.
>
> In terms of memory, pidin in gives the following output:
>
> CPU:ARM Release:6.4.0 FreeMem:106Mb/128Mb BootTime:Jan 01 00:00:00 UTC
> 1970
> Processor1: 1091023716 arm1136 532MHz FPU
>
>
> I would assume this is enough memory for the device?
>
>
>
>
>> Although the device designation (WUSB-54GC-AS) is different from mine
>> (WUSB-54GC), the USB vendor and device appear to be the same, so it
>> should be working (I've tested it here and it works fine).
>>
>> Is this on x86? Have you already stopped io-pkt-v4-hc which was
>> launched on boot?
>>
>> The driver code is here
>> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev
>> /u
>> sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
>>
>> Here's where the failure appears to be occuring (in usb_do_request):
>>
>> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib
>> /l
>> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy10
>> 01
>> &view=markup
>>
>>
>> So it looks like usbd_alloc is failing to allocate memory.
>>
>> Are you operating in a very low memory situation ("pidin in" should
>> help)?
>>
>> Robert.
>>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post16626
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post16701
>
--
cburgess@qnx.com
|
|
|
|
|
|
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 5:11 PM
post16705
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert and Colin,
In terms of procnto, currently I am running procnto-v6.
Pidin reports the following with the rum driver running:
# pidin -p io-pkt-v4-hc mem
pid tid name prio STATE code data stack
12303 1 /boot/io-pkt-v4-hc 21r SIGWAITINFO 944K 500K 4096(132K)*
12303 2 /boot/io-pkt-v4-hc 21r RECEIVE 944K 500K 8192(132K)
12303 3 /boot/io-pkt-v4-hc 21r REPLY 944K 500K 4096(20K)
libc.so.3 @ 1000000 448K 12K
devnp-rum.so @78000000 64K 8192
> Which procnto are you running? I think the imx31 can run procnto-v6 which
> would eliminate the 32Mb problem..
>
>
> Robert Craig wrote:
> > That should be plenty.... Hmmmm.... I seem to remember that ARM is
> > somewhat strange when it comes to how much memory a process can use at
> > one time, but I seem to remember that we have had people using the
> > Linksys dongle on an ARM platform...
> >
> > What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
> > running?
> >
> >
> > Robert.
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 5:13 PM
post16706
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
So that all looks fine (I would have been worried if networking were
taking 32 MB!)
Do other USB devices work on the platform (e.g. mass storage devices)?
Can you post the output from
pidin ar
?
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Monday, November 17, 2008 5:11 PM
To: general-networking
Subject: Re: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert and Colin,
In terms of procnto, currently I am running procnto-v6.
Pidin reports the following with the rum driver running:
# pidin -p io-pkt-v4-hc mem
pid tid name prio STATE code data
stack
12303 1 /boot/io-pkt-v4-hc 21r SIGWAITINFO 944K 500K
4096(132K)*
12303 2 /boot/io-pkt-v4-hc 21r RECEIVE 944K 500K
8192(132K)
12303 3 /boot/io-pkt-v4-hc 21r REPLY 944K 500K
4096(20K)
libc.so.3 @ 1000000 448K 12K
devnp-rum.so @78000000 64K 8192
> Which procnto are you running? I think the imx31 can run procnto-v6
> which would eliminate the 32Mb problem..
>
>
> Robert Craig wrote:
> > That should be plenty.... Hmmmm.... I seem to remember that ARM is
> > somewhat strange when it comes to how much memory a process can use
> > at one time, but I seem to remember that we have had people using
> > the Linksys dongle on an ARM platform...
> >
> > What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
> > running?
> >
> >
> > Robert.
_______________________________________________
General
http://community.qnx.com/sf/go/post16705
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 5:21 PM
post16707
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Yes other USB devices work fine on the platform, so far USB hubs, memory card readers and USB flash drives work without
a problem.
Pidin output is as follows:
# pidin ar
pid Arguments
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5 0x43fb4000,47
3 slogger
4 pipe
5 fs-etfs-imx31ads_512 -r 1024
6 devf-mx31ads
7 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
8 spi-master -d mx31 base=0x50010000,irq=13,waitstate=2
4105 io-audio -v -d imx31ads
4106 io-display -v -dvid=0,did=0 -c/etc/system/config/display.conf
4107 i2c-imx31ads
4108 devb-umass cam pnp blk cache=2m,auto=partition,automount=hd0t14:/fs/usb0 dos exe=all
4109 qconn port=8000
4110 ksh
12303 io-pkt-v4-hc -v -d rum
49168 pidin ar
> So that all looks fine (I would have been worried if networking were
> taking 32 MB!)
>
> Do other USB devices work on the platform (e.g. mass storage devices)?
>
>
> Can you post the output from
>
> pidin ar
>
> ?
>
> R.
>
>
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/18/2008 11:21 AM
post16801
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
I'm really not sure what's happening with this one. I've confirmed that
the driver has been used extensively with an i.MX35 platform without any
problems.
Is devb-umass always running? How about slaying that and trying again?
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Monday, November 17, 2008 5:22 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Yes other USB devices work fine on the platform, so far USB hubs, memory
card readers and USB flash drives work without a problem.
Pidin output is as follows:
# pidin ar
pid Arguments
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5
0x43fb4000,47
3 slogger
4 pipe
5 fs-etfs-imx31ads_512 -r 1024
6 devf-mx31ads
7 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
8 spi-master -d mx31 base=0x50010000,irq=13,waitstate=2
4105 io-audio -v -d imx31ads
4106 io-display -v -dvid=0,did=0 -c/etc/system/config/display.conf
4107 i2c-imx31ads
4108 devb-umass cam pnp blk
cache=2m,auto=partition,automount=hd0t14:/fs/usb0 dos exe=all
4109 qconn port=8000
4110 ksh
12303 io-pkt-v4-hc -v -d rum
49168 pidin ar
> So that all looks fine (I would have been worried if networking were
> taking 32 MB!)
>
> Do other USB devices work on the platform (e.g. mass storage devices)?
>
>
> Can you post the output from
>
> pidin ar
>
> ?
>
> R.
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16707
|
|
|
|
|
|
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/18/2008 6:17 PM
post16842
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Okay I tried changing startup so devb-umass is not started and now after running "ifconfig rum0 up", slog reads a little
differently (and I can see the LED on the adapter flash a couple times during):
Time Sev Major Minor Args
Jan 01 00:01:14 5 14 0 tcpip starting
Jan 01 00:01:14 3 14 0 Unable to attach to pci server: No such file or directory
Jan 01 00:01:14 3 14 0 Using pseudo random generator. See "random" option
Jan 01 00:01:14 5 14 0 initializing IPsec... done
Jan 01 00:01:14 5 14 0 IPsec: Initialized Security Association Processing.
Jan 01 00:01:14 5 14 0 USB device vendor 0x13b1, device 0x20 matched.
Jan 01 00:01:15 5 14 0 rum0 at pci0 dev 0 function 0rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:
2
1:29:de:ff:9e
Jan 01 00:01:15 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:01:15 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 01 00:01:15 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps
48Mb
ps 54Mbps
Jan 01 00:05:50 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:05:50 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:05:50 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:05:55 5 14 0 rum0: device timeout
Jan 01 00:05:57 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:06 5 14 0 rum0: device timeout
Jan 01 00:06:08 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:12 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:06:12 5 14 0 rum0: could not transmit buffer: 24
Jan 01 00:06:14 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:17 5 14 0 rum0: device timeout
Jan 01 00:06:19 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Strange considering there is not that much difference between the i.MX31 and i.MX35.
> I'm really not sure what's happening with this one. I've confirmed that
> the driver has been used extensively with an i.MX35 platform without any
> problems.
>
> Is devb-umass always running? How about slaying that and trying again?
>
>
|
|
|
|
|
|
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/19/2008 1:51 PM
post16914
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hmmm... As soon as I see a single NOMEM then that's an error condition
that's problematic. All the errors are indicative of something being
wrong at the USB layer.
02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
STALL
0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because of the
initial CMP_ERR).
You can see where this message is generated in usb_handle_error in
usb_conv_qnx.c in
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy1001
&view=markup
How about a "pidin -p io-usb mem" to see what io-usb is doing with
memory?
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Tuesday, November 18, 2008 6:17 PM
To: general-networking
Subject: Re: RE: RE: Problems getting USB wireless working (Ralink
RT2501USB chipset)
Okay I tried changing startup so devb-umass is not started and now after
running "ifconfig rum0 up", slog reads a little differently (and I can
see the LED on the adapter flash a couple times during):
Time Sev Major Minor Args
Jan 01 00:01:14 5 14 0 tcpip starting
Jan 01 00:01:14 3 14 0 Unable to attach to pci server: No such
file or directory
Jan 01 00:01:14 3 14 0 Using pseudo random generator. See
"random" option
Jan 01 00:01:14 5 14 0 initializing IPsec... done
Jan 01 00:01:14 5 14 0 IPsec: Initialized Security Association
Processing.
Jan 01 00:01:14 5 14 0 USB device vendor 0x13b1, device 0x20
matched.
Jan 01 00:01:15 5 14 0 rum0 at pci0 dev 0 function 0rum0:
MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:2
1:29:de:ff:9e
Jan 01 00:01:15 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:01:15 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps
11Mbps
Jan 01 00:01:15 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps
11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mb
ps 54Mbps
Jan 01 00:05:50 5 14 0 rum0: could not multi read MAC
register: NOMEM
Jan 01 00:05:50 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:05:50 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:05:55 5 14 0 rum0: device timeout
Jan 01 00:05:57 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:06 5 14 0 rum0: device timeout
Jan 01 00:06:08 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 rum0: could not transmit buffer: 24
Jan 01 00:06:14 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:17 5 14 0 rum0: device timeout
Jan 01 00:06:19 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Strange considering there is not that much difference between the i.MX31
and i.MX35.
> I'm really not sure what's happening with this one. I've confirmed
> that the driver has been used extensively with an i.MX35 platform
> without any problems.
>
> Is devb-umass always running? How about slaying that and trying
again?
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16842
|
|
|
|
|
|
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/19/2008 1:51 PM
post16915
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hmmm... As soon as I see a single NOMEM then that's an error condition
that's problematic. All the errors are indicative of something being
wrong at the USB layer.
02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
STALL
0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because of the
initial CMP_ERR).
You can see where this message is generated in usb_handle_error in
usb_conv_qnx.c in
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy1001
&view=markup
How about a "pidin -p io-usb mem" to see what io-usb is doing with
memory?
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Tuesday, November 18, 2008 6:17 PM
To: general-networking
Subject: Re: RE: RE: Problems getting USB wireless working (Ralink
RT2501USB chipset)
Okay I tried changing startup so devb-umass is not started and now after
running "ifconfig rum0 up", slog reads a little differently (and I can
see the LED on the adapter flash a couple times during):
Time Sev Major Minor Args
Jan 01 00:01:14 5 14 0 tcpip starting
Jan 01 00:01:14 3 14 0 Unable to attach to pci server: No such
file or directory
Jan 01 00:01:14 3 14 0 Using pseudo random generator. See
"random" option
Jan 01 00:01:14 5 14 0 initializing IPsec... done
Jan 01 00:01:14 5 14 0 IPsec: Initialized Security Association
Processing.
Jan 01 00:01:14 5 14 0 USB device vendor 0x13b1, device 0x20
matched.
Jan 01 00:01:15 5 14 0 rum0 at pci0 dev 0 function 0rum0:
MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:2
1:29:de:ff:9e
Jan 01 00:01:15 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:01:15 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps
11Mbps
Jan 01 00:01:15 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps
11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mb
ps 54Mbps
Jan 01 00:05:50 5 14 0 rum0: could not multi read MAC
register: NOMEM
Jan 01 00:05:50 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:05:50 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:05:55 5 14 0 rum0: device timeout
Jan 01 00:05:57 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:06 5 14 0 rum0: device timeout
Jan 01 00:06:08 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 rum0: could not transmit buffer: 24
Jan 01 00:06:14 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:17 5 14 0 rum0: device timeout
Jan 01 00:06:19 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Strange considering there is not that much difference between the i.MX31
and i.MX35.
> I'm really not sure what's happening with this one. I've confirmed
> that the driver has been used extensively with an i.MX35 platform
> without any problems.
>
> Is devb-umass always running? How about slaying that and trying
again?
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16842
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/19/2008 5:58 PM
post16939
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Thanks for not giving up on the problem yet!
Below is the output after I ran "ifconfig rum0 up" on the device (it seemed to increase in memory usage a little after
doing so).
# pidin -p io-usb mem
pid tid name prio STATE code data stack
7 1 proc/boot/io-usb 10r SIGWAITINFO 92K 364K 8192(132K)*
7 2 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 3 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 4 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 5 proc/boot/io-usb 10r NANOSLEEP 92K 364K 4096(20K)
7 6 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 7 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
libc.so.3 @ 1000000 448K 12K
devu-ehci-mx31.so @78000000 28K 4096
/dev/mem @28000000 ( 0) 8192
Regards,
Radek.
> Hmmm... As soon as I see a single NOMEM then that's an error condition
> that's problematic. All the errors are indicative of something being
> wrong at the USB layer.
>
> 02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
> STALL
> 0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because of the
> initial CMP_ERR).
>
> You can see where this message is generated in usb_handle_error in
> usb_conv_qnx.c in
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy1001
> &view=markup
>
> How about a "pidin -p io-usb mem" to see what io-usb is doing with
> memory?
>
> R.
>
>
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 4:53 PM
post17013
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Nothin obvious there either.
Someone mentioned that there may be a conflict with audio and USB on
that platform. I'm not sure of the details and I would have thought
that it would have shown up with devb-umass, but it's worthwhile not
starting audio (and, just to make sure, anything else that you don't
really need...) and see if that changes the behaviour at all.
I'll have to try and dig up a platform somewhere and try for myself...
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 19, 2008 5:59 PM
To: general-networking
Subject: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Thanks for not giving up on the problem yet!
Below is the output after I ran "ifconfig rum0 up" on the device (it
seemed to increase in memory usage a little after doing so).
# pidin -p io-usb mem
pid tid name prio STATE code data
stack
7 1 proc/boot/io-usb 10r SIGWAITINFO 92K 364K
8192(132K)*
7 2 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 3 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 4 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 5 proc/boot/io-usb 10r NANOSLEEP 92K 364K
4096(20K)
7 6 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 7 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
libc.so.3 @ 1000000 448K 12K
devu-ehci-mx31.so @78000000 28K 4096
/dev/mem @28000000 ( 0) 8192
Regards,
Radek.
> Hmmm... As soon as I see a single NOMEM then that's an error
> condition that's problematic. All the errors are indicative of
> something being wrong at the USB layer.
>
> 02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
> STALL 0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because
> of the initial CMP_ERR).
>
> You can see where this message is generated in usb_handle_error in
> usb_conv_qnx.c in
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib
> /l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy10
> 01
> &view=markup
>
> How about a "pidin -p io-usb mem" to see what io-usb is doing with
> memory?
>
> R.
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16939
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 5:44 PM
post17018
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Okay I changed the startup script so only the bare minimum is started.
pid Arguments:
---------------------
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5 0x43fb4000,47
3 slogger
4 pipe
5 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
6 ksh
7 io-pkt-v4-hc -v -d rum
Unfortunately I'm still getting the same USB error.
Radek.
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 5:50 PM
post17019
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That's the initial NOMEM plus subsequent USB errors?
Looks like it's time to go hunting for hardware... I'm running out of
ideas.
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Thursday, November 20, 2008 5:44 PM
To: general-networking
Subject: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Okay I changed the startup script so only the bare minimum is started.
pid Arguments:
---------------------
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5
0x43fb4000,47
3 slogger
4 pipe
5 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
6 ksh
7 io-pkt-v4-hc -v -d rum
Unfortunately I'm still getting the same USB error.
Radek.
_______________________________________________
General
http://community.qnx.com/sf/go/post17018
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 5:55 PM
post17020
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Yes that's correct (I should have clarified that...), here's the slog:
Jan 01 00:00:02 5 14 0 initializing IPsec... done
Jan 01 00:00:02 5 14 0 IPsec: Initialized Security Association Processing.javascript:if%
20(validateCreatePost(document.createPost))%20{%20submitForm(document.createPost,%20'submit');%20}%20else%20{%20void(0)%
20}
Jan 01 00:00:02 5 14 0 USB device vendor 0x13b1, device 0x20 matched.
Jan 01 00:00:02 5 14 0 rum0 at pci0 dev 0 function 0rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:
2
1:29:de:ff:9e
Jan 01 00:00:02 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:00:02 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 01 00:00:02 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps
48Mb
ps 54Mbps
Jan 01 00:00:12 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:00:12 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:00:12 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:00:16 5 14 0 rum0: device timeout
Jan 01 00:00:19 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:00:26 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:00:27 5 14 0 rum0: device timeout
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/25/2008 10:10 PM
post17324
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert,
Just giving you a quick update. Since the i.MX31 PDK BSP is now available, I have downloaded the BSP and tried using
the wireless adapter on the PDK board. To my surprise the wireless adapter works fine on the PDK. I thought that maybe
libstartup or the USB driver itself may be different between the two, however they are identical.
Still no luck on the ADS board however.
Cheers,
Radek.
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 11:00 AM
post17387
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Radek:
Well THAT'S good news. I still don't have any idea why it won't
work on the ADS board... It'll probably have a bit of a lower priority
on my front now that you've shown it to be working on a similar
platform.
Oh... I just had a thought. One thing about some of these platforms is
that the USB ports don't provide enough power to drive the WiFi chips.
Can you plug the dongle into a powered USB hub and see if that changes
things at all?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Tuesday, November 25, 2008 10:11 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert,
Just giving you a quick update. Since the i.MX31 PDK BSP is now
available, I have downloaded the BSP and tried using the wireless
adapter on the PDK board. To my surprise the wireless adapter works
fine on the PDK. I thought that maybe libstartup or the USB driver
itself may be different between the two, however they are identical.
Still no luck on the ADS board however.
Cheers,
Radek.
_______________________________________________
General
http://community.qnx.com/sf/go/post17324
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:38 PM
post17426
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert,
And we have success! - you were spot on the money there, the ADS board doesn't seem to have enough power on the USB port
to run the Wifi adapter.
Thanks alot for your help.
> Hi Radek:
> Well THAT'S good news. I still don't have any idea why it won't
> work on the ADS board... It'll probably have a bit of a lower priority
> on my front now that you've shown it to be working on a similar
> platform.
>
> Oh... I just had a thought. One thing about some of these platforms is
> that the USB ports don't provide enough power to drive the WiFi chips.
> Can you plug the dongle into a powered USB hub and see if that changes
> things at all?
>
> Robert.
>
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:40 PM
post17427
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
I should have thought of that one earlier. We hit it once before. At
least now it's indelibly etched in my mind :->>
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 26, 2008 4:39 PM
To: general-networking
Subject: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert,
And we have success! - you were spot on the money there, the ADS board
doesn't seem to have enough power on the USB port to run the Wifi
adapter.
Thanks alot for your help.
> Hi Radek:
> Well THAT'S good news. I still don't have any idea why it won't
work
> on the ADS board... It'll probably have a bit of a lower priority on
> my front now that you've shown it to be working on a similar platform.
>
> Oh... I just had a thought. One thing about some of these platforms
> is that the USB ports don't provide enough power to drive the WiFi
chips.
> Can you plug the dongle into a powered USB hub and see if that changes
> things at all?
>
> Robert.
>
_______________________________________________
General
http://community.qnx.com/sf/go/post17426
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:47 PM
post17429
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
... and that's a lesson learnt for me too. It didn't cross my mind that it would not have sufficient power for a
wireless adapter - a portable harddrive or multiple devices yes, but not for a single adapter so thanks.
Now before I go chasing a wild goose with one of my intended uses for the wireless adapter, is it possible to do
ethernet-based debugging over wireless (i.e. qconn)? Reason being once we have our target hardware we will no longer
have the luxury of an ethernet connection.
Cheers,
Radek.
> I should have thought of that one earlier. We hit it once before. At
> least now it's indelibly etched in my mind :->>
>
> Robert.
>
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:52 PM
post17430
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That one had us scratching our heads for a while too. I'm actually
surprised that a hard drive works for you (as opposed to a flash based
drive...).
In any case, you should have no problems at all debugging over wireless.
From an app point of view, it's all Ethernet / IP at the end of the day
so once you get connected, the rest is good. Our QNET protocol works
over WiFi links as well.
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 26, 2008 4:47 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
... and that's a lesson learnt for me too. It didn't cross my mind that
it would not have sufficient power for a wireless adapter - a portable
harddrive or multiple devices yes, but not for a single adapter so
thanks.
Now before I go chasing a wild goose with one of my intended uses for
the wireless adapter, is it possible to do ethernet-based debugging over
wireless (i.e. qconn)? Reason being once we have our target hardware we
will no longer have the luxury of an ethernet connection.
Cheers,
Radek.
> I should have thought of that one earlier. We hit it once before. At
> least now it's indelibly etched in my mind :->>
>
> Robert.
>
_______________________________________________
General
http://community.qnx.com/sf/go/post17429
|
|
|
|
|
|
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 5:01 PM
post17432
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That's the answer I was hoping to hear, at least we will have an affordable debugging solution on our target hardware.
As for the hard drive, I haven't tried it yet, it was more a comment that I would expect a portable hdd to require a
powered hub and hence I would click to try powering it to fix the problem, but not a wireless adapter. It is on the
list of things to try though so if it does work I will let you know.
> That one had us scratching our heads for a while too. I'm actually
> surprised that a hard drive works for you (as opposed to a flash based
> drive...).
>
> In any case, you should have no problems at all debugging over wireless.
> From an app point of view, it's all Ethernet / IP at the end of the day
> so once you get connected, the rest is good. Our QNET protocol works
> over WiFi links as well.
>
> Robert.
>
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/08/2009 4:20 PM
post19690
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
I'm having similar problems get rum0 to work on an x86 PC. I've followed this thread as best as I could (even so far as
trying the wireless dongle in a powered USB hub).
When I power up the target, I get one of the following behaviors:
1 The USB device doesn't seem to be detected at all.
2 The USB device is detected but I get a boat load of the "" messages displayed by slogger.
3 The rum0 interface appears to come up (ifconfig shows it with a DHCP address) but I can't connect to the target via
the wireless interface.
Sometimes if the device isn't detected during power up, if I remove it and insert it in a different USB port it will be
detected (at least to the point where ifconfig shows the rum0 interface).
Thanks,
Gordon Molek
Zebra Technologies Corporation
|
|
|
|
|
|