Can't obtain memory address for AR9380

[GoogleCodeExporter]

I'm running the atheros branch of iwleeprom. It finds a supported device but 
quits with 'Can't obtain memory address'.

debug level: 1
PCI devices:
    0000:00:00.0: class 0280   id 168c:0030   subid 168c:3112 [RW, ath9300] AR9300 Wireless Adapter (PCI-E) 
Supported devices detected: 
  [1] 0000:00:00.0 [RW] AR9300 Wireless Adapter (PCI-E) (168c:0030, 168c:3112)
Select device [1-1] (or 0 to quit): 1
Using device 0000:00:00.0 [RW] AR9300 Wireless Adapter (PCI-E) 
IO driver: ath9300
Supported ops:  read write parse

Can't obtain memory address

I'm running it under OpenWRT on mips, the specific wireless chipset is AR9380.

Original issue reported on code.google.com by whatasta...@gmail.com on 2 Mar 2013 at 3:18

[GoogleCodeExporter]

Hello I have the same issue, 

./iwleeprom
Supported devices detected: 
  [1] 0000:00:00.0 [RW] AR9580 Wireless Adapter (PCI-E) (168c:0033, 168c:a120)
Select device [1-1] (or 0 to quit): 1
Using device 0000:00:00.0 [RW] AR9580 Wireless Adapter (PCI-E) 
IO driver: ath9300

Can't obtain memory address

May you explain me why I cannot read the device?

Thanks in advance!

Original comment by ndarkn...@gmail.com on 20 Mar 2013 at 4:22

[GoogleCodeExporter]

I was trying to run this on my Netgear WNDR3700 with OpenWRT Attitude 
Adjustment and had the same issue:

./iwleeprom
Supported devices detected: 
  [1] 0000:00:11.0 [RW] AR922X Wireless Adapter (PCI) (168c:0029, 168c:a095)
  [2] 0000:00:12.0 [RW] AR922X Wireless Adapter (PCI) (168c:0029, 168c:a094)
Select device [1-2] (or 0 to quit): 1
Using device 0000:00:11.0 [RW] AR922X Wireless Adapter (PCI) 
IO driver: ath9k

Can't obtain memory address

uname -a
Linux router 3.3.8 #1 Sat Mar 23 16:49:30 UTC 2013 mips GNU/Linux

Original comment by thorsten...@googlemail.com on 13 May 2013 at 6:00

[GoogleCodeExporter]

For mips we can't reproduce because we have hardware for testing...
For those, who are trying on x86 or x64 platform:
do you have root privileges?

Original comment by alexan...@kalinichenko.org on 17 May 2013 at 9:13

[GoogleCodeExporter]

To me it looks like the different endianess causes problems. It attached a 
patch that fixes the endianess issue in map_device() for me. I use a MIPS32 big 
endian machine.

The patch also contains some fixed to ease cross-compiling with the OpenWRT 
toolchain. Please cleanup the patch if necessary.

With the patch applied I get one step closer but iwleeprom still fails on my 
TP-Link WDR3600 (AR9580 wireless chipset).

# cat /proc/cpuinfo 
system type     : Atheros AR9344 rev 2
machine         : TP-LINK TL-WDR3600/4300/4310
processor       : 0
cpu model       : MIPS 74Kc V4.12
BogoMIPS        : 278.93
wait instruction    : yes
microsecond timers  : yes
tlb_entries     : 32
extra interrupt vector  : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x0ff8, 0x0ff8, 
0x0ff8]
ASEs implemented    : mips16
shadow register sets    : 1
kscratch registers  : 0
core            : 0
VCED exceptions     : not available
VCEI exceptions     : not available

# ./iwleeprom 
Supported devices detected: 
  [1] 0000:00:00.0 [RW] AR9580 Wireless Adapter (PCI-E) (168c:0033, 168c:a120)
Select device [1-1] (or 0 to quit): 1
Using device 0000:00:00.0 [RW] AR9580 Wireless Adapter (PCI-E) 
IO driver: ath9300
No file names given nor actions selected!
No EEPROM actions will be performed, just write-enable test
HW: AR9300 (PCI-E) rev 0004
RF: integrated
Trying EEPROM access...
OTP address out of range: 0fff
OTP address out of range: 1001
ath9300_eeprom_check_header 00000000  @0fff r=0
Filling ath9300 EEPROM... DONE
OTP address out of range: 0401
ath9300_eeprom_check_header 00000000  @03ff r=0
ath9300_eeprom_check_header 00000000  @01ff r=0
Trying OTP access...
 DONE
ath9300_eeprom_check_header 00000000  @03ff r=0
ath9300_eeprom_check_header 00000000  @01ff r=0
NVM type identification failed!

eeprom check failed!

Original comment by till.wol...@gmail.com on 31 May 2013 at 12:47

Attachments:

• endian.patch

[GoogleCodeExporter]

Hi, is there maybe any progress?
I would like to use this tool on a TP-Link TL-WDR4300 with OpenWRT and habe the 
same problem...

Original comment by hurzhu...@gmail.com on 1 Aug 2013 at 10:04