Installing openWrt on a TP-Link Archer D7 (EU) v1.1

Installing and Using OpenWrt
1

Hello everyone.

I have a TP-Link Archer D7 (EU) v1.1. I've found on the table of hardware the page of the Tp-link Archer D7 v1.

Does anyone knows if the firmware is compatible with the TP-Link Archer D7 (EU) v1.1 ?

If not, where can I find a link ?

Thanks and best regards.

2

Since you need to solder a tll adapter anyway you can check it out. Usually (not always) 1.x equals 1.0. Same about regions.

3

It should work, but be aware that the included xDSL modem does not -and will never- be supported.

1 Like
4

Thanks for the replies.

I read that the (EU) version is a bit different for this particular model especially for the Wifi limitation in EU rather than the US or CN version. I just wanted to be sure before trying to update the firmware to the openwrt one.

I will try and will tell you if it worked or not.

I was aware that xDSL modem won't work.

I just need the WAN to work with the fiber and make the VLAN work.

5

While at uboot you can tftpboot initramfs kernel and test non-destructively

1 Like
6

Maximum routing performance, ~175 MBit/s - with the back to the wall.

7

Thank you all for the help.

I bought a usb to serial adapter and was able to set the router into the uboot mode (I think... the command prompt is AP135> )

After some tries and errors I managed to make the tftp server working fine.

The issue is the following : transfering the [...]initramfs-kernel.bin firmware to the router is working fine, but when I try to launch it via the command :

bootm 0x81000000
## Booting image at 81000000 ...
        Uncompressing Kernel Image ... ERROR: LzmaDecode.c, 543

Decoding error = 1
LZMA ERROR 1 - must RESET board to recover

...and the router reboot to the stock firmware.

I've read that the error is related to an incompatible firmware version. I already tried the 24.10 version, the 23 and the 22, with no changes.

Do you have any idea to help me ?

Best regards.

8

I had the same issue. Even changed to the .AU firmware from .EU firmware.

EU firmware has a different flash layout:

~ # cat /proc/mtd

dev: size erasesize name

mtd0: 00020000 00010000 "u-boot"

mtd1: 00120000 00010000 "kernel"

mtd2: 00e80000 00010000 "rootfs"

mtd3: 00010000 00010000 "config"

mtd4: 00010000 00010000 "romfs"

mtd5: 00010000 00010000 "reserve"

mtd6: 00010000 00010000 "radio"

Note that the .AU firmware has the same as the standard V1:

dev: size erasesize name

mtd0: 00020000 00010000 "u-boot"

mtd1: 00140000 00010000 "kernel"

mtd2: 00e50000 00010000 "rootfs"

mtd3: 00010000 00010000 "radioDECT"

mtd4: 00010000 00010000 "config"

mtd5: 00010000 00010000 "romfs"

mtd6: 00010000 00010000 "rom"

mtd7: 00010000 00010000 "radio"

From the serial console I just flashed openwrt-23.05.0-ath79-generic-tplink_archer-d7-v1-squashfs-sysupgrade.bin via the method on the device page and it booted Openwrt fine.

tftpboot 0x81000000 openwrt-ath79-generic-tplink_archer-d7-v1-squashfs-sysupgrade.bin
erase 0x9f020000 +f90000
cp.b 0x81000000 0x9f020000 0xf90000
reset
9

you're not doing the same thing as @Flatty, they were trying to boot an initramfs.

10

Yes, I know that. I had the same issue - unable to boot initramfs.

11

if you still got serial hooked up and want to play with the initramfs, you can try to bump the mem address.

12

How so?

I tried 2 diff mem addresses. My u-boot console is a bit garbled, so was hard to see the exact error.

I have a feeling the OP wanted to install openwrt anyway, and the ramfs was the step they were taking. This was my goal, but if the initramfs can work that will be good for others