OpenWrt Support for Mercusys MR80X v2 (AX3000 Dual-Band Wi-Fi 6 Router)

[ARahmanAR]

Hello OpenWrt developers

I’d like to request OpenWrt support for the Mercusys MR80X v2 (AX3000 Dual-Band Wi-Fi 6 Router).
Currently, only the MR80X v3 has a hardware entry and partial support:
https://openwrt.org/toh/hwdata/mercusys/mercusys_mr80x_v3

However, the v2 hardware revision has no firmware available and no ToH data entry yet.

---

Hardware Overview (MR80X v2)

Component	Details
Model	Mercusys MR80X v2
Wi-Fi Standard	IEEE 802.11ax (Wi-Fi 6)
Wi-Fi Speeds	574 Mbps @ 2.4 GHz + 2402 Mbps @ 5 GHz (up to 3000 Mbps total)
Chipset (likely)	Qualcomm IPQ5018 / IPQ6000 family (dual-core 64-bit)
CPU	Dual-core @ 1 GHz
RAM / Flash	TBD (awaiting teardown photos)
Antennas	4 × external high-gain antennas with beamforming
Ports	1 × Gigabit WAN + 3 × Gigabit LAN
Security	WPA3
Features	MU-MIMO, OFDMA, BSS Coloring, Target Wake Time (TWT)
App Support	MERCUSYS mobile app (Android/iOS)

---

Why Requesting Support

• The MR80X v2 is widely sold in many regions (especially Asia), yet lacks OpenWrt firmware.
• The hardware appears very similar to MR80X v3, so porting may be feasible once differences are identified.
• Having support for v2 will help many users benefit from OpenWrt’s performance, stability, and security.

[brada4]

Could you please provide device boot log from OEM firmware - Set system log level to maximum/debug, then after reboot copy kernel log, ie one showing “Linux version 4.xxxxxx” in the beginning in full”

That will non-destructively reveal the system resources. OEM upgrade file is 25MB in size, which means at least 32MB of flash which is very good.

It needs at least 512MB RAM for current Qualcomm wifi6 driver (256 is too short)

Please remove AI enhancements from the device specs. Only functional line is guess on CPU which may not even be true.

[ARahmanAR]

Thank you for your guidance. I currently have access only to the application-level system logs via the OEM firmware. Unfortunately, I do not have system-level access (SSH, telnet, or JTAG) to capture the full kernel boot log, which would show the “Linux version 4.xxxxx” entries and detailed hardware initialization.

2025-10-18 09:31:43 QoS INFO [14905] Service start

2025-10-18 09:31:43 QoS INFO [14905] Function disabled

2025-10-18 09:31:43 QoS INFO [14905] Service stop

2025-10-18 09:31:40 Remote Management INFO [15368] Service stop

2025-10-18 09:31:37 NAT INFO [13539] Initialization succeeded

2025-10-18 09:31:31 NAT INFO [13539] Initialization succeeded

2025-10-18 09:31:30 Led Controller INFO [1218] Start to run WAN1_ON

2025-10-18 09:31:30 Led Controller INFO [1218] Start to run WAN0_OFF

2025-10-18 09:31:30 Led Controller ERROR [1218] Config importing failed

2025-10-18 09:31:30 Led Controller DEBUG [1218] Failed to read LAN_OFF

2025-10-18 09:31:26 Led Controller ERROR [1218] Config importing failed

2025-10-18 09:31:26 Led Controller DEBUG [1218] Failed to read WAN1_OFF

2025-10-18 09:31:26 Led Controller INFO [1218] Start to run WAN0_ON

2025-10-18 09:31:26 Led Controller ERROR [1218] Config importing failed

2025-10-18 09:31:26 Led Controller DEBUG [1218] Failed to read LAN_OFF

2025-04-22 00:01:34 PPP INFO [13452] ppp receive IPCP ACK

2025-04-22 00:01:34 PPP INFO [13452] ppp receive IPV6CP ACK

2025-04-22 00:01:34 PPP INFO [13452] ppp receive IPCP NAK options

2025-04-22 00:01:34 PPP INFO [13452] ppp send IPV6CP Req options

