Git Product home page Git Product logo

iwleeprom's People

Stargazers

 avatar

Watchers

 avatar  avatar

iwleeprom's Issues

AR9300 patch issue

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Dear developers, I am so glad I find your code so I can possibly modify my 
AR9300 regdmn, here is the problem I encountered:

it recognized my AR9300:
root@ubuntu:/home/ubuntu/Desktop/ar9300# iwleeprom
Supported devices detected: 
  [1] 0000:03:00.0 [RW] AR9300 Wireless Adapter (PCI-E) (168c:0030, 106b:009a)
Select device [1-1] (or 0 to quit): 1
Using device 0000:03:00.0 [RW] AR9300 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 0003
RF: integrated
Trying EEPROM access...
Filling ath9300 EEPROM... DONE
ath9300_eeprom_check_header ffffffff  @0fff r=0
ath9300_eeprom_check_header ff65ffff  @03ff r=1
AR9300 device NVM type: EEPROM
NVM found at: 03ff
ath9k short eeprom base: 1023 (0x03ff) size: 0

but with the -p option, error occurred, can you advise how I should do?

Also with -o option, the dump seems working fine, so only the patch doesn't 
work, is there another way to edit the dump file by myself? THanks!!!

root@ubuntu:/home/ubuntu/Desktop/ar9300# iwleeprom -p
Supported devices detected: 
  [1] 0000:03:00.0 [RW] AR9300 Wireless Adapter (PCI-E) (168c:0030, 106b:009a)
Select device [1-1] (or 0 to quit): 1
Using device 0000:03:00.0 [RW] AR9300 Wireless Adapter (PCI-E) 
IO driver: ath9300
HW: AR9300 (PCI-E) rev 0003
RF: integrated
Trying EEPROM access...
Filling ath9300 EEPROM... DONE
ath9300_eeprom_check_header ffffffff  @0fff r=0
ath9300_eeprom_check_header ff65ffff  @03ff r=1
AR9300 device NVM type: EEPROM
NVM found at: 03ff
ath9k short eeprom base: 1023 (0x03ff) size: 0
Segmentation fault (core dumped)


Original issue reported on code.google.com by [email protected] on 28 Sep 2012 at 6:13

Patching channels with -a works in test (-c), but not without -c

What steps will reproduce the problem?
1. iwleeprom -d 0000:03:00.0 -a -D1 -m

What is the expected output? What do you see instead?
expected:
Card EEPROM patched successfully

actual result:
Using device 0000:03:00.0 [RW] PRO/Wireless 4965 AG or AGN [Kedron] Network 
Connection 
address: f7f00000
No file names given or patch option selected!
No EEPROM actions will be performed, just write-enable test
Write regulatory data for all channels unlock...
-> Checking and adding channels...
Regulatory base: 1c56
  1

Verification error at 1c5e

What version of the product are you using? On what operating system?
latest version as available here.
OS; Debian Linux Wheezy Amd64


Please provide any additional information below.

The card is an Intel ipw4965

Original issue reported on code.google.com by [email protected] on 13 Jul 2013 at 5:47

Patch MAC address option

Hi. Thank you for this project.

Could you, please, add a feauture to patch card MAC address. 
Unfortunately I can't understand, how to change the source code, but it should 
be relatively simple task.

Thank you.

Original issue reported on code.google.com by [email protected] on 11 May 2013 at 1:13

64-bit issues?

I am trying to modify the eeprom of an Intel 5100AGN miniPCIe card to work in 
my HP laptop. However, I am failing at the first step: getting a eeprom dump of 
the card.

I am building iwleeprom on an Intel Atom D510MO board, and I know the minipcie 
connection is good, since I'm using it normally for a Broadcom decoder and 
that's working fine.

System is Arch Linux, 64 bit:
Linux brain 3.2.9-1-ARCH #1 SMP PREEMPT Thu Mar 1 09:31:13 CET 2012 x86_64 
GNU/Linux
# gcc --version
gcc (GCC) 4.7.0 20120505 (prerelease)


After checking out revision 37, I see some warnings:

