[ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed
Oleksij Rempel
linux at rempel-privat.de
Wed Jul 3 14:48:04 EDT 2013
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
and please remove my latest "return" patch.
Am 03.07.2013 20:03, schrieb Bo Shi:
> Hi Oleksij，
> I find the detail test case, may be useful:
>
> case 1:
> 1. start arm board
> 2. install AR9271 driver --> success
> 3. ifconfig wlan0 up
> 4. reboot linux
> 5. install AR 9271 driver --> success
> 6. ifconfig wlan0 up
> 7. reboot
> 8. install AR 9271 driver --> success
>
> case 2:
> 1. start arm board
> 2. install AR9271 driver success
> 3. reboot linux
> 4. install AR 9271 driver fail: Target is unresponsive
>
> This mean the unresponsive only exist when wlan0 not up before system
> rebooted
>
>
>
> On Wed, Jul 3, 2013 at 11:01 PM, Bo Shi <cnshibo at gmail.com
> <mailto:cnshibo at gmail.com>> wrote:
>
> 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 at rempel-privat.de <mailto:linux at 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 at gmail.com
> <mailto:cnshibo at gmail.com>
> <mailto:cnshibo at gmail.com <mailto:cnshibo at 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 at rempel-privat.de>
> <mailto:linux at rempel-privat.de
> <mailto:linux at 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
>
>
>
--
Regards,
Oleksij
More information about the ath9k_htc_fw
mailing list