The TP-Link TL-MR3420 is a Fast Ethernet b/g/n 300M (two 3 dBi omni-antennas) wireless router with USB 2.0.
The TP-Link TL-MR3220 is a Fast Ethernet b/g/n Lite-N 150M (one 5 dBi omni-antennae) wireless router with USB 2.0.
The TP-Link TL-WR841ND / TL-WR842ND is a similar router, those pages may contain helpful information.
For new installations of OpenWrt (if your router is currently running stock firmware) download the Install image from the table below.
To upgrade from an older version of OpenWrt, download the Upgrade image.
For more information see Obtain firmware.
It is also advisable to download the stock OEM firmware image or your router in case you need to revert to the original firmware.
Note for “MR3420 V2”
There is a possible bug in the Trunk version of OpenWrt for MR3420v2 and it is possible that after you set it up with a USB you may have occasional 'Stuck Boots' when only the power LED will be on and USB will have power but the router is not booting itself.
The workaround for this bug is a manual reboot of router with “turning it off and turning it back on again”. But if you can solder a 5V 100uf capacitor to the USB on the board it will work better and manual reboot won't be required. (Tested and it's working)
If you are a new user to OpenWrt it is advised that you choose latest stable version of the software. Trunk version is for those who already know their way around OpenWrt.
Install the OpenWrt image using “Firmware Upgrade” from the original firmware.
Flash via tftp
Using a serial line
Download the factory update firmware: openwrt-ar71xx-generic-tl-mr3420-v1-squashfs-factory.bin
The device now uses the IP 192.168.0.86. It repeatedly tries to download a file named mr3420v2_tp_recovery.bin from a tftpd server with the IP 192.168.0.66. You can verify these continuous requests with a network sniffer (e.g. tcpdump or wireshark). After about 4 tries it gives up and boots normally.
The following steps will serve an openwrt firmware image to the device:
download an appropriate firmware file (e.g. lede-17.01.4-ar71xx-generic-tl-mr3420-v2-squashfs-factory.bin)
rename the file to mr3420v2_tp_recovery.bin
configure the static IP 192.168.0.66 for your local ethernet interface
connect your computer to one of the LAN ports of the router
install a tftpd server (e.g. atftpd on Linux or Tftpd64 on Windows)
run the tftpd server and let it serve the directory that contains the above firmware image: atftpd –no-fork –daemon FIRMWARE_DIRECTORY
the router immediately starts to download the firmware image
after some time you will see all LEDs flashing once followed by a normal restart of the router
The following procedure was tested with a Version V2 of TL-MR3220.
Enter failsafe mode:
remove the power plug from the router
press and hold the RESET button
insert the power plug
release the RESET button
Some seconds later no LED besides the one for USB (and maybe for attached ethernet ports) should be lit.
The device now uses the IP 192.168.0.86. It repeatedly tries to download a file named mr3220v2_tp_recovery.bin from a tftpd server with the IP 192.168.0.66. You can verify these continuous requests even from logviewer of your TFTP server like Tftpd32 or with a network sniffer (e.g. tcpdump or wireshark).
Given below is log taken the logviewer of opensource TFTP server Tftpd32
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 48:88:CA:27:00:06 [08/06 14:10:28.790]
Connection received from 192.168.0.86 on port 1890 [08/06 14:11:45.055]
Read request for file <mr3220v2_tp_recovery.bin>. Mode octet [08/06 14:11:45.076]
For MR3320 v2, Please use the filename “mr3220v2_tp_recovery.bin” (squashfs, not sysupgrade), connect to LAN, not WAN. Press and hold WDS/RESET, power on, the WDS-LED (padlock) lights up.
After some time you will see all LEDs flashing once followed by a normal restart of the router.
Pinout for MR3220 V2.2 (I have V2.3 as on photo with V2.2 on bottom) only
Pin 1 is clearly marked on the board.
To be able to use the UART on MR3220v2, TP18 to TP38 and TP28 to TP48 should be connected.
This is how I did mine:
To get the serial connection work reliably, you have to connect a 10k pullup resistor between the TX and the 3.3V pin. This is because the TX pin is connected to a voltage divider (2×5.6k) and a capacitor is put between the real pin and the TX connector. 1)
Now connect a serial hack adapter (DKU-5, CA-42 or similar containing the PL-2303 chip) and away you go!
This adapter can be also used provided a serial port is present on the PC.
Tested on MR3420 v2.2, but it requires a 4.7k pulldown resistor between Tx and GND.
When using it, router has to be powered on, and after that connect the pulldown, Tx and Rx pins.
(Tx from schematic goes to Tx pin of router, Rx from schematic to Rx of router).
The right settings for accessing the serial console are as follows:
Bits per second: 115200
Data bits: 8
Stop bits: 1
Flow control: None
Password to get into uboot prompt is tpl
Password to get root login is 5up
Note: (TP-Link MR3420 v1.2) In case the vlan switch configuration is not created automagically (⇐ 10.03.1) and there is eth0 and eth1 after bootup change /etc/config/network to reflect the vlan setup by adding the lines below. Also replace the 'option ifname “ethX”' accordingly (eth0.1, eth0.2). The proper ethernet port layout has still to be confimed.
Failsafe is a quite popular feature, of this router, thats lets you recover instantly from a misconfiguration above.
Use the QSS button instead of reset button, everything else is identical to generic failsafe document.
Failsafe may not work in Backfire before r29661, so it's confirmed to not work at Backfire 10.03.1 launch (r29592). Be extremely cautious on what you're doing or go directly to serial recovery.
Note for MR-3220 running on 12.09-rc1 (r34185): I did not get any UDP packets to port 4919 as promised either when connected to LAN or WAN, however repeatedly pushing the front button made the router to enter the failsafe mode, which allowed me to gain again access to the router. The problem almost bricking my router was in my network configuration, for some reason setting a fixed MAC address for a bridge caused the router to hang at /etc/init./network start.
FAILED SETTING SOLUTION (NOT THE FAILED FLASH!):
In case of failure or an installation package settings can sometimes cause the router cannot be accessed either administrator page (http://192.168.1.1) also through the console. This condition can be addressed in the following way;
1) turn off and turn on the Router
2) Shortly lights up press the SYS LED is that flashing LED SYS, will very quickly.
3) Now the Router has been accessible via TELNET
4 Router with TELNET) Login
5) type in the command: firstboot
6) type in the command:/etc/init.d/uhttpd start
7) went back to the Admin page in a browser with the address: http://192.168.1.1
Unlike standard modding mmc_over_gpio - where was necessary to find 4 unused GPIOs, in the deep modding we can use only one GPIO(or two GPIOs if whe want to use SD card as hotplug SPI device), because we will use a common SPI bus with NOR flash memory.
Due to the fact that on routers MR3420/MR3220 V1.x we have limit of available unused GPIOs, we forced to use the common SPI bus with NOR flash memory (spi0.0) where MMC/SD memory card will be - spi0.1
How to do this is described in this link.
With MR3220 v1.2 and CA-42 just connect TX, RX and GND, do not need any resistor.
toh/tp-link/tl-mr3420.txt · Last modified: 2019/07/15 15:41 by rubo77