You are here: OpenWrt Wiki » Table of Hardware » TP-Link » TP-Link TL-WR1043ND

Differences

This shows you the differences between two versions of the page.

--- toh:tp-link:tl-wr1043nd [2012/11/02 10:33]
written_direcon
+++ toh:tp-link:tl-wr1043nd [2013/05/15 00:27] (current)
hd7544 Additional findings and simpler soluton to WAN bug.
@@ Line 1: / Line 1: @@
 ====== TP-Link TL-WR1043ND ======
+TP-Link TL-WR1043ND is currently supported!
 ===== Supported Versions =====
+This router has the following versions/models.
 ^ Version/Model ^ S/N ^ Release Date ^ OpenWrt Version Supported ^ Model Specific Notes ^
+| (DE)v1.0 | - | | Backfire 10.03.1 | Similar, German WebUI |
 | v1.1 | - | | Backfire 10.03.1 | Similar to WR941ND.|
+| (DE)v1.1 | - | | Attitude Adjustment 12.09-beta2 | Similar, German WebUI, V1.1 in S/N sticker |
 | v1.4 | - | | Backfire 10.03.1 | Same v1 board as v1.1|
 | v1.5 | - | | Backfire 10.03.1 | Same v1 board as v1.1|
 | v1.6 | - | | Backfire 10.03.1 | Similar |
 | v1.7 | - | | Backfire 10.03.1 | Similar |
