[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi,
   I am porting ar9271 wifi module to an arm platform, after some days try,
still can not solve the problem, please help.

Environment:

1. lilnux kernel version 2.6.28.

2. compat-wireless-2011-12-31-p

3. without udev, but with mdev

4. firmware puts in lib/firmware/htc_9271.fw

compile ok, but when install ath9k_htc.ko, get error message:

==============================================================
usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
port status 10009
2nd port status 10009
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
ath9k_htc: probe of 1-1:1.0 failed with error -22

===============================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130619/f71678fa/attachment.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

Am 19.06.2013 12:14, schrieb Bo Shi:
> Hi,
>     I am porting ar9271 wifi module to an arm platform, after some days
> try, still can not solve the problem, please help.
>
> Environment:
>
> 1. lilnux kernel version 2.6.28.
> 2. compat-wireless-2011-12-31-p
>
> 3. without udev, but with mdev
>
> 4. firmware puts in lib/firmware/htc_9271.fw
>
> compile ok, but when install ath9k_htc.ko, get error message:
>
> ==============================================================
> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
> port status 10009
> 2nd port status 10009
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
> ath9k_htc: probe of 1-1:1.0 failed with error -22
>
> ===============================================================
>

Hmm...

"Firmware - htc_9271.fw download failed" comes because 
ath9k_hif_usb_download_fw returned -ENOMEM or -EIO

but "probe of 1-1:1.0 failed with error -22" is -EINVAL.

Try attached patch. may be we will find exact reason.

-- 
Regards,
Oleksij
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tmp.diff
Type: text/x-patch
Size: 972 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130619/b1f3fcda/attachment.bin 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij,
   I've patched your file, but it seems the code does not run to that part.

plugin wifi module first time:
=============================
Compat-wireless backport release: compat-wireless-2011-12-28-p
Backport based on linux-next.git next-20111228
cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc

plugin wifi module second time:
=============================
usb 1-1: USB disconnect, address 2
usb 1-1: new high speed USB device using FOTG2XX_DRV and address 3
port status 10009
2nd port status 10009
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed

plugin wifi module thrid time:
=============================
ath9k_htc: probe of 1-1:1.0 failed with error -22
usb 1-1: USB disconnect, address 3
usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
port status 10009
2nd port status 10009
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
ath9k_htc: probe of 1-1:1.0 failed with error -22


On Wed, Jun 19, 2013 at 9:21 PM, Oleksij Rempel <linux@rempel-privat.de>wrote:

> Am 19.06.2013 12:14, schrieb Bo Shi:
>
>  Hi,
>>     I am porting ar9271 wifi module to an arm platform, after some days
>> try, still can not solve the problem, please help.
>>
>> Environment:
>>
>> 1. lilnux kernel version 2.6.28.
>> 2. compat-wireless-2011-12-31-p
>>
>> 3. without udev, but with mdev
>>
>> 4. firmware puts in lib/firmware/htc_9271.fw
>>
>> compile ok, but when install ath9k_htc.ko, get error message:
>>
>> ==============================**==============================**==
>> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
>> port status 10009
>> 2nd port status 10009
>> usb 1-1: configuration #1 chosen from 1 choice
>> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>>
>> ==============================**==============================**===
>>
>>
> Hmm...
>
> "Firmware - htc_9271.fw download failed" comes because
> ath9k_hif_usb_download_fw returned -ENOMEM or -EIO
>
> but "probe of 1-1:1.0 failed with error -22" is -EINVAL.
>
> Try attached patch. may be we will find exact reason.
>
> --
> Regards,
> Oleksij
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130620/206fc9b8/attachment.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

Am 19.06.2013 20:14, schrieb Bo Shi:
> Hi Oleksij,
>     I've patched your file, but it seems the code does not run to that part.

There is no other part in driver which will print this message "
ath9k_htc: Firmware - htc_9271.fw download failed". You probably trying 
unpatched kernel.

> plugin wifi module first time:
> =============================
> Compat-wireless backport release: compat-wireless-2011-12-28-p
> Backport based on linux-next.git next-20111228
> cfg80211: Calling CRDA to update world regulator
> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
> ath9k_htc: probe of 1-1:1.0 failed with error -22
> usbcore: registered new interface driver ath9k_htc
>
> plugin wifi module second time:
> =============================
> usb 1-1: USB disconnect, address 2
> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 3
> port status 10009
> 2nd port status 10009
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
>
> plugin wifi module thrid time:
> =============================
> ath9k_htc: probe of 1-1:1.0 failed with error -22
> usb 1-1: USB disconnect, address 3
> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
> port status 10009
> 2nd port status 10009
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
> ath9k_htc: probe of 1-1:1.0 failed with error -22
>
>
> On Wed, Jun 19, 2013 at 9:21 PM, Oleksij Rempel <linux@rempel-privat.de
> <mailto:linux@rempel-privat.de>> wrote:
>
>     Am 19.06.2013 12:14, schrieb Bo Shi:
>
>         Hi,
>              I am porting ar9271 wifi module to an arm platform, after
>         some days
>         try, still can not solve the problem, please help.
>
>         Environment:
>
>         1. lilnux kernel version 2.6.28.
>         2. compat-wireless-2011-12-31-p
>
>         3. without udev, but with mdev
>
>         4. firmware puts in lib/firmware/htc_9271.fw
>
>         compile ok, but when install ath9k_htc.ko, get error message:
>
>         ==============================__==============================__==
>         usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
>         port status 10009
>         2nd port status 10009
>         usb 1-1: configuration #1 chosen from 1 choice
>         usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
>         ath9k_htc: probe of 1-1:1.0 failed with error -22
>
>         ==============================__==============================__===
>
>
>     Hmm...
>
>     "Firmware - htc_9271.fw download failed" comes because
>     ath9k_hif_usb_download_fw returned -ENOMEM or -EIO
>
>     but "probe of 1-1:1.0 failed with error -22" is -EINVAL.
>
>     Try attached patch. may be we will find exact reason.
>
>     --
>     Regards,
>     Oleksij
>
>     _______________________________________________
>     ath9k-devel mailing list
>     ath9k-devel at lists.ath9k.org <mailto:ath9k-devel@lists.ath9k.org>
>     https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>


-- 
Regards,
Oleksij

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij,

    I am new to ath9k, may be a stupid question, what do you mean "unpached
kernel", I need to patch something to linux kernel directly?

    my step to compile compat-wireless is:

    1. decompress new instance of compat-wireless-2011-12-31-p

    2. select driver: ./scripts/driver-select ath9k_htc, then patch the
diff you provided me.

    3. make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
KLIB=/usr/src/arm-linux-2.6.28/linux-2.6.28-fa
KLIB_BUILD=/usr/src/arm-linux-2.6.28/linux-2.6.28-fa

    4. copy all the ko files to  embedded system's folder:
 /lib/modules/2.6.28/kernel

    5. insmod all the ko, then "depmod -s"

    6. plugin wireless card

    Am I missing something? thanks in advance.


On Thu, Jun 20, 2013 at 2:18 AM, Oleksij Rempel <linux@rempel-privat.de>wrote:

> Am 19.06.2013 20:14, schrieb Bo Shi:
>
>  Hi Oleksij,
>>     I've patched your file, but it seems the code does not run to that
>> part.
>>
>
> There is no other part in driver which will print this message "
> ath9k_htc: Firmware - htc_9271.fw download failed". You probably trying
> unpatched kernel.
>
>  plugin wifi module first time:
>> =============================
>> Compat-wireless backport release: compat-wireless-2011-12-28-p
>> Backport based on linux-next.git next-20111228
>> cfg80211: Calling CRDA to update world regulator
>> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>> usbcore: registered new interface driver ath9k_htc
>>
>> plugin wifi module second time:
>> =============================
>> usb 1-1: USB disconnect, address 2
>> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 3
>> port status 10009
>> 2nd port status 10009
>> usb 1-1: configuration #1 chosen from 1 choice
>> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
>>
>> plugin wifi module thrid time:
>> =============================
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>> usb 1-1: USB disconnect, address 3
>> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
>> port status 10009
>> 2nd port status 10009
>> usb 1-1: configuration #1 chosen from 1 choice
>> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>>
>>
>> On Wed, Jun 19, 2013 at 9:21 PM, Oleksij Rempel <linux@rempel-privat.de
>> <mailto:linux@rempel-privat.de**>> wrote:
>>
>>     Am 19.06.2013 12:14, schrieb Bo Shi:
>>
>>         Hi,
>>              I am porting ar9271 wifi module to an arm platform, after
>>         some days
>>         try, still can not solve the problem, please help.
>>
>>         Environment:
>>
>>         1. lilnux kernel version 2.6.28.
>>         2. compat-wireless-2011-12-31-p
>>
>>         3. without udev, but with mdev
>>
>>         4. firmware puts in lib/firmware/htc_9271.fw
>>
>>         compile ok, but when install ath9k_htc.ko, get error message:
>>
>>         ==============================**__============================**
>> ==__==
>>
>>         usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
>>         port status 10009
>>         2nd port status 10009
>>         usb 1-1: configuration #1 chosen from 1 choice
>>         usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
>>         ath9k_htc: probe of 1-1:1.0 failed with error -22
>>
>>         ==============================**__============================**
>> ==__===
>>
>>
>>
>>     Hmm...
>>
>>     "Firmware - htc_9271.fw download failed" comes because
>>     ath9k_hif_usb_download_fw returned -ENOMEM or -EIO
>>
>>     but "probe of 1-1:1.0 failed with error -22" is -EINVAL.
>>
>>     Try attached patch. may be we will find exact reason.
>>
>>     --
>>     Regards,
>>     Oleksij
>>
>>     ______________________________**_________________
>>     ath9k-devel mailing list
>>     ath9k-devel at lists.ath9k.org <mailto:ath9k-devel at lists.**ath9k.org<ath9k-devel@lists.ath9k.org>
>> >
>>     https://lists.ath9k.org/**mailman/listinfo/ath9k-devel<https://lists.ath9k.org/mailman/listinfo/ath9k-devel>
>>
>>
>>
>
> --
> Regards,
> Oleksij
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130620/b60d289d/attachment-0001.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

Hi Bo,

i can imagine two variants:

- patch was rejected. you will need to edit this file manually:
drivers/net/wireless/ath/ath9k/hif_usb.c

- kernel was patched and compiled correctly, but your system still uses 
old ath9k_htc module.

Am 20.06.2013 03:58, schrieb Bo Shi:
>
> Hi Oleksij,
>
>      I am new to ath9k, may be a stupid question, what do you mean
> "unpached kernel", I need to patch something to linux kernel directly?
>
>      my step to compile compat-wireless is:
>
>      1. decompress new instance of compat-wireless-2011-12-31-p
>
>      2. select driver: ./scripts/driver-select ath9k_htc, then patch the
> diff you provided me.
>
>      3. make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
> KLIB=/usr/src/arm-linux-2.6.28/linux-2.6.28-fa
> KLIB_BUILD=/usr/src/arm-linux-2.6.28/linux-2.6.28-fa
>
>      4. copy all the ko files to  embedded system's folder:
>   /lib/modules/2.6.28/kernel
>
>      5. insmod all the ko, then "depmod -s"
>
>      6. plugin wireless card
>
>      Am I missing something? thanks in advance.
>

-- 
Regards,
Oleksij

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij,
    I got the error message. thanks for you patience.

*initial insmod all the ko with wifi module plugined:*
========================================================
Compat-wireless backport release: compat-wireless-2011-12-28-p
Backport based on linux-next.git next-20111228
cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
usb 1-1: Service connection timeout for: 259
ath9k_htc 1-1:1.0: ath9k_htc: Unable to initialize HTC services
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc

*unplug then plugin module*
==========================================================
usb 1-1: USB disconnect, address 2
usb 1-1: new high speed USB device using FOTG2XX_DRV and address 3
port status 10009
2nd port status 10009
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed*(error  -71)*
ath9k_htc: probe of 1-1:1.0 failed with error -22


On Thu, Jun 20, 2013 at 1:37 PM, Oleksij Rempel <linux@rempel-privat.de>wrote:

> Hi Bo,
>
> i can imagine two variants:
>
> - patch was rejected. you will need to edit this file manually:
> drivers/net/wireless/ath/**ath9k/hif_usb.c
>
> - kernel was patched and compiled correctly, but your system still uses
> old ath9k_htc module.
>
> Am 20.06.2013 03:58, schrieb Bo Shi:
>
>>
>> Hi Oleksij,
>>
>>      I am new to ath9k, may be a stupid question, what do you mean
>> "unpached kernel", I need to patch something to linux kernel directly?
>>
>>      my step to compile compat-wireless is:
>>
>>      1. decompress new instance of compat-wireless-2011-12-31-p
>>
>>      2. select driver: ./scripts/driver-select ath9k_htc, then patch the
>> diff you provided me.
>>
>>      3. make ARCH=arm CROSS_COMPILE=arm-none-linux-**gnueabi-
>> KLIB=/usr/src/arm-linux-2.6.**28/linux-2.6.28-fa
>> KLIB_BUILD=/usr/src/arm-linux-**2.6.28/linux-2.6.28-fa
>>
>>      4. copy all the ko files to  embedded system's folder:
>>   /lib/modules/2.6.28/kernel
>>
>>      5. insmod all the ko, then "depmod -s"
>>
>>      6. plugin wireless card
>>
>>      Am I missing something? thanks in advance.
>>
>>
> --
> Regards,
> Oleksij
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130620/19d52598/attachment.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

Am 20.06.2013 09:58, schrieb Bo Shi:
> Hi Oleksij,
>      I got the error message. thanks for you patience.
>
> *initial insmod all the ko with wifi module plugined:*
> ========================================================
> Compat-wireless backport release: compat-wireless-2011-12-28-p
> Backport based on linux-next.git next-20111228
> cfg80211: Calling CRDA to update world regulatory domain
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> usb 1-1: Service connection timeout for: 259
> ath9k_htc 1-1:1.0: ath9k_htc: Unable to initialize HTC services
> Failed to initialize the device
> ath9k_htc: probe of 1-1:1.0 failed with error -22
> usbcore: registered new interface driver ath9k_htc
>
> *unplug then plugin module*
> ==========================================================
> usb 1-1: USB disconnect, address 2
> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 3
> port status 10009
> 2nd port status 10009
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed*(error  -71)*
> ath9k_htc: probe of 1-1:1.0 failed with error -22


So, we have error -77.
according linux/include/uapi/asm-generic/errno.h
-77 = -EPROTO
according to:
linux/Documentation/usb/error-codes.txt
-EPROTO can be time out, cable or firmware problem.

To exclude firmware problem you will need to use UART port on the ar9271 
chip. But, if there was no power hiccups or resets, then firmware should 
work fine.
Other option is cable. I had some problems if cable was too long or 
damaged. Do you use cable?

This adapter seems to work on Raspberry Pi, which is arm too. so, I 
assume it can be physical problem.


>
> On Thu, Jun 20, 2013 at 1:37 PM, Oleksij Rempel <linux@rempel-privat.de
> <mailto:linux@rempel-privat.de>> wrote:
>
>     Hi Bo,
>
>     i can imagine two variants:
>
>     - patch was rejected. you will need to edit this file manually:
>     drivers/net/wireless/ath/__ath9k/hif_usb.c
>
>     - kernel was patched and compiled correctly, but your system still
>     uses old ath9k_htc module.
>
>     Am 20.06.2013 03:58, schrieb Bo Shi:
>
>
>         Hi Oleksij,
>
>               I am new to ath9k, may be a stupid question, what do you mean
>         "unpached kernel", I need to patch something to linux kernel
>         directly?
>
>               my step to compile compat-wireless is:
>
>               1. decompress new instance of compat-wireless-2011-12-31-p
>
>               2. select driver: ./scripts/driver-select ath9k_htc, then
>         patch the
>         diff you provided me.
>
>               3. make ARCH=arm CROSS_COMPILE=arm-none-linux-__gnueabi-
>         KLIB=/usr/src/arm-linux-2.6.__28/linux-2.6.28-fa
>         KLIB_BUILD=/usr/src/arm-linux-__2.6.28/linux-2.6.28-fa
>
>               4. copy all the ko files to  embedded system's folder:
>            /lib/modules/2.6.28/kernel
>
>               5. insmod all the ko, then "depmod -s"
>
>               6. plugin wireless card
>
>               Am I missing something? thanks in advance.
>
>
>     --
>     Regards,
>     Oleksij
>
>


-- 
Regards,
Oleksij

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij,
   I can download firmware now, maybe caused by cable(Thanks for you
suggestion). It seems AR9721 is much more care about usb signal quality,
under same condtion, rt3070 module can work but AR9721 can not.

    But now face another problem:
   After using reboot cmd to reboot my arm board(AR9721 module always power
on),  the module will  be unresponsive. If power off/on the whole
board(including AR9721 module), there is no problem. Any suggestion, thanks
in advance.

Bo

log:
===================================================================
/lib/modules/2.6.28/kernel/drivers/net/wireless/ath/ath9k#   modprobe
ath9k_htc.ko

usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc

===================================================================


On Thu, Jun 20, 2013 at 4:35 PM, Oleksij Rempel <linux@rempel-privat.de>wrote:

> Am 20.06.2013 09:58, schrieb Bo Shi:
>
>> Hi Oleksij,
>>
>>      I got the error message. thanks for you patience.
>>
>> *initial insmod all the ko with wifi module plugined:*
>>
>> ==============================**==========================
>> Compat-wireless backport release: compat-wireless-2011-12-28-p
>> Backport based on linux-next.git next-20111228
>> cfg80211: Calling CRDA to update world regulatory domain
>> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>> usb 1-1: Service connection timeout for: 259
>> ath9k_htc 1-1:1.0: ath9k_htc: Unable to initialize HTC services
>> Failed to initialize the device
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>> usbcore: registered new interface driver ath9k_htc
>>
>> *unplug then plugin module*
>>
>> ==============================**============================
>> usb 1-1: USB disconnect, address 2
>> usb 1-1: new high speed USB device using FOTG2XX_DRV and address 3
>> port status 10009
>> 2nd port status 10009
>> usb 1-1: configuration #1 chosen from 1 choice
>> usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed*(error  -71)*
>>
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>>
>
>
> So, we have error -77.
> according linux/include/uapi/asm-**generic/errno.h
> -77 = -EPROTO
> according to:
> linux/Documentation/usb/error-**codes.txt
> -EPROTO can be time out, cable or firmware problem.
>
> To exclude firmware problem you will need to use UART port on the ar9271
> chip. But, if there was no power hiccups or resets, then firmware should
> work fine.
> Other option is cable. I had some problems if cable was too long or
> damaged. Do you use cable?
>
> This adapter seems to work on Raspberry Pi, which is arm too. so, I assume
> it can be physical problem.
>
>
>
>> On Thu, Jun 20, 2013 at 1:37 PM, Oleksij Rempel <linux@rempel-privat.de
>> <mailto:linux@rempel-privat.de**>> wrote:
>>
>>     Hi Bo,
>>
>>     i can imagine two variants:
>>
>>     - patch was rejected. you will need to edit this file manually:
>>     drivers/net/wireless/ath/__**ath9k/hif_usb.c
>>
>>
>>     - kernel was patched and compiled correctly, but your system still
>>     uses old ath9k_htc module.
>>
>>     Am 20.06.2013 03:58, schrieb Bo Shi:
>>
>>
>>         Hi Oleksij,
>>
>>               I am new to ath9k, may be a stupid question, what do you
>> mean
>>         "unpached kernel", I need to patch something to linux kernel
>>         directly?
>>
>>               my step to compile compat-wireless is:
>>
>>               1. decompress new instance of compat-wireless-2011-12-31-p
>>
>>               2. select driver: ./scripts/driver-select ath9k_htc, then
>>         patch the
>>         diff you provided me.
>>
>>               3. make ARCH=arm CROSS_COMPILE=arm-none-linux-_**_gnueabi-
>>         KLIB=/usr/src/arm-linux-2.6.__**28/linux-2.6.28-fa
>>         KLIB_BUILD=/usr/src/arm-linux-**__2.6.28/linux-2.6.28-fa
>>
>>
>>               4. copy all the ko files to  embedded system's folder:
>>            /lib/modules/2.6.28/kernel
>>
>>               5. insmod all the ko, then "depmod -s"
>>
>>               6. plugin wireless card
>>
>>               Am I missing something? thanks in advance.
>>
>>
>>     --
>>     Regards,
>>     Oleksij
>>
>>
>>
>
> --
> Regards,
> Oleksij
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130629/77705da0/attachment.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

Am 29.06.2013 17:09, schrieb Bo Shi:
> Hi Oleksij,
>     I can download firmware now, maybe caused by cable(Thanks for you
> suggestion). It seems AR9721 is much more care about usb signal quality,
> under same condtion, rt3070 module can work but AR9721 can not.
>
>      But now face another problem:
>     After using reboot cmd to reboot my arm board(AR9721 module always
> power on),  the module will  be unresponsive. If power off/on the whole
> board(including AR9721 module), there is no problem. Any suggestion,
> thanks in advance.

Hi Bo,

there are some possibilities on what can go wrong:
- boot loader insight of adapter got some kind of error and can't 
download firmware. It is known bug and is on todo list.
- adapter didn't restarted at all, so it is with loaded firmware and 
awaiting other commands.

Can you use UART port on adapter to get log from firmware?
I any case it sounds like your board to not reset usb port on restart. 
May be some extra bug of usb host controller. Can you please take a look 
on it too?


-- 
Regards,
Oleksij

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Adrian Chadd]

On 29 June 2013 08:55, Oleksij Rempel <linux@rempel-privat.de> wrote:

> there are some possibilities on what can go wrong:
> - boot loader insight of adapter got some kind of error and can't
> download firmware. It is known bug and is on todo list.
> - adapter didn't restarted at all, so it is with loaded firmware and
> awaiting other commands.
>
> Can you use UART port on adapter to get log from firmware?
> I any case it sounds like your board to not reset usb port on restart.
> May be some extra bug of usb host controller. Can you please take a look
> on it too?

Hm, is it wedged at this point, or just running the normal firmware?



adrian

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij & Adrian,
    Currently, my module does not support UART:(
    What do you mean about 'reset usb port'(Sorry, I am not familiar with
USB protocol)? You mean usb controller self soft reset or usb controller
send soft reset cmd to AR9721 module? My AR9721 module powered by board
power directly, if reboot my board linux, there is no chance to do hard
reset.
    Is there any work around method for this issue? I am developing a
device need to be online day and night, the system may need to reboot under
some conditions.

   RT3070 module dose work after reboot on my board, but it seems AR9721 is
better than RT3070 under monitor mode.

   I am using v1.3 firwmare from linux-firmware git.

Thanks,
Bo


On Sun, Jun 30, 2013 at 3:34 AM, Adrian Chadd <adrian@freebsd.org> wrote:

> On 29 June 2013 08:55, Oleksij Rempel <linux@rempel-privat.de> wrote:
>
> > there are some possibilities on what can go wrong:
> > - boot loader insight of adapter got some kind of error and can't
> > download firmware. It is known bug and is on todo list.
> > - adapter didn't restarted at all, so it is with loaded firmware and
> > awaiting other commands.
> >
> > Can you use UART port on adapter to get log from firmware?
> > I any case it sounds like your board to not reset usb port on restart.
> > May be some extra bug of usb host controller. Can you please take a look
> > on it too?
>
> Hm, is it wedged at this point, or just running the normal firmware?
>
>
>
> adrian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130630/c1e98d44/attachment.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

Am 30.06.2013 11:55, schrieb Bo Shi:
> Hi Oleksij & Adrian,
>      Currently, my module does not support UART:(
>      What do you mean about 'reset usb port'(Sorry, I am not familiar
> with USB protocol)? You mean usb controller self soft reset or usb
> controller send soft reset cmd to AR9721 module? My AR9721 module
> powered by board power directly, if reboot my board linux, there is no
> chance to do hard reset.
>      Is there any work around method for this issue? I am developing a
> device need to be online day and night, the system may need to reboot
> under some conditions.
>
>     RT3070 module dose work after reboot on my board, but it seems
> AR9721 is better than RT3070 under monitor mode.
>
>     I am using v1.3 firwmare from linux-firmware git.

Hi Bo,

please use latest git version for testing. You can find source code of 
firmware here:
https://github.com/qca/open-ath9k-htc-firmware

Right now, i'm in dead end. I did some testing with my hardware, and my 
adapter was able to reboot even with direct power supply. It will be 
really good if you find access to uart port. Some adapter have it. For 
example:
ALFA AWUS036NHA
NETGEAR WNDA3200

We need to know, what exactly happens.

-- 
Regards,
Oleksij

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij,
   I have compiled the latest firmware, but got following msg:

========================================================
Compat-wireless backport release: compat-wireless-2012-01-16-3-gadea9d0-p
Backport based on linux-next.git next-20120120
cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
ath9k_htc 1-1:1.0: ath9k_htc: Please upgrade to FW version 1.3
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc
========================================================

due to my board system limitation, I am using compat-wireless 2012-01-26
version.

is it because of this?

Thanks in advance.
Bo



On Tue, Jul 2, 2013 at 4:21 PM, Oleksij Rempel <linux@rempel-privat.de>wrote:

> Am 30.06.2013 11:55, schrieb Bo Shi:
>
>  Hi Oleksij & Adrian,
>>      Currently, my module does not support UART:(
>>      What do you mean about 'reset usb port'(Sorry, I am not familiar
>> with USB protocol)? You mean usb controller self soft reset or usb
>> controller send soft reset cmd to AR9721 module? My AR9721 module
>> powered by board power directly, if reboot my board linux, there is no
>> chance to do hard reset.
>>      Is there any work around method for this issue? I am developing a
>> device need to be online day and night, the system may need to reboot
>> under some conditions.
>>
>>     RT3070 module dose work after reboot on my board, but it seems
>> AR9721 is better than RT3070 under monitor mode.
>>
>>     I am using v1.3 firwmare from linux-firmware git.
>>
>
> Hi Bo,
>
> please use latest git version for testing. You can find source code of
> firmware here:
> https://github.com/qca/open-**ath9k-htc-firmware<https://github.com/qca/open-ath9k-htc-firmware>
>
> Right now, i'm in dead end. I did some testing with my hardware, and my
> adapter was able to reboot even with direct power supply. It will be really
> good if you find access to uart port. Some adapter have it. For example:
> ALFA AWUS036NHA
> NETGEAR WNDA3200
>
> We need to know, what exactly happens.
>
> --
> Regards,
> Oleksij
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130703/c9ebadfb/attachment.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij?
    After remove compat-linux fw version check code line, I can download fw
1.4 now. But the reboot problem still exist:

init start:
=======================================================
Compat-wireless backport release: compat-wireless-2012-01-16-3-gadea9d0-p
Backport based on linux-next.git next-20120120
cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
ieee80211 phy0: Atheros AR9271 Rev:1
usb 1-1: ath9k_htc: USB layer initialized
usbcore: registered new interface driver ath9k_htc


after reboot linux:
=======================================================
Compat-wireless backport release: compat-wireless-2012-01-16-3-gadea9d0-p
Backport based on linux-next.git next-20120120
cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc
========================================================


On Wed, Jul 3, 2013 at 2:05 AM, Bo Shi <cnshibo@gmail.com> wrote:

> Hi Oleksij,
>    I have compiled the latest firmware, but got following msg:
>
> ========================================================
> Compat-wireless backport release: compat-wireless-2012-01-16-3-gadea9d0-p
> Backport based on linux-next.git next-20120120
> cfg80211: Calling CRDA to update world regulatory domain
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
> ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
> ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
> ath9k_htc 1-1:1.0: ath9k_htc: Please upgrade to FW version 1.3
> Failed to initialize the device
> ath9k_htc: probe of 1-1:1.0 failed with error -22
> usbcore: registered new interface driver ath9k_htc
> ========================================================
>
> due to my board system limitation, I am using compat-wireless 2012-01-26
> version.
>
> is it because of this?
>
> Thanks in advance.
> Bo
>
>
>
> On Tue, Jul 2, 2013 at 4:21 PM, Oleksij Rempel <linux@rempel-privat.de>wrote:
>
>> Am 30.06.2013 11:55, schrieb Bo Shi:
>>
>>  Hi Oleksij & Adrian,
>>>      Currently, my module does not support UART:(
>>>      What do you mean about 'reset usb port'(Sorry, I am not familiar
>>> with USB protocol)? You mean usb controller self soft reset or usb
>>> controller send soft reset cmd to AR9721 module? My AR9721 module
>>> powered by board power directly, if reboot my board linux, there is no
>>> chance to do hard reset.
>>>      Is there any work around method for this issue? I am developing a
>>> device need to be online day and night, the system may need to reboot
>>> under some conditions.
>>>
>>>     RT3070 module dose work after reboot on my board, but it seems
>>> AR9721 is better than RT3070 under monitor mode.
>>>
>>>     I am using v1.3 firwmare from linux-firmware git.
>>>
>>
>> Hi Bo,
>>
>> please use latest git version for testing. You can find source code of
>> firmware here:
>> https://github.com/qca/open-**ath9k-htc-firmware<https://github.com/qca/open-ath9k-htc-firmware>
>>
>> Right now, i'm in dead end. I did some testing with my hardware, and my
>> adapter was able to reboot even with direct power supply. It will be really
>> good if you find access to uart port. Some adapter have it. For example:
>> ALFA AWUS036NHA
>> NETGEAR WNDA3200
>>
>> We need to know, what exactly happens.
>>
>> --
>> Regards,
>> Oleksij
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130703/05b0d5a9/attachment-0001.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

can you please test this branch:
https://github.com/olerem/open-ath9k-htc-firmware/commits/suspend

there is a workaround which may help.


Am 03.07.2013 04:08, schrieb Bo Shi:
> Hi Oleksij?
>      After remove compat-linux fw version check code line, I can
> download fw 1.4 now. But the reboot problem still exist:
>
> init start:
> =======================================================
> Compat-wireless backport release: compat-wireless-2012-01-16-3-gadea9d0-p
> Backport based on linux-next.git next-20120120
> cfg80211: Calling CRDA to update world regulatory domain
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
> ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
> ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
> ieee80211 phy0: Atheros AR9271 Rev:1
> usb 1-1: ath9k_htc: USB layer initialized
> usbcore: registered new interface driver ath9k_htc
>
>
> after reboot linux:
> =======================================================
> Compat-wireless backport release: compat-wireless-2012-01-16-3-gadea9d0-p
> Backport based on linux-next.git next-20120120
> cfg80211: Calling CRDA to update world regulatory domain
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
> ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
> Failed to initialize the device
> ath9k_htc: probe of 1-1:1.0 failed with error -22
> usbcore: registered new interface driver ath9k_htc
> ========================================================
>
>
> On Wed, Jul 3, 2013 at 2:05 AM, Bo Shi <cnshibo@gmail.com
> <mailto:cnshibo@gmail.com>> wrote:
>
>     Hi Oleksij,
>         I have compiled the latest firmware, but got following msg:
>
>     ========================================================
>     Compat-wireless backport release:
>     compat-wireless-2012-01-16-3-gadea9d0-p
>     Backport based on linux-next.git next-20120120
>     cfg80211: Calling CRDA to update world regulatory domain
>     usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
>     ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
>     ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
>     ath9k_htc 1-1:1.0: ath9k_htc: Please upgrade to FW version 1.3
>     Failed to initialize the device
>     ath9k_htc: probe of 1-1:1.0 failed with error -22
>     usbcore: registered new interface driver ath9k_htc
>     ========================================================
>
>     due to my board system limitation, I am using compat-wireless
>     2012-01-26 version.
>
>     is it because of this?
>
>     Thanks in advance.
>     Bo
>
>
>
>     On Tue, Jul 2, 2013 at 4:21 PM, Oleksij Rempel
>     <linux at rempel-privat.de <mailto:linux@rempel-privat.de>> wrote:
>
>         Am 30.06.2013 11:55, schrieb Bo Shi:
>
>             Hi Oleksij & Adrian,
>                   Currently, my module does not support UART:(
>                   What do you mean about 'reset usb port'(Sorry, I am
>             not familiar
>             with USB protocol)? You mean usb controller self soft reset
>             or usb
>             controller send soft reset cmd to AR9721 module? My AR9721
>             module
>             powered by board power directly, if reboot my board linux,
>             there is no
>             chance to do hard reset.
>                   Is there any work around method for this issue? I am
>             developing a
>             device need to be online day and night, the system may need
>             to reboot
>             under some conditions.
>
>                  RT3070 module dose work after reboot on my board, but
>             it seems
>             AR9721 is better than RT3070 under monitor mode.
>
>                  I am using v1.3 firwmare from linux-firmware git.
>
>
>         Hi Bo,
>
>         please use latest git version for testing. You can find source
>         code of firmware here:
>         https://github.com/qca/open-__ath9k-htc-firmware
>         <https://github.com/qca/open-ath9k-htc-firmware>
>
>         Right now, i'm in dead end. I did some testing with my hardware,
>         and my adapter was able to reboot even with direct power supply.
>         It will be really good if you find access to uart port. Some
>         adapter have it. For example:
>         ALFA AWUS036NHA
>         NETGEAR WNDA3200
>
>         We need to know, what exactly happens.
>
>         --
>         Regards,
>         Oleksij
>
>
>


-- 
Regards,
Oleksij

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Bo Shi]

Hi Oleksij,
  After add a line "return;" according to you branch, my system can not
find the AR9271 device after reboot system. print following logs:

=============================================
 port status 10029
port status 10029
usb 1-1: device descriptor read/64, error -110
port status 10009
port status 10029
port status 10029
usb 1-1: device descriptor read/64, error -110
usb 1-1: new high speed USB device using FOTG2XX_DRV and address 4
2nd port status 10009
usb 1-1: device not accepting address 4, error -110
usb 1-1: new high speed USB device using FOTG2XX_DRV and address 5
2nd port status 10009
usb 1-1: device not accepting address 5, error -110
hub 1-0:1.0: unable to enumerate USB device on port 1

===========================================================


On Wed, Jul 3, 2013 at 5:32 PM, Oleksij Rempel <linux@rempel-privat.de>wrote:

> can you please test this branch:
> https://github.com/olerem/**open-ath9k-htc-firmware/**commits/suspend<https://github.com/olerem/open-ath9k-htc-firmware/commits/suspend>
>
> there is a workaround which may help.
>
>
> Am 03.07.2013 04:08, schrieb Bo Shi:
>
>> Hi Oleksij?
>>      After remove compat-linux fw version check code line, I can
>> download fw 1.4 now. But the reboot problem still exist:
>>
>> init start:
>> ==============================**=========================
>> Compat-wireless backport release: compat-wireless-2012-01-16-3-**
>> gadea9d0-p
>> Backport based on linux-next.git next-20120120
>> cfg80211: Calling CRDA to update world regulatory domain
>> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
>> ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
>> ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
>> ieee80211 phy0: Atheros AR9271 Rev:1
>> usb 1-1: ath9k_htc: USB layer initialized
>> usbcore: registered new interface driver ath9k_htc
>>
>>
>> after reboot linux:
>> ==============================**=========================
>> Compat-wireless backport release: compat-wireless-2012-01-16-3-**
>> gadea9d0-p
>> Backport based on linux-next.git next-20120120
>> cfg80211: Calling CRDA to update world regulatory domain
>> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
>> ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>> Failed to initialize the device
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>> usbcore: registered new interface driver ath9k_htc
>> ==============================**==========================
>>
>>
>> On Wed, Jul 3, 2013 at 2:05 AM, Bo Shi <cnshibo@gmail.com
>> <mailto:cnshibo@gmail.com>> wrote:
>>
>>     Hi Oleksij,
>>         I have compiled the latest firmware, but got following msg:
>>
>>     ==============================**==========================
>>     Compat-wireless backport release:
>>     compat-wireless-2012-01-16-3-**gadea9d0-p
>>     Backport based on linux-next.git next-20120120
>>     cfg80211: Calling CRDA to update world regulatory domain
>>     usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51000
>>     ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
>>     ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
>>     ath9k_htc 1-1:1.0: ath9k_htc: Please upgrade to FW version 1.3
>>     Failed to initialize the device
>>     ath9k_htc: probe of 1-1:1.0 failed with error -22
>>     usbcore: registered new interface driver ath9k_htc
>>     ==============================**==========================
>>
>>     due to my board system limitation, I am using compat-wireless
>>     2012-01-26 version.
>>
>>     is it because of this?
>>
>>     Thanks in advance.
>>     Bo
>>
>>
>>
>>     On Tue, Jul 2, 2013 at 4:21 PM, Oleksij Rempel
>>     <linux at rempel-privat.de <mailto:linux@rempel-privat.de**>> wrote:
>>
>>         Am 30.06.2013 11:55, schrieb Bo Shi:
>>
>>             Hi Oleksij & Adrian,
>>                   Currently, my module does not support UART:(
>>                   What do you mean about 'reset usb port'(Sorry, I am
>>             not familiar
>>             with USB protocol)? You mean usb controller self soft reset
>>             or usb
>>             controller send soft reset cmd to AR9721 module? My AR9721
>>             module
>>             powered by board power directly, if reboot my board linux,
>>             there is no
>>             chance to do hard reset.
>>                   Is there any work around method for this issue? I am
>>             developing a
>>             device need to be online day and night, the system may need
>>             to reboot
>>             under some conditions.
>>
>>                  RT3070 module dose work after reboot on my board, but
>>             it seems
>>             AR9721 is better than RT3070 under monitor mode.
>>
>>                  I am using v1.3 firwmare from linux-firmware git.
>>
>>
>>         Hi Bo,
>>
>>         please use latest git version for testing. You can find source
>>         code of firmware here:
>>         https://github.com/qca/open-__**ath9k-htc-firmware<https://github.com/qca/open-__ath9k-htc-firmware>
>>
>>         <https://github.com/qca/open-**ath9k-htc-firmware<https://github.com/qca/open-ath9k-htc-firmware>
>> >
>>
>>         Right now, i'm in dead end. I did some testing with my hardware,
>>         and my adapter was able to reboot even with direct power supply.
>>         It will be really good if you find access to uart port. Some
>>         adapter have it. For example:
>>         ALFA AWUS036NHA
>>         NETGEAR WNDA3200
>>
>>         We need to know, what exactly happens.
>>
>>         --
>>         Regards,
>>         Oleksij
>>
>>
>>
>>
>
> --
> Regards,
> Oleksij
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130703/dc1f2768/attachment.htm 

[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

[Oleksij Rempel]

Hi Bo,


Am 10.07.2013 04:24, schrieb Bo Shi:
> Hi Oleksij?
>      The issue has gone after patch this. thank you very very much.

Great! Thank you for testing.
Please write some feedback on github:
https://github.com/qca/open-ath9k-htc-firmware/issues/1
or to the mailing list

> |--- a/drivers/net/wireless/ath/ath9k/htc_drv_init.c
> +++ b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
> @@ -895,6 +895,7 @@ static int ath9k_init_device(struct ath9k_htc_priv *priv,
>          ath9k_init_leds(priv);
>          ath9k_start_rfkill_poll(priv);
>
> +       ath9k_hw_disable(priv->ah);
>          return 0;
>
>   err_world:|
>
>
>
> On Tue, Jul 9, 2013 at 5:26 PM, Oleksij Rempel <linux@rempel-privat.de
> <mailto:linux@rempel-privat.de>> wrote:
>
>     Hi Bo,
>
>     Am 09.07.2013 06:21, schrieb Bo Shi:
>
>         Hi Oleksij,
>         I got the uart log from ar9271,
>
>
>     that's good news :)
>
>
>         first part is a fresh power on. second
>         part is from reboot system, could you please help to check the
>         issue?
>         Thanks you.
>         Bo
>
>         ==============================__==============================__======================
>         fresh system start up?
>         result: success
>         ==============================__==============================__======================
>
>
>     .....
>
>
>
>         ==============================__==============================__======================
>         do nothing to wlan0 interface after previous success
>         installment, just
>         reboot linux:
>         result?ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>         ==============================__==============================__======================
>
>         !USB suspend
>
>            change clock to 22 and go to suspend now!??
>
>
>     this message is incomplete. I assume there was some hiccups on chip
>     reset.
>     ....
>
>
>
>         ==>[cUSB_REQ_COMP]: 0x%08x
>
>         VendorCmd: DownloadComplete!
>
>         5. usb only!!
>
>            A_WDT_INIT()
>
>            ==>warm start<==
>         ALLOCRAM start 0x50d7f4 size 106508
>         Enable Tx Stream mode
>         [+++Magpie_init]
>         [+++VBUF_init(100)]
>         [+++VBUF_init(100)]
>         <wlan_pci_probe>: Attaching the driver
>         <wlan_pci_probe>: Vendor id 0x168c Dev id 0x24
>         ath_pci_probe 24
>            ath_hal = 0x00510910
>
>         =>[dnQ] 0x0050f270
>         [=>[upQ] 0x0050f24c
>         [=>[hp dnQ] 0x0050f228
>         [=>[mp dnQ] 0x0050f204
>         [Tgt running
>
>
>     Usually my adapters was not able to boot if there was problem with
>     chip reset. Beside, only one case, where i get corrupt buffers and
>     chip was misconfigured after reboot and firmware upload.
>
>     May be it is that case. Please test this firmware:
>     https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix
>     <https://github.com/olerem/open-ath9k-htc-firmware/commits/suspend_fix>
>
>     with this kernel:
>     https://github.com/olerem/__linux-2.6/commits/github-wifi-__ath9k_htc-fw
>     <https://github.com/olerem/linux-2.6/commits/github-wifi-ath9k_htc-fw>
>     Or you can try to apply my patches on your kernel.
>
>     This firmware is not compatible with other kernel version. It wont
>     work without my kernel patches. And this firmware has an issue with
>     "ifconfig up"... so don't bring it up for now.
>
>
>
>         On Fri, Jul 5, 2013 at 10:50 PM, Bo Shi <cnshibo@gmail.com
>         <mailto:cnshibo@gmail.com>
>         <mailto:cnshibo at gmail.com <mailto:cnshibo@gmail.com>>> wrote:
>
>              Yes?they are the same. I will try uart log when I get another
>              module easy to open shield. Will let you know result ASAP.
>
>              ? 2013?7?5?????Oleksij Rempel ???
>
>                  Am 04.07.2013 03:05, schrieb Bo Shi:
>
>                      Sorry,
>                      'Target is unresponsive' with the latest patch
>         after reboot
>                      linux.
>
>                         I find if i do 'ifconfig wlan0 up'  or 'ifconfig
>         wlan0 up
>                        then
>                      ifconfig wlan0 down'  before reboot, everything
>         goes will
>                      after reboot.
>                      How 'ifconfig wlan0 up' command effect AR9217
>         hardware status?
>
>
>                      On Thu, Jul 4, 2013 at 2:48 AM, Oleksij Rempel
>                      <linux at rempel-privat.de <mailto:linux@rempel-privat.de>
>                      <mailto:linux@rempel-privat.de
>         <mailto:linux@rempel-privat.de>__>> wrote:
>
>                           Hi i can't reproduce your case, but i found
>         other case.
>                           It is enough to "rmmod ath9k_htc; sleep 1;
>         modprobe
>                      ath9k_htc;"
>                           some times more then one time.
>                           After some tesing i found that firmware can
>         freeze if
>                      after cpu
>                           reset we will continue configuration. So i
>         added some
>                      delay. Can you
>                           please test latest patch:
>         https://github.com/olerem/______open-ath9k-htc-firmware/______commits/suspend_fix
>         <https://github.com/olerem/____open-ath9k-htc-firmware/____commits/suspend_fix>
>
>         <https://github.com/olerem/____open-ath9k-htc-firmware/____commits/suspend_fix
>         <https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix>>
>
>
>
>         <https://github.com/olerem/____open-ath9k-htc-firmware/____commits/suspend_fix
>         <https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix>
>
>         <https://github.com/olerem/__open-ath9k-htc-firmware/__commits/suspend_fix
>         <https://github.com/olerem/open-ath9k-htc-firmware/commits/suspend_fix>>>
>
>
>                  Hi Bo,
>
>                  this bug seems to be same with this issue:
>         https://github.com/qca/open-____ath9k-htc-firmware/issues/1
>         <https://github.com/qca/open-__ath9k-htc-firmware/issues/1>
>
>
>         <https://github.com/qca/open-__ath9k-htc-firmware/issues/1
>         <https://github.com/qca/open-ath9k-htc-firmware/issues/1>>
>
>                  please fallow it
>
>                  --
>                  Regards,
>                  Oleksij
>
>
>
>
>     --
>     Regards,
>     Oleksij
>
>


-- 
Regards,
Oleksij