# make
gcc -Wall -O2 -o iwleeprom iwleeprom.c
iwleeprom.c:109:3: warning: data definition has no type or storage class 
[enabled by default]
iwleeprom.c:109:3: warning: type defaults to 'int' in declaration of 'nodev' 
[-Wimplicit-int]
iwleeprom.c:110:3: warning: type defaults to 'int' in declaration of 
'preserve_mac' [-Wimplicit-int]
iwleeprom.c:111:3: warning: type defaults to 'int' in declaration of 
'preserve_calib' [-Wimplicit-int]
iwleeprom.c: In function 'init_dump':
iwleeprom.c:251:2: warning: format '%Ld' expects argument of type 'long long 
int', but argument 3 has type 'size_t' [-Wformat]

Seems OK after building:

# ./iwleeprom
Supported devices detected: 
  [1] 0000:02:00.0 [RW] WiFi Link 5100 (8086:4232, 8086:1321)
Select device [1-1] (or 0 to quit): 1
Using device 0000:02:00.0 [RW] WiFi Link 5100 
No file names given or patch option selected!
No EEPROM actions will be performed, just write-enable test

But trying to dump fails and results in a zero-byte file:

# ./iwleeprom -D 1 -d 0000:02:00.0  -o eeprom.bin
debug level: 1
Using device 0000:02:00.0 [RW] WiFi Link 5100 
address: f0200000
Saving dump with byte order: LITTLE ENDIAN

Read not complete! Timeout at 0000x

# ./iwleeprom -D 1 -d 0000:02:00.0  -p               
debug level: 1
Using device 0000:02:00.0 [RW] WiFi Link 5100 
address: f0200000
Patching card EEPROM...
-> Changing subdev ID

Read not complete! Timeout at 0020x


Original issue reported on code.google.com by [email protected] on 27 May 2012 at 7:09

Crash whilst reading eeprom on AR9300 card

What steps will reproduce the problem?
1. Execute iwleeprom against ATheros 9300 series mini PCIE card 
2.
3.

What is the expected output? What do you see instead?

Expected not to crashdump. Actual behaviour is crash after eeprom is identified 
as being compressed. Actual output below:

Supported devices detected: 
  [1] 0000:02:00.0 [RW] AR9300 Wireless Adapter (PCI-E) (168c:0030, 106b:009a)
