Updating the DSL hardware driver blob

The following info was posted earlier to the popular ThinkBroadband forums:

Hacker Csaba Sipos from Hungary has discovered a slightly newer DSL driver blob for the BCM6368. The BCM6368 is the Broadcom System-on-Chip that powers the HG612 and a good many other VDSL2 CPE.

It seems that the DSL driver version currently shipped in the HG612 firmware is A2pv6C030b.d22g:

# xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C030b.d22g
******* Pass *********

However, Actiontec, a N.American CPE supplier, has included a slightly newer driver version in a GPL’ed source code tarball for its 6368-based devices [1]. That driver version is A2pv6C035f.d22g

# xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C035f.d22g
******* Pass *********

It looks like a very minor driver revision, but it might just squeeze a couple more bits per hour!

Anyone interested in giving it a whirl?! Csaba has already built some new firmware with the newer driver, if anyone wants to contact him to try it out?

EDIT1:

Over on the Netgear forums, [2] ARobertson676, Gigio755 and Scubbie have spotted even newer DSL drivers in the beta firmware for the Netgear DGND3700. The latest version with build date 03/06/2012  being A2pv6C035m.d23k

The Netgear firmware seems to have a header on its header, but thankfully the firmware-mod-kit can still extract its components, including the driver blob.  The amazing kit was developed by Craig Heffner, Jeremy Collake, Matthias Bucher and others.  [3]

$ wget http://www3.zshare.ma/files/3/82vk2ocjmhtgmi/DGND3700-V1.0.0.20_1.0.20_Static_PPA.chk

$ svn co http://firmware-mod-kit.googlecode.com/svn/ firmware-mod-kit-read-only

$ cd firmware-mod-kit-read-only/trunk

$ ./extract-ng.sh ~/DGND3700-V1.0.0.20_1.0.20_Static_PPA.chk
Firmware Mod Kit (build-ng) 0.78 beta, (c)2011-2012 Craig Heffner, Jeremy Collake  -- http://www.bitsum.com

Scanning firmware...

DECIMAL   	HEX       	DESCRIPTION
-------------------------------------------------------------
143       	0xFFFFFFFE	(null)

Extracting 321 bytes of  header image at offset 0
Extracting squashfs file system at offset 321
Extracting 160 byte footer from offset 8230091
Extracting squashfs files...
Firmware extraction successful!
Firmware parts can be found in 'fmk/*'

$ ls -l fmk/rootfs/etc/adsl/
total 828
-rw-rw-r-- 1 root root 846560 May 12 01:31 adsl_phy.bin

$ strings -n10 fmk/rootfs/etc/adsl/adsl_phy.bin  | grep -A1 A2pv6

Broadcom DSL Version A2pv6C035m
Built on 03/06/2012 17:48:07

EDIT2:  See second part of this blog series [4]

[1] http://peterkieser.com/2011/09/24/actiontec-releases-removed-from-open-source-download-area/

[2] http://forum1.netgear.com/showthread.php?t=76204

[3] http://code.google.com/p/firmware-mod-kit/

[4] http://huaweihg612hacking.wordpress.com/2012/11/11/dynamically-swapping-out-the-hardware-driver-blob/

About these ads

3 thoughts on “Updating the DSL hardware driver blob

  1. Did anybody try this new driver? I was able to extract adsl_phy.bin but no idea how to apply it on HG612 … can you then provide some hints for that? I see that under /etc/adsl/ there we have corresponding firmware but any attempt to replace it ended with failure …

  2. asbokid,
    What an amazing site.
    In spite of all that you’ve provided, I, like the previous poster am having problems changing the DSL blob and building new firmware. I’ve tried extracting and building with no changes, but it always ends with CRC error, 0 headers processed, Headers not supported and CRC may be incorrect… etc. Any notes you can offer would be greatly appreciated. I’ve run as root, incase it was permissions related, but no difference. I have not uploaded this firmware to my HG612 as I have no idea if it’s going to brick it. Comparing th eoriginal firmware with the one I build ( no changes) shows 0.4 meg of FF’s ( padding I imagine) in the rebuit on, as opposed to the original ?
    How can we change the blob in the HG612 tool you provided, as opposed to using the firmware-mod-kit that is giving me so much grief. ?

    Cheers

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s