ath9k-devel.lists.ath9k.org archive mirror
 help / color / mirror / Atom feed
From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9380 on Kirkwood 88FR131
Date: Tue, 03 Jul 2012 13:18:57 +0200	[thread overview]
Message-ID: <4FF2D521.5040102@neratec.com> (raw)
In-Reply-To: <4FF007E6.3080709@allnet.de>

On 07/01/2012 10:18 AM, Daniel Golle wrote:
> Hi!
> I'm trying to use a Senao EMP7606 module (AR9380) on a Marvell Kirkwood
> 88FR131-based board running OpenWrt r32511 with Linux 3.3.8 and
> compat-wireless-2012-06-14.
> I'm unable to figure out the reason for the card not working properly. Please
> advise me on how I should go on debugging/investigating the issue.
> ath9k_hw_reset is quite complex and I can't figure out why it returns -EIO.
I have had similar behaviour on the Ka-Ro TK71 board with same
processor and openwrt. It was working stable with all the cards
except 9380/9390. One of our clever hardware guys has figured
out that you need to solder pull-up resistor on PERST# pin of pci
express slot.

So if you can, just try to solder R402 10k resistor between pins
22 and 24.

I know it's not really software solution but it was only one that had
worked for us. Seems like timing or power up requirements for
these wifi cards are little bit different.

