See also the [[toh:​tp-link:​TL-MR3020]],​ [[toh:​tp-link:​TL-MR3040]] and [[toh:​tp-link:​TL-WR703N]]. or [[toh/​tp-link/​tl-mr10u|TP-Link TL-MR10U]], [[toh/​tp-link/​tl-mr11u|TP-Link TL-MR11U]], [[toh/​tp-link/​tl-mr12u|TP-Link TL-MR12U]] and [[toh/​tp-link/​tl-mr13u|TP-Link TL-MR13U]]\\ **''​Note:''​** Many of these routers are marketed as a //"3G travel router"//​ but **none actually include a 3G modem** - the marketing term rather means that the OEM firmware supports USB 3G modems because it contains drivers for USB modems! Ignore that, because with OpenWrt ANY router with USB supports 3G hardware... ;-)

-

The TL-WR703N is marketed as a //"3G travel router"//​. **It does not include a 3G modem** ​- it simply means that the OEM firmware supports USB 3G modems, and that the oem firmware contains drivers for USB modems! Ridiculous, since with OpenWrt ANY router with USB supports 3G hardware... ;-)

- Please see [[doc:​howto:​generic.flashing]] for a generic description of the OpenWrt installation process.

- Please see [[doc:​howto:​generic.flashing]] for a generic description of the OpenWrt installation process.

-

​

+

+

==== Building Custom Images ====

+

:!: If you've got a modified version of this hardware which has 16MB of flash, then you will not be able to **build** images larger than 4MB, even though the bootloader will allow you to subsequently utilize all 16MB of flash (i.e. by adding packages after firstboot). ​ See http://​wiki.openwrt.org/​toh/​tp-link/​tl-wr703n#​mb.flash.mod for how to solve this problem.

+

+

===== Warnings / Gotchas =====

+

Please check the firmware version first, either:

+

* in the Chinese webadmin interface: "Build 120925"​ correspond to a v1.7 firmware

+

* on the internal sticker located on the Ethernet jack (may have 12B042)

+

* ** DO NOT RELY ON THE VERSION GIVEN BY THE EXTERNAL STICKER ON CASE BOTTOM ** : it may report falsely "​1.6",​ even if the firmware is actually a V1.7

+

+

{{:​meta:​icons:​tango:​48px-dialog-warning.svg.png?​nolink}} **WARNING __If you have a V1.7 firmware, SOME OpenWrt trunks (e.g. r36641) will brick your router, unless you have access to the serial console!__ ​ NEWER TRUNKS will install without issue via tftp and will work fine. **

+

+

Below is the version of the new bootloader (which disables the LAN port) of a version 1.7 hardware model (bought in December 2012).

+

<​code>​

+

root@tpl2:​~#​ grep -a U-Boot /dev/mtd0ro | cut -d'​I'​ -f1

+

U-Boot 1.1.4 (Sep 25 2012 - 09:04:47)

+

</​code>​

+

+

For more info visit this forum topic:

+

https://​forum.openwrt.org/​viewtopic.php?​id=40986

+

+

Firmware rev.140120 has admin1/​admin1 set for web login/​password

==== Power consumption ===

==== Power consumption ===

Line 40:

Line 68:

Power consumption will be higher if a USB device is attached to its USB port!

Power consumption will be higher if a USB device is attached to its USB port!

-

*Hint: If the router seems to be damaged because of a too high voltage, connect 3.3V _after_ the voltage regulator. This resets an electrical fuse or something, and the router works again.

+

*Hint: If the router seems to be damaged because of a too high voltage, connect 3.3V _after_ the voltage regulator. This replaces the function of the damaged regulator, and the router works again.

+

Be sure to power 5 volts into the micro-usb port at the same time if you want to have the usb port on the device work.

+

