The TD-W9980 is a VDSL-capable router launched in 2014. It's identical to the TD-W8980, so check that page out as some information is there and some here. The device works very well with OpenWrt, including the integrated DSL modem. Just the 5 GHz Wifi cannot be used and for VDSL you'll need to use a propriertary binary blob as described in this article.
This page is also for TD-W9980B which is nearly identical, with the exception that you can't flash via the Web UI exploit.
Failsafe-Mode is not accessible via ethernet when triggered with the WPS button and indicated by led. (fixed for TDW8970)
Device is not supported/built sysupgrade for yet, possible profile (plus fix for failsafe) can be found here
Install OpenWrt via Serial Interface
This installation method works for all firmware versions of all devices that are mentioned on this page. However, it is necessary to open the case and to solder a pin header to prepare the installation.
How to open the case
Note: This may void your warranty
This case is pretty easy to open. First remove the four screws, and then pry the case with a small flat screwdriver, starting from the top (as that's the only non-tight place where you can actually put something) till the eight marked points of the case pop out.
Then you need to detach the U.FL RF connectors and make sure they're not in the way for pulling the board out. On W9980B one of them is hidden between tho components (one of them is a big red one). Gently push away the red one and pull the cable out.
Because there's copper pads on each side of the board which are glued to the plastic case while also being soldered onto the board, you're going to have to keep them attached for convenience and keep them in mind when manipulating with the board.
The UART is not populated, so you're going to have to solder a header on it. Look into the serial console informations at the start of the page for pinout for JTAG.
How to flash the W9980 with OpenWrt 18.06.1.
Provide Firmware via TFTP Server
Before starting the process, it is a good ideal to start a TFTP server on your PC listening on its Ethernet interface on IP 192.168.1.2/24. The default TFTP server IP for the u-boot that will be downloaded in the next step.
Connect a computer to the router via the JTAG (be careful not to fry the router with 5 Volts and use a logic converter to drop it down to the router's 3 Volt TX and RX pins). DO NOT CONNECT VCC!
Start 'screen', 'minicom' or similar serial console software.
Note: Make sure it accepts user input by interrupting normal booting by pressing 't' on U-Boot loading. If it doesn't, try another software. (screen recommended)
Left R225 pad, bottom of the board:
You need to keep a left side of R225 shorted to JTAG GND from boot to finishing of uploading the U-Boot image. A soldered cable will work, but an alligator clip connected to the GND on the JTAG and a small flathead screw driver or scissors pressed against the pad (shown in the image below) work as well, as long as you can hold them steady for about 30 seconds.
(The image above works for W9980 and W9980B, but is reportedly different for the very similar model w8980)
How the setup you end up with may look like (I opted for the scissors as the R225 pad is really tiny and I didn't have a proper soldering iron for that):
So, short the pin, power on the router and you should see a message similar to this:
ROM VER: 1.1.4
EEPROM Data OK
Upload the U-Boot Image from another terminal via:
# cat u-boot.asc > /dev/ttyUSB0
Watch the loading progress via the console and wait a few minutes until it boots the U-Boot file.
Interrupt booting by pressing “t” key several times.
Disconnect the R225 pin from GND. Though you can keep it there until the flashing is done.
Now we need to upload the new firmware via tftp and erase the OEM firmware via the following commands:
tftp $(loadaddr) openwrt-18.06.1-lantiq-xrx200-tplink_tdw8980-squashfs-sysupgrade.bin
# Note: If you get timeouts (T) executing this command, you probably did not set up the networking/tftpd correctly or your ethernet cable is bad.
sf erase 0x20000 0x7a0000
sf write $(loadaddr) 0x20000 0x$(filesize)
Allow the router to boot normally by rebooting it. You can now SSH into OpenWrt and start configuring the router. If a release version was flashed, the web configuration should be available now, too.
Install OpenWrt via Web Interface Hack (without opening the case)
TD-W9980 only, the B version supposedly uses a different encryption format the StatPOSTer tool can't deal with. Also note that the instructions in this section are written for 15.05 and W8970 image is used, but 18.06 is already out and W8980 may be a better fit.
This hack comes from member ejs on Kitz Forum. In this post, a description and link to required software is given.
The configuration (which is essential) is hidden (you need to become forum member), so I've added it here for ease of use.
A Unix-like OS, capable of the dd command (the bash of Windows 10 Linux subsystem is fine also)
An USB stick
Get the USB stick formatted as msDOS/vFAT
Copy the firmware (openwrt-15.05.1-lantiq-xrx200-TDW8970-sysupgrade.image) to the USB stick.
Create a 1310720 bytes block-size slice of the firmware file using dd (this one needs to be on the USB stick as well).
This command creates the file openwrt-15.05.1-lantiq-xrx200-TDW8970-sysupgrade-1.image:
Verify that the size of mtd1 (kernel partition) on the USB stick is 1310720 bytes.
ls -la /var/usbdisk/sda1/mtd1
Install the OpenWrt firmware
If you haven't aleady, insert the USB stick in the router (any port will do)
Copy the two .image files from the USB stick to the router. Note that the first cat command terminates with “no such space left on device”.
This is expected behaviour. The remainder is in the slice which is written.
The TD-W9980, is advertised to support at most ITU G.993.2. This excludes VDSL vectoring support. The DSL drivers in trunk actually are the drivers from TP-Link, and do not include vectoring support either. However, I've got this router to run with full vectoring support using a 5.7.6 (77f69e99cd0e0d4d58454880a21438543f1571dc) firmware from http://xdarklight.github.io/lantiq-xdsl-firmware-info/ on my line (NL/XS4ALL):
ATU-C Vendor ID: Broadcom 176.199
ATU-C System Vendor ID: Broadcom
Chipset: Lantiq-VRX200 Unknown
Firmware Version: 188.8.131.52.0.7
API Version: 184.108.40.206
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 31928
Errored seconds (ES): Near: 0 / Far: 11
Severely Errored Seconds (SES): Near: 0 / Far: 0
Loss of Signal Seconds (LOSS): Near: 0 / Far: 0
Unavailable Seconds (UAS): Near: 116 / Far: 116
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency / Interleave Delay: Down: Fast (0.15 ms) / Up: Interleave (8.0 ms)
Data Rate: Down: 77.848 Mb/s / Up: 32.253 Mb/s
Line Attenuation (LATN): Down: 9.2dB / Up: 7.7dB
Signal Attenuation (SATN): Down: 9.2dB / Up: 7.6dB
Noise Margin (SNR): Down: 4.1dB / Up: 5.0dB
Aggregate Transmit Power (ACTATP): Down: -5.1dB / Up: 13.7dB
Max. Attainable Data Rate (ATTNDR): Down: 85.842 Mb/s / Up: 35.400 Mb/s
Line Uptime Seconds: 613
Line Uptime: 10m 13s
Download a proprietary firmware blob from http://xdarklight.github.io/lantiq-xdsl-firmware-info/. The firmware version 5.7.6 with the sha1sum 77f69e99cd0e0d4d58454880a21438543f1571dc works well for German DSL lines, for example. If you'll need something different than Annex B for your provider, then just select an appropriate firmware. Make sure to follow the instructions on the download page to extract the firmware blob from the downloaded file. For 77f69e99cd0e0d4d58454880a21438543f1571dc, that means to use a recent 7zip version (15.09 or newer) and run it as follows:
7z e DM200_V220.127.116.11.zip
7z e DM200-V18.104.22.168.img dsl_vr9_firmware_xdsl-05.07.06.0A.00.07_05.07.01.0C.00.02.bin
Copy the resulting dsl_vr9_firmware_xdsl-05.07.06.0A.00.07_05.07.01.0C.00.02.bin file onto the router device (using scp on Linux or WinSCP on windows). The full path of the .bin file has to be put into the firmware field of the DSL configuration in OpenWrt.
One awesome thing to mention (at least with trunk) is that the reset button resets the configuration, which is very nice. I couldn't find any notion of this, but because of the DSL port, the failsafe mode of OpenWRT (nicely triggered with the WPS button on the back) doesn't make the device accessible. Probably because of something like this https://lists.openwrt.org/pipermail/openwrt-devel/2015-February/031071.html. Anyway, when I made some network changes which were totally wrong, holding the reset button saved the day, restoring the device back into standard OpenWRT configuration, allowing me to access it again.
Restore TP-LINK FW though serial connection
Successfully tested on TD-W9980 Ver 1.0, adapted from TD-W8970 page.
Prepare the file
The router's EEPROM size is 8MiB (8 388 608 bytes). Firsts 128KiB (131 072 bytes) are for bootloader, and the lasts 256KiB (262 144 bytes) aren't contained in any firmware download. If you loose it, only a previous firmware backup of this EEPROM part can be used to restore it. Between them, you should reflash the “midle” space (from 0x20000 to 0x7c0000, so it's 0x7a0000 sized, 7 995 392 bytes), it's the rootfs.
Obtain the firmware from TP-Link website. You need to care about model version v1. If the name of your TP-Link original firmware contains “boot”, it means that it's likely to contains bootloader, 512 blank bytes, and the rootfs (you should see that the file is 512 bytes too big to be just bootloader + rootfs). Looking at it with an hexadecimal editor, with 512 bytes pages, you will see that if bootloader is taking the 256 first pages (0 to 255), but then the firmware doesn't start at the following page (256) but in page 257.
Here's the Linux command to cut the firsts 257 * 512 bytes :
dd if=orig.bin of=tplink.bin skip=257 bs=512
Then the “tplink.bin” file should be exactly 7 995 392 bytes. It can be used to reflash the space from 0x20000, for 7a0000 bytes.
I suppose that the space from 0 to 0x20000 can also re-programmed using the first 131 072 bytes of the TP-Link firmware files but I didn't tested it.
Restore the file
Read this completely before to actually do it
Prepare your Image, as explained before if the the file contains boot you need to strip the header off with “dd if=orig.bin of=tplink.bin skip=257 bs=512” like I did for “TD-W9980v1_0.6.0_1.13_up_boot(160125)_2016-01-25_15.45.32.bin”
Host the file on a computer using 192.168.1.2 as IP address, with “tftpd-hta” server for example (on Debian, default home directory of this tftp server is /srv/tftp/), connected to the router
Switch on the device with UART Boot (see previous section about that, using u-boot.asc and then “t” key to interrupt booting)
Enter the following commands :
Set the device's IP if you don't want the default 192.168.1.1: (so you don't have to move your TFTP server onto a different subnet)
setenv ipaddr 192.168.1.1
Set the address of your TFTP server:
setenv serverip 192.168.1.2
Set the board type (not sure if this is necessary, work on W9980 anyway, copied from W8970 procedure):
setenv bootargs 'board=WD8970'
Download the image into RAM (*not* flash):
tftpboot 0x80800000 tplink.bin
Erase the rootfs flash area:
sf erase 0x20000 0x7a0000
Write image to flash:
sf write 0x80800000 0x20000 0x7a0000
The rootfs area is from 0x20000 to 0x7c0000 (0x7a0000 sized), erase command is from 0x20000, during 0x7a0000, and write is also from 0x20000, during 0x7a0000. You can double check the image size in after the tftpboot command.
Be careful when erasing/writing the flash the radio is required for WLAN and should not be overwritten or erased. A backup is nice to have if something went wrong, it stores also the MAC address for your WLAN (ART Partition).