Good Luck,
Wojtek
> Initially, everything seems to work fine (scanning, creating interfaces,
> hostapd/wpa_supplicant, ...), it fails once there is any traffic:
>
> [143531.857501] ath: phy1: Unable to reset channel, reset status -5
> [143531.863721] ath: phy1: Unable to set channel
> [143531.978747] ath: phy1: Could not kill baseband RX
> [143532.817467] ath: phy1: Unable to reset channel, reset status -5
> [143532.823664] ath: phy1: Unable to set channel
> [143532.938686] ath: phy1: Could not kill baseband RX
> <7>[143533.424522] ath: phy1: NF calibrated [ctl] [chain 1] is -99
> <7>[143541.165276] ath: phy1: TPC[23] 0x00000000
> <7>[143541.824957] ath: phy1: LOOP-Ctlidx 0: cfgCtl 0x10 pCtlMode 0x06 ctlIndex
> 0x10 chan 5220
> <7>[143542.784839] ath: phy1: TPC[26] 0x00000000
> <7>[143542.965311] ath: phy1: TPC[04] 0x00000000
> [143544.205106] ath: phy1: Unable to reset channel, reset status -5
> [143544.211328] ath: phy1: Unable to set channel
> [143544.439405] ath: phy1: Unable to reset channel, reset status -5
> [143544.445606] ath: phy1: Unable to set channel
> [143544.560614] ath: phy1: Could not kill baseband RX
> [143553.557001] ath: phy1: Unable to reset channel, reset status -5
> [143553.563285] ath: phy1: Unable to set channel
> [143553.678305] ath: phy1: Could not kill baseband RX
> [143554.517471] ath: phy1: Unable to reset channel, reset status -5
> [143554.523673] ath: phy1: Unable to set channel
> [143554.638692] ath: phy1: Could not kill baseband RX
> <7>[143563.554433] ath: phy1: qnum: 0, txq depth: 1
> <7>[143566.105190] ath: phy1: TPC[14] 0x0000001e
> <7>[143567.424684] ath: phy1: TPC[07] 0x00000000
> <7>[143576.124649] ath: phy1: TPC[04] 0x00000000
> <7>[143576.907763] ath: phy1: AWAKE -> FULL-SLEEP
> <7>[143578.044838] ath: phy1: TPC[19] 0x0000001c
> <7>[143578.224765] ath: phy1: TPC[19] 0x00000014
> <7>[143591.065833] ath: phy1: **** ofdmlevel 3=>3, rssi=0[lo=7 hi=40]
> <7>[143599.105129] ath: phy1: TPC[16] 0x00000014
> [143604.126032] ath: phy1: Unable to reset channel, reset status -5
> [143604.132272] ath: phy1: Unable to set channel
> [143604.247294] ath: phy1: Could not kill baseband RX
> [143605.077538] ath: phy1: Unable to reset channel, reset status -5
> [143605.083743] ath: phy1: Unable to set channel
> [143605.198762] ath: phy1: Could not kill baseband RX
> <7>[143609.349690] ath: phy1: TPC[12] 0x00000016
> <7>[143615.238106] ath: phy1: chain 0: mag mismatch=0 phase mismatch=0
> <7>[143622.685104] ath: phy1: TPC[04] 0x0000001e
> <7>[143623.044849] ath: phy1: TPC[30] 0x00000000
> <7>[143625.081839] ath: phy1: chain 0: mag mismatch=0 phase mismatch=0
> <7>[143628.635917] ath: phy1: Enable MIB counters
> <7>[143632.534854] ath: phy1: TPC[29] 0x00000000
> ...
>
> root at OpenWrt:/proc# lspci
> 00:00.0 Memory controller: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM
> SoC (rev 03)
> 00:01.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN
> adaptor (rev 01)
>
> root at OpenWrt:/proc# cat iomem
> 00000000-07ffffff : System RAM
>    00008000-0030dfff : Kernel code
>    0032e000-0035a9cb : Kernel data
> e0000000-e7ffffff : PCIe 0 MEM
>    e0000000-e001ffff : 0000:00:01.0
>      e0000000-e001ffff : ath9k
>    e0020000-e002ffff : 0000:00:01.0
> f1010300-f101031f : rtc-mv
> f1011000-f101101f : mv64xxx_i2c.0
>    f1011000-f101101f : mv64xxx_i2c adapter
> f1012000-f10120ff : serial8250.0
>    f1012000-f101201f : serial
> f1030000-f103ffff : regs
>    f1030800-f10308cf : regs control and error
>    f1030a00-f1030a24 : regs deco
> f1050000-f1050fff : orion-ehci.0
>    f1050000-f1050fff : ehci_hcd
> f1060800-f10608ff : xor 0 low
> f1060900-f10609ff : xor 1 low
> f1060a00-f1060aff : xor 0 high
> f1060b00-f1060bff : xor 1 high
> f1072000-f1075fff : ge00 base
> f1076000-f1079fff : ge01 base
> f1080000-f1084fff : sata base
> f1090000-f10903ff : mvsdio
>    f1090000-f10903ff : mvsdio
> f4000000-f40003ff : orion_nand
> f5000000-f50007ff : sram
>
> root at OpenWrt:/proc# cat /proc/interrupts
>             CPU0
>    1:   14378078  orion_irq  orion_tick
>    5:          2  orion_irq  mv_xor.0
>    6:          2  orion_irq  mv_xor.1
>    7:          2  orion_irq  mv_xor.2
>    8:          2  orion_irq  mv_xor.3
>    9:       5495  orion_irq  ath9k
>   19:         70  orion_irq  ehci_hcd:usb1
>   22:          0  orion_irq  mv_crypto
>   28:         52  orion_irq  mvsdio
>   29:         34  orion_irq  mv64xxx_i2c
>   33:       3370  orion_irq  serial
>   46:         21  orion_irq  mv643xx_eth
>   47:          0  orion_irq  mv643xx_eth
>   49:          0  orion_irq  mv_tdma
>   92:          1         -  mvsdio cd
> Err:          0
>
>
> Thanks a lot for the support!
>
>
> Best regards
>
>
> Daniel
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

  parent reply	other threads:[~2012-07-03 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-01  8:18 [ath9k-devel] AR9380 on Kirkwood 88FR131 Daniel Golle
2012-07-01 19:51 ` Adrian Chadd
2012-07-02  0:31   ` Daniel Golle
2012-07-03 11:18 ` Wojciech Dubowik [this message]
2012-07-04 20:48   ` Daniel Golle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FF2D521.5040102@neratec.com \
    --to=wojciech.dubowik@neratec.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).