Archer D7 support

Hello everyone!
Sorry for the delay but I am very busy lately :pensive:
I had time to get the Archer D50 working from flash (https://github.com/openwrt/openwrt/pull/2031). This is a cheaper version of the D7. So if this PR will be accepted I'll create an ath79 version of the D7 commit that will replace the ar71xx commit.

@powo01 Thanks for working on this router :slight_smile: You should be able to fix the flashing problem in a cleaner way. That is creating a new entry in the mktplinkfw2.c file (Look here) and using TPLINK_FLASHLAYOUT := 16Mqca

1 Like

Hello,

One Remark:
please have a look to the TP-Link header of the original firmware files. For the Archer D7 the Version is "Ver 2.0" not "Ver 1.0".

Hello,
I finally created an ath79 version of my previous ar71xx commit.
You can find it here
If someone (with a backup of the flash) can check that the instruction for flashing and restoring the firmware are correct, I will create a pull request.
Here there is a compiled fw with LUCI: https://mega.nz/#F!jIpxxSRY!nHqu4x2_G-xcC_zyj8MjSw

P.s. that "Ver 2.0" shouldn't matter but I fixed it anyway

Hi,

it looks like that there are different versions of the Archer D7 in field
My Archer-D7 is sold as AT/CH Version and has a different partition table like your
e.g. there is no "DECT" partition in my D7

My partition table looks liks

[    0.916028] Creating 8 MTD partitions on "spi0.0":
[    0.920892] 0x000000000000-0x000000020000 : "u-boot"
[    0.927481] 0x000000020000-0x000000176400 : "kernel"
[    0.934145] 0x000000176400-0x000000fc0000 : "rootfs"
[    0.940402] mtd: device 2 (rootfs) set to be root filesystem
[    0.946246] 1 squashfs-split partitions found on MTD device rootfs
[    0.952531] 0x000000360000-0x000000fc0000 : "rootfs_data"
[    0.959698] 0x000000fc0000-0x000000fd0000 : "config"
[    0.966381] 0x000000fd0000-0x000000fe0000 : "romfs"
[    0.972983] 0x000000fe0000-0x000000ff0000 : "rom"
[    0.979345] 0x000000ff0000-0x000001000000 : "art"
[    0.985760] 0x000000020000-0x000000fc0000 : "firmware"

in Openwrt specific is rootfs_data and firmware, original firmware is without that both

Do you have a an Archer D7b? That could be the problem as shown here
In this case I could create a D7b version of the commit....

Yes device looking like the Archer D7b Type

original firmware bootline begins with

bootargs=console=ttyS0,115200 root=31:02 rootfstype=squashfs init=/sbin/init mtdparts=ath-nor0:128k(u-boot),1152k(kernel),14848k(rootfs),64k(config) ....

Original Partition Table

7 cmdlinepart partitions found on MTD device ath-nor0
Creating 7 MTD partitions on "ath-nor0":
0x000000000000-0x000000020000 : "u-boot"
0x000000020000-0x000000140000 : "kernel"
0x000000140000-0x000000fc0000 : "rootfs"
0x000000fc0000-0x000000fd0000 : "config"
0x000000fd0000-0x000000fe0000 : "romfs"
0x000000fe0000-0x000000ff0000 : "reserve"
0x000000ff0000-0x000001000000 : "radio"

Ok I created a new commit with both versions here
And here you can find the new compiled firmware for both versions... let me know if it works! :slight_smile:

2 Likes

I have tested the prebuild image at my device, the prebuild image for the D7b is working

I have some suggestions:

As long the internal DSL modem is not usable, the is no need for the "ppp" related packages in the image and also the WAN connection should be linked to the Lan4/WAN port in DHCP/DHCPv6 Mode. I have done in my build for the 18.02.
I have no DSL, but a fibre media converter for internet access. This device would be connected via the WAN/LAN4 port.

Thanks for your work :slight_smile:

1 Like

While (probably) true for your specific use case, anyone who wants to use their Archer D7 (with an external/ dedicated) modem on an ADSL/ VDSL line will still need PPPoE.

The term "fibre media converter" however rings several alarm bells, as this usually implies WAN throughputs up to and exceeding 1 GBit/s line speed, something no ath79/ ar71xx device, such as your archer d7, can deliver - it caps out around roughly 150 MBit/s, 200 MBit/s if you push it (ignoring lags).

@slh I only use the D7b as a wlan access point, my booked internet line speed is 200/100 MBit/s at the moment, without the hardware nat support near the limit of the device. Inhouse I was able to measure speeds up 200 MBit/s via 5 GHz WLAN via the D7b ( Notebook <- D7b -> 1 GBit/s Link -> Backbone ) with ipref3.
ItΒ΄s right the special needs of external DSL was out of my view, the Linespeed of DSL now also reach up to 250 MBit/s

1 Like

The ppp packages are from the default openwrt configuration, I didn't add it. In my build I added only LUCI and nano.
For what concern the "Lan 4" as a WAN port in DHCP client mode, it should be already present in my build (and in the commit).
Actually, in the commit and in my build I put in the same vlan the internal port connected to the DSL modem and the "Lan 4". I did a quick test few days ago and seemed to be working without problems...

1 Like

Hi @numero53 could you please tell me how I can install OpenWrt on Archer D50? I ordered one on Ebay for around 11€. They are a secret hint to be honest if OpenWrt will work on it. I just used it with OEM als a WDS-Repeater and were able to transfer about 14 MByte/s to a local NAS, but still having trouble to access the internet proper even when my clients were configured with correct ip, gateway and DNS. So I just wanted to use the D50 as an AP. In my FritzBox 7490 it was connected with 866 Mbit/s. So that's why I switched from wired to wireless. Through WAN or LAN Ports I unfortunately just reach 3 - 4 MByte/s from my internal NAS via FTP or SAMBA, I don't know why exaktly this is a problem but has something to do with the Fact that my NAS has 1 GBE Interface and if you switch somewhere in between to 100 Mbit/s FastEthernet it drops down to that Datarate of maximum 3 to 4 MByte/s. That also happens with other OpenWRT devices. Just one other device (Tenda F1201) did even with Fast-Ethernet-Switch reach the 100MBit/s on my Laptop. - The performance issue happens with Windows and Ubuntu via Ethernet-Connection and also with wireless. - Also Performance of wireless under Ubuntu or Linux in gernal sucks for AC-Wifi somehow.

But back to my orginal question: Could you please provide how to switch from OEM to OpenWRT Firmware? - I noticed that there is already a support page in OpenWRT-Wiki but no special instruction. - I guess we could manage it via TFTP flash through the known IPs 192.168.0.66 and 192.168.0.88 but not sure. So I wanted to know and also I am sure we have to strip somehow the bootloader off before flashing an image.

So it would be great to bring this device with proper Atheros-Chipsets to fly!

Hi @suppenkasper0815,
The Archer D50 is a very cheap device nowdays... good choice!
In the commit message I wrote all the instruction needed for a clean OpenWrt install using a USB-UART adapter.
You should open the device and follow the "Flash instruction under U-Boot, using UART" section.
However this is not the right thread... If you have other question about the Archer D50 you should create a new thread :wink:

1 Like

Thank you very much!

Is it maybe possible to split or cut my and relevant posts for Archer D50 into a new thread by an admin?

Is there no way without opening the device? I guess it's as hard as the opening mentioned of Archer D7. I also guess the pining is at the same place and you also need to connect the RX Pin by cable like on D7. Am I right? :wink:

Have you already performance experiences with both devices?

Your instructions are pretty clear so far I can say atm.

By the way, I also saw Archer D7 under 20€ at the same shop I'm eBay. - So if the performance is equal to Archer C7 this should be the choice for future devices...

Thank you very much already for your great job you've done so far!

Hey @numero53 ,

I have no 3 devices. One D50, One D7 and one D7b, so I can test every image and scenario. - The major problem at the Moment is now already the case-opening...

Could you please give some hints or pictures? I found the 2 screws under the information plate, but haven't found how to reject the clip on the upper side and the side clips.

Would love to get some hints before the case is broken...

Thanks guys

Hi guys,

I managed to use the initram build of @numero53

A great work! Just noticed it's not possible to use wwan 5GHz and AP mode at the same time. That's a pity and worked with the good old 4/32 tplink 841 and Co devices...

Maybe there will be a possibility, because in OEM it was also possible to use WDS to login my wifi and use the 5GHz at the same time as AP.

But anyway, I'm not sure what is the correct position to write it into flash because there a several addresses. I read an adress 0x80800000 and the one from I booted 0x81000000.

This is my D7, but I also get soon a D7b and would love to get some hints. - I can also try out things because they are just gadgets for me if you wanna have something tested...

Actually the throughput was better than with WDS Mode in OEM. In OEM max was 130 Mbit/s and with the openwrt it's usually around 200 Mbit/s.

1 Like

Hi guys
I was following your efforts for about a week or so and decided to give your work a try on my device.
I got an archer D7 v1.1
The firmware on it was unfortunately quite recent.
I have the strange issue that pressing "any key" which apparently equates to the letter "t" does not work on UART to interrupt the normal boot sequence.
I've tried all kinds of keys and also another USB-UART adapter, and also quadrouple-checked that I'm on the correct pins and voltages.

Is there something special to it that I'm missing out?
Default settings for screen with 115200 bauds should work right?

Yeah opening that thing isn’t the easiest thing but I postet some hints a while ago at https://openwrt.org/toh/tp-link/archer-d7

Hi everybody. Thank you for your nice work. I have Archer D7 and managed to open the box. I don't have any usb uart adapter I was wondering if it's possible to use raspberry pi gpio to connect to router. Also what is the correct voltage. I know rpi gpio is 3.3 volt. Do I need a level shifter to connect to Arher D7?

Hi, I have a question. In the port.serial section of website it is written that vcc should not be connected but in your image if I understand correctly rx, gnd and vcc are connected and tx is not connected. Is this the correct way to connect?