-| v1.8 :!:| - | | Tested OK with trunk r33288 | Similar |
+| v1.8 :!:| - | | <color red>Suspect of hardware bug that bring down WiFi after a while.</color>[[https://forum.openwrt.org/viewtopic.php?id=43478|1]] Tested OK with Backfire 10.03.1 but newer v1.8 models with the current TP-LINK bootloader (ver. "U-Boot 1.1.4 (Mar 31 2012 - 10:40:21)") will need the bootloader downgrade described below for the WAN port to work with Backfire 10.03.1; Tested OK with Attitude Adjustment 12.09-rc1 | Similar |
-| v1.9 :!:| - | | Tested OK with Backfire 10.03.1 | Unknown |
+| v1.9 :!:| - | | Tested OK with Backfire 10.03.1 but as these models ship with the current TP-LINK bootloader (ver. "U-Boot 1.1.4 (Mar 31 2012 - 10:40:21)"), they will need the bootloader downgrade described below for the WAN port to work with Backfire 10.03.1 | Unknown |
-| (DE)v1.0 | - | | Backfire 10.03.1 | Similar, German WebUI |
+| v1.10 :!:| - | | Tested OK with **Attitude Adjustment 12.09-rc1** :!: **Backfire 10.03.1 = BRICK!!** | Similar rev:1.1 board|
+| v1.11 :!:| - | | Tested OK with **Attitude Adjustment 12.09** Not tested with 10.03.1|Downgrade U-Boot first |
+| (DE)v1.2 :!:| - | ? 03-2013 ? | Tested OK with **Attitude Adjustment 12.09-rc1** :!: **Backfire 10.03.1 = BRICK!!**  | |
-The supported versions include future releases, unless otherwise stated. The versions above indicate the first version that such device is officially supported.
+The list above shows the earliest OpenWRT release to be supported. Higher releases should be supported unless otherwise stated.
+:!: **WARNING: flashing the WRONG OpenWRT version on models v1.10 WILL CAUSE A BRICK** (see above).
 ===== Hardware Highlights =====
+**TP-Link Ultimate Wireless N Gigabit Router** (TL-WR1043ND)
 ^ CPU ^ Ram ^ Flash ^ Network ^ Gigabit ^ USB ^ Serial ^ JTag ^
 | Atheros AR9132@400MHz  | 32MB | 8MB | 4x1 | Yes | Yes | Yes | Yes |
 See paragraphs [[toh/tp-link/tl-wr1043nd#Hardware]] or [[toh/tp-link/tl-wr1043nd#Tags]] for more details.
+Manufacture advertised features:
+  * 802.11b/g/n WLAN with up to 300Mbps throughput
+  * 3 removable omni antennas (RP-SMA connector)
+  * 500 mW (27 dBm) maximal power output
+  * integrated 4-port Gigabit Switch (LAN ports)
+  * Gigabit Ethernet WAN port
+  * a USB 2.0 port
+  * QSS (WPS) push button
 ===== Warnings / Gotchas =====
-:!: **It has been [[https://dev.openwrt.org/ticket/11898 | reported]] that recent factory firmware includes a new bootloader revision which disables the WAN port at boot (likely to deal with [[https://dev.openwrt.org/ticket/6819 | switch leakage]]). A fix has been implemented in trunk between [[https://dev.openwrt.org/changeset/32942 | r32942]] - [[https://dev.openwrt.org/changeset/32942 | r32944]], while 45-46 fixes the leakage.**
+*** POSSIBLE SIMPLER SOLUTION ***
-Below is the version of the new bootloader (which disables the wan port) of a version 1.8 hardware model (bought in august 2012).
+I spent several hours today getting 12.09 installed on my V 1.10 router.  I performed all the downgrades recommended, verified the boootloader version, but could not get a WAN connection.  I finally noticed that my LAN and WAN were being assigned the same MAC address.  I changed the MAC address of the WAN interface to what it should be (last digit +1) and all was well.
+I then restored the bootloader to the latest version, U-Boot 1.1.4 (Apr 28 2013 - 16:01:02), and confirmed it via the code below.  Once again after installing the latest 12.09 factory-squashfs.bin, my I had to WAN connection and both LAN and WAN MAC addresses were the same.  Changing the WAN interface MAC address to what it should be solved my problem.
+As far as I can tell, the complex step below are apparently not necessary.  The latest bootloaoder may indeed disable the WAN during boot, which is great as it doesn't expose my devices to the WAN interface during that brief windows, but it's not staying locked.  It seems to be more of a simple MAC address issue.  Another note:  Before changing the MAC address to what it's assigned TP-Link address, I cloned my laptops MAC address, which gave the router connectivity on the WAN port, but my laptop could not get any web traffic.  Other devices connected could, but not my laptop.
+:!: **WARNING: v1.10 supports only Attitude Adjustment 12.09-rc1 or above. Backfire 10.03.1 causes a BRICK!!**
+:!: **WAN port disable bug (newer models v1.8+).** It has been [[https://dev.openwrt.org/ticket/11898 | reported]] that recent TP-Link stock firmware packages include a new bootloader revision, which disables the WAN (port 0) at boot. This was a unhelpful fix to deal with the [[https://dev.openwrt.org/ticket/6819 | switch leakage]], which has been implemented in trunk between [[https://dev.openwrt.org/changeset/32942 | r32942]] - [[https://dev.openwrt.org/changeset/32942 | r32944]] (45-46 fixes the leakage).
+**ALL newer hardware models v1.8 or above (from ~April 2012) is affected by this WAN port bug.** Below is the code for the affected bootloader that disables the WAN port at boot after flashing.
 <code>
 root@tpl2:~# grep -a U-Boot /dev/mtd0ro | cut -d'I' -f1
@@ Line 30: / Line 63: @@
 </code>
-:!: **This device does NOT deliver enough USB power for many USB 3G modems.  This can lead to erratic behavior, connections that only work for a few seconds, connections that completely fail to start.  If a 3G USB modem is to be used, consider other routers, e.g. [[http://wiki.openwrt.org/toh/buffalo/wzr-hp-ag300h | Buffalo WZR-HP-AG300H]]**
+  * Check of the TP-LINK firmware, ver. TL-WR1043ND_V1_120405 with a published date 2012/4/5: This firmware updates the bootloader code to a March 31, 2012 release date but has the same WAN port disabled on boot behavior as the Feb. 6, 2012 firmware, and so routers shipping with this firmware need the boot loader downgrade described below
+<code>
+U-Boot 1.1.4 (Mar 31 2012 - 10:40:21)
+U-Boot
+</code>
+:!: **WAN port disable bug (inelegant) workaround.** The older german stock firmware (v3.9.17/100331) does not feature this bug. The work around involves webreverting/downgrading to this older version and then reflashing OpenWRT.
+  * Step 1 (optional, only required if OpenWRT is installed): If your WAN port is now disabled follow the guide [[http://wiki.openwrt.org/toh/tp-link/tl-wr1043nd#back.to.original.firmware | here]] to web revert back to stock firmware.
+  * Step 2: Install german stock firmware (v3.9.17) through the TP-Link web interface. Download the firmware file "wr1043nv1_de_3_9_17_up_boot(100331).bin /.zip". (Google it or get it [[https://www.dropbox.com/el/?r=/s/f5kmuhld737veel/wr1043nv1_de_3_9_17_up_boot%2528100331%2529.bin&b=clk:124224095:13687220193071768671:777:446&z=AADjSCWkSnwuH8evw7wIbFDVpQJ9iogbHn-rdWJwu5h3tQ | here]]). After the German firmware flash, the u-boot code on a v1.9 router should be downgraded to the Nov. 17, 2009 version:
+<code>
+grep -a U-Boot /dev/mtd0ro | cut -d'I' -f1
+</code>
+<code>
+U-Boot 1.1.4 (Nov 17 2009 - 11:56:26)
+U-Boot
+</code>
+  * Step 3: Flash the correct OpenWRT firmware image according to your router model/version:!:. This should re-enable the WAN port.
+:!: **WARNING: flashing the WRONG OpenWRT version on models v1.10 WILL CAUSE A BRICK.**
+=== USB 3G Modems ===
+:!: **USB 3G modem issue (insufficient power).** The device does NOT deliver enough power for most USB 3G modems, which can lead to erratic behavior, droped/failed connections. If a 3G USB modem is to be used, consider other routers. (e.g. [[http://wiki.openwrt.org/toh/buffalo/wzr-hp-ag300h | Buffalo WZR-HP-AG300H]])
+== Compartible USB 3G modems: ==
+  * Huawei E1550
 ===== Installation =====
+ **Precompiled image**
   - Download a precompiled [[http://downloads.openwrt.org/attitude_adjustment/12.09-beta2/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin|Attitude Adjustment 12.09 Beta 2 (stable image)]].
-  Or follow the generic instructions on these pages:
+  - For v1.10 first flash old German firmware than flash precompiled [[http://downloads.openwrt.org/attitude_adjustment/12.09-rc1/ar71xx/generic/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin|Attitude Adjustment 12.09 rc1 (stable image)]] ; tested and works [[http://forum.lowyat.net/topic/2481658/all|credits go to sayboon]] for his tutorial
-  - [[doc:howto:obtain.firmware]] You //should// download a stable image with factory and SquashFS in the Name.
-  - [[doc:howto:generic.flashing]] Now write this firmware-file onto the flash-chip of your device
+ **Generic flash instructions**
+  * [[doc:howto:obtain.firmware]] You //should// download a stable image with factory and SquashFS in the Name (from the ar71xx platform)
+  * [[doc:howto:generic.flashing]] Now write this firmware-file onto the flash-chip of your device
+  * You can always [[doc:howto:obtain.firmware.generate|build]] your own image based on Kamikaze or on Backfire. Choose Atheros AR71xx/AT7240/AR913x platform and use TP-Link WR1043ND v1 Profile.
-  * You can allways [[doc:howto:obtain.firmware.generate|build]] your own image based on Kamikaze or on Backfire. Choose Atheros AR71xx/AT7240/AR913x platform and use TP-Link WR1043ND v1 Profile.
 Notes:
-  * The precompiled stable image does not include the kernel module for the wireless interface. To use wifi, you need to install kmod-ath9k and regenerate the configuration, see [[doc:uci:wireless|wireless configuration]]. Update: it appears that version Backfire 10.03.1 does contain the wifi driver. Wifi can work "out of the box" right after installation and just need to be enabled.
+**Wireless issues**
+  * In Backfire 10.03.1 (or above), the wifi interface is present but **disabled** by default. After flashing, you need to enable it in the settings (Network/WiFi) to get it working "out of the box".
+  * Older precompiled versions **DO NOT** include the kernel module for the wifi interface. To activate wifi, you need to install kmod-ath9k and regenerate the configuration (see [[doc:uci:wireless|wireless configuration]]).
-It appears that in order to use the "Firmware upgrade" option in the original firmware for installing OpenWRT, the WR1043ND must be connected to internet, or at least to a dhcp server on its WAN port - otherwise it won't flash the OpenWRT image, but come up with original firmware again after reboot. UPDATE: not a problem with hardware v1.8 running stock firmware 20110429: leaving connected back to back the Windows client PC performing the upgrade was good enough.
+**Firmware flashing bug for older models**
+  * In older router models, the WAN port MUST be connected to the internet or a DHCP server while flashing the OpenWRT image through the TP-Link web interface ("firmware upgrade" option). If the WAN port is disconnected, OpenWRT will NOT flash and the router will revert to stock firmware after reboot.
+  * UPDATE: This appears to be fixed in models v1.8 or later, running stock firmware 20110429. Leaving connected back to back the Windows client PC performing the upgrade was good enough.
 ==== Flash Layout ====
@@ Line 202: / Line 272: @@
 <code>
 dd if=orig.bin of=tplink.bin skip=257 bs=512
+</code>
+You should transfer the firmeware image to the /tmp folder and revert back to original firmware:
+<code>
+mtd -r write tplink.bin linux
 </code>
@@ Line 241: / Line 317: @@
 Some issues with 10.03.1-rc4 on Hardware Ver.1.8 see [[https://forum.openwrt.org/viewtopic.php?pid=123269#p123269|this post]] for workaround.
+There is a problem with VLAN-IDs > 9 (at least on v1.4 with 10.03.1-RC6 r28680 and v1.8 with 12.09-rc1 r34185). Using a VLAN-ID > 9 makes the router inaccessible on this interface.
 ==== Failsafe mode ====
 See [[doc:howto:generic.failsafe|OpenWrt Failsafe Mode]] for general information.
+Based on generic failsafe, here are peculiarities :
-Power up your router. When the 'SYS' light starts to blink, press and hold the //QSS// button on the right side of the front panel until the blinking of 'SYS' LED gets faster. If that won't work instead of holding the button press it and keep pressing it until the blinking gets faster. Alternatively you may try both methods on the //RESET// button on the back panel between USB and power plug.
+   - Listen on the WAN port. (tcpdump .....)
+   - Power up your router. When the 'SYS' light starts to blink, press and hold the //QSS// button on the right side of the front panel until the blinking of 'SYS' LED gets faster. If that won't work instead of holding the button press it and keep pressing it until the blinking gets faster. Alternatively you may try both methods on the //RESET// button on the back panel between USB and power plug.
+   - After entering the failsafe mode (sys LED flashing very fast) , swap your Ethernet connection from WAN port to LAN port 1 and the telnet 192.168.1.1 to repair your device as explained [[doc:howto:generic.failsafe#in.failsafe.mode|here]].
 ==== Recovery via serial console ====
@@ Line 277: / Line 360: @@
 | **RAM:**             | 32 MiB   |
 | **Wireless:**        | Atheros AR9103 2.4ghz 802.11bgn |
+| **Wireless Power:**        | Maximal power output is 27 dBm (500 mW) |
+| **802.11n:**        | 3 x 3 : 2 |
 | **Ethernet:**        | [[http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PNid=18&PFid=15&Level=5&Conn=4&ProdID=197|RealTek RTL8366RB 5-port Gigabit switch  w/ vlan support]], [[doc:techref:swconfig]] |
 | **Internet:**        | n/a  |
 | **USB:**             | Yes 1 x 2.0 (OHCI platform; device name ''1-1'')    |
+| **Power:**        | 12V DC 1.5A |
 | **[[doc:hardware:port.serial|Serial]]:**          | [[#Serial|Yes]] |
 | **[[doc:hardware:port.jtag|JTAG]]:**            | [[#JTAG|Yes]]  |
@@ Line 287: / Line 373: @@
 ==== Performance ====
-See -> [[doc:hardware:performance]] for results and [[doc:howto:performance]] for help for measuring
+  * [[doc:hardware:performance|Filesystems performance]] results and [[doc:howto:performance]] howto for help on measuring.
+  * [[inbox:benchmark.usb|USB Benchmarks]] results.
+This router gets around 180 Megabits/s WAN to LAN throughput, tested using nuttcp.
 ==== Power ====
@@ Line 293: / Line 382: @@
 === Power Consumption ===
-With a cheap Wattmeter i measured 6,9W idle and 9W under load.
+With a cheap Wattmeter i measured 6.9W idle and 9W under load.
 === PSU (power supply) ===
@@ Line 313: / Line 402: @@
 I successfully used the ATX PSU (from my computer) to power the router.
 All I did was buying a plug with above specifications and soldered a Molex-plug to the other end.
+=== Powering with different Voltages ===
+:!: ** WARNING: For sure you will lose your warranty if you run the router with to high voltage and I don't guarantee it will works for you. Your router might break, so just run it with to high voltage if you know what you are doing and you don't care if the router breaks. **
+Because I wanted to run the router directly from solar and the 12V battery can have between 10.4V and 14.8V I tested the router with different voltages and it runs fine with voltages between 10V and 15V. Could not see any failures or loss in performance.
 === Power consumption on DC-Side ===
-I have measured simultanously Voltage and Current on the DC-Side of the Router with 2 analogue Multimeters.
+I have measured simultaneously Voltage and Current on the DC-Side of the Router with 2 analogue Multimeters.
 It looks like my AC-DC Adapter is stabilized and delivers exactly 12 Volts.
@@ Line 378: / Line 472: @@
 {{:inbox:wr1043ndserial.jpg|}}
+If you use the serial connection more often or want to have a permanent modification you can build a stereo audio jack at the back of the router and use the FTDI serial cable TTL-232R-3V3-AJ. As jumper wire you can recycle an old floppy drive power cable.
+{{:media:wr1043ndserjack.jpg|}}
+=== Receive (RX) Disabled ===
+Some revisions require a jumper between the RX serial pin and the resistor R362 to enable serial writes. See this post for details:
+[[https://forum.openwrt.org/viewtopic.php?pid=176448#p176448]]
+If you find that the serial console will not accept write commands, check with a multimeter that you have continuity between RX and R362.
+If you don't have continuity you will need to jumper them, here is my working example:
+{{:media:tl-wr1043nd.rxjumper.png|}}
+I went to the right hand side of the resistor for ease of soldiering, but there may be better solutions.
+I also noticed that the small hole just below R362 has continuity to the RX pin so that may provide a cleaner solution with a much smaller jumper.
 ==== JTAG ====
@@ Line 395: / Line 509: @@
 Backup:
-Backup wholeflash:
+Backup whole flash:
 <code>
@@ Line 418: / Line 532: @@
 At the moment it is <b>NOT</b> possible to <b>UNBRICK</b> the router by <b>JTAG</b> (no write access to flashrom).</p>
 </HTML>
-so be very carefull not to overwrite the u-boot.
+so be very careful not to overwrite the u-boot.
@@ Line 488: / Line 602: @@
 **NOTE:** If you accidentally bricked your router by overwriting the bootloader, try the following:
-  - Desolder the Spansion SPI-Flash ([[http://www.spansion.com/Support/Datasheets/S25FL064P_00_03_e.pdf|here]] is the datasheet) from the board. I used tin foil to "mask" out everything else which I did not want to desolder and used a heat gun. It worked quite nice.
+  - Desolder the Spansion SPI-Flash ([[http://www.spansion.com/Support/Datasheets/S25FL064P_00.pdf|here]] is the datasheet) from the board. I used tin foil to "mask" out everything else which I did not want to desolder and used a heat gun. It worked quite nice.
-  - Find a way to connect the SPI flash to something with SPI interface.... I used a AVR microcontroller. {{:toh:tp-link:spi_flash1.pdf|Here}} you can download a pdf containing the layout for the adapter board I made to solder the Spansion SPI flash chip on, in order to connect it to the AVR. Attention, the PDF is mirrored and it is intended to manufacuring boards with the [[http://thomaspfeifer.net/direct_toner_pcb.htm | direct toner method]].
+  - Find a way to connect the SPI flash to something with SPI interface.... I used a AVR microcontroller. {{:toh:tp-link:spi_flash1.pdf|Here}} you can download a pdf containing the layout for the adapter board I made to solder the Spansion SPI flash chip on, in order to connect it to the AVR. Attention, the PDF is mirrored and it is intended to manufacturing boards with the [[http://thomaspfeifer.net/direct_toner_pcb.htm | direct toner method]].
   - Write the bootloader into the flash. I got my bootloader out of another wr1043nd.
   - Solder the chip back into the router.
@@ Line 593: / Line 707: @@
 {{:inbox:tplink-wr1043nd-rammod-small.jpg|}}
-**To make router see all new 64 mb of RAM do via putty SSH client**
-<code>
-.nvram set sdram_init=0x0013
-.nvram commit
-.reboot
-</code>
 <code>
@@ Line 610: / Line 717: @@
 ==== I²C GPIO Mod ====
-An I²C-bus can easily be added using the GPIO-lines of the AR913x-SoC. So far, the only usable ones which have been confirmed to work are GPIO 5 (the QSS-LED, easily solderable at D10,left pin with '+') as SDA and GPIO 20 (labeled on the pcb, next to the RAM chip) as SCL. There are only two pull-up resistors of 4,7k-10k needed, which have to be soldered between the apropriate GPIO line and Vcc (found at the spot labeled TP3V3, about 2 cm above the WiFi-shielding). The common ground can be obtained from the TP_GND spot (between P1 and the flash chip). Remember this bus runs at 3.3V level, when connecting I²C-devices.
+An I²C-bus can easily be added using the GPIO-lines of the AR913x-SoC. So far, the only usable ones which have been confirmed to work are GPIO 5 (the QSS-LED, easily solderable at D10,left pin with '+') as SDA and GPIO 20 (labeled on the pcb, next to the RAM chip) as SCL. There are only two pull-up resistors of 4,7k-10k needed, which have to be soldered between the apropriate GPIO line and Vcc (found at the spot labeled TP3V3, about 2 cm above the WiFi-shielding). The common ground can be obtained from the TP_GND spot (between P1 and the flash chip). Remember this bus runs at 3.3V level, when connecting I²C-devices. \\
+To improve signal integrity (in this case namely a solid logic low level on GPIO5), you can replace R373 with a piece of wire and remove the LED D31. R373 seems to be the current limit resistor for the LED D31.
 {{ http://wiki.openwrt.org/_media/toh/tp-link/i2c-gpio.png }}
 Unfortunately the precompiled packages don't seem to work properly, so building from sources is most likely necessary. Therefore, make sure the apropriate part of your OpenWRT-config file looks like that:
@@ Line 645: / Line 753: @@
 but should be okay for static wan settings on other ISPs:
 http://www.ip6.ro/firmware/wr1043nd/
+===== Other models with the same hardware =====
+  * [[http://www.canyon-tech.com/archive/connectivity/wireless/CNP-WF514N3A|Canyon CNP-WF514N3A]] description and internal photos [[http://www.dd-wrt.com/phpBB2/viewtopic.php?t=148618|here]]
+  * [[http://www.proware.com.cn/product-detail.asp?productId=1010195&t=4#info|Proware PW-RN611D/MH5-WR1043ND]] probably another clone...
 ===== Tags =====
 {{tag>GigabitEthernet 5Port 1PHY USB JTAG 802.11bgn ath9k 3Ant DetachableAntenna 32RAM 8Flash MIPS MIPS32 24Kc JumboFrames vlan}}

toh/tp-link/tl-wr1043nd.1351848784.txt.bz2 · Last modified: 2012/11/02 10:33 by written_direcon

OpenWrt

Wiki Search

Actions

Donate

Translations

Differences