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
Next revisionBoth sides next revision
toh:bt:homehub_v2a [2018/02/20 20:13] – ↷ Links adapted because of a move operation toh:bt:homehub_v2a [2024/02/12 13:28] – [Installation] revert Version change bill888
Line 1: Line 1:
-====== BT HomeHub 2.0 Type A ====== +====== BT Home Hub 2.0 Type A ====== 
- +{{:media:bt:homehub2a-cover.png?nolink&0x150}}
-Forum[[https://forum.openwrt.org/viewtopic.php?id=51348]]+
  
 These black boxes were given away with a BT broadband subscription.  They comes in two variants labelled Type A and Type B.  The two look identical, and although they provide the same functionality, they are very different on the inside. These black boxes were given away with a BT broadband subscription.  They comes in two variants labelled Type A and Type B.  The two look identical, and although they provide the same functionality, they are very different on the inside.
Line 14: Line 13:
  
  
-===== Hardware Highlights ===== +{{section>meta:infobox:broadcom_dsl#infobox_for_dataentries&noheader&nofooter&noeditbutton}} 
-^ SoC ^ CPU Speed ^ Ram ^ Flash ^ Ethernet ^ USB ^ Wifi ^ Serial ^ JTag ^ VOIP ^ FXS ^ + 
-| Broadcom 6358 | 300MHz | 64MiB | 16MiB | 4 x 10/100 | Yes | 11n/g | Yes | Yes | yes | yes |+{{section>meta:infobox:broadcom_wifi#infobox_for_dataentries&noheader&nofooter&noeditbutton}}
  
 ===== Supported Versions ===== ===== Supported Versions =====
-Supported since [[https://dev.openwrt.org/changeset/44985|r44985]] (Chaos Calmer).  As with all Broadcom-based units, **internal ADSL is not supported**.+<!-- ToH: { 
 +  "source": "json", 
 +  "dom": "t", 
 +  "paging": false, 
 +  "rotate": true, 
 +  "shownColumns": ["brand", "model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], 
 +  "filterColumns": {"model": "^Home Hub 2$", "version": "^Type A$"} 
 +} --> 
 + 
 +<!-- ToH: { 
 +  "source": "json", 
 +  "dom": "t", 
 +  "paging": false, 
 +  "shownColumns": ["unsupported_functions"], 
 +  "filterColumns": {"model": "^Home Hub 2$", "version": "^Type A$"} 
 +} --> 
 + 
 + 
 +===== Hardware Highlights ===== 
 +<!-- ToH: { 
 +  "source": "json", 
 +  "dom": "t", 
 +  "paging": false, 
 +  "rotate": true, 
 +  "shownColumns": ["model", "version", "cpu", "cpumhz", "flashmb", "rammb", "wlanhardware", "wlan24ghz", "wlan50ghz", "ethernet100mports", "ethernet1gports", "modem", "usbports"], 
 +  "filterColumns": {"model": "^Home Hub 2$", "version": "^Type A$"} 
 +} --> 
 + 
 + 
 +===== Installation ===== 
 +<!-- ToH: { 
 +  "source": "json", 
 +  "dom": "t", 
 +  "paging": false, 
 +  "rotate": true, 
 +  "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareoemstockurl"], 
 +  "filterColumns": {"model": "^Home Hub 2$", "version": "^Type A$"} 
 +} --> 
 +Old firmwares: 
 +^ Version ^ Release date ^ Link ^ kernel ^ Tested ^ 
 +| OpenWrt 17.01.5 (LEDE Reboot) | 2018-16-06 | [[https://downloads.openwrt.org/releases/17.01.5/targets/brcm63xx/generic/lede-17.01.5-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin|lede-17.01.5-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin]] | 4.4.92 |  ✔  | 
 +| OpenWrt 15.05.1 (Chaos Calmer) | 2016 | [[https://archive.openwrt.org/chaos_calmer/15.05.1/brcm63xx/generic/openwrt-15.05.1-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin|openwrt-15.05.1-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin]] | 3.18.23 |  ✔  | 
 + 
 +-> [[docs:guide-user:installation:generic.flashing|Install OpenWrt (generic explanation)]]
  
 Installation requires the flashing of a custom CFE first.  Since Type A units always had readily identifiable JTAG pins, [[#flashing_the_new_bootloader|flashing the new bootloader with JTAG]] is the tried-and-tested approach on these units, but **requires 1mm-pitch soldering and some form of JTAG hardware** (although this can be just a Raspberry Pi). Installation requires the flashing of a custom CFE first.  Since Type A units always had readily identifiable JTAG pins, [[#flashing_the_new_bootloader|flashing the new bootloader with JTAG]] is the tried-and-tested approach on these units, but **requires 1mm-pitch soldering and some form of JTAG hardware** (although this can be just a Raspberry Pi).
Line 31: Line 73:
  
 <WRAP center round download 60%> <WRAP center round download 60%>
-[[https://mega.co.nz/#!0dBGXYDD!a5FwQ8_-UMiuZDcR9h1pr1t8SmacK_FpdVtKbfFl98k|CFE-BTHH2A-anyflash.bin]]\\ <color grey>md5sum=d11b987f17198584a27eb183090609fc</color></WRAP>+[[https://drive.google.com/uc?export=download&id=19T4RxIAmNZfgfz7gHl24yXkJCzvEyMEw|CFE_HomeHub2A-anyflash.bin]]\\ <color grey>md5sum=d11b987f17198584a27eb183090609fc</color></WRAP>
 <WRAP center round download 60%> <WRAP center round download 60%>
-[[https://mega.nz/#!NJg1zBbY!2ncHJ6w7f2mBLftqxtpLHNUA8tWoY5yJawRuPFGJPu0|CFE-BTHH2A-anyflash-oxplot-tjtag-pi.bin]]\\ <color grey>md5sum=7f7dcd973ada548d1ebcd9cbcaec17c8</color>+<del>[[https://mega.nz/#!NJg1zBbY!2ncHJ6w7f2mBLftqxtpLHNUA8tWoY5yJawRuPFGJPu0|CFE-BTHH2A-anyflash-oxplot-tjtag-pi.bin]]</del>\\ <color grey>md5sum=7f7dcd973ada548d1ebcd9cbcaec17c8</color> 
 +</WRAP> 
 +<WRAP center round info 60%> 
 +Some users reported after installing the new CFE, if the UART serial port is left disconnected, the bootloader always stops avoiding to load Openwrt. A solution is to pull the UART RX to ground (0V) with a wire. Then OpenWrt will boot automatically without the serial cable connected.
 </WRAP> </WRAP>
  
 Using the OEM firmware for flashing the new bootloader might be also possible.  Please post here or at the forum topic if you work out how to do it. Using the OEM firmware for flashing the new bootloader might be also possible.  Please post here or at the forum topic if you work out how to do it.
- 
-Available firmwares: 
-| Version | Release date | Link | Notes | 
-| Trunk | continuously | [[https://downloads.openwrt.org/snapshots/trunk/brcm63xx/generic/openwrt-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin|openwrt-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin]] | unstable version | 
-| LEDE 17.01.1 | 2017-18-03 | [[https://downloads.lede-project.org/releases/17.01.1/targets/brcm63xx/generic/lede-17.01.1-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin|lede-17.01.1-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin]] | . | 
-| Chaos Calmer | 2016-03-15 |[[https://downloads.openwrt.org/chaos_calmer/15.05.1/brcm63xx/generic/openwrt-15.05.1-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin|openwrt-15.05.1-brcm63xx-generic-HomeHub2A-squashfs-cfe.bin]] | . | 
-| Barrier Breaker | 2014-10-02 | [[https://drive.google.com/uc?export=download&id=0B-EMoBe-_OdBVExGUEdncGFaTlE|OpenWrt-HH2A-Barrier_Breaker_14.07-CFE.zip]] | unofficial backport, leds not working | 
- 
- 
-===== Installation ===== 
- -> [[doc:howto:obtain.firmware]]\\ 
- -> [[docs:user-guide:installation:generic.flashing|Install OpenWrt]] 
  
 Installing Openwrt in this router requires two steps: Installing Openwrt in this router requires two steps:
   - [[#flashing_the_new_bootloader|Install the CFE bootloader]].   - [[#flashing_the_new_bootloader|Install the CFE bootloader]].
-  - [[#cfe_easy_installation|Install openwrt]].+  - [[#cfe_easy_installation|Install OpenWrt]].
  
 ==== Flash Layout ==== ==== Flash Layout ====
Line 60: Line 93:
 This section deals with how you install OpenWrt once the OEM bootloader [[#flashing_the_new_bootloader|is replaced by a new CFE]]. This section deals with how you install OpenWrt once the OEM bootloader [[#flashing_the_new_bootloader|is replaced by a new CFE]].
 With this procedure you will flash the firmware using the [[docs:techref:bootloader|bootloader]] web interface (foolproof): With this procedure you will flash the firmware using the [[docs:techref:bootloader|bootloader]] web interface (foolproof):
-  *Set a **static IP** on your computer, use 192.168.1.35 (or any compatible), and connect the ethernet cable to the router. +  * Set a **static IP** on your computer, use 192.168.1.35 (or any compatible), and connect the ethernet cable to the router. 
-  *Unplug the power cord +  * Unplug the power cord 
-  *Press the button labeled as //Find Handset//, don't release it yet! +  * Press the button labeled as //Find Handset//, don't release it yet! 
-  *Plug the power cord +  * Plug the power cord 
-  *Wait 10 seconds +  * Wait 10 seconds 
-  *Release the //Find Handset// button +  * Release the //Find Handset// button 
-  *Browse to http://192.168.1.1 +  * Browse to ''%%http://192.168.1.1%%'' 
-  *Select .bin file +  * Select .bin file 
-  *Upgrade the image +  * Upgrade the image 
-  *Wait for it to reboot +  * Wait for it to reboot 
-  *Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed.+  * Telnet to 192.168.1.1 and set a root password, or browse to ''%%http://192.168.1.1%%'' if LuCI is installed.
  
 ==== Installation using the TFTP method ==== ==== Installation using the TFTP method ====
-->  [[docs:user-guide:installation:generic.flashing.tftp]]+->  [[docs:guide-user:installation:generic.flashing.tftp]]
 If you want to install a firmware using TFTP, follow these steps (as an alternative to the above install process). If you want to install a firmware using TFTP, follow these steps (as an alternative to the above install process).
-  * Connect a [[docs:hardware:port.serial|serial]] TTL cable to send commands to CFE via serial console software, for loading the firmware via TFTP.+  * Connect a [[docs:techref:hardware:port.serial|serial]] TTL cable to send commands to CFE via serial console software, for loading the firmware via TFTP.
   * Start a TFTP server in your PC. Copy the //**firmware.bin**// file to the TFTP server's directory.   * Start a TFTP server in your PC. Copy the //**firmware.bin**// file to the TFTP server's directory.
   * Set the IP at your pc to 192.168.1.35 (or any compatible), and connect the ethernet cable to the router.   * Set the IP at your pc to 192.168.1.35 (or any compatible), and connect the ethernet cable to the router.
Line 94: Line 127:
  
 ==== Upgrading OpenWrt ==== ==== Upgrading OpenWrt ====
-->  [[docs:user-guide:generic.sysupgrade]]+->  [[docs:guide-user:installation:generic.sysupgrade]]
  
 If you have already installed OpenWrt and like to reflash for e.g. upgrading to a new OpenWrt version you can upgrade using the mtd command line tool. It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing. If you have already installed OpenWrt and like to reflash for e.g. upgrading to a new OpenWrt version you can upgrade using the mtd command line tool. It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.
Line 100: Line 133:
 === LuCI Web Upgrade Process === === LuCI Web Upgrade Process ===
  
-  * Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL+  * Browse to ''%%http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/%%'' LuCI Upgrade URL
   * Upload image file for sysupgrade to LuCI   * Upload image file for sysupgrade to LuCI
   * Wait for reboot   * Wait for reboot
Line 111: Line 144:
 <code> <code>
 cd /tmp/ cd /tmp/
-wget http://http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc +wget https://downloads.openwrt.org/releases/17.01.5/targets/brcm63xx/smp/lede-17.01.5-brcm63xx-smp-HomeHub2A-squashfs-cfe.bin 
-sysupgrade /tmp/xxx.abc+sysupgrade /tmp/lede-17.01.5-brcm63xx-smp-HomeHub2A-squashfs-cfe.bin
 </code> </code>
  
Line 131: Line 164:
 ==== Interfaces ==== ==== Interfaces ====
 The default network configuration is: The default network configuration is:
-^ Interface Name ^ Description ^ Default configuration ^ +^ Interface Name   ^ Description          ^ Default configuration   
-| br-lan | LAN & WiFi | 192.168.1.1/24 |  +| br-lan           | LAN & WiFi           | 192.168.1.1/24          
-| eth0  | LAN ports (1 to 4) | bridged | +| eth0             | LAN ports (1 to 4)   | bridged                 
-| wlan0 | WiFi | disabled | +| wlan0            | WiFi                 | disabled                |
  
  
 ==== Failsafe mode ==== ==== Failsafe mode ====
--> [[docs:user-guide:troubleshooting:failsafe_and_factory_reset]]+-> [[docs:guide-user:troubleshooting:failsafe_and_factory_reset]]
  
  
 ===== Hardware ===== ===== Hardware =====
 ==== Info ==== ==== Info ====
-| **[[wp>Instruction set]]:**    | [[wp>MIPS architecture|MIPS]] | +[[wp>Instruction set]]  | [[wp>MIPS architecture|MIPS]] | 
-| **Vendor:**          | [[wp>Broadcom]] | +Vendor          | [[wp>Broadcom]] | 
-| **[[docs:techref:bootloader]]:**     | unknown (custom Thomson Speedtouch bootloader)\\ Can be replaced by [[docs:techref:bootloader:cfe]] | +[[docs:techref:bootloader]]     | unknown (custom Thomson Speedtouch bootloader)\\ Can be replaced by [[docs:techref:bootloader:cfe]] | 
-| **[[docs:hardware:soc|System-On-Chip]]:**  | [[http://www.broadcom.com/products/Broadband-Carrier-Access/xDSL-CPE-Solutions/BCM6358|Broadcom 6358KFBG]] | +[[docs:techref:hardware:soc|System-On-Chip]]  | [[http://www.broadcom.com/products/Broadband-Carrier-Access/xDSL-CPE-Solutions/BCM6358|Broadcom 6358KFBG]] | 
-| **[[docs:hardware:cpu|CPU]]/Speed**        | BMIPS4350 V1.0 / 300 Mhz | +[[docs:techref:hardware:cpu|CPU]]/Speed       | BMIPS4350 V1.0 / 300 Mhz | 
-| **Flash-Chip:**      | [[http://www.spansion.com/Support/Datasheets/S29GL-N_00.pdf|Spansion S29GL128N90TFIR2]] or\\ [[https://www.micron.com/~/media/documents/products/data-sheet/nor-flash/parallel/m29w/m29w128g.pdf|ST/Numonyx/Micron M29W128GL]]; \\ both are parallel NOR flash, 128KB block size x 128 blocks, TSOP56 | +Flash-Chip  | [[http://www.spansion.com/Support/Datasheets/S29GL-N_00.pdf|Spansion S29GL128N90TFIR2]] or\\ [[https://www.micron.com/~/media/documents/products/data-sheet/nor-flash/parallel/m29w/m29w128g.pdf|ST/Numonyx/Micron M29W128GL]]; \\ both are parallel NOR flash, 128KB block size x 128 blocks, TSOP56 | 
-| **Flash size:**      | 16 MiB | +Flash size  | 16 MiB  
-| **RAM:**             | [[http://www.hynix.com/datasheet/pdf/dram/HY5DU124(8,16)22D(L)TP(Rev0.1).pdf|Hynix HY5DU121622DTP]] or \\ [[http://www.samsung.com/global/business/semiconductor/file/2011/product/2007/6/11/DDR_DDR2/DDRSDRAM/Component/512Mbit/K4H511638D/ds_k4h51xx38d_tsop2_rev12.pdf|Samsung K4H511638D]] | +RAM         | [[http://www.hynix.com/datasheet/pdf/dram/HY5DU124(8,16)22D(L)TP(Rev0.1).pdf|Hynix HY5DU121622DTP]] or \\ [[http://www.samsung.com/global/business/semiconductor/file/2011/product/2007/6/11/DDR_DDR2/DDRSDRAM/Component/512Mbit/K4H511638D/ds_k4h51xx38d_tsop2_rev12.pdf|Samsung K4H511638D]] | 
-| **RAM size:**      | 64 MiB | +RAM size    | 64 MiB  
-| **Wireless:**        | [[http://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM94322MP2D|BCM94332MP2D]] 802.11a/b/g/n Mini PCI card or \\ soldered module| +Wireless    | [[http://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM94322MP2D|BCM94332MP2D]] 802.11a/b/g/n Mini PCI card or \\ soldered module| 
-| **Ethernet:**        | Broadcom  {{:media:datasheets:bcm5325_pinout.png?linkonly|BCM5325}} supporting 16 VLANs via [[doc:uci:network#swconfig]] | +Ethernet    | Broadcom  {{:media:datasheets:bcm5325_pinout.png?linkonly|BCM5325}} supporting 16 VLANs via [[docs:techref:swconfig]] | 
-| **Internet:**        | ADSL2+ +Internet    | ADSL2+ 
-| **Slic:**        | [[http://www.silabs.com/Support%20Documents/TechnicalDocs/si3216.pdf|Silicon Labs Si3216-FM]] Programmble Wideband SLIC/CODEC with ringing/battery voltage generation +Slic        | [[http://www.silabs.com/Support%20Documents/TechnicalDocs/si3216.pdf|Silicon Labs Si3216-FM]] Programmble Wideband SLIC/CODEC with ringing/battery voltage generation 
-| **DECT**        | Inventel DECT module appearing as Bluetooth HCI on SPI bus  | +DECT        | Inventel DECT module appearing as Bluetooth HCI on SPI bus  | 
-| **USB:**             | Yes | +USB         | Yes | 
-| **[[docs:hardware:port.serial|Serial]]:**          | [[#Serial|Yes]] | +[[docs:techref:hardware:port.serial|Serial]]  | [[#Serial|Yes]] | 
-| **[[docs:hardware:port.jtag|JTAG]]:**            | [[#JTAG|Yes]]  |+[[docs:techref:hardware:port.jtag|JTAG]]      | [[#JTAG|Yes]]   |
  
 ==== Photos ==== ==== Photos ====
Line 176: Line 209:
  
 If the sockets/ports are on the front of the board at the bottom, the unpopulated 2mm pitch serial port header is located near the top of the board to the right (varying slightly between rev1 and rev2).  In addition to populating it you need to bridge two absent resistor locations on the front of the board (R105, R106).  From the top going downwards, the connections are: If the sockets/ports are on the front of the board at the bottom, the unpopulated 2mm pitch serial port header is located near the top of the board to the right (varying slightly between rev1 and rev2).  In addition to populating it you need to bridge two absent resistor locations on the front of the board (R105, R106).  From the top going downwards, the connections are:
- +<a2s> 
-^ 3.3v ^ +   #-----------------# 
-GND +   | VCC GND TX  RX  | 
-TX +J10| .-. .-. .-. .-. | 
-RX ^+   | '-' '-' '-' '-'
 +   #-'---------------# 
 +      
 +</a2s>
  
 Rev2 close-up: \\ Rev2 close-up: \\
Line 190: Line 226:
 |{{media:bt:homehub2a_jtag.jpg?400x250|}} | {{media:bt:homehub2a_rev2_jtag.jpg?400x250|}} | |{{media:bt:homehub2a_jtag.jpg?400x250|}} | {{media:bt:homehub2a_rev2_jtag.jpg?400x250|}} |
  
-The docs for this [[docs:hardware:port.jtag#pin_header_-_1_row|JST-SH-8 type of header]] suggest sources for cables/sockets.+The docs for this [[docs:techref:hardware:port.jtag#pin_header_-_1_row|JST-SH-8 type of header]] suggest sources for cables/sockets.
  
-More general information about the JTAG port, JTAG cable, etc can be found on the [[docs:hardware:port.jtag|JTAG hardware page]].+More general information about the JTAG port, JTAG cable, etc can be found on the [[docs:techref:hardware:port.jtag|JTAG hardware page]].
  
 === Flashing the new bootloader === === Flashing the new bootloader ===
Line 201: Line 237:
 UrJTAG or OpenOCD may also work; reports welcomed. UrJTAG or OpenOCD may also work; reports welcomed.
  
-A session of flashing CFE with zjtag using a [[docs:hardware:port.jtag.cable.buffered|WIGGLER]] cable:+A session of flashing CFE with zjtag using a [[docs:techref:hardware:port.jtag.cable.buffered|WIGGLER]] cable:
 <code># ./zjtag -flash:custom /window:1e000000 /start:1e000000 /length:20000 /wiggler /BE <code># ./zjtag -flash:custom /window:1e000000 /start:1e000000 /length:20000 /wiggler /BE
  
Line 320: Line 356:
  
 ===== Hardware mods ===== ===== Hardware mods =====
-As a beginner, you really should inform yourself about [[docs:hardware:soldering]] in general and then obtain some practical experience!+As a beginner, you really should inform yourself about [[docs:techref:hardware:soldering]] in general and then obtain some practical experience!
  
 ==== USB mod ==== ==== USB mod ====
Line 1050: Line 1086:
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
-{{tag>bcm63xx bcm6358 16flash 64ram}}+{{tag>bcm63xx bcm6358 16flash 64ram 4port fastethernet}}
  • Last modified: 2024/03/10 19:19
  • by danitool