User Tools

Site Tools


toh:bt:homehub_v2b

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
toh:bt:homehub_v2b [2013/07/02 10:45]
lorema so is this supported or not?
toh:bt:homehub_v2b [2014/12/09 10:05] (current)
Reflected_God [Installation]
Line 1: Line 1:
 ====== BT HomeHub 2.0 Type B ====== ====== BT HomeHub 2.0 Type B ======
 +
 Black boxes given away with a bt broadband subscription. It comes in two versions Type A and Type B. The two versions look identical, and although they provide similar functionality,​ they are quite different on the inside. Black boxes given away with a bt broadband subscription. It comes in two versions Type A and Type B. The two versions look identical, and although they provide similar functionality,​ they are quite different on the inside.
  
Line 7: 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. ​ +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.
- +
-Until the patches come through to trunk, source mods for building OpenWRT for Type B are here: +
-https://​sourceforge.net/​p/​hh2b4ever/​code/​ci/​7c17843ab0596dccb2bd972ed9df6c4ccd9995a8/​tree/​ +
- +
-latest info:  binary at sourceforge for annexa works, although the leds are squiffy and the ADSL reports a fault but works. +
-see http://​www.psidoc.com/​showthread.php/​495-OpenWRT-on-HHV2B for details +
- +
-News 25/3/2012: Thanks to blogic, some patches went into trunk today.... +
-[[toh:​BT:​homehub_v2b:​trunkbuild|Building from trunk]] +
  
 ===== 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  |   | - |  ​?  ​| - |+| Type B  |   | - |  ​Barrier Breaker 14.07 | - |
  
 +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.
  
 +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 =====