More information and a rough diagram here [[http://​img513.imageshack.us/​img513/​4295/​saai.jpg]]

==== Serial console ====

==== Serial console ====

-

The serial console connector does not utilise the regular TP-Link pinouts. Two pads labelled TP_OUT and TP_IN are the TX and RX signals.

+

The serial console connector does not utilise the regular TP-Link pinouts. Two pads labelled TP_OUT and TP_IN are the TX and RX signals. 115200 8n1. You have to connect your RS232-USB apdater also to the 5V pin on the board.

Note that the pads can very easily be lifted. ​ There is slightly more mechanical strength if you can solder to the surface-mount components to which the pads are connected--but this also takes care--your device could easily be destroyed. ​ Make sure that your connection is secured so that tension cannot be applied to the solder points when you connect to an external device.

Note that the pads can very easily be lifted. ​ There is slightly more mechanical strength if you can solder to the surface-mount components to which the pads are connected--but this also takes care--your device could easily be destroyed. ​ Make sure that your connection is secured so that tension cannot be applied to the solder points when you connect to an external device.

Snapshot image was broken around 18/11/2011, but from 26/11/2011 that was fixed.

+

Download latest [[http://​downloads.openwrt.org/​barrier_breaker/14.07/ar71xx/generic/​openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin|squashfs-factory.bin]] for the initial flash. Use a "sysupgrade" ​file for any future updates if already on openwrt.

-

+

-

Snapshot image was broken around 29/05/2012, but from 01/06/2012 that was fixed.

+

-

+

-

**Snapshot images are always risky. Check the forum discussion for latest opinions on available images.**

Note that this will not destroy the contents of the file system, so any old modules under /​lib/​modules/​x.y.z will still get loaded. If you don´t get a telnet login after reboot, try rebooting again.

+

To flash from the Chinese web interface, at the present time you would select the last menu item on the left, and then the third submenu item. This initiates a popup with two buttons--the upper right one allows you to browse to find the file you want to flash on your PC, the lower left one initiates the flash.

To flash from the Chinese web interface, at the present time you would select the last menu item on the left, and then the third submenu item. This initiates a popup with two buttons--the upper right one allows you to browse to find the file you want to flash on your PC, the lower left one initiates the flash.

Line 78:

Line 93:

==== Failsafe mode ====

==== Failsafe mode ====

-

When the configuration no longer allows you to log in via any network connection (e.g. lost password), the OpenWrt failsafe mode can be entered via the single "​Reset"​ button on the device. However, in contrast to the [[http://​wiki.openwrt.org/​doc/​howto/​generic.failsafe|generic failsafe instructions]],​ for the TL-WR703N you have to wait for ca. 12 seconds before pushing the "​Reset"​ button after powering on the device. If the button is pushed immediately after powering on, the single blue LED will start blinking, supposedly indicating some failsafe firmware recovery mody of the embedded bootloader (not yet discovered how to use it). In this mode, the OpenWrt failsafe is not being started. Instead, wait for slightly longer than 10 seconds and - as soon as the LED starts blinking for the first time after powering on the device, push the "​Reset"​ button for ca. 1-2 seconds. Immediately afterwards, the LED will blink rapidly (multiple Hz) and OpenWrt will be in [[http://​wiki.openwrt.org/​doc/​howto/​generic.failsafe|failsafe mode]].

+

When the configuration no longer allows you to log in via any network connection (e.g. lost password), the OpenWrt failsafe mode can be entered via the single "​Reset"​ button on the device. However, in contrast to the [[http://​wiki.openwrt.org/​doc/​howto/​generic.failsafe|generic failsafe instructions]],​ for the TL-WR703N you have to wait for ca. 10 (10-12) seconds before pushing the "​Reset"​ button after powering on the device. If the button is pushed immediately after powering on, the single blue LED will start blinking, supposedly indicating some failsafe firmware recovery mody of the embedded bootloader (not yet discovered how to use it). In this mode, the OpenWrt failsafe is not being started. Instead, wait for slightly longer than 10 seconds and - as soon as the LED starts blinking for the first time after powering on the device, push the "​Reset"​ button for ca. 1-2 seconds. Immediately afterwards, the LED will blink rapidly (multiple Hz) and OpenWrt will be in [[http://​wiki.openwrt.org/​doc/​howto/​generic.failsafe|failsafe mode]].\\

+

- The above didn't work on a Ver 1.6 box running OpenWRT r33312. To get into failsafe mode, power up the device and wait until the LED starts flashing (about 2Hz). Once it starts flashing (within about 4 seconds) then quickly press the button. The LED will then flash much faster and the device will be in failsafe mode.

==== Back to original image ====

==== Back to original image ====

Line 85:

Line 101:

* Download the original image: http://​www.tp-link.com.cn/​download/​2011930104462.rar extact to tftp folder

* Download the original image: http://​www.tp-link.com.cn/​download/​2011930104462.rar extact to tftp folder

* Setup your eth0 to 192.168.1.100,​ you can check detail by '​printenv'​

* Setup your eth0 to 192.168.1.100,​ you can check detail by '​printenv'​

-

* Run blow command under U-Boot:

+

* Run below command under U-Boot:

tftpboot 0x81000000 wr703nv1_cn_3_12_11_up(110926).bin

tftpboot 0x81000000 wr703nv1_cn_3_12_11_up(110926).bin

Line 91:

Line 107:

cp.b 0x81000000 0x9f020000 0x3c0000

cp.b 0x81000000 0x9f020000 0x3c0000

bootm 9f020000

bootm 9f020000

+

+

* Instructions on the [[https://​forum.openwrt.org/​viewtopic.php?​id=37361|forum]] for flashing wr703n with mr3020 firmware which is in english and not in chinese.

+

* Detailed instructions on the [[https://​forum.openwrt.org/​viewtopic.php?​pid=198336#​p198336|forum]] for flashing

I've setup over 15 of the v1.7 hardware nodes with Chaos Calmer trunk r45157, with some nodes running non-stop for weeks without issue. WiFi, USB and ethernet works great; mostly using the WR703n'​s to support [[http://​virtualhere.com/​|VirtualHere]] USB-over-IP services. While this works great for me, this could brick your device: //proceed at your own risk//.

+

+

Huge thanks to Interdev for the [[https://​forum.openwrt.org/​viewtopic.php?​pid=264171#​p264171|original sketch]]. Below are the specific steps that works beautifully for me.

Create a file named "​aa",​ using the following contents. Don't forget to replace 192.168.0.9 with the IP of your tftp server.

+

<​code>​

+

cd /tmp

+

tftp -gl i1 192.168.0.9

+

tftp -gl i2 192.168.0.9

+

tftp -gl busybox 192.168.0.9

+

chmod 755 busybox ​

+

./busybox dd if=i1 of=/​dev/​mtdblock1 conv=fsync

+

./busybox dd if=i2 of=/​dev/​mtdblock2 conv=fsync

+

./busybox reboot -f

+

</​code>​

+

+

Now you should have 5 files in your TFTP server'​s folder:

+

* openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin

+

* busybox

+

* i1

+

* i2

+

* aa

+

+

==== Install OpenWRT ====

+

Use the following commands to install OpenWRT on a stock/​factory Chinese v1.7 TL-WR703N running 3.17.1 Build 140120. Assuming you have a Linux or BSD-based TFTP server, just run the commands from there. **DO NOT POWER OFF EQUIPMENT! INTERRUPTING IT WILL BRICK (and you need a 3.3V serial to revive it).**

+

+

Again, replace 192.168.0.9 with the IP of your TFTP server, and 192.168.0.100 with the IP assigned to the WR703N.

+

+

Each of the following steps are necessary, don't skip them.

+

+

=== Set password to admin42 ===

+

This is only necessary to complete the OpenWRT install, password will be reset to the [[doc:​howto:​firstlogin|default OpenWRT password]] upon completion of your install.

Wait until the WR703N starts to blink; OpenWRT is now loading. Check your DHCP server, ARP table, or use nmap, to find the IP address. See [[doc:​howto:​firstlogin|OpenWrt – First Login]] for login instructions. ​

The USB port on the WR703n is not compatible with USB1 devices (aka full speed) and only works properly with USB2 (aka high speed) devices. You can however plug a USB-Serial adapter as long as you plug that through a <$10 USB2. While you're at it, use another USB port to plug in a USB key and write data there (like serial console logs) so as not to wear out the built in flash.

-

===== Wi-Fi Client Bridging =====

+

See this page for more tips and how to create a serial console server out of your WR703n:

- you could read about [[doc:​techref:​bootloader]] in general and about [[doc:​techref:​bootloader:​uboot|Das U-Boot]] in particular.

+

+

==== U-Boot 1.1.4 modification for routers ====

+

Forum member [[https://​forum.openwrt.org/​profile.php?​id=72549|pepe2k]] made a modification of **U-Boot 1.1.4** for **Qualcomm Atheros** SoCs based devices (the project is still being developed, so new devices and SoCs will be supported in the future). Up to date information,​ binary images and sources can be found on official [[https://​github.com/​pepe2k/​u-boot_mod|GitHub repository]].

+

+

This modification started from [[http://​code.google.com/​p/​wr703n-uboot-with-web-failsafe/​|wr703n-uboot-with-web-failsafe]] project, but supports more devices, all modern web browsers, has a lot of improvements and other modifications (like U-Boot NetConsole, custom commands, overclocking possibilities etc.).

+

+

More information:​

+

+

* Official repository on GitHub: [[https://​github.com/​pepe2k/​u-boot_mod|U-Boot 1.1.4 modification for routers]]

+

* Discussion about this project on [[https://​forum.openwrt.org/​viewtopic.php?​id=43237|OpenWrt forum]]

+

* An article (in Polish) about one of the first version of this project on [[http://​www.tech-blog.pl/​2013/​03/​29/​zmodyfikowany-u-boot-dla-routerow-tp-link-z-atheros-ar9331-z-trybem-aktualizacji-oprogramowania-przez-www-i-konsola-sieciowa-netconsole/​|www.tech-blog.pl]]

===== Hardware Mods =====

===== Hardware Mods =====

-

- as a beginner, you really should inform yourself about [[doc:​hardware:​soldering]] in general and then even obtain some experience!

-

Here are some interesting hardware ​hacks for the TL-WR703N, from the OpenWRT forum:

+

Note: If you are a beginner, you should inform yourself about [[doc:​hardware:​soldering]] in general and even then obtain some experience!

+

+

Here are some interesting hardware ​modifications ​for the TL-WR703N, from the OpenWRT forum:

*[[http://​www.tl-wr703n.blogspot.com/​2012/​08/​tl-wr703n-poe-power-over-ethernet-rj45.html|POE (Power Over Ethernet) RJ45]] and on the [[https://​forum.openwrt.org/​viewtopic.php?​pid=176528#​p176528|forum]] and on [[http://​dev.wlan-si.net/​wiki/​Routers/​TP-LINK/​WR703N|wlan-si web site]]

+

*[[https://​forum.openwrt.org/​viewtopic.php?​pid=196884|POE and USB to serial mod]]

This project implements a webradio with cheep usb soundcard and a speaker of an old mobile phone within the casing of the router. There are two analogue controllers for selecting the stream and the volume. Therefor an attiny85 is connected to the uart.

+

+

[[http://​piie.net/​index.php?​section=tplink-radio|Building a tiny webradio with analog volume and tune controller]]

==== 64MB RAM Mod ====

==== 64MB RAM Mod ====

-

The Device uses a DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/​8=32MiByte) 400MHz chip Zentel A3S56D40FTP. Replace it with any 32Mbit x 16bit chip. 333MHz instead of 400MHz also works fine. It's quite hard to find these chips. ​The best chance ​is to have a look at DDR-SODIMM. Since there are no 64Mbit x 16Bit DDR1 Chips available -> no 128 MB mod!

+

The Device uses a DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/​8=32MiByte) 400MHz chip Zentel A3S56D40FTP. Replace it with any 32Mbit x 16bit chip. 333MHz instead of 400MHz also works fine. It's quite hard to find these chips. ​One of the ways to get them is to have a look at DDR SO-DIMM (because SO-DIMM modules are shipped with x16 chips). Since there are no 64Mbit x 16bit DDR1 Chips available -> no 128 MB mod!

+

+

The most easy approach is to seek for a 4-chip DDR 256 MB module. These all have x16 chips too. Chips only on one side (not to be confused with double-sided 256 MB modules with 4 chips on each side) and only 4 of them - that's the best chance to get some. They represent a small percent among usual 8-chip modules but this is equalized with the amount and "cheap as dirt" price of such DDR 256 MB modules.

+

+

Chip can also be salvaged from dead HDD with 64Mb cache, for example 2Tb Western Digital WD2002FYPS

:!: If you've made (or bought) a WR703N with 16MB of flash, you will still have difficulty **building** images larger than 4MB, even though you can use all 16MB once you've flashed an image (functionality provided by an appropriate bootloader, such as pepe2k u-boot mod). The reason is because the WR703N profile has a limit of 4MB, which is enforced by the **mktplinkfw** (make TP-Link Firmware) tool when the image is created.

+

+

To enlarge this limit to 16MB, you can try the following (worked for me on BB, b41353):<​code bash>

See: https://​forum.openwrt.org/​viewtopic.php?​pid=238165 for more information.

+

+

=== Remarks ===

+

16mb chips are most **likely not supported by the boot loader which resides on your old chip**, therefore you cannot simply burn the 4mb chip content on the new 16m chip and everything will be working. If you try this the LED will glow purple-ish. You will have to replace the bootloader with one supporting your new chip.

+

+

=== Supported Chips ===

+

from pepe2k u-boot mod:

+

* Winbond W25Q128 (16 MB, JEDEC ID: EF 4018)

+

* Macronix MX25L128 (16 MB, JEDEC ID: C2 2018, C2 2618)

+

* Spansion S25FL127S (16 MB, JEDEC ID: 01 2018)

+

+

=== Create a working image ===

+

In order to replace the 4mb flash chip with a 16mb one you may at first dump two important partitions: ​

+

* 64k u-boot + 64k data section: at the beginning of the chip. The data section is important as it contains MAC and PIN as well as Model information.

Flash this image with your SPI-programmer on your new chip and solder it in. You can now hold the button for 3 seconds (will blink each second) and release to make the bootloader start a httpd at **192.168.1.1**.

==== MiniPwner Home ====

==== MiniPwner Home ====

Line 776:

Line 1007:

* See the schematic for pin outs of the GPIO and serial ports. Due to space restrictions,​ the extra 8 GPIO's from PORTB are not routed out.

* See the schematic for pin outs of the GPIO and serial ports. Due to space restrictions,​ the extra 8 GPIO's from PORTB are not routed out.

+

===== Custom OpenWrt image with LuCi integrated =====

+

http://​www.superwrt.eu/​en/​firmware/​tp-link-wr703n/​

-

===== Custom IPv6 image for wr703n =====

+

Note: Luci is integrated in all released (i.e. not nightly snapshot) builds of OpenWrt, so no need to get SuperWRT just for integrated Luci.