WHR-HP-G54
From DD-WRT Wiki
Revision as of 10:14, 27 October 2007 (edit) Sash (Talk | contribs) m ← Previous diff |
Revision as of 22:37, 29 October 2007 (edit) (undo) S2s2 (Talk | contribs) (→Built-in amplifier) Next diff → |
||
Line 5: | Line 5: | ||
== Installation == | == Installation == | ||
See the instructions on [[Installation#Buffalo_WHR-G54S.2C_WHR-HP-G54.2C_WZR-HP-G54.2C_WZR-RS-G54_and_WHR-G125|flashing the Buffalo WHR-HP-G54 and similar routers]]. | See the instructions on [[Installation#Buffalo_WHR-G54S.2C_WHR-HP-G54.2C_WZR-HP-G54.2C_WZR-RS-G54_and_WHR-G125|flashing the Buffalo WHR-HP-G54 and similar routers]]. | ||
- | == Built- | + | == Built-In Amplifier & Enhanced Receive Sensitivity == |
- | The WHR-HP-G54 has an additional amplifier in the unit (the HP stands for High-Power). Buffalo sells this router with the tag line "MIMO Performance" for this reason. | + | The WHR-HP-G54 has an additional amplifier in the unit (the HP stands for High-Power) and increased receiver sensitivity. Buffalo sells this router with the tag line "MIMO Performance" for this reason. |
- | + | It is necessary to manually set '''boardflags=0x3758''' to activate the built-in amplifier ''and'' the increased receive sensitivity on the unit [although this may be fixed in a later release]: | |
- | + | nvram set boardflags=0x3758<br> | |
+ | nvram commit<br> | ||
+ | reboot<br> | ||
- | [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=11748 | + | It does not seem to be documented as to how (or if) the output power amplifier is compensated for when setting power levels, or what value to enter into the gui to get the device's rated 80 mW transmit power. '''See the following threads:''' |
+ | |||
+ | [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=11748] Power output | ||
+ | [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=15265] Boardflags | ||
+ | |||
+ | Output the current boardflags value: | ||
+ | nvram get boardflags | ||
+ | |||
+ | 0x0758 - no amp and receive sensitivity normal<br> | ||
+ | 0x1758 - enhanced receive sensitivity<br> | ||
+ | 0x2758 - amp on, normal receive<br> | ||
+ | 0x3758 - both 'on' - this is the one you want!<br> | ||
== Comparison to the [[WHR-G54S]] == | == Comparison to the [[WHR-G54S]] == |
Revision as of 22:37, 29 October 2007
Contents |
Installation
See the instructions on flashing the Buffalo WHR-HP-G54 and similar routers.
Built-In Amplifier & Enhanced Receive Sensitivity
The WHR-HP-G54 has an additional amplifier in the unit (the HP stands for High-Power) and increased receiver sensitivity. Buffalo sells this router with the tag line "MIMO Performance" for this reason.
It is necessary to manually set boardflags=0x3758 to activate the built-in amplifier and the increased receive sensitivity on the unit [although this may be fixed in a later release]:
nvram set boardflags=0x3758
nvram commit
reboot
It does not seem to be documented as to how (or if) the output power amplifier is compensated for when setting power levels, or what value to enter into the gui to get the device's rated 80 mW transmit power. See the following threads:
[1] Power output [2] Boardflags
Output the current boardflags value: nvram get boardflags
0x0758 - no amp and receive sensitivity normal
0x1758 - enhanced receive sensitivity
0x2758 - amp on, normal receive
0x3758 - both 'on' - this is the one you want!
Comparison to the WHR-G54S
The WHR-HP-G54 is able to broadcast farther and recieve from farther away than the WHR-G54S due to the onboard amplifier. A post on the forum has a more objective review.
Command Outputs
cat /proc/cpuinfo Output
system type : Broadcom BCM5352 chip rev 0 processor : 0 cpu model : BCM3302 V0.8 BogoMIPS : 199.47 wait instruction : no microsecond timers : yes tlb_entries : 32 extra interrupt vector : no hardware watchpoint : no VCED exceptions : not available VCEI exceptions : not available
dmesg Output
CPU revision is: 00029008 Linux version 2.4.33-pre2 (root@linux) (gcc version 4.1.0) #774 Tue May 16 20:11 :46 CEST 2006 Setting the PFC value as 0x15 Determined physical RAM map: memory: 01000000 @ 00000000 (usable) On node 0 totalpages: 4096 zone(0): 4096 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd cons ole=ttyS0,115200 CPU: BCM5352 rev 0 at 200 MHz Using 100.000 MHz high precision timer. Calibrating delay loop... 199.47 BogoMIPS Dentry cache hash table entries: 2048 (order: 2, 16384 bytes) Inode cache hash table entries: 1024 (order: 1, 8192 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 4096 (order: 2, 16384 bytes) Checking for 'wait' instruction... unavailable. POSIX conformance testing by UNIFIX PCI: no core PCI: Fixing up bus 0 Initializing RT netlink socket Starting kswapd devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x1 squashfs: version 3.0 (2006/03/15) Phillip Lougher pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en abled ttyS00 at 0xb8000300 (irq = 3) is a 16550A ttyS01 at 0xb8000400 (irq = 3) is a 16550A PCI: Setting latency timer of device 00:01.0 to 64 imq driver loaded. Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0 Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0 Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0 Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0 Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0 Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0 Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0 Amd/Fujitsu Extended Query Table v1.1 at 0x0040 number of CFI chips: 1 cfi_cmdset_0002: Disabling fast programming due to code brokenness. Flash device: 0x400000 at 0x1c000000 Physically mapped flash: squashfs filesystem found at block 824 Creating 5 MTD partitions on "Physically mapped flash": 0x00000000-0x00040000 : "pmon" 0x00040000-0x003f0000 : "linux" 0x000ce170-0x0028c9f6 : "rootfs" mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-o nly 0x003f0000-0x00400000 : "nvram" 0x00290000-0x003f0000 : "ddwrt" sflash: found no supported devices Initializing Cryptographic API IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 2048) ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team IPP2P v0.8.1_rc1 loading ipt_random match loaded netfilter PSD loaded - (c) astaro AG ipt_osf: Startng OS fingerprint matching module. ipt_IPV4OPTSSTRIP loaded arp_tables: (C) 2002 David S. Miller ip_conntrack_rtsp v0.01 loading ip_nat_rtsp v0.01 loading NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> VFS: Mounted root (squashfs filesystem) readonly. Mounted devfs on /dev diag boardtype: 00000467 PCI: Setting latency timer of device 00:05.0 to 64 eth1: Broadcom BCM4318 802.11 Wireless Controller 3.90.39.0 vlan0: add 01:00:5e:00:00:01 mcast address to master interface vlan0: dev_set_promiscuity(master, 1) device eth0 entered promiscuous mode device vlan0 entered promiscuous mode device eth1 entered promiscuous mode HTB init, kernel part version 3.17 HTB init, kernel part version 3.17 vlan1: Setting MAC address to 00 0d 0b 04 ec a1. vlan1: add 01:00:5e:00:00:01 mcast address to master interface HTB init, kernel part version 3.17 HTB init, kernel part version 3.17
Note: dmesg
performed on DD-WRT v23sp1 mini.
GPIO
The WHR-HP-G54 has the following GPIOs operational:
- 0 - Input - AOSS button on top - State 00 is down, state 01 is up
- 1 - Output - Bridge LED - Lights 3rd LED on front panel
- 2 - Output - WLAN LED
- 3 - Output - Extra LED between bridge and WLAN (newer routers no longer have this LED)
- 4 - Input - Reset Button
- 5 - Input - Bridge/Auto Switch - State 01 is auto, state 00 is brd
- 6 - Output - AOSS LED - Lights small orange LED on top
- 7 - Output - DIAG LED - Lights red LED on front below the LED activated by 1
- 9 - Output - Power LED
Note: nvram show | grep gpio
shows 14 available as well. It is unknown what it does. Pin 8 also does not appear to do anything.
It seems that one must reverse enable
and disable
for the command to work, i.e. if you want to turn on a LED, use disable
, off, use enable
.
POE
While the device does not natively support Power Over Ethernet, a linksys WAPPOE (5 volt, not the 12 volt kind) will work just fine.