Differences

This shows you the differences between two versions of the page.

toh:buffalo:wbmr-hp-g300h [2012/12/15 17:03]
toh:buffalo:wbmr-hp-g300h [2014/10/09 14:32] (current)
theoradicus tag phy -> nic
Line 1: Line 1:
====== Buffalo WBMR-HP-G300H ====== ====== Buffalo WBMR-HP-G300H ======
 +
 +<html><b><u><font color=red>We need information for debrick this device with JTAG pinout, if you know how to repair full-brick, help us !</font></b></u></html>
===== Installation ===== ===== Installation =====
->[[doc:howto:generic.flashing]] ->[[doc:howto:generic.flashing]]
 +Only suitably encrypted images may be flashed from the web interface in the stock Buffalo firmware. It is therefore not possible to install OpenWRT in this way. There are two alternatives:
 +
 +==== Option 1: Install from DD-WRT ====
 +
 +DD-WRT have a licensing agreement with Buffalo, and can therefore provide encrypted firmware images. So it is possible to proceed as follows:
 +
 +  * Flash the DD-WRT image from the web interface of the stock Buffalo firmware. (Be careful to choose the right image file, ie the one for an initial install, not the one for upgrading from a previous version of DD-WRT.)
 +
 +  * Just a warning before flashing. This OpenWRT image is for annex b not a. The instructions under Configure ADSL imply that you can install annex a after flashing but the package is not included in the image, so you will be stuck with no internet. So check which annex your internet service provider uses before flashing.
 +
 +  * Get on-line. See DD-WRT documentation for this.
 +
 +  * telnet into DD-WRT, then download and flash the OpenWRT image file:
 +
 +  cd /tmp
 +  wget http://downloads.openwrt.org/attitude_adjustment/12.09/lantiq/ar9/openwrt-lantiq-ar9-WBMR-squashfs.image
 +  mtd -r write openwrt-lantiq-ar9-WBMR-squashfs.image linux
 +
 +Do **not** try to revert to DD-WRT using mtd or you may have to debrick (see https://forum.openwrt.org/viewtopic.php?id=43954).
 +
 +**Revert back to DD-Wrt from the OpenWrt WebUI**
 +
 +The latest official DD-Wrt release (Build 21061 / 2013-04-26) for the WBMR, includes a tftp uImage for the device. You can use this uImage to flash from the OpenWrt WebUI to DD-Wrt. Just go to the dd-wrt website, find WBMR in the router database and download the **uImage.bin** file. Then go to your OpenWrt box and navigate to System --> Backup / Flash firmware. Browse and find the uImage. Click on "flash image". You'll see a verification page (the correct md5 hash of the uImage.bin file is 8b2c7024f4a477ef9db9a2d6094d283e). Click "proceed" and after 4-5 minutes DD-Wrt will be installed on the device.
 +
 +It does not appear to be possible to flash OpenWRT from the DD-WRT web interface.
 +
 +==== Option 2: Install with TFTP ====
 +
 +  * Use TFTP to boot a ramdisk image of OpenWRT.
 +  * Set password to enable ssh.
 +  * Download the OpenWRT image you wish to flash and copy it to the /tmp directory on the router using scp.
 +  * Run: sysupgrade imagefilename to flash the image.
 +
 +
 +=== 2.1 ===
 +The router bootloader has a tftp client, which will try to connect to 192.168.11.2 and load a file called firmware.ram. Download https://downloads.openwrt.org/barrier_breaker/14.07/lantiq/xway/openwrt-lantiq-xway-WBMR-uImage and rename it as firmware.ram to your tftp server root folder.
 +
 +=== 2.2 ===
 +Install and start a tftp server. For linux there is a package called tftp-server, tftpd-hpa or similar and on MacOS X TftpServer Version 3.4.1 was used.
 +
 +Some people have reported tftpd-hpa not working as tftp server in debricking.  Wireshark shows the server complaining 'must use absolute filename' and the transfer does not start. Others have reported that at least tftp-hpa versions released year 2013 and after work. To be sure use tftpd with the default configuration.
 +
 +=== 2.3 ===
 +Check that the file exists in your tftp server root folder e.g. /srv/tftp or /var/lib/tftp or your current directory depending on your software.
 +
 +=== 2.4 ===
 +
 +Setup your interface. It doesn't matter which port of the router you use. Set your tftp server IP to 192.168.11.2/24.
 +
 +Optional for Linux using tftpd. Confirm the server is available with:
 +
 +<code>
 +nmap -p 69 192.168.11.2
 +</code>
 +
 +If running correctly you will see something like:
 +
 +<code>
 +PORT  STATE  SERVICE
 +69/tcp closed tftp
 +</code>
 +
 +Otherwise try restarting inetd:
 +
 +<code>
 +For Debian Wheezy
 +
 +root@Hostname:~# /etc/init.d/openbsd-inetd restart
 +</code>
 +
 +
 +=== 2.5 ===
 +
 +Push the AOSS button and power on the router. Keep the AOSS button for about 5 seconds pushed. When the AOSS button is pushed the LED below power will also light up on start. You can verify with wireshark, if everything works as expected. There should be a tftp request from 192.168.11.1 to 192.168.11.2 for a file firmware.ram. Then This file will be transmitted and after that the ip 192.168.11.1 vanishs, because you see your computer asking to whom this ip belongs.
 +
 +=== 2.6 ===
 +Ping 192.168.1.1 You may also do a DHCP request, which will be answered if your router booted fine. Router may not necessarily give any signal via LED if it is ready or not.
 +
 +=== 2.7 ===
 +
 +Flash a working image: Telnet to device, set ssh password, copy squashfs image to your device with scp and sysupgrade squashfsimage.
 +
 +
 +
 +===== Configuration =====
 +
 +Although the WBMR-HP-G300H is supported in the current stable Attitude Adjustment 12.9 release, the pre-compiled image is fairly basic and must be tuned to work properly (ADSL, wifi, LUCI web interface and LEDs).
 +
 +==== Turn on ADSL nas0 interface in Attitude Adjustment 12.09 ====
 +
 +The ADSL interface is disabled in the Attitude Adjustment 12.09 image so turn it on:
 +<code>
 +/etc/init.d/br2684ctl enable
 +/etc/init.d/br2684ctl start
 +</code>
 +
 +With Barrier Breaker 14.07 this is not necessary.
 +
 +==== Configure ADSL ====
 +
 +=== Attitude Adjustment 12.09 ===
 +
 +Precompiled image contains ADSL annex B only (for ISDN lines). For POTS (old-fashioned telephone line), you need annex A. Remove kmod-ltq-dsl-firmware-b-ar9 and install kmod-ltq-dsl-firmware-a-ar9 instead.
 +
 +Add suitable configuration in /etc/config/network
 +
 +  * PPPoA example: [[doc:uci:network#PPPoA ADSL internet connection]]
 +
 +  * PPPoE example:
 +<code>
 +config adsl-device 'adsl'
 + option fwannex 'a'
 + option annex 'a2p'
 +
 +config atm-bridge 'atm'
 + option vpi '8'
 + option vci '35'
 + option encaps 'llc'
 + option payload 'bridged'
 + option unit '0'
 +
 +config interface 'wan'
 + option ifname 'nas0'
 + option proto 'pppoe'
 + option username 'user@isp.net'
 + option password 'XXXXXXXXX'
 +</code>
 +
 +fwannex a is for normal telephone lines, fwannex b is for ISDN. Option annex a2p means ADSL2+, annex a is standard ADSL. Username and password options are often not needed.
 +
 +=== Barrier Breaker 14.07 ===
 +
 +In /etc/config/network setup ADSL type. For analog telephone lines use annex a and for ISDN use annex b, see example below.
 +
 +<code>
 +config adsl 'dsl'
 + option annex 'b'
 + option firmware '/lib/firmware/adsl.bin'
 +</code>
 +
 +The preinstalled ADSL firmware is annex b. To use annex a remove the firmware package and install the annex a firmware https://downloads.openwrt.org/barrier_breaker/14.07/lantiq/xway/packages/base/kmod-ltq-adsl-ar9-fw-a_0.1-1_lantiq.ipk. VPI and VCI values can be defined in the same /etc/config/network file or in web interface under Network, Interfaces.
 +
 +==== Configure WIFI ====
 +
 +=== Attitude Adjustment 12.09 ===
 +
 +For wifi install kmod-ath9k and generate a wireless config.
 +<code>
 +opkg install kmod-ath9k
 +wifi detect >> /etc/config/wireless
 +</code>
 +
 +=== Barrier Breaker 14.07 ===
 +
 +Module is installed by default.
 +
 +==== LUCI web interface ====
 +
 +Install the package luci. Then you need to enable and start uhttpd
 +
 +<code>
 +opkg install luci
 +/etc/init.d/uhttpd enable
 +/etc/init.d/uhttpd start
 +</code>
 +
 +==== Configure switch ====
 +
 +See below: [[toh:buffalo:wbmr-hp-g300h#Wired stations cannot ping each other]] .
 +
 +
 +
 +==== LEDs ====
 +
 +=== Attitude Adjustment 12.09 ===
 +
 +LED configuration must be placed in /etc/config/system. Here is an example:
 +
 +<code>
 +config led
 +    option default '0'
 +    option name 'power'
 +    option sysfs 'soc:green:power'
 +    option trigger 'default-on'
 +
 +config led
 +    option default '0'
 +    option name 'power2'
 +    option sysfs 'soc:red:power'
 +    option trigger 'none'
 +
 +config led
 +    option default '0'
 +    option name 'wifi'
 +    option sysfs 'soc:green:wlan'
 +    option trigger 'phy0tpt'
 +
 +config led
 +    option default '0'
 +    option name 'security'
 +    option sysfs 'soc:red:security'
 +    option trigger 'phy0tpt'
 +
 +config led
 +    option default '0'
 +    option name 'dsl'
 +    option sysfs 'soc:green:adsl'
 +    option trigger 'netdev'
 +    option dev 'nas0'
 +    option mode 'link tx rx'
 +
 +config led
 +    option default '0'
 +    option name 'online'
 +    option sysfs 'soc:green:internet'
 +    option trigger 'none'
 +
 +config led
 +    option default '0'
 +    option name 'online2'
 +    option sysfs 'soc:red:internet'
 +    option trigger 'netdev'
 +    option dev 'nas0'
 +    option mode 'tx rx'
 +
 +config led
 +    option default '0'
 +    option name 'usb'
 +    option sysfs 'soc:green:usb'
 +    option trigger 'default-on'
 +
 +config led
 +    option default '0'
 +    option name 'movie'
 +    option sysfs 'soc:blue:movie'
 +    option trigger 'timer'
 +    option delayon '1000'
 +    option delayoff '1000'
 +</code>
 +
 +There are some slightly better LED's in Barrier Breaker (warning: experimental!) trunk.
 +
 +=== Barrier breaker 14.07 ===
 +
 +Go to the web interface System, Led configuration to define the leds. For dsl use nas0 and check "Linkon, Transmit and Receive". (Is there a better way to define adsl led? If linkon is defined on nas0 adsl light will be always on, transmit and receive will blink it.)
===== Hardware ===== ===== Hardware =====
Line 12: Line 259:
| **[[doc:techref:Bootloader]]:**    | U-Boot 1.00 | | **[[doc:techref:Bootloader]]:**    | U-Boot 1.00 |
| **[[doc:hardware:soc|System-On-Chip]]:**  | Lantiq AR9 | | **[[doc:hardware:soc|System-On-Chip]]:**  | Lantiq AR9 |
-| **[[doc:hardware:cpu|CPU]]/Speed**        | MIPS 34Kc / 333MHz |+| **[[doc:hardware:cpu|CPU]]/Speed**        | MIPS 34Kc / 333MHz [[http://www.lantiq.com/uploads/tx_abzlantiqproducts/PB-e-0016-v1_lres.pdf|Lantiq PSB 50810]] |
| **Flash-Chip:**      |  | | **Flash-Chip:**      |  |
| **Flash size:**      | 32MB | | **Flash size:**      | 32MB |
| **RAM:**            | 64MB  | | **RAM:**            | 64MB  |
| **Wireless:**        | Atheros AR9280 Rev:2 | | **Wireless:**        | Atheros AR9280 Rev:2 |
-| **Ethernet:**        | 4 x Gigabit |+| **Ethernet:**        | 4 x Gigabit Atheros AR8316 |
| **Modem:**          | Lantiq ADSL2+  | | **Modem:**          | Lantiq ADSL2+  |
-| **USB:**            | Yes 1 x 2.0 (driver dwc_otg)    |+| **USB:**            | Yes 1 x 2.0 (driver dwc_otg)    |
| **[[doc:hardware:port.serial|Serial]]:** | [[#Serial|Yes]] | | **[[doc:hardware:port.serial|Serial]]:** | [[#Serial|Yes]] |
| **[[doc:hardware:port.jtag|JTAG]]:**    | [[#JTAG|Yes]]  | | **[[doc:hardware:port.jtag|JTAG]]:**    | [[#JTAG|Yes]]  |
Line 29: Line 276:
==== Disassemble ==== ==== Disassemble ====
-For disassembling the device you need a Torx T8 screwdriver that is _AT LEAST_ 1,6cm long (with some preasure Torx T9 works too). A normal torx bit won't fit because the screws are sunk very deep so you won't reach them+For disassembling the device you need a Torx T8 screwdriver WITH HOLE that is AT LEAST 16mm long (with some preasure Torx T9 works too). A normal torx bit won't fit because the screws are sunk very deep so you won't reach them.
- +
-==== Remaining Problems ==== +
- +
-<html><font color=red><del>JFFS2 builds won't work because of kernel panic at start up (no init found) as of r34578. See bug report #12596 and #12373.</del></font></html> +
- +
-Some models of the WBMR-HP-G300H need the jffs2 builds with 128K blocks. Specially those with erase size "0x0020000". Release >= r34578 works fine. +
- +
-<html><font color=red>Warning: Since at least r34699 there is no support for this router anymore at all.</font></html> See [[https://dev.openwrt.org/ticket/12622|Ticket 12622]] The last one that worked for me was r34655. Maybe someone could figure it out what the highest working svn reslease version is.+
==== Serial ==== ==== Serial ====
Line 49: Line 288:
PIN 4: RX\\ PIN 4: RX\\
Use the following settings: ''115200 8N1''. Use the following settings: ''115200 8N1''.
 +
 +<html><font color=red>Caution: Be very careful with the serial interface! It is very fragile! Therefore never use the Vcc Pin. I destroyed my Buffalo by applying all four cables (works fine) and then unplug the main power supply. This will destroy the router electrically! So never ever use Vcc aka Pin1!!!<br>
 +Also with only GND, TX and RX without VCC I destroyed the router electrically. So is better unplug serial before unplug the main power.
 +</font></html>
 +
 +==== JTAG ====
 +The [[doc:hardware:port.jtag#pin.header2|pinout]] use the standard MIPS
 +
 +
==== Flash ==== ==== Flash ====
Line 80: Line 328:
</code> </code>
-===== Wired stations cannot ping each other ===== 
-This is a known bug: [[https://dev.openwrt.org/ticket/11143|switch eth0(Atheros AR8316) no traffic between ports possible]]\\ 
-Based on the comments from the bug you can try these commands: 
-<code> 
-swconfig dev eth0 vlan 1 set ports "0 1 2 3 4 5" 
-swconfig dev eth0 set apply 
-</code> 
-If these work you can add the following lines to your /etc/config/network: 
-<code>config switch 
- option name 'eth0' 
- option reset '1' 
-config switch_vlan 
- option vlan '1' 
- option device 'eth0' 
- option ports '0 1 2 3 4 5'</code> 
-===== How to recover from bricking ===== +===== Bugs =====
-The router bootloader has a tftp client, which will try to connect to 192.168.11.2 and load a file called firmware.ram.+
-1. Build ramdisk image. These images have uImage in their name, but you can't take the one which you get a during normal build or download. You have to setup a buildroot environment and configure it to build a [[doc:howto:build|ramdisk image]] (make menuconfig --> Target Images --> ramdisk). The uImage file which worked for me was about the same size of a squashfs image (~3.5MB).\\ +=== Barrier breaker 14.07 ===
-TODO It would be helpfull to provide a uImage, but I don't know where to upload one.+
-Note: If you don't want to build you own ramdisc image here is mine: [[http://wiki.openwrt.org/_media/toh/buffalo/openwrt-lantiq-ar9-wbmr-uimage.tar00.zip]] and [[http://wiki.openwrt.org/_media/toh/buffalo/openwrt-lantiq-ar9-wbmr-uimage.tar01.zip]]. It is a tar split archive. The .zip extension has no meaning but was nessesarry to get it uploaded to openwrt.orgs wiki archive. To extract the image you have to use the following command:+None we hope.
-<code> 
-cat openwrt-lantiq-ar9-wbmr-uimage.tar* | tar xzpvf - 
-</code> 
- 
-The OpenWRT version of the image is "Attitude Adjustment, r33838". No further packages have been added. 
- 
-2. Install and start a tftp server. For linux there is a package called tftpd-hpa and on MacOS X TftpServer Version 3.4.1 was used. 
- 
-3. Copy openwrt-lantig-ar9-WBMR-uImage as firmware.ram into the root directory of your tftp server (e.g. /srv/tftp or /var/lib/tftp or your current directory depending on your software) 
-4. Setup your interface. It doesn't matter which port of the router you use. Set your IP to 192.168.11.2/24. It may be nessecary to set your gateway ip to 192.168.11.1 (confirmation needed) 
-5. Push the AOSS button and power on the router. Keep the AOSS button for about 5 seconds pushed. When the AOSS button is pushed the LED below power will also light up on start. You can verify with wireshark, if everything works as expected. There should be a tftp request from 192.168.11.1 to 192.168.11.2 for a file firmware.ram. Then This file will be transmitted and after that the ip 192.168.11.1 vanishs, because you see your computer asking to whom this ip belongs.+===== Troubleshooting ======
-6. Wait. If you have wifi configured in your image you see wifi come up after a while. Another way is to ping 192.168.1.1 or the ip you have configured in your image. You may also do a DHCP request, which will be answered if your router booted fine. My router did not give any signal via LED if it is ready or not. Also during normal operation no LED is on, except for the one in the LAN ports.+==== Broken setup ====
-7. Flash a working image. Now you have access again, but keep in mind, that this image is not flashed and only runs in ram. Flash a clean image via your preferred way. You can do this with the webinterface or ssh/telnet and sysupgrade.+If the device does not boot you can recover using the "Install with tftp" option.
-===== DSL Firmware =====+==== DSL Firmware =====
If PPP discovery is failing: If PPP discovery is failing:
Line 132: Line 353:
Sep  8 15:50:01 OpenWrt daemon.notice netifd: Interface 'wan' is now down Sep  8 15:50:01 OpenWrt daemon.notice netifd: Interface 'wan' is now down
</code> </code>
-it way be worth checking that the correct firmware is loaded for your DSL annex, POTS is annex a and ISDN is annex b.+it way be worth checking that the correct firmware is loaded for your DSL annex, POTS (normal telephone lines) is annex a and ISDN is annex b.
To check this execute To check this execute
Line 141: Line 362:
If the incorrect firmware is loaded, remove it and install the other before trying again. If the incorrect firmware is loaded, remove it and install the other before trying again.
-===== Link Dump =====+ 
 + 
 + 
 +===== Useful commands ===== 
 +Check DSL line status: 
 +<code>/etc/init.d/dsl_control status</code> 
 + 
 +Update firmware: 
 +<code>sysupgrade openwrt-lantiq-xway-WBMR-squashfs.image</code> 
 + 
 +===== Feedback ===== 
 + 
 +2013-08-29 admax: "Good instructions, tftp flashing works well, stable device. Configuring took some time but has been running well ever since." 
 + 
 +2013-08-30 kitsunemura: "Really well written wiki. Device is really stable, I used the recovery method once and it worked fine. I don't really recommend using Transmission on this router because it is not really stable. Using NFS is the fastest way to transfer files from/to USB(EXT4)." 
 + 
 +2014-10-09 admax: "Barrier breaker is even better." 
 + 
 +===== WebLinks =====
  * [[https://forum.openwrt.org/viewtopic.php?id=34072|OpenWrt Forum Thread on Buffalo WBMR-HP-G300H]]   * [[https://forum.openwrt.org/viewtopic.php?id=34072|OpenWrt Forum Thread on Buffalo WBMR-HP-G300H]]
  * [[https://forum.openwrt.org/viewtopic.php?id=35764|Which image file for WBMR-HP-G300H]]   * [[https://forum.openwrt.org/viewtopic.php?id=35764|Which image file for WBMR-HP-G300H]]
===== Tags ===== ===== Tags =====
-{{tag>GigabitEthernet 5Port 2PHY USB JTAG 64RAM 32Flash MIPS ADSL2plus}}+{{tag>GigabitEthernet 5Port 2NIC USB JTAG 64RAM 32Flash MIPS ADSL2+ lantiq ar9}}

Back to top

toh/buffalo/wbmr-hp-g300h.1355587391.txt.bz2 · Last modified: 2012/12/15 17:03 (external edit)