2025-04-22 00:01:34 PPP INFO [13452] ppp send IPCP Req options(addr=0.0.0.0;)

2025-04-22 00:01:34 PPP INFO [13452] ppp receive PAP AuthAck Login ok

2025-04-22 00:01:34 PPP INFO [13452] ppp send LCP ACK

2025-04-22 00:01:34 PPP INFO [13452] ppp receive LCP Request options(authtype=PPP_PAP;mru=1480;)

2025-04-22 00:01:34 PPP INFO [13452] ppp receive LCP ACK

2025-04-22 00:01:34 PPP INFO [13452] ppp receive LCP Request options(authtype=PPP_PAP;mru=1480;)

2025-04-22 00:01:34 PPP INFO [13452] ppp send LCP Request options

2025-04-22 00:01:34 PPP INFO [13452] pppoe receive PADS sess-id(57808)

2025-04-22 00:01:34 PPP INFO [13452] pppoe send PADR Host-Uniq(348c)

2025-04-22 00:01:34 PPP INFO [13452] pppoe receive PADO form AC-MAC

2025-04-22 00:01:34 PPP INFO [13452] pppoe receive PADO AC-Name(EPZ-AN-9)

2025-04-22 00:01:34 PPP INFO [13452] pppoe send PADI Host-Uniq(348c)

2025-04-22 00:01:34 PPP INFO [13452] pppoe send PADT due to(resending PADI)

2025-04-22 00:01:33 Led Controller ERROR [1218] Config importing failed

2025-04-22 00:01:33 Led Controller DEBUG [1218] Failed to read WAN1_OFF

2025-04-22 00:01:33 Led Controller INFO [1218] Start to run WAN0_OFF

2025-04-22 00:01:33 Led Controller ERROR [1218] Config importing failed

2025-04-22 00:01:33 Led Controller DEBUG [1218] Failed to read LAN_OFF

2025-04-22 00:01:29 Led Controller INFO [1218] Start to run STATUS_ON

2025-04-22 00:01:28 QoS INFO [12776] Service start

2025-04-22 00:01:28 QoS INFO [12776] Function disabled

2025-04-22 00:01:27 Led Controller INFO [1218] Start to run GENERAL

2025-04-22 00:01:20 Traffic Statistics INFO [11743] Service start

2025-04-22 00:01:05 Factory Reset INFO [10664] Service start

2025-04-22 00:01:04 Parental Controls INFO [10423] Service start

2025-04-22 00:01:04 Parental Controls INFO [10423] Function enabled

2025-04-22 00:01:03 Access Control INFO [10214] Service start

2025-04-22 00:01:03 Access Control INFO [10214] Function disabled

2025-04-22 00:01:02 NAT INFO [9381] IPSEC ALG enabled

2025-04-22 00:01:02 NAT INFO [9381] L2TP ALG enabled

2025-04-22 00:01:02 NAT INFO [9381] PPTP ALG enabled

2025-04-22 00:01:02 NAT INFO [9381] SIP ALG enabled

2025-04-22 00:01:02 NAT INFO [9381] RTSP ALG enabled

2025-04-22 00:01:02 NAT INFO [9381] H323 ALG enabled

2025-04-22 00:01:02 NAT INFO [9381] TFTP ALG enabled

2025-04-22 00:01:02 NAT INFO [9381] FTP ALG enabled

2025-04-22 00:00:59 NAT DEBUG [9381] Flush conntrack

2025-04-22 00:00:59 NAT INFO [9381] Function enabled

2025-04-22 00:00:59 NAT NOTICE [9381] Create NAT chain succeeded

2025-04-22 00:00:57 NAT INFO [9381] Initialization succeeded

2025-04-22 00:00:57 NAT INFO [9381] Initialization succeeded

2025-04-22 00:00:55 Basic Security INFO [8818] Service start

2025-04-22 00:00:55 Basic Security NOTICE [8818] Flush conntrack table succeeded

2025-04-22 00:00:52 Firewall INFO [7765] Service start

2025-04-22 00:00:24 Led Controller INFO [1218] Start to run WIFI_ON

