I have recently (well, recently got around to looking at, lol) acquired a BT HomeHub v5 Type B. The hardware page for this particular router states that its less flexible than its Type A twin, being a Broadcom based chip rather than Lantiq.
My question is has anyone successfully gotten OpenWrt on this particular device, and is it worth continuing research? I've been successfully using OpenWrt on a BT HomeHub 3 Type A for a couple of years now, having successfully flashed using the solderless method, with the USB Stick & TFTP ethernet combination.
I need to extend WiFi coverage at home, and want to add a second OpenWrt device for this purpose. The Home hub was my last hope, since the Plusnet TG582n that I have requires building a serial interface and soldering direct to the mobo - a process I'd rather not have to go through! (Not that I'm not capable, its just, I don't want to spend so much time).
Broadcom’s chips primarily require closed source code, so this makes development of OpenWrt very difficult. Typically speaking, if a device uses Broadcom, there won’t be support available in OpenWrt or most other open source platforms.
a) the BT HomeHub v5 Type B currently isn't supported by OpenWrt at all
b) there are no drivers for the VDSL modem
c) support for the wireless would be so basic and slow, that you can consider it non-existent
So even if you would spend weeks of development on getting a) to work, b) and c) will never do.
Thanks for your replies folks, you've confirmed what I suspected would be the answer . Saves me reading pages of stuff about the various Home hubs to come to the same conclusion.
Am I right in thinking that there have been one or two exceptions to the "no Openwrt with Broadcom" rule? I thought one variant of the TG582n was a broadcom with a working openwrt? Albeit without a working ADSL and limited to 2.4g 802(iirc no /n)
There are no -zero- exceptions when it comes to Broadcom xDSL/ cable/ fibre modem or -phone/ DECT drivers.
There are few exceptions when it comes to Broadcom fullmac (in contrast to the more prevalent softmac chipsets in routers and notebooks) wireless drivers (e.g. the bcm4366 in the Netgear r8000 or the -slow and bad- onboard wifi of the RPi series). Still, support for them is not great, their features are rather limited and Broadcom and its successors don't care about them anymore, don't bet on it to work.
There are no exceptions when it comes to their proprietary hardware acceleration (ctf.ko).
What you get, is basic SOC suppport and wired (unaccelerated) network support, for the few devices developers have spent their time on, despite all of the above.
Do not buy Broadcom devices, if you want to run OpenWrt!
The only exception to that rule, is the RPi4 (and maybe the RPi5 in a few months' time, but there are cheaper and better alternatives to that) - and even there the wireless is bad, which means you'd need an external wireless AP to cover that.
If you want to buy a device, check the ToH, read its device page in full, to get an idea which components are supported, to what extent, and which are not, how easy -or difficult- it is to flash OpenWrt and how fast it might be. If in doubt, ask - but Broadcom isn't on anyone's wish list.
Without sourcing different hardware, it looks like my only viable option is getting out the soldering iron and serial flashing that TG582. Don't need xDSL and 802.11g is fine for one room.
I thought that was clear…
The RPis older than v4 are junk for running OpenWrt (ethernet speeds limited by the single USB2 hub).
The RPi4 can be a very fast and capable wired-only router, just its wireless side is indeed junk - but considering market availability and pricing, there are cheaper and better options these days (that doesn't make it junk, at all, just expensive).
Sorry for the misunderstanding, I was making a poor attempt to be funny (I'm autistic but I do try to get sarcasm—I'm clearly not as good as deliverling it as I thought😂)
You were totally clear in what you said originally, I did get it. The broadcom chip makes for badly supported (non existent) wifi due to the proprietary driver. You were just saying the wireless of a Pi4 is naff, the rest is good just expensive (as a router)... I forget the film Im trying to reference (i think its dumb and dumber where she says "if you were the last man on earth" and he pauses then says "so, youre saying theres a chance"... (ill add more of these faces next time. Otherwise i get the feeling my communications will be even more painful—i mean because of me, not you )
A pedantic aspie, and now shit at humour too... can this day get better? (Chandler Bing reference. RIP)
On that note, Ive sourced a TP-Link Archer and can get my hands on a HH5/6 plusnet branded version of the above—and plusnet used the A so its not broadcom! Still need soldering the four wires for serial flashing though, so the TPlink will be the easier; using the stock firmware flash UI.
I would first suggest to try it without soldering, just trying to keep the serial cables (probably extended by small strips of tin foil, you may hold in place with scotch tape or blu-tack) firmly in place (the whole procedure, including the backup, takes just shy of an hour).
The vias you'd be soldering to are very fragile, once you break them (too much heat for too long - or not enough heat for way too long), the device is gone for good - so less the you need tinker with it/, the better. There've been quite a few reported casualties from users who cooked their vias to deaths, leaving the router in an unusable state.
(I used tin foil strips to rx/ tx (and a more conventional method to connect GND at a safe/ more sturdy location), partially isolated with tape and taped down at the free spaces on the PCB (safely away from SMD components) - then pressed down to the via solder points with a rubber gloved finger on mine, keep it firm and steady).
. Saves me reading pages of stuff about the various Home hubs to come to the same conclusion.
ive three RPi3 with which to fall back on.
)
(Chandler Bing reference. RIP)