ArmadeusWiki - User contributions [en]

Talk:USB to WiFi adapter

2012-09-26T16:04:35Z

Sly: /* Workaround */

== About Zydas zd1211 tries ==
[[User:JulienB|JulienB]] 09:52, 4 February 2009 (UTC) : now working

== Chipset RTL8188CUS ==

I will give you the details for the RTL8188CUS driver for the APF28:
# the build procedure
# the error I got for AFP28 with AFP28dev
# and the workaround to fix it

===Build procedure===
I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 .
You can get the driver here (chose RTL8188CUS) :
[http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true]

Add those option in the makefile :
<pre class="host">
- change line 39 :
CONFIG_PLATFORM_I386_PC = n
- add line 40 :
CONFIG_PLATFORM_ARM_ARMADEUS = y

- Near line 261 add:
ifeq ($(CONFIG_PLATFORM_ARM_ARMADEUS), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WEXT_PRIV
ARCH := arm
CROSS_COMPILE := /path-to-your/armadeus/buildroot/output/host/usr/bin/arm-linux-
KVER := 2.6.35.3
KSRC ?= /path-to-your/armadeus/buildroot/output/build/linux-2.6.35.3
endif
</pre>

And I need to rebuild the linux kernel with define WEXT_PRIV :
<pre class="host">
make linux-menuconfig
</pre>

I use this trick for that :
<pre class="config">
Device Drivers --->
[*] Network device support --->
[*] Wireless LAN --->
<M> USB ZD1201 based Wireless device support
</pre>

Which give me :
<pre class="config">
│ Selects: WIRELESS_EXT [=y] && WEXT_PRIV [=n] && FW_LOADER [=y]
</pre>
Rebuild the kernel :
<pre class="host">
make linux-rebuild
</pre>
finally copy the driver to the target directory :
<pre class="host">
cp 8192cu.ko /path-to-your/armadeus/buildroot/output/target/lib/modules/2.6.35.3\+/kernel/drivers/net/wireless/
</pre>

===Known issue===
Here is the test I made :
<pre class="apf">
insmod /lib/modules/2.6.35.3\+/kernel/drivers/net/wireless/8192cu.ko
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
udhcpc -i wlan0
</pre>
Then I can ping wifi adress with 0% packet loss.

I connect with ssh it work ok for the few command I did.

'''Then I try to connect with SFTP from my PC (using FileZilla) :'''

'''the wifi goes down and the usb with it.'''

Here is the part of "messages" where the error is :
<pre class="host">
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:1
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:2
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:3
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: fatal error
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal command 010028 (park)=0 ithresh=1 Async period=256 HALT
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal status 49098 Async Halt FATAL FLR
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: reset command 01002a (park)=0 ithresh=1 Async period=256 Reset HALT
Jan 10 01:23:29 armadeus kern.warn kernel: ###=> usb_read_port_complete => urb status(-108)
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: HC died; cleaning up
Jan 10 01:23:29 armadeus kern.debug kernel: hub 2-0:1.0: state 0 ports 1 chg 0000 evt 0000
Jan 10 01:23:29 armadeus kern.info kernel: usb 2-1: USB disconnect, address 2
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering device
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: usb_disable_device nuking all URBs
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering interface 2-1:1.0
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:4
Jan 10 01:23:29 armadeus kern.warn kernel: [dvobjpriv:c8aa401c][ERROR] continual_urb_error:5 > 4
Jan 10 01:23:29 armadeus kern.warn kernel: issue_deauth to 00:18:84:19:e1:62
Jan 10 01:23:29 armadeus kern.warn kernel: rtw_sta_flush
Jan 10 01:23:30 armadeus kern.warn kernel: (2)871x_drv - drv_close, bup=1, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: -871x_drv - drv_close, bup=1
Jan 10 01:23:30 armadeus kern.warn kernel: ===> rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: usb_read_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: usb_write_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: ###> rtw_cmd_thread break.................
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... check & free all cmd_obj resources
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
Jan 10 01:23:30 armadeus kern.warn kernel: <=== rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: +r871xu_dev_remove, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: free_recv_skb_queue not empty, 5
Jan 10 01:23:30 armadeus kern.warn kernel: =====> rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: <===== rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: -r871xu_dev_remove, done
Jan 10 01:23:40 armadeus kern.err kernel: FEC: MDIO read timeout
Jan 10 01:23:42 armadeus kern.err kernel: FEC: MDIO read timeout
</pre>

And the error by using iperf -c to connect to an iperf server :

<pre class="host">
fsl-ehci fsl-ehci.0: fatal error
###=> usb_read_port_complete => urb status(-108)
fsl-ehci fsl-ehci.0: HC died; cleaning up
usb 2-1: USB disconnect, address 2
+rtw_dev_remove
rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:1
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:2
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:3
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:4
[dvobjpriv:c8abd01c][ERROR] continual_urb_error:5 > 4
issue_deauth to 00:18:84:19:e1:62
rtw_sta_flush
(2)871x_drv - drv_close, bup=1, hw_init_completed=1
-871x_drv - drv_close, bup=1
===> rtw_dev_unload
usb_read_port_cancel
usb_write_port_cancel
###> rtw_cmd_thread break.................
rtw_cmd_thread: leaving... check & free all cmd_obj resources
rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
<=== rtw_dev_unload
+r871xu_dev_remove, hw_init_completed=1
free_recv_skb_queue not empty, 4
=====> rtl8192c_free_hal_data =====
<===== rtl8192c_free_hal_data =====
-r871xu_dev_remove, done
FEC: MDIO read timeout
FEC: MDIO read timeout
</pre>

--[[User:Sly|Sly]] 20:33, 31 July 2012 (UTC)

It should work now with the last git dev branch (5.1)
===old Workaround===
Here is the workaround to fix this issue:
Disable dynamic frequency scaling by setting the scaling_governor to "userspace" or "performance"
====1st solution: change governor at runtime====

<pre class="apf">
echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
</pre>
you will have to use this command each time you boot your board.

====2nd solution: rebuild your kernel with default governor set to userspace or performance====
<pre class="host">
make linux-menuconfig
</pre>

<pre class="config">
CPU Power Management --->
Default CPUFreq governor (userspace) --->
( ) performance
( ) powersave
(X) userspace
( ) ondemand
( ) conservative
</pre>

build and update your APF kernel..

USB to WiFi adapter

2012-09-26T16:01:28Z

Sly: /* Tested hardware */

How-to use USB to Wi-Fi adapters on your APF boards.

==Prerequesities==
{{Note| You have to be sure that [[Wireless Tools]] are installed on your rootfs before going further.}}

* To use USB dongles with [[APF9328]], you'll need an [[APF9328DevFull]] development board, with USB Host configured. See [[ISP1761_Linux_driver|this page]] to know how to do that.

==Tested hardware==
{| border="1" cellpadding="5" cellspacing="0" summary="microSDs"
|- style="background:#efefef;"
! rowspan="2" | '''Constructor''' || rowspan="2" | '''Model''' || colspan="4" | '''Status''' || rowspan="2" | '''Chipset'''
|----- style="background:#efefef;"
| '''APF9328''' || '''APF27''' || '''APF51''' || '''APF28'''
|----------------
| rowspan="3" | '''D-Link''' || [http://www.ldlc.com/fiche/PB00023863.html DWL-G122] '''(not rev E1 !)''' || style="background:#00ff00;" | OK || style="background:#00ff00;" | OK || NT || NT || rowspan="2" | Ralink RT2571WF
|----------------
| WPA-110 || style="background:#00ff00;" | OK || style="background:#00ff00;" | OK || NT || NT
|----------------
| DWA-140 || NT || NT || NT || style="background:#ff0000;" | KO || Ralink RT2870
|----------------
| '''SMC''' || WUSB-G || NT || style="background:#00ff00;" | OK || NT || NT || ZyDas zd1212
|----------------
| '''Realtek''' || RTL8188CUS || NT || NT || NT || style="background:#00ff00;" | OK || RTL8188CUS [[Talk:USB_to_WiFi_adapter#Chipset_RTL8188CUS |see discussion]]
|}

==Ralink RT2571WF==
The RT2571WF Wi-Fi chipset can be found in the following devices:
* [http://www.ldlc.com/fiche/PB00023863.html D-Link DWL-G122] '''(not rev E1 !)'''
* D-Link WPA-110

Drivers are included in Linux kernel > 2.6.29, but firmware must be downloaded from serialmonkey website at [http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz this address].

===Kernel configuration===

* If not already done, Wireless network must be configured by selecting these options in ''make linux-menuconfig'':
<pre class="config">
[*] Networking support --->
Wireless --->
<*> Generic IEEE 802.11 Networking Stack (mac80211)
</pre>

* then, select the chipset :
<pre class="config">
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Wireless LAN (IEEE 802.11)
<M> Ralink driver support
<M> Ralink rt2501/rt73 (USB) support
</pre>

===Wi-Fi configuration===

First mount the module:
<pre class=apf>
# modprobe rt73usb
</pre>

Then copy the firmware named ''rt73.bin'' (found in Module directory of
[http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz rt73-cvs] archive) in apf /lib/firmware directory. If /lib/firmware doesn't exist create it.

<pre class=apf>
mkdir -p /lib/firmware
tftp -g -r rt73.bin <yourIP>
mv rt73.bin /lib/firmware
</pre>

Your Wi-Fi module driver is ready, you can now connect the dongle and after go further with the [[WiFi|Wi-Fi configuration]].

==Ralink RT2870==
* Activate the driver in Linux configuration (if not already done):
<pre class=host>
$ make linux-menuconfig
</pre>
* Load driver
<pre class=apf>
# modprobe rt2800_usb
</pre>
* Be sure to have rt2870.bin in /lib/firmware

==ZyDas zd1212 chipset==
* Tested with SMC WUSB-G (which is in [http://www.linuxwireless.org/en/users/Drivers/zd1211rw/devices the compatibility list]).
**[http://www.ldlc.com/fiche/PB00067971.html Go here to buy this device in France (LDLC)]
** Other ways to get it ?

====Configure Linux====
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
[*] Networking support --->
Wireless --->
<*> Generic IEEE 802.11 Networking Stack (mac80211)

Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Wireless LAN (IEEE 802.11)
...
<M> ZyDAS ZD1211/ZD1211B USB-wireless support
[*] ZyDAS ZD1211 debugging
</pre>

<pre class="host">
$ make linux26 && make
</pre>

Reinstall your system.

====Get firmware====
* http://zd1211.ath.cx/get-firmware
* copy the archive to your TFTP export directory

====Install firmware on your APF====
<pre class=apf>
# mkdir -p /lib/firmware/
# cd /lib/firmware/
# tftp -g -r zd1211-firmware-1.4.tar.bz2 192.168.0.17
# bunzip2 zd1211-firmware-1.4.tar.bz2
# tar xf zd1211-firmware-1.4.tar
# mv zd1211-firmware zd1211
</pre>

====Connect your USB adapter====
<pre class=apf>
usb 1-1: new high speed USB device using mxc-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: New USB device found, idVendor=083a, idProduct=4505
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=0
usb 1-1: Product: USB2.0 WLAN
usb 1-1: Manufacturer: SMC
</pre>

====Launch driver====
<pre class=apf>
# modprobe zd1211rw
usb 1-1: reset high speed USB device using mxc-ehci and address 2
zd1211rw 1-1:1.0: phy0
usbcore: registered new interface driver zd1211rw

# ifconfig wlan0 up
firmware: requesting zd1211/zd1211b_ub
firmware: requesting zd1211/zd1211b_uphr
</pre>

===Realtek rtl8187===
[http://www.linuxwireless.org/en/users/Drivers/rtl8187 Compatibility list] <br>
Tested devices:
* Netgear WG111v3

====Configure Linux====
<pre class="host">
$ make linux26-menuconfig
</pre>

<pre class="config">
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Wireless LAN (IEEE 802.11)
...
<M> Realtek 8187 and 8187B USB support
</pre>

<pre class="host">
$ make linux26 && make
</pre>

====Launch driver====
<pre class=apf>
# modprobe rtl8187
cfg80211: Calling CRDA to update world regulatory domain
ieee80211 phy0: hwaddr 00:22:3f:df:2c:04, RTL8187BvE V0 + rtl8225z2, rfkill mask 2
rtl8187: wireless switch is on
usbcore: registered new interface driver rtl8187

# ifconfig wlan0 up
ADDRCONF(NETDEV_UP): wlan0: link is not ready
</pre>

==To go further==
* [[WiFi| Configure your Wi-Fi network interface]]
* [[Links | Browse the net (in text mode) from your terminal]]

==Links==
* [http://www.linuxwireless.org/en/users/Drivers/zd1211rw zd1211 driver on linuxwireless.org]

[[Category:Network]]
[[Category:WiFi]]
[[Category:USB]]

Talk:USB to WiFi adapter

2012-09-25T14:46:09Z

Sly: /* Build procedure */

== About Zydas zd1211 tries ==
[[User:JulienB|JulienB]] 09:52, 4 February 2009 (UTC) : now working

== Chipset RTL8188CUS ==

I will give you the details for the RTL8188CUS driver for the APF28:
# the build procedure
# the error I got for AFP28 with AFP28dev
# and the workaround to fix it

===Build procedure===
I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 .
You can get the driver here (chose RTL8188CUS) :
[http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true]

Add those option in the makefile :
<pre class="host">
- change line 39 :
CONFIG_PLATFORM_I386_PC = n
- add line 40 :
CONFIG_PLATFORM_ARM_ARMADEUS = y

- Near line 261 add:
ifeq ($(CONFIG_PLATFORM_ARM_ARMADEUS), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WEXT_PRIV
ARCH := arm
CROSS_COMPILE := /path-to-your/armadeus/buildroot/output/host/usr/bin/arm-linux-
KVER := 2.6.35.3
KSRC ?= /path-to-your/armadeus/buildroot/output/build/linux-2.6.35.3
endif
</pre>

And I need to rebuild the linux kernel with define WEXT_PRIV :
<pre class="host">
make linux-menuconfig
</pre>

I use this trick for that :
<pre class="config">
Device Drivers --->
[*] Network device support --->
[*] Wireless LAN --->
<M> USB ZD1201 based Wireless device support
</pre>

Which give me :
<pre class="config">
│ Selects: WIRELESS_EXT [=y] && WEXT_PRIV [=n] && FW_LOADER [=y]
</pre>
Rebuild the kernel :
<pre class="host">
make linux-rebuild
</pre>
finally copy the driver to the target directory :
<pre class="host">
cp 8192cu.ko /path-to-your/armadeus/buildroot/output/target/lib/modules/2.6.35.3\+/kernel/drivers/net/wireless/
</pre>

===Known issue===
Here is the test I made :
<pre class="apf">
insmod /lib/modules/2.6.35.3\+/kernel/drivers/net/wireless/8192cu.ko
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
udhcpc -i wlan0
</pre>
Then I can ping wifi adress with 0% packet loss.

I connect with ssh it work ok for the few command I did.

'''Then I try to connect with SFTP from my PC (using FileZilla) :'''

'''the wifi goes down and the usb with it.'''

Here is the part of "messages" where the error is :
<pre class="host">
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:1
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:2
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:3
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: fatal error
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal command 010028 (park)=0 ithresh=1 Async period=256 HALT
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal status 49098 Async Halt FATAL FLR
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: reset command 01002a (park)=0 ithresh=1 Async period=256 Reset HALT
Jan 10 01:23:29 armadeus kern.warn kernel: ###=> usb_read_port_complete => urb status(-108)
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: HC died; cleaning up
Jan 10 01:23:29 armadeus kern.debug kernel: hub 2-0:1.0: state 0 ports 1 chg 0000 evt 0000
Jan 10 01:23:29 armadeus kern.info kernel: usb 2-1: USB disconnect, address 2
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering device
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: usb_disable_device nuking all URBs
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering interface 2-1:1.0
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:4
Jan 10 01:23:29 armadeus kern.warn kernel: [dvobjpriv:c8aa401c][ERROR] continual_urb_error:5 > 4
Jan 10 01:23:29 armadeus kern.warn kernel: issue_deauth to 00:18:84:19:e1:62
Jan 10 01:23:29 armadeus kern.warn kernel: rtw_sta_flush
Jan 10 01:23:30 armadeus kern.warn kernel: (2)871x_drv - drv_close, bup=1, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: -871x_drv - drv_close, bup=1
Jan 10 01:23:30 armadeus kern.warn kernel: ===> rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: usb_read_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: usb_write_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: ###> rtw_cmd_thread break.................
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... check & free all cmd_obj resources
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
Jan 10 01:23:30 armadeus kern.warn kernel: <=== rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: +r871xu_dev_remove, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: free_recv_skb_queue not empty, 5
Jan 10 01:23:30 armadeus kern.warn kernel: =====> rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: <===== rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: -r871xu_dev_remove, done
Jan 10 01:23:40 armadeus kern.err kernel: FEC: MDIO read timeout
Jan 10 01:23:42 armadeus kern.err kernel: FEC: MDIO read timeout
</pre>

And the error by using iperf -c to connect to an iperf server :

<pre class="host">
fsl-ehci fsl-ehci.0: fatal error
###=> usb_read_port_complete => urb status(-108)
fsl-ehci fsl-ehci.0: HC died; cleaning up
usb 2-1: USB disconnect, address 2
+rtw_dev_remove
rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:1
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:2
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:3
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:4
[dvobjpriv:c8abd01c][ERROR] continual_urb_error:5 > 4
issue_deauth to 00:18:84:19:e1:62
rtw_sta_flush
(2)871x_drv - drv_close, bup=1, hw_init_completed=1
-871x_drv - drv_close, bup=1
===> rtw_dev_unload
usb_read_port_cancel
usb_write_port_cancel
###> rtw_cmd_thread break.................
rtw_cmd_thread: leaving... check & free all cmd_obj resources
rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
<=== rtw_dev_unload
+r871xu_dev_remove, hw_init_completed=1
free_recv_skb_queue not empty, 4
=====> rtl8192c_free_hal_data =====
<===== rtl8192c_free_hal_data =====
-r871xu_dev_remove, done
FEC: MDIO read timeout
FEC: MDIO read timeout
</pre>

--[[User:Sly|Sly]] 20:33, 31 July 2012 (UTC)

===Workaround===
Here is the workaround to fix this issue:
Disable dynamic frequency scaling by setting the scaling_governor to "userspace" or "performance"
====1st solution: change governor at runtime====

<pre class="apf">
echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
</pre>
you will have to use this command each time you boot your board.

====2nd solution: rebuild your kernel with default governor set to userspace or performance====
<pre class="host">
make linux-menuconfig
</pre>

<pre class="config">
CPU Power Management --->
Default CPUFreq governor (userspace) --->
( ) performance
( ) powersave
(X) userspace
( ) ondemand
( ) conservative
</pre>

build and update your APF kernel..

Talk:USB to WiFi adapter

2012-09-25T14:43:42Z

Sly: /* Build procedure */

== About Zydas zd1211 tries ==
[[User:JulienB|JulienB]] 09:52, 4 February 2009 (UTC) : now working

== Chipset RTL8188CUS ==

I will give you the details for the RTL8188CUS driver for the APF28:
# the build procedure
# the error I got for AFP28 with AFP28dev
# and the workaround to fix it

===Build procedure===
I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 .
You can get the driver here (chose RTL8188CUS) :
[http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true]

Add those option in the makefile :
<pre class="host">
- change line 39 :
CONFIG_PLATFORM_I386_PC = n
- add line 40 :
CONFIG_PLATFORM_ARM_ARMADEUS = y

- Near line 261 add:
ifeq ($(CONFIG_PLATFORM_ARM_ARMADEUS), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WEXT_PRIV
ARCH := arm
CROSS_COMPILE := /path-to-your/armadeus/buildroot/output/host/usr/bin/arm-linux-
KVER := 2.6.35.3
KSRC ?= /path-to-your/armadeus/buildroot/output/build/linux-2.6.35.3
endif
</pre>

And I need to rebuild the linux kernel with define WEXT_PRIV.
<pre class="host">
make linux-menuconfig
</pre>

I use this trick for that :
<pre class="config">
Device Drivers --->
[*] Network device support --->
[*] Wireless LAN --->
<M> USB ZD1201 based Wireless device support
</pre>

Which give me :
<pre class="config">
│ Selects: WIRELESS_EXT [=y] && WEXT_PRIV [=n] && FW_LOADER [=y]
</pre>

finally copy the driver to the target directory:
<pre class="host">
cp 8192cu.ko /path-to-your/armadeus/buildroot/output/target/lib/modules/2.6.35.3\+/kernel/drivers/net/wireless/
</pre>

===Known issue===
Here is the test I made :
<pre class="apf">
insmod /lib/modules/2.6.35.3\+/kernel/drivers/net/wireless/8192cu.ko
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
udhcpc -i wlan0
</pre>
Then I can ping wifi adress with 0% packet loss.

I connect with ssh it work ok for the few command I did.

'''Then I try to connect with SFTP from my PC (using FileZilla) :'''

'''the wifi goes down and the usb with it.'''

Here is the part of "messages" where the error is :
<pre class="host">
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:1
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:2
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:3
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: fatal error
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal command 010028 (park)=0 ithresh=1 Async period=256 HALT
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal status 49098 Async Halt FATAL FLR
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: reset command 01002a (park)=0 ithresh=1 Async period=256 Reset HALT
Jan 10 01:23:29 armadeus kern.warn kernel: ###=> usb_read_port_complete => urb status(-108)
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: HC died; cleaning up
Jan 10 01:23:29 armadeus kern.debug kernel: hub 2-0:1.0: state 0 ports 1 chg 0000 evt 0000
Jan 10 01:23:29 armadeus kern.info kernel: usb 2-1: USB disconnect, address 2
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering device
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: usb_disable_device nuking all URBs
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering interface 2-1:1.0
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:4
Jan 10 01:23:29 armadeus kern.warn kernel: [dvobjpriv:c8aa401c][ERROR] continual_urb_error:5 > 4
Jan 10 01:23:29 armadeus kern.warn kernel: issue_deauth to 00:18:84:19:e1:62
Jan 10 01:23:29 armadeus kern.warn kernel: rtw_sta_flush
Jan 10 01:23:30 armadeus kern.warn kernel: (2)871x_drv - drv_close, bup=1, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: -871x_drv - drv_close, bup=1
Jan 10 01:23:30 armadeus kern.warn kernel: ===> rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: usb_read_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: usb_write_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: ###> rtw_cmd_thread break.................
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... check & free all cmd_obj resources
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
Jan 10 01:23:30 armadeus kern.warn kernel: <=== rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: +r871xu_dev_remove, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: free_recv_skb_queue not empty, 5
Jan 10 01:23:30 armadeus kern.warn kernel: =====> rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: <===== rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: -r871xu_dev_remove, done
Jan 10 01:23:40 armadeus kern.err kernel: FEC: MDIO read timeout
Jan 10 01:23:42 armadeus kern.err kernel: FEC: MDIO read timeout
</pre>

And the error by using iperf -c to connect to an iperf server :

<pre class="host">
fsl-ehci fsl-ehci.0: fatal error
###=> usb_read_port_complete => urb status(-108)
fsl-ehci fsl-ehci.0: HC died; cleaning up
usb 2-1: USB disconnect, address 2
+rtw_dev_remove
rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:1
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:2
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:3
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:4
[dvobjpriv:c8abd01c][ERROR] continual_urb_error:5 > 4
issue_deauth to 00:18:84:19:e1:62
rtw_sta_flush
(2)871x_drv - drv_close, bup=1, hw_init_completed=1
-871x_drv - drv_close, bup=1
===> rtw_dev_unload
usb_read_port_cancel
usb_write_port_cancel
###> rtw_cmd_thread break.................
rtw_cmd_thread: leaving... check & free all cmd_obj resources
rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
<=== rtw_dev_unload
+r871xu_dev_remove, hw_init_completed=1
free_recv_skb_queue not empty, 4
=====> rtl8192c_free_hal_data =====
<===== rtl8192c_free_hal_data =====
-r871xu_dev_remove, done
FEC: MDIO read timeout
FEC: MDIO read timeout
</pre>

--[[User:Sly|Sly]] 20:33, 31 July 2012 (UTC)

===Workaround===
Here is the workaround to fix this issue:
Disable dynamic frequency scaling by setting the scaling_governor to "userspace" or "performance"
====1st solution: change governor at runtime====

<pre class="apf">
echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
</pre>
you will have to use this command each time you boot your board.

====2nd solution: rebuild your kernel with default governor set to userspace or performance====
<pre class="host">
make linux-menuconfig
</pre>

<pre class="config">
CPU Power Management --->
Default CPUFreq governor (userspace) --->
( ) performance
( ) powersave
(X) userspace
( ) ondemand
( ) conservative
</pre>

build and update your APF kernel..

Talk:WPA supplicant

2012-08-14T03:47:01Z

Sly: New page: Dans : <pre class="apf"> # wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient </pre> le "dhclient" ne fait pas parti des mot clef de wpa_supplicant, et semble inutile !...

Dans :
<pre class="apf">
# wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
</pre>
le "dhclient" ne fait pas parti des mot clef de wpa_supplicant, et semble inutile !
--[[User:Sly|Sly]] 03:47, 14 August 2012 (UTC)

WPA supplicant

2012-08-14T03:43:28Z

Sly: /* Links */

When dealing with "strong" encryption of WiFi networks, you have to setup a WPA or WPA2 configuration.
To handle the requirements of these protocols during association, a userspace daemon is needed: it is called a WPA supplicant.
The most used one on Linux is ''wpa_supplicant''; we will see here how to install and configure it.

{{Note|wpa_supplicant is also able to handle WEP connections}}

==Installation==
<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Package Selection for the target --->
Networking --->
[*] wpa_supplicant
[ ] Enable WPA with EAP
[*] Install wpa_cli binary
[ ] Install wpa_passphrase binary
</pre>

EAP is only needed if you plan to use WPA in Enterprise mode == with a Radius server.

==Usage==
wpa_supplicant needs a configuration file in ''/etc/wpa_supplicant.conf''.
Here is an example:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="''SSID''"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
psk="''PASSPHRASE''"
}

Then you can create the Wifi connexion with WPA Supplicant:
<pre class="apf">
# ifconfig wlan0 up
# wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
</pre>

==Stop it==
To stop WPA Supplicant daemon and switch off the connexion, you can use this command:
<pre class="apf">
# wpa_cli terminate
</pre>

==Links==
* [http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/README wpa_supplicant README]
* [http://hostap.epitest.fi/wpa_supplicant/ wpa_supplicant Webpage]

[[Category:Wireless]]
[[Category:Security]]
[[Category:WiFi]]

WPA supplicant

2012-08-14T03:42:35Z

Sly: /* Links */

WiFi

2012-08-14T03:40:51Z

Sly: /* Links */

==Pre-requites==
{{Note| To configure Wi-Fi you need to [[Wireless Tools| install wireless tools]] first (done by default for APF27 / PPS / APF51) and of course to have a running Wi-Fi interface like: the [[Libertas_driver|one on APW extension board or PPS devt board]] or a [[USB_to_WiFi_adapter|USB to Wi-Fi adapter]], with corresponding Linux drivers loaded.}}

==Common operations==
====List network interfaces supporting Wi-Fi====
<pre class=apf>
# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality:0/100 Signal level:112/146 Noise level:0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
</pre>
{{Note|Here our Wi-Fi network interface is called ''wlan0''. Depending on the number of your network interfaces or their model, this name could change. For example if using the Libertas drivers, the interface will be called ''eth1'' (if ''eth0'' is already used). In that case replace ''wlan0'' with your interface name.}}

====Activate the WLAN interface====
<pre class=apf>
# ifconfig wlan0 up
</pre>
==== Show all Access Points (AP) available for your APF (here with wlan0 interface) ====
<pre class=apf>
# iwlist wlan0 scan

wlan0 Scan completed :
Cell 01 - Address: XX:XX:XX:66:47:48
ESSID:"TOTO"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=88/100 Signal level:25/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000009d398fec8
Extra: Last beacon: 1390ms ago
...
</pre>

==== Connect to an unencrypted AP ====
<pre class=apf>
# iwconfig wlan0 essid AP_NAME
</pre>
* Check it:
<pre class=apf>
# iwconfig wlan0
</pre>

==== Get an IP address ====
<pre class=apf>
# udhcpc -i wlan0
</pre>

==Encryption settings==
When configuring Wi-Fi cryptography, only WEP can be setup easily from a terminal with single commands. If you want to configure your interface for WPA/WPA2, install and configure [[WPA supplicant|wpa_supplicant]].

==== WEP configuration ====

This example is given for a Wi-Fi Access Point named ''armadeus'', the encoding key used here is not recommended, of course ;) :

<pre class=apf>
# iwconfig wlan0 essid armadeus
# iwconfig wlan0 key 12345678901234567890
# ifconfig wlan0 up (if interface is not already up)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
# ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
</pre>

Now, the Wi-Fi adapter is ready and attached :
<pre class=apf>
# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"armadeus"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1B:2F:E7:E4:08
Bit Rate=2 Mb/s Tx-Power=7 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:XXXXXXXXXXXXXXXXXXXXXXXXXX Security mode:restricted
Power Management:off
Link Quality:0/100 Signal level:73/146 Noise level:0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

</pre>

==Accessing outside world==
We can manually configure the network to access Internet via the Wi-Fi interface instead of the Ethernet one:

<pre class=apf>
# ifconfig eth0 down
# ifconfig wlan0 192.168.0.212
# route add default gw 192.168.0.1 dev wlan0
</pre>

And configure the nameserver in /etc/resolv.conf
<pre class=apf>
domain dev.null
nameserver 192.168.0.207
~
~
~
</pre>

If you have a DHCP server on your network, you can also use it and previous steps (route+resolv.conf) will be done automatically:
<pre class=apf>
# udhcpc -i wlan0
</pre>

We can now ping the best website in the world :
<pre class=apf>
# ping www.armadeus.org
PING www.armadeus.org (213.186.33.5): 56 data bytes
64 bytes from 213.186.33.5: seq=0 ttl=122 time=66.735 ms
64 bytes from 213.186.33.5: seq=1 ttl=122 time=50.392 ms
^C
--- www.armadeus.org ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 50.392/58.563/66.735 ms
</pre>

== Surf on the net ==

To surf on the web, you can use (for example) ''links'' software :
<pre class=apf>
# links www.armadeus.org
</pre>

It's an ASCII internet browser. [[Links| For more informations about Links]].

==Links==
* [[Wireless_Tools|Wireless Tools installation]]
* [[USB_to_WiFi_adapter|USB to Wi-Fi adapters tested with Armadeus boards]]
* [[Network_interface_bandwidth_measurement| Measure the bandwidth of your interface]]
* [[WPA_supplicant|WPA_supplicant]]

[[Category:WiFi]]

GPIO LEDS

2012-08-08T18:30:32Z

Sly: /* Usage */ full path is better

How to use leds-gpio driver to manage states of connected leds of your Armadeus board.

==Introduction==

You can manage a led connected to a GPIO pin. The LED management is similar with the standard GPIO sysfs driver, but you have some new features like triggers (e.g. "heartbeat" LED blinks like a heart at the rate oh the CPU load) . Here are the GPIO used for the user LED for each APF board:
* APF9328: PORT A / bit 2
* APF27: GPIO_PORTF | 14
* APF28: PINID_GPMI_RDY1 (Bank 0 - pin 21)
* APF51: GPIO_PORTA | 2

==Configuration==

First, you need to enable the leds-gpio driver in your kernel and some triggers like the "heartbeat" trigger to make the LED flash like a heartbeat.

<pre class="config">
Device Drivers --->
--- LED support
[*] LED Class Support
*** LED drivers ***
<*> LED Support for GPIO connected LEDs
[*] Platform device bindings for GPIO LEDs
*** LED Triggers ***
[*] LED Trigger support
<*> LED Timer Trigger
<*> LED Heartbeat Trigger
<*> LED backlight Trigger
<*> LED Default ON Trigger
</pre>

Then, in your ''apfXX-dev.c'', you would need to define your LED <b>before</b> the variable ''platform_devices[]''. This code is already implemented for the APF27, APF28 and APF51 so the source code hereafter (for the APF27) is only present as a reference sample to understand how to activate a GPIO LED driver.

<source lang="c">

#include <linux/leds.h>

/* GPIO LED */
#if defined(CONFIG_LEDS_GPIO) || defined(CONFIG_LEDS_GPIO_MODULE)
static struct gpio_led apf27dev_led[] = {
{
.name = "apfdev:green:user",
.default_trigger = "heartbeat",
.gpio = (GPIO_PORTF | 14),
.active_low = 1,
},
};

static struct gpio_led_platform_data apf27dev_led_data = {
.num_leds = ARRAY_SIZE(apf27dev_led),
.leds = apf27dev_led
};

static struct platform_device apf27dev_led_dev = {
.name = "leds-gpio",
.id = -1,
.dev = {
.platform_data = &apf27dev_led_data,
},
};
#endif /* CONFIG_LEDS_GPIO */
</source>

Add the LED to get it managed by the kernel.

<source lang="c">
static struct platform_device *platform_devices[] __initdata = {
#if defined(CONFIG_LEDS_GPIO) || defined(CONFIG_LEDS_GPIO_MODULE)
&apf27dev_led_dev,
#endif
ALSA_SOUND

};
</source>

Then rebuild and update your bard with the new kernel.
Upon the next kernel boot you should see the LED flash like a heartbeat (if you have activated the "heartbeat" trigger)

==Usage==
<pre class="apf">
# ls /sys/class/leds/apfdev\:green\:user/
brightness max_brightness subsystem uevent
device power trigger
</pre>

You can change the trigger behaviors. By default, Heartbeat is selected:
* "heatbeat": led blinks like a heart and blink frequency will change according o the CPU activity.
* "nand-disk": the led will blink each time nand access occur (try with ''sync'' command to see it blinking).
<pre class="apf">
# cat /sys/class/leds/apfdev\:green\:user/trigger
none nand-disk mmc0 timer [heartbeat] backlight gpio default-on

# echo none > /sys/class/leds/apfdev\:green\:user/trigger
</pre>

Switch on and off the LED

<pre class="apf">
# cat /sys/class/leds/apfdev\:green\:user/max_brightness > /sys/class/leds/apfde
v\:green\:user/brightness

# echo 0 > /sys/class/leds/apfdev\:green\:user/brightness
</pre>

It is possible to switch led state using the APF28Dev user button. This button is seen as gpio17 (as seen under APF28Dev [[datasheet]]) under Linux, then configure the led trigger as gpio :

<pre class="apf">
# echo "gpio" > /sys/class/leds/apfdev:green:user/trigger
</pre>

New config files are available :
<pre class="apf">
# ls /sys/class/leds/apfdev:green:user/
brightness gpio power uevent
desired_brightness inverted subsystem
device max_brightness trigger
</pre>

Then the trigger gpio can be configured with ''gpio'' file :

<pre class="apf">
# echo 17 > /sys/class/leds/apfdev:green:user/gpio
</pre>

Then pushing the user switch will now commute the LED state.

==Links==
* http://www.kernel.org/doc/Documentation/leds/leds-class.txt

Talk:USB to WiFi adapter

2012-07-31T21:19:45Z

Sly: /* 3)Here is the part of "messages" where the error is : */

== About Zydas zd1211 tries ==
[[User:JulienB|JulienB]] 09:52, 4 February 2009 (UTC) : now working

== Chipset RTL8188CUS ==

I will give you the detail for the RTL8188CUS driver error I got for AFP28 with AFP28devdev.

===1)I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 .===
You can get the driver here (chose RTL8188CUS) :
[http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true]

Add those option in the makefile :
<pre class="host">
- change line 39 :
CONFIG_PLATFORM_I386_PC = n
- add line 40 :
CONFIG_PLATFORM_ARM_ARMADEUS = y

- Near line 261 :
ifeq ($(CONFIG_PLATFORM_ARM_ARMADEUS), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WEXT_PRIV
ARCH := arm
CROSS_COMPILE := arm-linux-
KVER := 2.6.35.3
KSRC ?= /path-to-your/armadeus/buildroot/output/build/linux-2.6.35.3
endif
</pre>

And I need to rebuild the linux kernel with define WEXT_PRIV.

I use this trick for that :
<pre class="config">
Device Drivers --->
[*] Network device support --->
[*] Wireless LAN --->
<M> USB ZD1201 based Wireless device support
</pre>

Which give me :
<pre class="config">
│ Selects: WIRELESS_EXT [=y] && WEXT_PRIV [=n] && FW_LOADER [=y]
</pre>

===2)Here is the test I made :===
<pre class="apf">
modprobe 8192cu
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
udhcpc -i wlan0
</pre>
Then I can ping wifi adress with 0% packet loss.

I connect with ssh it work ok for the few command I did.

'''Then I try to connect with SFTP from my PC (using FileZilla) :'''

'''the wifi goes down and the usb with it.'''

===3)Here is the part of "messages" where the error is :===
<pre class="host">
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:1
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:2
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:3
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: fatal error
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal command 010028 (park)=0 ithresh=1 Async period=256 HALT
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal status 49098 Async Halt FATAL FLR
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: reset command 01002a (park)=0 ithresh=1 Async period=256 Reset HALT
Jan 10 01:23:29 armadeus kern.warn kernel: ###=> usb_read_port_complete => urb status(-108)
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: HC died; cleaning up
Jan 10 01:23:29 armadeus kern.debug kernel: hub 2-0:1.0: state 0 ports 1 chg 0000 evt 0000
Jan 10 01:23:29 armadeus kern.info kernel: usb 2-1: USB disconnect, address 2
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering device
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: usb_disable_device nuking all URBs
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering interface 2-1:1.0
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:4
Jan 10 01:23:29 armadeus kern.warn kernel: [dvobjpriv:c8aa401c][ERROR] continual_urb_error:5 > 4
Jan 10 01:23:29 armadeus kern.warn kernel: issue_deauth to 00:18:84:19:e1:62
Jan 10 01:23:29 armadeus kern.warn kernel: rtw_sta_flush
Jan 10 01:23:30 armadeus kern.warn kernel: (2)871x_drv - drv_close, bup=1, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: -871x_drv - drv_close, bup=1
Jan 10 01:23:30 armadeus kern.warn kernel: ===> rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: usb_read_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: usb_write_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: ###> rtw_cmd_thread break.................
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... check & free all cmd_obj resources
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
Jan 10 01:23:30 armadeus kern.warn kernel: <=== rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: +r871xu_dev_remove, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: free_recv_skb_queue not empty, 5
Jan 10 01:23:30 armadeus kern.warn kernel: =====> rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: <===== rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: -r871xu_dev_remove, done
Jan 10 01:23:40 armadeus kern.err kernel: FEC: MDIO read timeout
Jan 10 01:23:42 armadeus kern.err kernel: FEC: MDIO read timeout
</pre>

And the error by using iperf -c to connect to an iperf server :

<pre class="host">
fsl-ehci fsl-ehci.0: fatal error
###=> usb_read_port_complete => urb status(-108)
fsl-ehci fsl-ehci.0: HC died; cleaning up
usb 2-1: USB disconnect, address 2
+rtw_dev_remove
rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:1
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:2
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:3
reg 0x1cc, usb read 1 fail, status:-19 value=0x0, vendorreq_times:4
[dvobjpriv:c8abd01c][ERROR] continual_urb_error:5 > 4
issue_deauth to 00:18:84:19:e1:62
rtw_sta_flush
(2)871x_drv - drv_close, bup=1, hw_init_completed=1
-871x_drv - drv_close, bup=1
===> rtw_dev_unload
usb_read_port_cancel
usb_write_port_cancel
###> rtw_cmd_thread break.................
rtw_cmd_thread: leaving... check & free all cmd_obj resources
rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
<=== rtw_dev_unload
+r871xu_dev_remove, hw_init_completed=1
free_recv_skb_queue not empty, 4
=====> rtl8192c_free_hal_data =====
<===== rtl8192c_free_hal_data =====
-r871xu_dev_remove, done
FEC: MDIO read timeout
FEC: MDIO read timeout
</pre>

--[[User:Sly|Sly]] 20:33, 31 July 2012 (UTC)

Talk:USB to WiFi adapter

2012-07-31T20:55:23Z

Sly: /* 1)I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 . */

Talk:USB to WiFi adapter

2012-07-31T20:39:49Z

Sly: /* 2)Here is the test I made : */

== About Zydas zd1211 tries ==
[[User:JulienB|JulienB]] 09:52, 4 February 2009 (UTC) : now working

== Chipset RTL8188CUS ==

I will give you the detail for the RTL8188CUS driver error I got for AFP28 with AFP28devdev.

===1)I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 .===
You can get the driver here (chose RTL8188CUS) :
[http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true]

Add those option in the makefile :
<pre class="host">
- change line 39 :
CONFIG_PLATFORM_I386_PC = n
- add line 40 :
CONFIG_PLATFORM_ARM_ARMADEUS = y

- Near line 261 :
ifeq ($(CONFIG_PLATFORM_ARM_ARMADEUS), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WEXT_PRIV
ARCH := arm
CROSS_COMPILE := arm-linux-
KVER := 2.6.35.3
KSRC ?= /path-to-your/armadeus/buildroot/output/build/linux-2.6.35.3
endif
</pre>
===2)Here is the test I made :===
<pre class="apf">
modprobe 8192cu
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
udhcpc -i wlan0
</pre>
Then I can ping wifi adress with 0% packet loss.

I connect with ssh it work ok for the few command I did.

'''Then I try to connect with SFTP from my PC (using FileZilla) :'''

'''the wifi goes down and the usb with it.'''

===3)Here is the part of "messages" where the error is :===
<pre class="host">
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:1
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:2
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:3
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: fatal error
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal command 010028 (park)=0 ithresh=1 Async period=256 HALT
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal status 49098 Async Halt FATAL FLR
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: reset command 01002a (park)=0 ithresh=1 Async period=256 Reset HALT
Jan 10 01:23:29 armadeus kern.warn kernel: ###=> usb_read_port_complete => urb status(-108)
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: HC died; cleaning up
Jan 10 01:23:29 armadeus kern.debug kernel: hub 2-0:1.0: state 0 ports 1 chg 0000 evt 0000
Jan 10 01:23:29 armadeus kern.info kernel: usb 2-1: USB disconnect, address 2
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering device
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: usb_disable_device nuking all URBs
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering interface 2-1:1.0
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:4
Jan 10 01:23:29 armadeus kern.warn kernel: [dvobjpriv:c8aa401c][ERROR] continual_urb_error:5 > 4
Jan 10 01:23:29 armadeus kern.warn kernel: issue_deauth to 00:18:84:19:e1:62
Jan 10 01:23:29 armadeus kern.warn kernel: rtw_sta_flush
Jan 10 01:23:30 armadeus kern.warn kernel: (2)871x_drv - drv_close, bup=1, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: -871x_drv - drv_close, bup=1
Jan 10 01:23:30 armadeus kern.warn kernel: ===> rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: usb_read_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: usb_write_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: ###> rtw_cmd_thread break.................
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... check & free all cmd_obj resources
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
Jan 10 01:23:30 armadeus kern.warn kernel: <=== rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: +r871xu_dev_remove, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: free_recv_skb_queue not empty, 5
Jan 10 01:23:30 armadeus kern.warn kernel: =====> rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: <===== rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: -r871xu_dev_remove, done
Jan 10 01:23:40 armadeus kern.err kernel: FEC: MDIO read timeout
Jan 10 01:23:42 armadeus kern.err kernel: FEC: MDIO read timeout
</pre>
--[[User:Sly|Sly]] 20:33, 31 July 2012 (UTC)

Talk:USB to WiFi adapter

2012-07-31T20:35:12Z

Sly: /* Chipset RTL8188CUS */

== About Zydas zd1211 tries ==
[[User:JulienB|JulienB]] 09:52, 4 February 2009 (UTC) : now working

== Chipset RTL8188CUS ==

I will give you the detail for the RTL8188CUS driver error I got for AFP28 with AFP28devdev.

===1)I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 .===
You can get the driver here (chose RTL8188CUS) :
[http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true]

Add those option in the makefile :
<pre class="host">
- change line 39 :
CONFIG_PLATFORM_I386_PC = n
- add line 40 :
CONFIG_PLATFORM_ARM_ARMADEUS = y

- Near line 261 :
ifeq ($(CONFIG_PLATFORM_ARM_ARMADEUS), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WEXT_PRIV
ARCH := arm
CROSS_COMPILE := arm-linux-
KVER := 2.6.35.3
KSRC ?= /path-to-your/armadeus/buildroot/output/build/linux-2.6.35.3
endif
</pre>
===2)Here is the test I made :===
<pre class="apf">
modprobe 8192cu
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
udhcpc -i wlan0
</pre>
Then I can ping wifi adress with 0% packet loss
I connect with ssh it work ok for the few command I did.
Then I try to connect with SFTP and the wifi goes down and the usb with it.

===3)Here is the part of "messages" where the error is :===
<pre class="host">
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:1
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:2
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:3
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: fatal error
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal command 010028 (park)=0 ithresh=1 Async period=256 HALT
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal status 49098 Async Halt FATAL FLR
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: reset command 01002a (park)=0 ithresh=1 Async period=256 Reset HALT
Jan 10 01:23:29 armadeus kern.warn kernel: ###=> usb_read_port_complete => urb status(-108)
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: HC died; cleaning up
Jan 10 01:23:29 armadeus kern.debug kernel: hub 2-0:1.0: state 0 ports 1 chg 0000 evt 0000
Jan 10 01:23:29 armadeus kern.info kernel: usb 2-1: USB disconnect, address 2
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering device
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: usb_disable_device nuking all URBs
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering interface 2-1:1.0
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:4
Jan 10 01:23:29 armadeus kern.warn kernel: [dvobjpriv:c8aa401c][ERROR] continual_urb_error:5 > 4
Jan 10 01:23:29 armadeus kern.warn kernel: issue_deauth to 00:18:84:19:e1:62
Jan 10 01:23:29 armadeus kern.warn kernel: rtw_sta_flush
Jan 10 01:23:30 armadeus kern.warn kernel: (2)871x_drv - drv_close, bup=1, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: -871x_drv - drv_close, bup=1
Jan 10 01:23:30 armadeus kern.warn kernel: ===> rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: usb_read_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: usb_write_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: ###> rtw_cmd_thread break.................
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... check & free all cmd_obj resources
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
Jan 10 01:23:30 armadeus kern.warn kernel: <=== rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: +r871xu_dev_remove, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: free_recv_skb_queue not empty, 5
Jan 10 01:23:30 armadeus kern.warn kernel: =====> rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: <===== rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: -r871xu_dev_remove, done
Jan 10 01:23:40 armadeus kern.err kernel: FEC: MDIO read timeout
Jan 10 01:23:42 armadeus kern.err kernel: FEC: MDIO read timeout
</pre>
--[[User:Sly|Sly]] 20:33, 31 July 2012 (UTC)

Talk:USB to WiFi adapter

2012-07-31T20:33:08Z

Sly: /* Chipset RTL8188CUS */ new section

== About Zydas zd1211 tries ==
[[User:JulienB|JulienB]] 09:52, 4 February 2009 (UTC) : now working

== Chipset RTL8188CUS ==

I will give you the detail for the RTL8188CUS driver error I got.

===1)I build the driver for chip RTL8188CUS from source rtl8188C_8192C_usb_linux_v3.4.3_4369.20120622 .===
You can get the driver here (chose RTL8188CUS) :
[http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true]

Add those option in the makefile :
<pre class="host">
- change line 39 :
CONFIG_PLATFORM_I386_PC = n
- add line 40 :
CONFIG_PLATFORM_ARM_ARMADEUS = y

- Near line 261 :
ifeq ($(CONFIG_PLATFORM_ARM_ARMADEUS), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WEXT_PRIV
ARCH := arm
CROSS_COMPILE := arm-linux-
KVER := 2.6.35.3
KSRC ?= /path-to-your/armadeus/buildroot/output/build/linux-2.6.35.3
endif
</pre>
===2)Here is the test I made :===
<pre class="apf">
modprobe 8192cu
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant.conf -Dwext -B dhclient
udhcpc -i wlan0
</pre>
Then I can ping wifi adress with 0% packet loss
I connect with ssh it work ok for the few command I did.
Then I try to connect with SFTP and the wifi goes down and the usb with it.

===3)Here is the part of "messages" where the error is :===
<pre class="host">
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:1
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:2
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:3
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: fatal error
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal command 010028 (park)=0 ithresh=1 Async period=256 HALT
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: fatal status 49098 Async Halt FATAL FLR
Jan 10 01:23:29 armadeus kern.debug kernel: fsl-ehci fsl-ehci.0: reset command 01002a (park)=0 ithresh=1 Async period=256 Reset HALT
Jan 10 01:23:29 armadeus kern.warn kernel: ###=> usb_read_port_complete => urb status(-108)
Jan 10 01:23:29 armadeus kern.err kernel: fsl-ehci fsl-ehci.0: HC died; cleaning up
Jan 10 01:23:29 armadeus kern.debug kernel: hub 2-0:1.0: state 0 ports 1 chg 0000 evt 0000
Jan 10 01:23:29 armadeus kern.info kernel: usb 2-1: USB disconnect, address 2
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering device
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: usb_disable_device nuking all URBs
Jan 10 01:23:29 armadeus kern.debug kernel: usb 2-1: unregistering interface 2-1:1.0
Jan 10 01:23:29 armadeus kern.warn kernel: reg 0x608, usb read 4 fail, status:-19 value=0x0, vendorreq_times:4
Jan 10 01:23:29 armadeus kern.warn kernel: [dvobjpriv:c8aa401c][ERROR] continual_urb_error:5 > 4
Jan 10 01:23:29 armadeus kern.warn kernel: issue_deauth to 00:18:84:19:e1:62
Jan 10 01:23:29 armadeus kern.warn kernel: rtw_sta_flush
Jan 10 01:23:30 armadeus kern.warn kernel: (2)871x_drv - drv_close, bup=1, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: -871x_drv - drv_close, bup=1
Jan 10 01:23:30 armadeus kern.warn kernel: ===> rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: usb_read_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: usb_write_port_cancel
Jan 10 01:23:30 armadeus kern.warn kernel: ###> rtw_cmd_thread break.................
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... check & free all cmd_obj resources
Jan 10 01:23:30 armadeus kern.warn kernel: rtw_cmd_thread: leaving... call up terminate_cmdthread_sema
Jan 10 01:23:30 armadeus kern.warn kernel: <=== rtw_dev_unload
Jan 10 01:23:30 armadeus kern.warn kernel: +r871xu_dev_remove, hw_init_completed=1
Jan 10 01:23:30 armadeus kern.warn kernel: free_recv_skb_queue not empty, 5
Jan 10 01:23:30 armadeus kern.warn kernel: =====> rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: <===== rtl8192c_free_hal_data =====
Jan 10 01:23:30 armadeus kern.warn kernel: -r871xu_dev_remove, done
Jan 10 01:23:40 armadeus kern.err kernel: FEC: MDIO read timeout
Jan 10 01:23:42 armadeus kern.err kernel: FEC: MDIO read timeout
</pre>
--[[User:Sly|Sly]] 20:33, 31 July 2012 (UTC)