2025-04-22 00:00:13 Remote Management INFO [3369] Service stop

2025-04-22 00:00:09 IP & MAC Binding INFO [2818] Daemon connection succeeded

2025-04-22 00:00:09 IP & MAC Binding INFO [2818] ARP Binding disabled

2025-04-22 00:00:09 IP & MAC Binding INFO [2818] Config interface initialization succeeded

2025-04-22 00:00:09 IP & MAC Binding INFO [2818] Initialization succeeded

2025-04-22 00:00:08 UPnP INFO [2669] Service start

2025-04-22 00:00:08 UPnP INFO [2669] Service stop

2025-04-22 00:00:05 Remote Management INFO [2199] Service stop

2025-04-22 00:00:00 Time Settings INFO [1285] Service start

1970-01-01 00:00:27 Led Controller INFO [1218] Start to run STATUS_SAN

1970-01-01 00:00:26 Led Controller INFO [1218] Service start

MR80X v2 | AX3000 Dual-Band Wi-Fi 6 Router - Welcome to MERCUSYS

[brada4]

Obviously not the log hoped for…..

Look harder for any log, there is a slim hope it gets more logs than starting PPPoE WAN…..

[Wallbanger]

And hook up serial…much more info

[ARahmanAR]

Noted. What would you suggest as the next step from here?

[brada4]

Try to find FCC ID on packaging, it may lead to internal pictures without opening the case

[ARahmanAR]

The sticker shows CE, UKCA, R-NZ, and EAC certifications — but it does not list any FCC ID.

[brada4]

Well, sticker shows US.

There is V2 EU gpl source, if you examine that maybe it positions it as v1 or v3 equivalent, or a clone of somesimilar tplink, but ok, open it up, try to iidentify chips, connect ttl. Really not muchto find about us/2.20 without opening the device.

[ARahmanAR]

Qualcomm IPQ0509 dual core CPU

Qualcomm QCN6102 radio chip

[brada4]

Try to shoot chips at angle to get some contrast. I only see realtek crab logo, must be a switch.

See four ttl pins at the bottom left from bigger chip shield?

PS I ike the positioning of word TOP on this PCB

[ARahmanAR]

[ARahmanAR]

Please build a pre-configured OpenWRT image for this model that has WiFi enabled.

[brada4]

That is not how it works, somebody with the device has to do the development….

[ARahmanAR]

After building firmware, can I pre-configure the OpenWRT image

[frollic]

@ARahmanAR

can I pre-configure the OpenWRT image

Once it's built, it's too late to preconfigure.
Unless you mean created support, when you say built.

[OpenWrt Wiki] Build System Usage

@ARahmanAR

The hardware appears very similar to MR80X v3, so porting may be feasible once differences are identified.

Not even close, different SoCs.

[ARahmanAR]

Noted. What would you suggest as the next step ?

[frollic]

[OpenWrt Wiki] Adding new device support

[brada4]

Acquire usb ttl adapter (3.3V most likely) and try to get boot log and boot images from same SoC

You can extract OEM DTS from raw partition backup on the router or find them in oem gpl bundle.

[brada4]

Inside gpl source

CONFIG_TARGET_NAME="arm-openwrt-linux-uclibc"
CONFIG_ROOTFS_PATH="../image/ax55v1/rootfs"

Which leads to cousin device…

Add support for TP-LINK AX55 V1

Hi, I have TP-LINK AX55 (AX3000) V1, is it possible to add support for this device? https://fccid.io/2AXJ4AX55/Internal-Photos/10-Internal-Photos-5422587 https://static.tp-link.com/upload/gpl-code/2022/202208/20220829/GPL_AX55v1.tar.gz Looks like it have 512MB RAM, 128MB flash and 1GHz dual core Qualcomm IPQ0518 (V2 version have some broadcom processor), Realtek switch and one USB3.0 port. I can try to read logs from serial later if needed and if I can disassembly router (I don't see any vis…

Looks yours has better switch chip…

Try to get ttl adapter, then cross check with that device. Note OEM kernel is 32bit on 64bit CPU