Activating Afterburner (125Mbps) on the recent wl-500g units

wsrom command unknown

Hi all,

I tried to run Olegs procedure to active
in order to activate afterburner. My WL100g
supports Afterburner and I'm curious to see
if it works.

However, I couldn't run wsrom command.

It's unknown at my unit.

I use Olegs customized firmware 1.7.5.6-5.

Thanks in advance for any help.

Regards

Nik

Quote:

Originally Posted by Nik

However, I couldn't run wsrom command.

It's unknown at my unit.

I use Olegs customized firmware 1.7.5.6-5.

Upgrade to 1.8.1.7-2a

Quote:

Originally Posted by coder

After reading the information shown on this thread I logged into my wrt54g v1.1 openwrt unit and issued the command:

Code:

# wl revinfo vendorid: 14e4 deviceid: 4320 radiorev: 2205017f chipnum: 4306 chiprev: 3 corerev: 5 boardid: 1603 boardvendor: 16a5 boardrev: 45 driverrev: 332150a ucoderev: f500cb bus: 1

As you can see it seems like a potential afterburner-upgradable unit due to corerev and chiprev values.

I quickly downloaded the srom.mipsel binary and issue the first command:

Code:

# ./b43_srom.mips 14e44320 Found pci device 14e44320 at /proc/bus/pci/01/08.0@0x40002000 Enabling device... Device memory mapped ok SROM CRC ok 0000 4001 0000 1603 16a5 4320 8000 0002 0002 0008 1000 1800 0000 0000 ffff ffff ffff ffff 0010 ffff ffff ffff ffff ffff ffff ffff ffff 0018 ffff ffff ffff ffff ffff ffff ffff ffff 0020 ffff ffff ffff ffff 000c 419d 7221 ffff 0028 ffff ffff ffff ffff ffff ffff 3545 111c 0030 fbcc fe84 ffff ffff 0040 ffff ffff ffff 0038 003e 000d ffff 0000 0000 0000 0000 6b01

The value at offset 0039 is not 000f so I did not issue the second command because I was afraid of bricking the card.

Any hints? Maybe wrt54g v1.1 units are also afterburner capable... that would be superb for our backbone here in Valencia (Spain).

Thanks in advance :-)

Your unit seems to be upgradable. Use 20d instead of 20f.

Also, you can write 20f - this should not damage your board (in fact b43_srom can be used to recover partially corrupted srom), while should enable other features.

@OpenWrt:/tmp# ./b43_srom.mips 14e44320
Found pci device 14e44320 at /proc/bus/pci/00/01.0@0x18001000
Enabling device...
PCI: Enabling device /proc/bus/pci/00/01.0 (0004 -> 0006)
Device memory mapped ok
Bus error

This is a WRT54G v2. Core and chiprev is the same as the WRT54GS.

@OpenWrt:/tmp# wl revinfo
vendorid: 14e4
deviceid: 4320
radiorev: 2205017f
chipnum: 4712
chiprev: 1
corerev: 7
boardid: 101
boardvendor: 14e4
boardrev: 10
driverrev: 332150a
ucoderev: f500cb
bus: 0

Do you've wl.o module loaded at the time of running utility? Also, can you please post

Code:

cat /proc/pci cat /proc/bus/pci/devices

output?
Seems start address was picked incorrectly - this is due to the fact, that it's not the real bcm4306, but bcm4712 integrated.

Quote:

Originally Posted by Oleg

Do you've wl.o module loaded at the time of running utility?

Yes, I have.

Quote:

Originally Posted by Oleg

Also, can you please post

Code:

cat /proc/bus/pci

output?
Seems start address was picked incorrectly.

Do You mean /proc/pci?

Code:

PCI devices found: Bus 0, device 0, function 0: Class 0501: PCI device 14e4:0800 (rev 1). IRQ 3. Non-prefetchable 32 bit memory at 0x18000000 [0x18000fff]. Non-prefetchable 32 bit memory at 0x1fc00000 [0x1fffffff]. Non-prefetchable 32 bit memory at 0x1c000000 [0x1dffffff]. Non-prefetchable 32 bit memory at 0x1a000000 [0x1bffffff]. Bus 0, device 1, function 0: Class 0280: PCI device 14e4:4320 (rev 1). IRQ 4. Non-prefetchable 32 bit memory at 0x18001000 [0x18001fff]. Bus 0, device 2, function 0: Class 0200: PCI device 14e4:4713 (rev 1). IRQ 5. Non-prefetchable 32 bit memory at 0x18002000 [0x18002fff]. Bus 0, device 3, function 0: Class 0c03: PCI device 14e4:4717 (rev 1). IRQ 6. Non-prefetchable 32 bit memory at 0x18003000 [0x18003fff]. Bus 0, device 4, function 0: Class 0c03: PCI device 14e4:4716 (rev 1). IRQ 2. Non-prefetchable 32 bit memory at 0x18004000 [0x18004fff]. Bus 0, device 5, function 0: Class 0b30: PCI device 14e4:0816 (rev 1). IRQ 2. Non-prefetchable 32 bit memory at 0x18005000 [0x18005fff]. Bus 0, device 6, function 0: Class 0500: PCI device 14e4:080f (rev 1). IRQ 3. Non-prefetchable 32 bit memory at 0x18006000 [0x18006fff]. Non-prefetchable 32 bit memory at 0x0 [0x7ffffff]. Non-prefetchable 32 bit memory at 0x10000000 [0x17ffffff]. Non-prefetchable 32 bit memory at 0x80000000 [0x9fffffff].