-->[[doc:howto:generic.flashing]]+ 
 +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 [[toh:​bt:​homehub_v2b#​support_and_links|Support and Links 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: 
 + 
 +openwrt-lantiq-xway-BTHOMEHUBV2B-uImage 
 +(kernel image to install) 
 + 
 +openwrt-lantiq-xway-BTHOMEHUBV2B-uImage-initramfs 
 +(initramfs image, used only during the installation process) 
 + 
 +plus one of the following root filesystem images:  
 + 
 +openwrt-lantiq-xway-BTHOMEHUBV2B-squashfs-ubinized.bin 
 +(squashfs/​ubifs overlay) 
 + 
 +openwrt-lantiq-xway-BTHOMEHUBV2B-ubifs-ubinized.bin 
 +(ubifs) 
 + 
 +The following instructions assume you are using the overlay image. Simply replace openwrt-lantiq-xway-BTHOMEHUBV2B-squashfs-ubinized.bin with openwrt-lantiq-xway-BTHOMEHUBV2B-ubifs-ubinized.bin if you prefer to use the pure ubifs image. 
 + 
 +Copy kernel images to your tftpboot folder: 
 + 
 +    cp openwrt-lantiq-xway-BTHOMEHUBV2B-uImage-initramfs /​var/​lib/​tftpboot/​ 
 +    cp openwrt-lantiq-xway-BTHOMEHUBV2B-uImage /​var/​lib/​tftpboot/​ 
 + 
 +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 
 +    nand erase 0x004000 0x1ffC000 
 +    nand write 81000000 0x004000 0x200000 
 + 
 +DO NOT BOOT THIS IMAGE YET! Instead, load the ramdisk image and boot that: 
 + 
 +    tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage-initramfs 
 +    bootm 81000000 
 + 
 +VERY IMPORTANT! The above lines are only for the very first time that you install a ubi-enabled image. On subsequent occasions you should not erase the whole nand, only the kernel partition, otherwise wear leveling data for the ubi partition will be lost. So for subsequent installs the above five lines become: 
 + 
 +    tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage 
 +    nand erase 0x004000 0x200000 
 +    nand write 81000000 0x004000 0x200000 
 + 
 +    tftpboot 81000000 openwrt-lantiq-xway-BTHOMEHUBV2B-uImage-initramfs 
 +    bootm 81000000 
 + 
 +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 (download pscp and use "pscp -scp" instead of just "​scp"​ if you are using Windows): 
 + 
 +    scp openwrt-lantiq-xway-BTHOMEHUBV2B-squashfs-ubinized.bin root@192.168.1.1:/​tmp 
 + 
 +On the Home Hub, format the ubi partition using the ubi image just copied: 
 + 
 +    ubidetach -p /dev/mtd7 
 +    ubiformat /dev/mtd7 -f /​tmp/​openwrt-lantiq-xway-BTHOMEHUBV2B-squashfs-ubinized.bin 
 + 
 +    reboot 
 + 
 +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 
 + 
 +You can add this boot options using [[doc:devel:packages:​uboot-envtools|uboot-envtools package]]
 +If this is not already the case, interrupt the boot process and execute them manually from the uboot prompt. 
 + 
 +===== Alternative adsl firmware ===== 
 + 
 +The default openwrt-supplied adsl firmware works well for the majority of people. If, however, you're using a POTS (Annex-A) connection and you suffer from frequent adsl disconnections,​ it may be worth trying out replacing the standard firmware blob (/​lib/​firmware/​ltq-dsl-fw-a-danube.bin,​ md5sum: a6c7836e2cc3d26172b15e4732ae636f) with the original BT-distributed firmware blob (md5sum: a8a49c615da9453fe790073c224c5e58). This method has cured the "adsl disconnections"​ problem for the author of this section, and is documented at http://​openwrt.ebilan.co.uk/​viewtopic.php?​f=4&​t=68 (you can download the BT-distributed firmware blob from that location too). 
 + 
 +===== Support and Links ===== 
 + 
 +Following the sad closure of http://​psidoc.com,​ the best source of support is probably http://​openwrt.ebilan.co.uk. 
 + 
 +Instructions on how to obtain access to the bootloader can be found here: 
 +http://​openwrt.ebilan.co.uk/​viewtopic.php?​f=11&​t=6 
 + 
 +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 
 + 
 +For reference, the initial work done to get OpenWRT running on the Home Hub 2B is available here: 
 + 
 +http://​sourceforge.net/​projects/​hh2b4ever/​ 
 + 
 +https://​sourceforge.net/​p/​hh2b4ever/​code/​ci/​7c17843ab0596dccb2bd972ed9df6c4ccd9995a8/​tree/​ 
 + 
 + 
  
 ===== Firmware ===== ===== Firmware =====
Line 77: Line 162:
 | **Vendor:​** ​         | [[wp>​Lantiq]] ​ | | **Vendor:​** ​         | [[wp>​Lantiq]] ​ |
 | **[[doc:​techref:​Bootloader]]:​** ​    | [[doc:​techref:​bootloader:​uboot|U-Boot]] | | **[[doc:​techref:​Bootloader]]:​** ​    | [[doc:​techref:​bootloader:​uboot|U-Boot]] |
-| **[[doc:​hardware:​soc|System-On-Chip]]:​** ​ |[[http://www.lantiq.com/products/broadband-customer-premises-equipment/​adsl/​xwaytm-danube/​xwaytm-danube-s/|Lantiq Danube-S ​PSB 50712]] ​@ 333MHz ​+| **[[doc:​hardware:​soc|System-On-Chip]]:​** ​ |[[http://pdf.datasheetarchive.com/indexerfiles/Datasheets-UD3/DSAUD0055683.pdf|Lantiq Danube ​PSB-S 50712 (MIPS 24Kec)]]| 
-| **[[doc:​hardware:​cpu|CPU]]/​Speed:​** ​       | MIPS34Kc@333 MHz |+| **[[doc:​hardware:​cpu|CPU]]/​Speed:​** ​       | 333 MHz Dual Core|
 |**NOR Flash:** |[[http://​www.spansion.com/​Support/​Datasheets/​S29AL004D_00.pdf|Spansion S29AL004D]] ​ 4MiB | |**NOR Flash:** |[[http://​www.spansion.com/​Support/​Datasheets/​S29AL004D_00.pdf|Spansion S29AL004D]] ​ 4MiB |
 |**NAND Flash:** |[[http://​www.kontest.ru/​datasheet/​samsung/​k9f5608u0d.pdf|Samsung K9F5608U0D-JIB0]] 32MiB | |**NAND Flash:** |[[http://​www.kontest.ru/​datasheet/​samsung/​k9f5608u0d.pdf|Samsung K9F5608U0D-JIB0]] 32MiB |
Line 107: Line 192:
  
 ==== GPIOs ==== ==== GPIOs ====
-The CPU has 2 x 16 possible GPIO\\ +The CPU has 2 x 16 possible GPIO pins.\\ 
-The board provides a further 24? GPOs (for leds) controlled by stp\\ +For each pin there are control bits:\\ 
-for each pin there are control bits  +DIR: direction ​(0=input, 1=output)\\ 
-dir = direction +IN/​OUT: ​value read from/​written to pin\\ 
-out = value? +ALTSEL0/ALTSEL1: function multiplexed to the pin (see pinctrl driver)\\ 
-altsel0/altsel1 +OD: 0=open drain, 1='​normal mode' ​push-pull\\ 
-od - 0=open drain, 1='​normal mode' ​puch pull +PUDSEL: ​pullup/down select ​(1=up)\\ 
-pudsel = pullup/down select 1=up +PUDEN: pullup/down enable ​(1=enabled)\\
-puden = pull up/down enable+
  
 uboot initial values\\ uboot initial values\\
Line 123: Line 207:
 |GPIO-01|0 in |1 |1 |0 |1 |0 |0 | FXO Interrupt| |GPIO-01|0 in |1 |1 |0 |1 |0 |0 | FXO Interrupt|
 |GPIO-02|0 in |1 |0 |0 |1 |0 |0 | Reset button| |GPIO-02|0 in |1 |0 |0 |1 |0 |0 | Reset button|
-|GPIO-03|1 out|1 ||0 |1 |0 |0 | CLK-OUT2 - (25mhz for amd9669i? - danube_clock.c in u-boot)|+|GPIO-03|1 out |1 ||0 |1 |0 |0 | CLK-OUT2 - (25mhz for amd9669i? - danube_clock.c in u-boot)|
 |GPIO-04|1 out|1 |1 |0 |1 |0 |0 | - stp-st (maybe also likely boot clock select 1 = 36mhz)| |GPIO-04|1 out|1 |1 |0 |1 |0 |0 | - stp-st (maybe also likely boot clock select 1 = 36mhz)|
 |GPIO-05|1 out|1 |1 |0 |1 |0 |0 | - stp-d| |GPIO-05|1 out|1 |1 |0 |1 |0 |0 | - stp-d|
Line 136: Line 220:
 |GPIO-12|0 in |1 |1 |0 |1 |0 |0 || |GPIO-12|0 in |1 |1 |0 |1 |0 |0 ||
 |GPIO-13|1 out|1 |1 |0 |1 |0 |0 |- USB Power| |GPIO-13|1 out|1 |1 |0 |1 |0 |0 |- USB Power|
-|GPIO-14|0 in |1 |0 |0 |1 |1 |1 | find handset button ​pulled up+|GPIO-14|0 in |1 |0 |0 |1 |1 |1 |-| 
-|GPIO-15|0 in |1 |0 |0 |0 |0 |0 |-| +|GPIO-15|0 in |1 |0 |0 |0 |0 |0 |- find handset button
 |name|dir|out|altsel0|altsel1|od|pudsel|puden|usage| |name|dir|out|altsel0|altsel1|od|pudsel|puden|usage|
 |-      |BE   ​|D7|87|00|FC|50|50|-| |-      |BE   ​|D7|87|00|FC|50|50|-|
Line 188: Line 272:
 |INIT_VAL_P1_PUDEN ​      ​|0850| |INIT_VAL_P1_PUDEN ​      ​|0850|
  
 +The board provides a further 24? GPOs (for leds) controlled by stp.\\
  
 ==== Buttons ==== ==== Buttons ====
Line 196: Line 281:
  
 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 ====
Line 229: Line 316:
  
 The calibration data is stored in the first 0x4000 bytes of the nand\\ The calibration data is stored in the first 0x4000 bytes of the nand\\
-the first 0x60 of these contain PCI register fixups, organised as Reg16:​Value32. ​ These need to be written to the PCI register space BEFORE the PCI device is probed...  ​This leads to the issue that the PCI device ​is probed before the nand is active, so before we can get to the data, so a scheme of hardcoding these register fixups and calling the writing routine as a DECLARE_PCI_FIXUP_EARLY routine works. ​ The actual eeprom data can be read later as part of the ath9k initialisation by utilising the hook ltqpci_plat_dev_init().\\ +the first 0x60 of these contain PCI register fixups, organised as Reg16:​Value32. ​ These need to be written to the PCI register space BEFORE the PCI device is probed...  ​Support for this is now in trunk (Barrier Breaker).
- +
-The eeprom data needs to be byte-swapped,​ then the data which is meant to be words byte swapped again. ​ We can't currently tell Ath9k to handle this without patching ath9k, but once done, it works.\\+
  
-unfortunately,​ wireless (PCI) and NAND (EBU) interact. ​ for the moment, PCI gets inhibited while the nand chip is selected; I felt it better to have some wireless degradation rather than file system corruption.\\+unfortunately,​ wireless (PCI) and NAND (EBU) interact. ​ for the moment, PCI gets inhibited while the nand chip is selected; I felt it better to have some wireless degradation rather than file system corruption.
  
  
toh/bt/homehub_v2b.1372754725.txt.bz2 · Last modified: 2013/07/02 10:45 by lorema