upgrade Prism2 firmware problem
Bob Beers
bbeers
Mon Nov 25 11:04:49 PST 2002
Hi,
I have been trying to load latest firmware (1.1.1 and 1.5.6)
onto my WMP11 using the instructions from
http://lists.shmoo.com/pipermail/hostap/2002-November/000295.html
on a Slack8.1 box, based on driver update file from Intersil
website:
ISL3PRDSUIT-EXE_WIN_(2-0-9).zip
I have the 2002-10-12 release of hostap, and made the change
to add PRISM2_DOWNLOAD_SUPPORT.
Here's my card's current info:
bash-2.05a# dmesg | grep ident
ident: nic h/w: id=0x8013 1.0.0
ident: pri f/w: id=0x15 1.0.7
ident: sta f/w: id=0x1f 1.3.5
but I encounter this error for the primary firmware:
bash-2.05a# ./prism2_srec -vr wlan0 tmp/image-5.hex
S3 f/w info: version: component=0x0015 1.1.1
S3 f/w info: compatibility: role=0x0000 iface_id=0x0003
variant=1 range=4-4
S3 f/w info: compatibility: role=0x0001 iface_id=0x0002
variant=2 range=1-1
S3 f/w info: build seq#: 0
S3 f/w info: platform: id=0x800c 1.0.0
S3 f/w info: platform: id=0x8013 1.0.0
S3 f/w info: platform: id=0x8017 1.0.0
S3 f/w info: platform: id=0x801b 1.0.0
S3 f/w info: platform: id=0x8022 1.0.0
Invalid S3 firmware info len: len=18 words=7
S3 parse error; line=10
Start address 0x003f0000
S3 plug record: PDR=0x0003 plug: addr=0x007E12B8 len=12
S3 plug record: PDR=0x0005 plug: addr=0x007E1110 len=2
S3 plug record: PDR=0x0006 plug: addr=0x007E12F0 len=10
S3 plug record: PDR=0x0007 plug: addr=0x007E1304 len=10
S3 plug record: PDR=0x0008 plug: addr=0x007E12C4 len=8
S3 plug record: PDR=0x0400 plug: addr=0x007E1114 len=2
S3 plug record: PDR=0x0402 plug: addr=0x007E111E len=4
S3 plug record: PDR=0x0403 plug: addr=0x007E1116 len=16
S3 plug record: PDR=0x0404 plug: addr=0x007E1126 len=10
S3 plug record: PDR=0x0408 plug: addr=0x007E1112 len=2
S3 plug record: PDR=0x0001 plug: addr=0x007E12CC len=16
S3 CRC-16 generation record: start=0x007E17FE len=2 prog=0
Before S3 sort
S3 area count: 3
addr=0x007E0000..0x007E0977 (len=2424)
addr=0x007E0A00..0x007E131F (len=2336)
addr=0x007E17FE..0x007E17FF (len=2)
After S3 sort
S3 area count: 3
addr=0x007E0000..0x007E0977 (len=2424)
addr=0x007E0A00..0x007E131F (len=2336)
addr=0x007E17FE..0x007E17FF (len=2)
Total data length: 4762
Errors found - file cannot be used
Parsing 'tmp/image-5.hex' failed.
and this error (the same really, for the secondary):
bash-2.05a# ./prism2_srec -vr wlan0 tmp/image-2.hex
S3 f/w info: version: component=0x001f 1.5.6
S3 f/w info: compatibility: role=0x0000 iface_id=0x0004
variant=6 range=1-10
S3 f/w info: compatibility: role=0x0001 iface_id=0x0001
variant=1 range=1-1
S3 f/w info: compatibility: role=0x0001 iface_id=0x0002
variant=2 range=1-1
S3 f/w info: compatibility: role=0x0001 iface_id=0x0003
variant=1 range=4-4
S3 f/w info: build seq#: 0
S3 f/w info: platform: id=0x800a 1.0.0
S3 f/w info: platform: id=0x800b 1.0.0
S3 f/w info: platform: id=0x800c 1.0.0
S3 f/w info: platform: id=0x800d 1.0.0
S3 f/w info: platform: id=0x8012 1.0.0
S3 f/w info: platform: id=0x8013 1.0.0
S3 f/w info: platform: id=0x8014 1.0.0
S3 f/w info: platform: id=0x8016 1.0.0
S3 f/w info: platform: id=0x8017 1.0.0
S3 f/w info: platform: id=0x8018 1.0.0
S3 f/w info: platform: id=0x801a 1.0.0
S3 f/w info: platform: id=0x801b 1.0.0
S3 f/w info: platform: id=0x801c 1.0.0
S3 f/w info: platform: id=0x8021 1.0.0
S3 f/w info: platform: id=0x8022 1.0.0
S3 f/w info: platform: id=0x8023 1.0.0
S3 f/w info: platform: id=0x800a 1.0.0
S3 f/w info: platform: id=0x800e 1.0.0
S3 f/w info: platform: id=0x8015 1.0.0
S3 f/w info: platform: id=0x8019 1.0.0
S3 f/w info: platform: id=0x801d 1.0.0
S3 f/w info: platform: id=0x8024 1.0.0
Invalid S3 firmware info len: len=18 words=7
S3 parse error; line=29
Start address 0x003f0c01
S3 plug record: PDR=0x0202 plug: addr=0x007F1302 len=100
S3 plug record: PDR=0x0203 plug: addr=0x007F1366 len=128
S3 plug record: PDR=0x0204 plug: addr=0x007F14E6 len=80
S3 plug record: PDR=0x0405 plug: addr=0x007F1536 len=4
S3 plug record: PDR=0x0300 plug: addr=0x007F153A len=28
S3 plug record: PDR=0x0301 plug: addr=0x007F1556 len=34
S3 plug record: PDR=0x0101 plug: addr=0x007F1748 len=6
S3 plug record: PDR=0x0103 plug: addr=0x007ED1CA len=12
S3 plug record: PDR=0x0104 plug: addr=0x007ED302 len=2
S3 plug record: PDR=0x0105 plug: addr=0x007F1754 len=2
S3 plug record: PDR=0x0105 plug: addr=0x007ED338 len=2
S3 plug record: PDR=0x0105 plug: addr=0x007F1850 len=2
S3 plug record: PDR=0x0107 plug: addr=0x007ED1D8 len=2
S3 plug record: PDR=0x0006 plug: addr=0x007ED1A4 len=10
S3 plug record: PDR=0x0406 plug: addr=0x007F17E8 len=2
S3 plug record: PDR=0x0303 plug: addr=0x007F157C len=2
S3 CRC-16 generation record: start=0x007E1800 len=65684
prog=0
Before S3 sort
S3 area count: 3
addr=0x007E1800..0x007ED6DF (len=48864)
addr=0x007F0800..0x007F1893 (len=4244)
addr=0x007FE000..0x007FECF9 (len=3322)
After S3 sort
S3 area count: 3
addr=0x007E1800..0x007ED6DF (len=48864)
addr=0x007F0800..0x007F1893 (len=4244)
addr=0x007FE000..0x007FECF9 (len=3322)
Total data length: 56430
Errors found - file cannot be used
Parsing 'tmp/image-2.hex' failed.
In examining the image-2.hex and image-5.hex files, it does
look like lines 29 and 10 are different somehow (S317 vs
S311) and perhaps not being parsed correctly. Here's the
first parts of the two image files:
14905 Nov 25 13:33 image-5.hex
============================
S311FF200000050001001500010001000100B1
S313FF2000000600020000000300010004000400B9
S313FF2000000600020001000200020001000100BE
S30BFF200000020003000000D0
S311FF200000050004000C8000000100000039
S311FF20000005000400138000000100000032
S311FF2000000500040017800000010000002E
S311FF200000050004001B800000010000002A
S311FF20000005000400228000000100000023
S317FF20000007000180616B3031303130312E6865780000DF
S705003F0000BB
S311FF00000003000000B8127E000C00000098
S311FF0000000500000010117E000200000049
S311FF00000006000000F0127E000A0000005F
S311FF0000000700000004137E000A00000049
S311FF00000008000000C4127E00080000008B
S311FF0000000004000014117E000200000046
S311FF000000020400001E117E000400000038
S311FF0000000304000016117E001000000033
S311FF0000000404000026117E000A00000028
S311FF0000000804000012117E000200000040
S311FF00000001000000CC127E001000000082
S311FF100000FE177E0002000000000000004A
<snip>
167650 Nov 25 13:33 image-2.hex
============================
S311FF200000050001001F000600010005009E
S313FF2000000600020000000400060001000A00B0
S313FF2000000600020001000100010001000100C0
S313FF2000000600020001000200020001000100BE
S313FF2000000600020001000300010004000400B8
S30BFF200000020003000000D0
S311FF200000050004000A800000010000003B
S311FF200000050004000B800000010000003A
S311FF200000050004000C8000000100000039
S311FF200000050004000D8000000100000038
S311FF20000005000400128000000100000033
S311FF20000005000400138000000100000032
S311FF20000005000400148000000100000031
S311FF2000000500040016800000010000002F
S311FF2000000500040017800000010000002E
S311FF2000000500040018800000010000002D
S311FF200000050004001A800000010000002B
S311FF200000050004001B800000010000002A
S311FF200000050004001C8000000100000029
S311FF20000005000400218000000100000024
S311FF20000005000400228000000100000023
S311FF20000005000400238000000100000022
S311FF200000050004000A800000010000003B
S311FF200000050004000E8000000100000037
S311FF20000005000400158000000100000030
S311FF2000000500040019800000010000002C
S311FF200000050004001D8000000100000028
S311FF20000005000400248000000100000021
S317FF2000000700018072663031303530362E6865780000CA
S705003F0C01AE
S311FF0000000202000002137F0064000000F3
S311FF0000000302000066137F008000000072
S311FF00000004020000E6147F005000000020
S311FF0000000504000036157F000400000018
S311FF000000000300003A157F001C00000002
S311FF0000000103000056157F0022000000DF
S311FF0000000101000048177F000600000009
S311FF00000003010000CAD17E000C000000C6
S311FF0000000401000002D37E000200000095
S311FF0000000501000054177F0002000000FD
S311FF0000000501000038D37E00020000005E
S311FF0000000501000050187F000200000000
S311FF00000007010000D8D17E0002000000BE
S311FF00000006000000A4D17E000A000000EC
S311FF00000006040000E8177F000200000065
S311FF000000030300007C157F0002000000D7
S311FF10000000187E009400010000000000B4
<snip>
Is there something else I should/could be doing?
I had to modify split_combined_hex script due to "-d option
for mktemp not supported under linux", hence my directory
name has no random numbers.
Thanks for any help.
--
Bob Beers
More information about the Hostap
mailing list