Select device [1-1] (or 0 to quit): 1
Using device 0000:02:00.0 [RW] AR9300 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 0003
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 00650000  @03ff r=1
AR9300 device NVM type: EEPROM  (data block @03ff)
Found block at 3ff: code=3 ref=5 length=635 major=2 minor=12 (RAW: 0cb22765)
Calculating EEPROM CRC...
CRC (stored): c0a1
CRC (eval)  : c0a1
compression : block
*** Error in `iwleeprom': free(): invalid next size (normal): 0x09e527b0 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x767e2)[0xb760e7e2]
/lib/i386-linux-gnu/libc.so.6(+0x77530)[0xb760f530]
iwleeprom[0x804c55c]
iwleeprom[0x804c896]
iwleeprom[0x804a0a1]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0xb75b1935]
iwleeprom[0x80489a1]
======= Memory map: ========
08048000-08051000 r-xp 00000000 00:10 30689      /usr/local/sbin/iwleeprom
08051000-08052000 r--p 00008000 00:10 30689      /usr/local/sbin/iwleeprom
08052000-08053000 rw-p 00009000 00:10 30689      /usr/local/sbin/iwleeprom
08053000-08057000 rw-p 00000000 00:00 0 
09e49000-09e72000 rw-p 00000000 00:00 0          [heap]
b7548000-b7563000 r-xp 00000000 07:00 3660       
/lib/i386-linux-gnu/libgcc_s.so.1
b7563000-b7564000 r--p 0001a000 07:00 3660       
/lib/i386-linux-gnu/libgcc_s.so.1
b7564000-b7565000 rw-p 0001b000 07:00 3660       
/lib/i386-linux-gnu/libgcc_s.so.1
b7577000-b7597000 rw-s fbdc0000 00:05 1028       /dev/mem
b7597000-b7598000 rw-p 00000000 00:00 0 
b7598000-b7745000 r-xp 00000000 07:00 3635       
/lib/i386-linux-gnu/libc-2.17.so
b7745000-b7747000 r--p 001ad000 07:00 3635       
/lib/i386-linux-gnu/libc-2.17.so
b7747000-b7748000 rw-p 001af000 07:00 3635       
/lib/i386-linux-gnu/libc-2.17.so
b7748000-b774b000 rw-p 00000000 00:00 0 
b775a000-b775f000 rw-p 00000000 00:00 0 
b775f000-b7760000 r-xp 00000000 00:00 0          [vdso]
b7760000-b7780000 r-xp 00000000 07:00 3611       /lib/i386-linux-gnu/ld-2.17.so
b7780000-b7781000 r--p 0001f000 07:00 3611       /lib/i386-linux-gnu/ld-2.17.so
b7781000-b7782000 rw-p 00020000 07:00 3611       /lib/i386-linux-gnu/ld-2.17.so
bfa45000-bfa66000 rw-p 00000000 00:00 0          [stack]
Aborted

What version of the product are you using? On what operating system?
Using svn build as of 28/7/2013 on ubuntu x64 live 13.04 dvd

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 28 Jul 2013 at 6:39

eeprom not modified for Atheros AR9380 card

What steps will reproduce the problem?
1. Save eeprom dump
2. Modify dump
3. Flash modified dump back to card

What is the expected output? What do you see instead?

Eeprom content should change. Instelad, nothing happens, also CRC  stays the 
same.
Issue similar to #17, but NVM type is EEPROM.

~/atheros$ sudo ./iwleeprom -D 1 -d 0000:02:00.0 -i mod.rom 
debug level: 1
Using device 0000:02:00.0 [RW] AR9300 Wireless Adapter (PCI-E) 
IO driver: ath9300
Supported ops:  read write parse
address: 58700000
HW: AR9300 (PCI-E) rev 0003
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 00650000  @03ff r=1
AR9300 device NVM type: EEPROM  (data block @03ff)
Found block at 3ff: code=3 ref=5 length=635 major=2 minor=12 (RAW: 0cb22765)
Calculating EEPROM CRC...
CRC (stored): c211
CRC (eval)  : c211
compression : block
ath9300 short eeprom base: 383 (0x017f) size: 641
About to write device EEPROM, press 'Y' if you are sure... Y
Writing data to EEPROM...
  '.' = match, 'x' = write
Dump file byte order: LITTLE ENDIAN
0000 [.......xx.......................................................]
0080 [................................................................]
0100 [................................................................]
0180 [................................................................]
0200 [................................................................]
0280 [................................................................]
0300 [................................................................]
0380 [................................................................]

EEPROM has been written from 'mod.rom'
~/atheros$



What version of the product are you using? On what operating system?

Tried on Ubuntu 14.10 and 9.04

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 25 Feb 2015 at 11:11

Can't obtain memory address for AR9380

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 [email protected] on 2 Mar 2013 at 3:18

ar9227 is supported?

Hello friends, I have wireless PCI adapter with ar9227 chip. 
Displays this: 
Supported devices detected: 
NONE 
they can support?

Original issue reported on code.google.com by [email protected] on 13 Jul 2014 at 2:27

More detail in verify error

May I suggest the following change to the write verification in eeprom_write16 
(line 325 in head):

<<<
        if (value != (data >> 16)) {
                if (debug)
                        fprintf(stderr, "Verification error at %.4x (read %.2x, expecting %.2x)\n", addr, data >> 16, value);
                else   
                        die("Verification error at %.4x (read %.2x, expecting %.2x)\n", addr, data >> 16, value);
        }
>>>

Original issue reported on code.google.com by [email protected] on 1 Sep 2012 at 4:48

Patching iwl4965 fails

What steps will reproduce the problem?
1. Compile & install the version as found in branches/atheros
2. iwleeprom -p -m -D1

What is the expected output? What do you see instead?
expected: patch succeeded
actual: read errors, and fails to write


What version of the product are you using? On what operating system?
- Version: as from the branches/atheros folder
- os: Debian Linux Wheezy, Amd64


Please provide any additional information below.
Please see the attached file for result log

Original issue reported on code.google.com by [email protected] on 13 Jul 2013 at 6:16

Attachments:

Need to init_card() before initpower()

Currently line 1011...1014 is:
<<<
        if(init_device)
                initpower();

        init_card();
>>>

It needs to be:
<<<
        init_card();

        if(init_device)
                initpower();
>>>
since init_card() sets up the memory map (mappedAddress) which is used by 
initpower().

Original issue reported on code.google.com by [email protected] on 1 Sep 2012 at 4:43

Writing centrino 6200 eeprom works, but resets after a reboot.

Hi there,

I'm trying to change the pci vid of an intel centrino 6200 (to get around a pci 
whitelist issue, no idea if that'll actually work though), so I checked out the 
atheros branch, modified iwlio.c to allow writing to the 6200, dumped the 
eeprom to a file, changed the vid, then wrote it to the 6200 again.

Now when I read back the eeprom, I see the changed vid, but when I reboot the 
machine the eeprom is back to what it originally was.
The same thing happens when I pass the -p argument to iwleeprom, the changes 
don't stick after a reboot.

Now I realize that writing the 6200 eeprom is not supported, but I was hoping 
someone could provide me some insight.

Thanks for writing such a nice tool :)

Original issue reported on code.google.com by [email protected] on 14 Nov 2011 at 5:07

cannot reprogram device id and subsystem of iwl4965

When trying to reprogram my card from IBM (8086:4230, 8086:1110) to generic 
(8086:4229, 8086:1103) I get this:

# ./iwleeprom -d 0000:02:00.0 -m -c -i iwl4965agn-generic.eeprom -D 1
debug level: 1
Using device 0000:02:00.0 [RW] PRO/Wireless 4965 AG or AGN [Kedron] Network 
Connection 
address: fbefe000
Dump file byte order: LITTLE ENDIAN
0000 [========Verification error at 0010 (read 4230, expecting 4229)
.=Verification error at 0014 (read 1110, expecting 1103)
.=====================================================]
0080 [================================================================]
0100 [================================================================]
0180 [================================================================]
0200 [================================================================]
0280 [================================================================]
0300 [================================================================]
0380 [================================================================]

Any idea if these cards just can't be reprogrammed?

Original issue reported on code.google.com by [email protected] on 1 Sep 2012 at 5:00

  • Merged into: #3

622ANHMW read ok pathing ok after power off heed to patch again

I'm get 622ANHMW (Intel® Centrino® Advanced-N 6200) wifi card for branded 
notebook (i'm think it's Lenovo) and put it in Acer 3830TG.
KALI Linux and Ubuntu working fine. Windows 7 x64 gets "Device could not start 
(code10)" error. Found https://communities.intel.com/thread/14740 solution, all 
working now fine, but!
After i power off and power on the notebook, old eeprom restored, and i need to 
boot Linux and flash modified eeprom again to start wifi card in windows.


What version of the product are you using? On what operating system?
Used latest release from SVN, kompiled under KALI linux 1.0.9 x64


Solution from Intel:
The card worked fine under linux but failed to initialize in Windows (7), no 
matter which Intel driver version I tried.
Under Win7 Device Manager it reported as PCI\VEN_8086&DEV_4239&SUBSYS_13118086 
which apparently is Lenovo branded card and will not work with Windows on my 
laptop (ASUS). I browsed windows .inf file and found generic (unbranded) 
counterpart that should identify as PCI\VEN_8086&DEV_422C&SUBSYS_13018086, then 
booted linux with intention to edit card EEPROM (no warranty - no worries).

Then under linux I:
1) downloaded iwleeprom tool
$ svn checkout http://iwleeprom.googlecode.com/svn/trunk/ iwleeprom-read-only

2) edited iwleeprom.c to enable RW capability for writing 6200 EEPROM
$ vi iwleeprom-read-only/iwleeprom.c
modified line:
{ 0x8086, 0x4239, 0, EEPROM_SIZE_5K,   "Centrino Advanced-N 6200"},
to read:
{ 0x8086, 0x4239, 1, EEPROM_SIZE_5K,   "Centrino Advanced-N 6200"},

3) compiled iwleeprom binary
$ cd iwleeprom-read-only && make

4) noted down PCI bus on which WIFI card was on
$ lspci -nv
03:00.0 0280: 8086:422c (rev 35)
        Subsystem: 8086:1301

5) dumped card's EEPROM to a file
$ ./iwleeprom -d 0000:03:00.0 -o eeprom.bak
$ cp eeprom.bak eeprom.mod

6) used hex editor to modify device identification from branded to generic (as 
per identification on top), minding this is little endian
$ hexer eeprom.mod
FROM:
00000000:  40 5a 50 00 00 60 00 00  01 00 35 00 80 02 86 80  @ZP..`....5.....
00000010:  39 42 86 80 11 13 01 0d  8b 03 00 05 f0 00 40 00  ,B............@.
(...)
TO:
00000000:  40 5a 50 00 00 60 00 00  01 00 35 00 80 02 86 80  @ZP..`....5.....
00000010:  2c 42 86 80 01 13 01 0d  8b 03 00 05 f0 00 40 00  ,B............@.
(...)

7) saved and written the modified file into card's eeprom (root/sudo)
(Note that following step can break your hardware. Use at your own risk)
# ./iwleeprom -d 0000:03:00.0 -m -c -i eeprom.mod

8) rebooted to windows

Then I installed latest drivers that identified this card as generic Intel 6200 
AGN.
Issue has been solved - card now works both under linux and under windows.


Original issue reported on code.google.com by novsinclair on 7 Nov 2014 at 2:32

Write a AR9485 wifi card BAD CHECKSUM

What steps will reproduce the problem?
1. Read a AR9485 wifi card
2. Write a AR9485 wifi card

What is the expected output? What do you see instead?
It Reads the AR9485 wifi card without error
It ERRORS out with "BAD Checksum" when you try to write the rom that you just 
read.

What version of the product are you using? On what operating system?
Ubuntu 14.04 LTS

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 20 Apr 2014 at 7:02

eeprom writing not really working with ar9380 minipcie card

What steps will reproduce the problem?
1. dump eeprom file with iwleeprom
2. modify the regdomain in the dump from 64 to 37 with an hex editor
3. correct crc of the dump using iwleeprom internal crc calculator (with -s 
switch) to have a 100% valid eeprom dump
4. write back the dump to real eeprom using -i switch, iwleeprom says EEPROM 
has been written, but in reality nothing changed in the real eeprom

What is the expected output? What do you see instead?
the real eeprom is not modified

What version of the product are you using? On what operating system?
iwleeprom r43 atheros branch in ubuntu 14.04

Please provide any additional information below.

ubuntu@ubuntu:~/atheros$ iwleeprom -s
Supported devices detected: 
  [1] 0000:07:00.0 [RW] AR9300 Wireless Adapter (PCI-E) (168c:0030, 106b:009a)
Select device [1-1] (or 0 to quit): 1
Using device 0000:07:00.0 [RW] AR9300 Wireless Adapter (PCI-E) 
IO driver: ath9300
HW: AR9300 (PCI-E) rev 0003
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 00650000  @03ff r=1
AR9300 device NVM type: EEPROM  (data block @03ff)
Found block at 3ff: code=3 ref=5 length=635 major=2 minor=12 (RAW: 0cb22765)
Calculating EEPROM CRC...
CRC (stored): c510
CRC (eval)  : c510
compression : block
ath9300 short eeprom base: 383 (0x017f) size: 641

==== BASE ====
Version     : 02
Template    : 05
Cust data   : C8611110C76DDV3AB
MAC address : e4:ce:8f:50:a1:01
Reg. domain : 0064 001f
Tx mask     : 0111
Rx mask     : 0111
Capabilities: 03
       Bands: 5GHz 2.4GHz
       HT 2G: HT20 HT40
       HT 5G: HT20 HT40
Misc flags  : 00
Big endian  :  0

==== MISC ====
rfSilent       : 00
BT options     : 00
deviceCap      : 00
deviceType     : 05
pwrTableOffset : 00
tuning params  : 00 00
featureEnable  : 0d
miscConfig     : 14
txrxgain       : 00
swreg          : 00000000

==== GPIO ====
EEPROM WE      : 06
WLAN disable   : 00
WLAN LED       : 08
Rx band select : ff





ubuntu@ubuntu:~/atheros$ iwleeprom -n -i dump9300mod -F ath9300 -s
Forced driver name: ath9300
Device-less operation...
 Using IO driver (forced): ath9300
  byte order: LITTLE ENDIAN
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 00650000  @03ff r=1
AR9300 device NVM type: EEPROM  (data block @03ff)
Found block at 3ff: code=3 ref=5 length=635 major=2 minor=12 (RAW: 0cb22765)
Calculating EEPROM CRC...
CRC (stored): c4e3
CRC (eval)  : c4e3
compression : block
ath9300 short eeprom base: 383 (0x017f) size: 641

==== BASE ====
Version     : 02
Template    : 05
Cust data   : C8611110C76DDV3AB
MAC address : e4:ce:8f:50:a1:01
Reg. domain : 0037 001f
Tx mask     : 0111
Rx mask     : 0111
Capabilities: 03
       Bands: 5GHz 2.4GHz
       HT 2G: HT20 HT40
       HT 5G: HT20 HT40
Misc flags  : 00
Big endian  :  0

==== MISC ====
rfSilent       : 00
BT options     : 00
deviceCap      : 00
deviceType     : 05
pwrTableOffset : 00
tuning params  : 00 00
featureEnable  : 0d
miscConfig     : 14
txrxgain       : 00
swreg          : 00000000

==== GPIO ====
EEPROM WE      : 06
WLAN disable   : 00
WLAN LED       : 08
Rx band select : ff






ubuntu@ubuntu:~/atheros$ iwleeprom -i dump9300mod
Supported devices detected: 
  [1] 0000:07:00.0 [RW] AR9300 Wireless Adapter (PCI-E) (168c:0030, 106b:009a)
Select device [1-1] (or 0 to quit): 1
Using device 0000:07:00.0 [RW] AR9300 Wireless Adapter (PCI-E) 
IO driver: ath9300
HW: AR9300 (PCI-E) rev 0003
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 00650000  @03ff r=1
AR9300 device NVM type: EEPROM  (data block @03ff)
Found block at 3ff: code=3 ref=5 length=635 major=2 minor=12 (RAW: 0cb22765)
Calculating EEPROM CRC...
CRC (stored): c510
CRC (eval)  : c510
compression : block
ath9300 short eeprom base: 383 (0x017f) size: 641
About to write device EEPROM, press 'Y' if you are sure... Y
Writing data to EEPROM...
  '.' = match, 'x' = write
Dump file byte order: LITTLE ENDIAN
0000 [................................................................]
0080 [................................................................]
0100 [...............................................................x]
0180 [x...............................................................]
0200 [................................................................]
0280 [................................................................]
0300 [................................................................]
0380 [...............................................x................]

EEPROM has been written from 'dump9300mod'


>but in reality nothing changed...

Original issue reported on code.google.com by [email protected] on 13 May 2014 at 3:07

Invalid eeprom signature error with Centrino Wireless-N 1000

What steps will reproduce the problem?
1. Using Debian 7
2. Centrino wireless-n 1000
3. Notebook Acer Aspire 5750

What is the expected output? What do you see instead?
After successful compilation, i get the eeprom dump with no errors but when i 
attempt to write the eeprom, i get the "Invalid eeprom signature"

What version of the product are you using? On what operating system?
At first attempted with svn 41, but with svn 34 and 15 the same error occurred.

Please provide any additional information below.
As i could see, this error has something to do with the iwleeprom tool not 
recognize the Endian thing of the firmware dump. But I have attempted with both 
Big Endian and Little Endian format and nothing worked. Even with the firmware 
dump being made with the iwlwifi module loaded and not loaded into the kernel. 
Although the hex bytes changing position into the file, between the tries, 
nothing has worked. 

Original issue reported on code.google.com by [email protected] on 29 Mar 2014 at 3:59

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.