Differences

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

toh:bt:homehub_v2b [2014/07/29 14:37]
benm
toh:bt:homehub_v2b [2014/10/08 16:23] (current)
benm
Line 8: Line 8:
The homehub V2 includes ADSL2+, 802.11b/g/n wireless, host USB port, 4 wired ethernet ports, DECT, FXS & FXO ports and VOIP functionality. The homehub V2 includes ADSL2+, 802.11b/g/n wireless, host USB port, 4 wired ethernet ports, DECT, FXS & FXO ports and VOIP functionality.
-The firmware of both units can be successfully hacked for use on other ISPs (see www.psidoc.com).  The Type A firmware is a litlte more flexible than the Type B firmware in terms of what can be done after gaining access. However, the Type B can be made to work with OpenWRT.+The firmware of both units can be successfully hacked for use on other ISPs (see http://openwrt.ebilan.co.uk/).  The Type A firmware is a litlte more flexible than the Type B firmware in terms of what can be done after gaining access. However, the Type B can be made to work with OpenWRT.
===== Supported Versions ===== ===== Supported Versions =====
^ Version/Model ^ Launch Date ^ S/N ^ OpenWrt Version Supported ^ Model Specific Notes ^ ^ Version/Model ^ Launch Date ^ S/N ^ OpenWrt Version Supported ^ Model Specific Notes ^
| Type A  |  | - |  ?  | - | | Type A  |  | - |  ?  | - |
-| Type B  |  | - |  Barrier Breaker | - |+| Type B  |  | - |  Barrier Breaker 14.07 | - |
-Attitude Adjustment contains a profile for the Type B, but support is incomplete. Unofficial patches do however exist to build a working image. A community build using these patches is also available, of trunk version 34686 (ie a snapshot shortly before the Attitude Adjustment release). See below for details.+Attitude Adjustment contained a profile for the Type B, but support was incomplete. A community build exists of trunk version 34686 (ie a snapshot shortly before the Attitude Adjustment release). See http://openwrt.ebilan.co.uk/ for details.
-Barrier Breaker contains full support for router/modem functionality on the Type B. Telephony (DECT and FXO/FXS) is not supported.+The Type B is supported in Barrier Breaker. That is to say, router/modem functionality is fully working. Telephony (DECT and FXO/FXS) is not supported.
===== Hardware Highlights ===== ===== Hardware Highlights =====
^ CPU ^ Ram ^ Flash ^ Ethernet ^ USB ^ Wireless ^ Serial ^ JTag ^ VOIP ^ FXS ^ ^ CPU ^ Ram ^ Flash ^ Ethernet ^ USB ^ Wireless ^ Serial ^ JTag ^ VOIP ^ FXS ^
-| Lantiq Danube@333MHz | 64MB | 32MB NAND+512k NOR | 4 | Yes | 11ng | Yes | Yes | yes | yes |+| Lantiq Danube@333MHz | 64MB | 32MB NAND+512k NOR | 4 | yes | 11ng | yes | ??? | yes | yes |
===== Installation ===== ===== Installation =====
-These instructions assume you have already unblocked your Home Hub 2B, have updated uboot and have access to the uboot console. If you have not yet done this, see next section. 
-The main main flash memory on the Home Hub 2B is nand, not nor, As a result, a squashfs/ubifs overlay is used instead of the standard squashfs/jffs2 overlay image used on most other routers, Similarly, a ubifs image is used instead of a jffs2 image. Also, there are two separate files to flashed, on for the kernel, the other for the (ubinized) root filesytem.+These instructions assume you are installing Barrier Breaker 14.07 final release, or a recent trunk build (from r42316 onwards). Earlier versions require a different installation procedure.  
 + 
 +They also assume you have already unblocked your Home Hub 2B, have updated uboot and have access to the uboot console. If you have not yet done this, see next section. 
 + 
 +The main main flash memory on the Home Hub 2B is nand, not nor, Because of this, ubi is used for bad block management on the root partition. So a squashfs/ubifs overlay is used instead of the standard squashfs/jffs2 overlay image used on most other routers, Similarly, a ubifs image is used instead of a jffs2 image. Also, whereas for most routers OpenWRT consists of a single image containing the the kernel and root filesystem concatenated, for the Home Hub there are two separate files to be flashed, one for the kernel, the other for the (ubinized) root filesytem.
You will need the following files: You will need the following files:
Line 52: Line 55:
    cp openwrt-lantiq-xway-BTHOMEHUBV2B-uImage /var/lib/tftpboot/     cp openwrt-lantiq-xway-BTHOMEHUBV2B-uImage /var/lib/tftpboot/
-From the uboot prompt on the Home Hub:+Erase the nand flash, preserving only the first 0x4000 bytes which contain calibration data for the wireless card. Then flash the kernel image. From the uboot prompt on the Home Hub:
    tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage     tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage
    nand erase 0x004000 0x1ffC000     nand erase 0x004000 0x1ffC000
-    nand write 81000000 0x004000 0x160000+    nand write 81000000 0x004000 0x200000
DO NOT BOOT THIS IMAGE YET! Instead, load the ramdisk image and boot that: DO NOT BOOT THIS IMAGE YET! Instead, load the ramdisk image and boot that:
Line 66: Line 69:
    tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage     tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage
-    nand erase 0x004000 0x160000 +    nand erase 0x004000 0x200000 
-    nand write 81000000 0x004000 0x160000+    nand write 81000000 0x004000 0x200000
    tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage-initramfs     tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage-initramfs
    bootm 81000000     bootm 81000000
-Now log in to a console on the Home Hub, make sure that the dropbearkey process has finished running and enable ssh by setting a root password.+Now use the ramdisk image to flash the root filesystem. Log in to a console on the Home Hub, make sure that the dropbearkey process has finished running and enable ssh by setting a root password.
From the PC, copy the ubinized root filesystem image to the Home Hub: From the PC, copy the ubinized root filesystem image to the Home Hub:
Line 85: Line 88:
    reboot     reboot
-At this point cross your fingers and hope that everything works!!!+To boot into OpenWRT automatically, the uboot environment needs to be set up to execute the following commands automatically on power on: 
 + 
 +    nand read 81000000 0x004000 0x200000 
 +    bootm 81000000 
 + 
 +If this is not already the case, interrupt the boot process and execute them manually from the uboot prompt.
===== Support and Links ===== ===== Support and Links =====
Line 94: Line 102:
http://openwrt.ebilan.co.uk/viewtopic.php?f=11&t=6 http://openwrt.ebilan.co.uk/viewtopic.php?f=11&t=6
-Unofficial patches and a community build based on them can be found here:+The unofficial patches used to generate the first fully working images and a community build of trunk r34686 using them can be found here:
http://openwrt.ebilan.co.uk/viewtopic.php?f=4&t=3 http://openwrt.ebilan.co.uk/viewtopic.php?f=4&t=3
Line 268: Line 276:
All buttons are active low. All buttons are active low.
 +
 +There is also a recessed reset button. If anyone can find out what gpio it is connected to, please update this page.
==== LEDS ==== ==== LEDS ====

Back to top

toh/bt/homehub_v2b.1406637452.txt.bz2 · Last modified: 2014/07/29 14:37 (external edit)