I have an upgradable wl500g unit running openwrt.
After writing sram, and modifying nvram variables i still can't get it working.

Code:

root@ittakert:~# nvram get wl_afterburner auto root@ittakert:~# wl gmode 54g Mode is 54g Afterburner (6) root@ittakert:~# wl status SSID: "huwico@joshome" Mode: Managed RSSI: 0 dBm noise: 0 dBm Channel: 1 BSSID: XX:XX:XX:XX:XX:XX Capability: ESS Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]

I have an associated b client if that helps.

Quote:

Originally Posted by Josephus

I have an upgradable wl500g unit running openwrt.
After writing sram, and modifying nvram variables i still can't get it working.

Code:

root@ittakert:~# nvram get wl_afterburner auto root@ittakert:~# wl gmode 54g Mode is 54g Afterburner (6) root@ittakert:~# wl status SSID: "huwico@joshome" Mode: Managed RSSI: 0 dBm noise: 0 dBm Channel: 1 BSSID: XX:XX:XX:XX:XX:XX Capability: ESS Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]

I have an associated b client if that helps.

i have no idea how openwrt works with this
but linux does not report 125mbps.. use a afterburner capable client to test it..
wl status did not report 125mbps for me either.. allthough it does work

Quote:

Originally Posted by Josephus

I have an upgradable wl500g unit running openwrt.
After writing sram, and modifying nvram variables i still can't get it working.

I have an associated b client if that helps.

Yes, according to broadcom you should use afterburner capable only devices in this network, otherwise it will switch to normal operation (so, yours 802.11b disables it). Also, in fact, it's the same 802.11g, but with reduced timings, allowing to pass more data in the same time. That's why it will not report new speed.

Quote:

Originally Posted by Kaloz

Yes, I have.

Do You mean /proc/pci?

I mean both to see all requested resources. But /proc/pci output also looks strange - for some reason only 4096 bytes are requested by device, it should be at least 8192 for srom image...
I will try to check sources for the 4712 specific srom mapping. Stay tuned. :)

Quote:

Originally Posted by Oleg

I mean both to see all requested resources. But /proc/pci output also looks strange - for some reason only 4096 bytes are requested by device, it should be at least 8192 for srom image...
I will try to check sources for the 4712 specific srom mapping. Stay tuned. :)

Don't forget, that the v2 hardware includes the radio itself. This can be a clue here imho :)

Quote:

Originally Posted by Kaloz

Don't forget, that the v2 hardware includes the radio itself. This can be a clue here imho :)

Can you please post an output for the

Code:

cat /proc/bus/pci/devices

Also, pci config could unveil things try this one and attach /tmp/1 to the message...

Code:

cat /proc/bus/pci/00/01.0 > /tmp/1

Also, this unit seems to have 2 usb controllers... It would be great if you do

Code:

cat /proc/bus/pci/00/03.0 > /tmp/3 cat /proc/bus/pci/00/04.0 > /tmp/4

and then attach /tmp/3 & /tmp/4 - I just want to check for their types.

Just found many answers myself - usb - one is host and another is device, as for srom - it's not on the pci bus, it's at the "silicon backplane" bus, so it does not work this way for bcm4712.
Also, broadcom sources does not provide any info on how to access srom at this internal bus, althought there something similar called sflash - flash on the silicon backplane.

1 Attachment(s)

Code:

cat /proc/bus/pci/devices @OpenWrt:/# cat /proc/bus/pci/devices 0000 14e40800 3 18000000 1fc00000 1c000000 1a000000 00000000 00000000 00000000 00001000 00400000 02000000 02000000 00000000 00000000 00000800 0008 14e44320 4 18001000 00000000 00000000 00000000 00000000 00000000 00000000 00001000 00000000 00000000 00000000 00000000 00000000 00000800 wl 0010 14e44713 5 18002000 00000000 00000000 00000000 00000000 00000000 00000000 00001000 00000000 00000000 00000000 00000000 00000000 00000800 et 0018 14e44717 6 18003000 00000000 00000000 00000000 00000000 00000000 00000000 00001000 00000000 00000000 00000000 00000000 00000000 00000800 0020 14e44716 2 18004000 00000000 00000000 00000000 00000000 00000000 00000000 00001000 00000000 00000000 00000000 00000000 00000000 00000800 0028 14e40816 2 18005000 00000000 00000000 00000000 00000000 00000000 00000000 00001000 00000000 00000000 00000000 00000000 00000000 00000800 0030 14e4080f 3 18006000 00000000 10000000 80000000 00000000 00000000 00000000 00001000 08000000 08000000 20000000 00000000 00000000 00000800

Code:

cat /proc/bus/pci/00/01.0 > /tmp/1 cat /proc/bus/pci/00/03.0 > /tmp/3 cat /proc/bus/pci/00/04.0 > /tmp/4

attached :)

1 Attachment(s)

Kaloz, thanks.

I've prepared yet another utility, which uses wl ioctl to access srom. You should be able to read srom, but writability is depends on the wl.o driver version.

So, it's attached (sorry for zip format, that's the only way to attach it to the thread).

This utility requires wl.o driver to be loaded.

Usage: wlsrom <interface> [ <word-offset> <word-value> ]

So, to dump current srom content try running like this:

Code:

wlsrom eth2

To upgrade to afterburner run it like this (check for old value at 0x39 before upgrade):

Code:

wlsrom eth2 39 20f

Let me know if it works for you.