Hi, I have this same version (MR80X v4 BR) and also managed to install the latest version.
I'm was able to run the same tests as @GabrielBFern and the results seemed pretty consistent with yours here.
I'm currently running the router as my gateway using PPPoE protocol on wan interface, with 3 different VLANs on my lan interface and 3 different wireless AP on each band (6 in total) and the networking is working as expected and very stable over Ethernet and over Wifi connections.
The only glitch that I encountered so far was on the led setup for the wan port, I needed to change trigger device for this led from wan to eth1 in order to function properly.
I followed the MR80X_v3 commit instructions and the installation occurred without errors.
The PCB is in fact very different from the v3 models posted here before, but the SoCs are essentially the same. In my case to obtain a good and stable UART connection I soldered some cable jumpers on the smd pads for the UART, this is a easy process, and identifying the pins is very straightforward since the pins are labeled on the pcb, but you need to be very careful to not damage one of the antennas cables that run over the UART pads.
If anyone have any suggestion on what to test next, please feel free to ask.
Hey I got MR80X v4 BR and I believe its not possible to upload the openwrt firmware directly through the Mercusys router web interface. When I tried to upload the Openwrt it said something like "unsupported file".
I'm waiting for UART to USB dongle that I got from internet to arrive in my home to try OpenWrt in this router.
Yeah, currently the only method for this device is via uart, a have been trying to tweak the original firmware to get an ssh/telnet prompt but with no success.
Maybe the tp-link oem easy installation method could be possible with this device, since I found some similarities in this device stock firmware with some tp-link devices stock firmwares, but I don’t have the necessary knowledge of this method to confirm this hunch and implement this.
Any insights are welcome, I have a series of this devices to flash in the near future, and skip the process of open this case will be so much a relief…
Does holding down the reset button during boot trigger tftpboot like on other tplinks? Placing the tftp server on the PC with a fixed IP of 192.168.0.66 and the firmware image as firmware.bin. Has anyone done a tcpdump or wireshark capture to check the behavior in uboot if the reset boot is held when the power is turned on?
I have recently purchased a MR80X router with the intent of running OpenWRT on it. Sadly, the product was v2 not v3. As previously mentioned in this thread, the MR80X v2 uses a Qualcomm IPQ0509 SoC.
As of writing, the "main" branch has support for the IPQ50XX platform. However, as this router is not oficially supported, it is not avaliable in menuconfig. I downloaded a copy of the GPL source code from the Mercuysus website with the hope of finding the .dts file for this system, with sadly no luck. It appears that the downloaded archive contains source code for many generic platforms. Not this device alone.
With all that said, is there a way of obtaining the neccessary dts file? I assume that support for this device cant be added without it.
Any advice is much appreciated, thanks in advance!
I have not test this method exactly, but I can confirm that booting with reset button pressed activate the recovery web server to upload a firmware image on 192.168.1.1.
Since I was unable to find any information about the V2 revision of the MR80X, so I took a look at the GPL kernel sources and the latest firmware itself, the latter with Binwalk and a hex editor, and unfortunately it too has an IPQ5010, so should be avoided.
I had ordered mine two weeks ago, and it just arrived this evening, and it turned out to be V2, despite the fact that the representative of the store I spoke with (local, but not in my immediate area) looked at one that showed V3, and I had expressly stated that I need V3 (or V4, as they are pretty much the same), and explained that different hardware revisions can be completely different routers, I still got a different hardware revision than I had payed for, so I will be giving the store a call next morning and requesting either a replacement or a full refund.
Update: I see that this thread already points this out, somehow it did not appear in my search results when searching for the V2 MR80X. Sorry for pointing out something redundant without properly checking.
Update 2: I took another look, and I mistakenly wrote “IPQ5010”, it is “IPQ5018”.
Another one with Mr80x v4 here.
I couldn't flash with the recovery web server (maybe I did something wrong, dunno).
But since the contact points are soldered, it was pretty easy to get UART connection with a pogo pin clip. I had more difficult opening the damn casing than flashing OpenWRT.
Now the steps to flash the OpenWRT changes according to the OS you are using, but considering that you have opened the router, connected it to your computer via a SERIAL adapter of some sort and was able successfully interrupt the boot, you can just follow the instructions in the commit here: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=7921e48d43571861f15aa56717798709ff7507b6
Hi, @lmrodrigues Can you tell us how do you disassembled the router? I have just bought this router and want to use OpenWRT on it as you already did. Thanks in advance.
