Broadcom63xx SoC integrates ADSL/ADSL2+ features, routing, and external Wireless NIC.
This SoC is widely used by most xDSL platforms in the world. It is one of the most successful xDSL platforms due to the simplicity of migrating old platforms (e.g: BCM6345) to new ones without much software impact. The cost of the complete solution (SoC, DSL line-driver, Wi-Fi
- The OpenWrt support for the Broadcom BCM63xx SoC family currently only works with following models:
- There are working drivers for USB (OHCI and EHCI) and Ethernet under the GPL
- → adsl_support effort to make it work again on Linux kernel 184.108.40.206 from 2004-08-14
- xDSL and ATM are not supported. Not by some binary nor are there GPL drivers available!
- Belkin has released "GPL code for the F5D7633", but it only has binary Broadcom drivers.
- TP-link also has some code out for the platform –> see TP-link GPL code for many of their products
- D-Link GPL download center: D-Link GPL code for all of their products (DSL-2640B, DSL-2740B).
- Netgear has released some sources for DSL-driver: DG834GBv4 GPL and closed code
- Inteno has released some sources for ARxx and DG200-FG200 Series which uses Broadcom BCM6368 chip: bcm963xx_4.02L.01 & bcm963xx_3.12L.01
Some SoCs like BCM6358 or BCM6368 have two cores, however OpenWrt only uses 1 core. Spite there being SMP code for using two cores in the kernel (see smp-bmips.c), it seems hard to use both cores: it is needed to initialize the second cpu; also the irq code code currently only enables irqs on the first cpu, so only userspace can use the second core, all interrupt handlers will use the first one.
There are eight main 63xx variants:
|SoC||CPU MHz||Dual Core||USB Device||USB Host||PCMCIA/PCCARD||PCI||PCIe||Wireless NIC||ADSL2||ADSL2+||VDSL||VDSL2||Fiber||OpenWrt|
- The third digit, when set to 3 (like in BCM6335, BCM6338) denotes a single-chip and cost-reduction oriented design.
- There are also some other variants like bcm6341, which is a DSP used in VoIP products in conjunction with a BCM6348 SoC.
The support for Broadcom 63xx is at this state :
- Full Linux support for BCM6338, BCM6345, BCM6348 and BCM6358 with runtime detection of the SoC on which the kernel is running
- GPL drivers for Ethernet, OHCI, EHCI, SPI, Watchdog
- No available drivers (neither binary, nor GPL) for DSL, ATM, VoIP, on-board SLIC/SLAC
Bootloader: Some devices use RedBoot such as Inventel Liveboxes. Most of the others use CFE with a built-in LZMA decompressor. CFE is not using standard LZMA compression arguments, and most noticeably, changes the dictionary size, so beware. Thomson routers have their own bootloader.
There is source code released for redboot (Inventel Livebox), and probably can be modified to work with other routers. Also there is some source code for Uboot (aka TBSBOOT).
|Here the uboot/TBSBOOT source code with the toolchain included for vx160 SoCs but with some code for bcm6338, bcm6348 and bcm6358:
And the Redboot source code for Inventel Liveboxes (bcm6348)
On several CPE (Customer-premises equipment) hardware devices and especially on smart phones, the OEM bootloaders are feature poor (no netboot, no booting from a USB stick, etc.), obfuscated (require some magic values to be correct) or completely messed up and make it cumbersome, difficult or impossible to install free software on the device. It is thus paramount to always have at least some products available, that have OEM bootloaders that keep installing free software easy (cf. generic.flashing). And it could be interesting to port such bootloaders to devices, which happen to come with a restricted bootloader. Compare the available bootloader out there, their license, available code and feature sets. Please also remember that available source code it NOT enough, it has to be under some license, that allow for modification and redistribution.
There exists an utility to backup the entire flash:
You must connect your PC with the bcm63xx router via serial TTL port while CFE is running. Then execute cfetool with a command like this, maybe different with different boot address / flash sizes.
./cfetool.py --read=dump.bin --addr=0xB8000000 --size=0x1000000 --block=0x10000 --addr=0xB8000000 -> Flash Memory Address (see CFE bootlog --> Boot Address) --size=0x1000000 -> 16Mb Flash --block=0x10000 -> Memory dumped each iteration (default is 10Kb 0x2800)cfetool expects the serial port used is /dev/ttyUSB0 in your PC, but you can change it with "–serial=/dev/ttyUSB1".
Note: not all CFEs have internally the dm/sm command, as a result of this cfetool may not work with some devices. Alternatively you can dump the flash via traditional methods like JTAG or with an OpenWrt ramdisk firmware version.
|BT Voyager 2100|
|ZTE ZXDSL 831A|
|US Robotics USR9105|
|US Robotics USR9106|
|Belkin F5D7632 v2|
|Huawei EchoLife HG510|
|Dynalink RTA1320 (Nateks Unispot21)|
|Siemens CL 110|
|Thomson SpeedTouch ST516 v6|
|Thomson SpeedTouch ST530 v6 (same as above with USB port)|
|D-Link DSL-2740B hw C2, C3|
|Neuf Box 4|
|ALICE GATE VoIP 2 Plus Wi-Fi Business|
|US Robotics USR9113|
|BT Homehub 2 Type A|
|Motorola NVG510 Commonly used with AT&T copper Uverse, which supports VOIP but not TV. (Motorola GPL source). Also on WikiDevi|
|Netgear DGND3700 (v2)|
|Zyxel P-870HN-51b (commonly shipped to VDSL2 customers by Sonera in Finland)|
|NETGEAR VVG2000 (sold to VDSL2 customers by Bezeq in Israel)|
|D-Link DSL-6740U (sold to VDSL2 customers by Bezeq in Israel)|
|Netgear DGND3700 (v1)|
|Inteno DG301 (commonly shipped to Sonera customers in Finland)|
doc/hardware/soc/soc.broadcom.bcm63xx.txt · Last modified: 2013/09/01 18:37 by pteridium