Hi
I was looking for OpenWRT Tp-link model AX80 EU v1, but it turned out, that it is out of stock, and was replaced by AX80 EU v2 (looks like AX80V for Japan market). Couldn't find much information about it.
My question is: what steps do I have to do to build OpenWRT for this device (or, probably, v1 build should work with some tweaks)?
I am not in the firmware hacking business, and I do not have device yet.
v2 has different firmware from v1
firmware is extractable
v2 firmware has a very little difference from v1
hardware base is mostly the same (as far as I understand from system.tdb)
Differences in system.dbt: emmc configuration, some clock/phys/phandle options I do not yet understand
OEM firmware for AX80 EU v2
The GPL tarball content suggests V2 is still using MT7986 (A/B) as its CPU SoC
Emre_Y
April 27, 2026, 7:48am
3
I would've ported that but we don't have v2 devices here. Also I don't have enough incentives to do so. I ain't getting paid for this
@Emre_Y Thanks for your prior efforts on porting AX80 EU v1 to OpenWrt.
It appears certain ImmortalWRT (OpenWrt fork) dev / user has started to tinker & analyze the V2 device:
opened 04:50PM - 09 Apr 26 UTC
Hello!
I have identified that the TP-Link Archer AX80 V2 (JP/EU versions) differ… s significantly from the V1 hardware. While V1 uses the MT7915 via PCIe, the V2 utilizes an internal WBSYS bus for the MT7975 radio.
Using standard OpenWrt/ImmortalWrt V1 images results in a Kernel Panic (Level 1 translation fault) because the mt7915e driver attempts to access a disabled PCIe controller at 11280000.
Hardware Details (V2):
* SoC: MediaTek MT7986 (Filogic 820)
* RAM: 512MB
* Flash: 128MB SPI NAND (GigaDevice)
* Wi-Fi: MT7986 + MT7975 connected via WBSYS (Address 18000000)
Evidence from GPL Source (V2.0) and Boot Logs:
1. Partition Table Change: V2 uses an 8MB tp_data partition and no mali_data partition.
2. PCIe Status: Factory logs show mtk-pcie link down.
3. DTS Discovery:
The factory DTS (mt7986b-spim-nand-rfb.dts) defines the wireless as:
&wbsys {
mediatek,mtd-eeprom = <&factory 0x0000>;
status = "okay";
};
And the base definition in mt7986b.dtsi:
wbsys: wbsys@18000000 {
compatible = "mediatek,wbsys";
reg = <0 0x18000000 0 0x1000000>;
interrupts = <GIC_SPI 213 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 214 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 215 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 216 IRQ_TYPE_LEVEL_HIGH>;
chip_id = <0x7986>;
};
Could you please add a target or DTS profile for the Archer AX80 V2? I have a stable UART connection and can provide further logs or test experimental builds.
[failed_kernel_boot.txt](https://github.com/user-attachments/files/26609558/failed_kernel_boot.txt)
[full_factory _boot _log.txt](https://github.com/user-attachments/files/26609560/full_factory._boot._log.txt)
[success_boot_no_wi_fi_dts_table.txt](https://github.com/user-attachments/files/26609559/success_boot_no_wi_fi_dts_table.txt)
Emre_Y
April 27, 2026, 8:42am
5
I don't know why they make v2 and they literally make the same device, not even MT7986A this time? Still MT7986B. Wow TP-Link, really?
Don’t know if V2 is using MT7986B or MT7986A, but I suppose the new variant doesn’t make much sense given minimal difference in functionality.
Oh, somebody is already working on the same problem. Thanks for the link.
