User Tools

Site Tools


toh:tp-link:tl-wr1043nd

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
toh:tp-link:tl-wr1043nd [2014/03/01 08:10]
mexus
toh:tp-link:tl-wr1043nd [2015/06/28 20:09] (current)
lucian_radu [Supported Versions]
Line 1: Line 1:
 ====== TP-Link TL-WR1043ND ====== ====== TP-Link TL-WR1043ND ======
-One of the first cheap devices with an gigabit Ethernet switch. Manufacture advertised features: 3 removable omni antennas (RP-SMA connectors) and 24 dBm (251 mW, v1.x, v2.x) maximal TX power output. Note: maximal TX power and available channels are limited in some countries!+One of the first cheap devices with an gigabit Ethernet switch. Manufacture advertised features: 3 removable omni antennas ([[wp>​RP-SMA|RP-SMA connectors]]) and 24 dBm (251 mW, v1.x, v2.x) maximal TX power output. Note: maximal TX power and available channels are limited in some countries!
  
-**NOTE**: My personal experience with the V1 hardware version bought ​in Nov 2013  has been nothing but troubleThis device is unreliable ​ with daily unexplained slow downs and reboots, after considerable attempts at resolving these issues I can only guess it is a hardware issueAs a band-aid I have a  daily CRON reboot job but still a manual reboot is necessary sometimes(Daniel Sokolowski) +**WARNING:** These routers seem to have unstable wifi in 12.09They'​re hit by bugs [[https://​dev.openwrt.org/​ticket/​9654|9654]][[https://​dev.openwrt.org/​ticket/​12372|12372]] ​and [[https://​dev.openwrt.org/​ticket/​13966|13966]]. Fixed in 14.07
- +
- +
-My V2 works flawlessNo erratic behaviorstable ​and fast connection, nice coverageI have Extroot with 4GB flash drive(Dimitar Tanchev)+
  
 ===== Supported Versions ===== ===== Supported Versions =====
Line 21: Line 18:
 | v1.7 | - | | | Backfire 10.03.1 | | | v1.7 | - | | | Backfire 10.03.1 | |
 | v1.8 | - | | 2010-08-04 <​sup><​sub>​(and probably other versions prior to 2012-02-02)</​sub></​sup>​ | Backfire 10.03.1 | | | v1.8 | - | | 2010-08-04 <​sup><​sub>​(and probably other versions prior to 2012-02-02)</​sub></​sup>​ | Backfire 10.03.1 | |
 +| ::: | - | | 2011-04-28 | Barrier Breaker 14.07 | (no issues) |
 | ::: | - | | 2012-02-02, 2012-03-31 <​sup><​sub>​(and probably later versions)</​sub></​sup>​ | Attitude Adjustment 12.09-rc1 | Tested OK with Backfire 10.03.1 but **require** [[toh:​tp-link:​tl-wr1043nd#​bootloader.downgrade|bootloader downgrade]]. [[https://​forum.openwrt.org/​viewtopic.php?​id=42539|Suspect of hardware bug that bring down WiFi after a while.]] | | ::: | - | | 2012-02-02, 2012-03-31 <​sup><​sub>​(and probably later versions)</​sub></​sup>​ | Attitude Adjustment 12.09-rc1 | Tested OK with Backfire 10.03.1 but **require** [[toh:​tp-link:​tl-wr1043nd#​bootloader.downgrade|bootloader downgrade]]. [[https://​forum.openwrt.org/​viewtopic.php?​id=42539|Suspect of hardware bug that bring down WiFi after a while.]] |
-| v1.9 | - | | 2012-03-31 | | Tested OK with Backfire 10.03.1 but **require** [[toh:​tp-link:​tl-wr1043nd#​bootloader.downgrade|bootloader downgrade]]. |+| v1.9 | - | | 2012-03-31 | | Tested OK with Backfire 10.03.1 but **require** [[toh:​tp-link:​tl-wr1043nd#​bootloader.downgrade|bootloader downgrade]]. ​Tested OK with Barrier Breaker (14.07) with U-Boot 1.1.4 (Mar 31 2012 - 10:40:21)|
 | v1.10 | - | | | Attitude Adjustment 12.09-rc1 | Similar v1.1 board. **Backfire 10.03.1 = BRICK**:​!:​.| | v1.10 | - | | | Attitude Adjustment 12.09-rc1 | Similar v1.1 board. **Backfire 10.03.1 = BRICK**:​!:​.|
 | v1.11 | - | | | Attitude Adjustment 12.09 | **Backfire 10.03.1 = BRICK**:!: | | v1.11 | - | | | Attitude Adjustment 12.09 | **Backfire 10.03.1 = BRICK**:!: |
-| v2.1  | - | | 2013-06-18 | Barrier Breaker ​(trunk R38958) ​ ​| ​ |+| v2.1  | - | | 2013-06-18 | Barrier Breaker ​14.07  ​|  ​
 +| v3.0  | - | | - | - | Maybe same HW as v2.x but OEM IPv6 and guest network support.[[https://​fccid.io/​document.php?​id=2644079|FCC ID: TE7WR1043NDV3]] ​|
  
 +Wan to Lan Throughput V1.x 122.7 Mbps [[http://​www.smallnetbuilder.com/​lanwan/​router-charts/​bar/​74-wan-to-lan|http://​www.smallnetbuilder.com/​lanwan/​router-charts/​bar/​74-wan-to-lan]]
 +
 +^ HW v1.x ^ HW v2.x ^ HW v3.x ^
 +|  {{:​media:​tl-wr1043ndv1_profile.jpg?​200|}} ​ |  {{:​media:​tl-wr1043ndv2_profile.jpg?​200|}} ​ | {{:​media:​tl-wr1043ndv2_profile.jpg?​200|}} ​ |
  
-^ HW V1.x ^ HW V2.x ^ 
-|  {{:​media:​tl-wr1043ndv1_profile.jpg?​200|}} ​ |  {{:​media:​tl-wr1043ndv2_profile.jpg?​200|}} ​ | 
  
  
  
 ===== Hardware Highlights ===== ===== Hardware Highlights =====
-^ HW Version ^ CPU ^ Ram ^ Flash ^ Network ^ Gigabit ​^ USB ^ Serial ^ JTag ^ +^ HW Version ^ CPU ^ Ram ^ Flash ^ Network ^ Wireless ​^USB ^ Serial ^ JTag ^ Wiki ^ FCC 
-| 1.x | Atheros AR9132@400MHz ​ | 32MB | 8MB | 4x1 Yes | Yes | Yes | Yes | +| 1.x | Atheros AR9132@400MHz ​ | 32MB | 8MB | 1x WAN 4x LAN (Gbit) ​AR9103 [bgn 3x3:​2] ​| Yes | Yes | Yes | [[https://​wikidevi.com/​wiki/​TP-LINK_TL-WR1043ND_v1.x|here]] | [[https://​fcc.io/​TE7/​WR1043NX|here]] ​
-| 2.x | Qualcomm Atheros QCA9558@720MHz | 64MB | 8MB | 4x1 | Yes | Yes | Yes | No |+| 2.x | Qualcomm Atheros QCA9558@720MHz | 64MB | 8MB | 1x WAN 4x LAN (Gbit) | QCA9558 [bgn 3x3:​3] ​| Yes | Yes | No | [[https://​wikidevi.com/​wiki/​TP-LINK_TL-WR1043ND_v2.x|here]] | [[https://​fcc.io/​TE7/​WR1043NDV2|here]] | 
 +| 3.x | Qualcomm Atheros QCA9558@720MHz | 64MB | 8MB | 1x WAN 4x LAN (Gbit) | QCA9558 [bgn 3x3:​3] ​| Yes | Yes | No | [[https://​wikidevi.com/​wiki/​TP-LINK_TL-WR1043ND_v3.x|here]] | - |
  
 See paragraphs [[toh/​tp-link/​tl-wr1043nd#​Hardware]] or [[toh/​tp-link/​tl-wr1043nd#​Tags]] for more details. See paragraphs [[toh/​tp-link/​tl-wr1043nd#​Hardware]] or [[toh/​tp-link/​tl-wr1043nd#​Tags]] for more details.
Line 44: Line 46:
  
 <color red>//​Due to numerous reports that WAN bug does not occur with stock uboot, doing uboot downgrade may be possibly obsolete.//</​color>​ <color red>//​Due to numerous reports that WAN bug does not occur with stock uboot, doing uboot downgrade may be possibly obsolete.//</​color>​
 +
 +
 +:!: **WAN port disabled after installation of Barrier Breaker 14.07 (apparently model v1.8 specific and maybe not related to the WAN port bug):** After installation of Barrier Breaker (and maybe other releases), the WAN port does not work. Bootloader downgrade does not help. 
 +**Possible solution (also check before downgrading the bootloader!):​** Check whether the MAC addresses of the LAN and the WAN interface are set to be the same. WAN MAC should be LAN MAC+1 (e.g. LAN 01:​02:​03:​04:​b6 -> WAN 01:​02:​03:​04:​b7). If addresses are the same, you can overwrite the WAN MAC in LuCI/the web interface by going to Network -> Interfaces -> "​Edit"​ button for WAN -> "​Advanced Settings"​ tab -> enter the new MAC address in the field "​Override MAC address"​. Thanks to nischris and the [[https://​forum.openwrt.org/​viewtopic.php?​id=46354|forum]] and the [[https://​dev.openwrt.org/​ticket/​11898|bug tracker]]. ​ Duplicated MAC addresses does not need to be a problem on v1.8 hardware (tested on router with U-Boot 1.1.4 Apr 28 2011 - 15:55:09).
 +
  
 :!: **WAN port disable bug (newer models v1.8+ with U-boot 2012-02-02 and later).** 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 an 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). :!: **WAN port disable bug (newer models v1.8+ with U-boot 2012-02-02 and later).** 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 an 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).
Line 87: Line 94:
  
 ==== USB 3G Modems ==== ==== USB 3G Modems ====
-:!**USB 3G modem issue (insufficient power).** TL-WR1043ND v1.x does NOT deliver enough power for most USB 3G modems, which can lead to erratic behavior such as droped/failed connections. If a 3G USB modem is to be used, consider other routers with a USB port that delivers enough ​Amperes. ​(e.g. [[http://​wiki.openwrt.org/​toh/​buffalo/​wzr-hp-ag300h|Buffalo WZR-HP-AG300H]])+| {{:meta:icons:​tango:​48px-emblem-important.svg.png?​nolink}} | The TL-WR1043ND v1.x does **not** ​deliver enough power for most USB 3G modems, which can lead to erratic behavior such as dropped/failed connections. If a 3G USB modem is to be used, consider other routers with a USB port that delivers enough ​amperes ​(e.g. the [[http://​wiki.openwrt.org/​toh/​buffalo/​wzr-hp-ag300h|Buffalo WZR-HP-AG300H]]). |
  
-== Compatible ​USB 3G modems == +== USB 3G modems ​confirmed working with TL-WR1043ND v1: == 
-  * e.g. Huawei ​E1550+  * Huawei ​E303   
 +  * Huawei E303c 
 +  * Huawei E3131   
 +  * Huawei E3272 
 +  * Huawei E3531 
 +  * ZTE MF823L 
 +  * ZTE MF190 
 +  * ZTE MF193 
 +  * ZTE MF626
  
- +== USB 3G modems confirmed working with TL-WR1043ND v2: ==
-== Note for TL-WR1043ND v2: == +
-I got a stable 3g connection on my router! I don't see any erratic behavior! +
-I tested the router with the following 3g modems:+
   * TCT Mobile One Touch X500D   * TCT Mobile One Touch X500D
   * TCT Mobile X220L   * TCT Mobile X220L
   * ZTE MF632   * ZTE MF632
 +  * Vodafone K3765 (Huawei)
 +  * Huawei E160E
  
 ===== Installation ===== ===== Installation =====
-  - [[doc:​howto:​obtain.firmware]] and [[about/​latest|Latest OpenWrt Release]] - required image file is "​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin"​ for v1.x routers, "​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin"​ for v2.x routers. Files can be found in the "​ar71xx"​ directory. You can use the quick links from the table below.+  - [[doc:​howto:​obtain.firmware]] and [[about/​latest|Latest OpenWrt Release]] - required image file is "[[http://​downloads.openwrt.org/​latest/​ar71xx/​generic/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin|openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin]]" for v1.x routers, "​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin"​ for v2.x routers. Files can be found in the "​ar71xx"​ directory. You can use the quick links from the table below.
   - [[doc:​howto:​generic.flashing]] Now write this firmware-file onto the flash-chip of your device   - [[doc:​howto:​generic.flashing]] Now write this firmware-file onto the flash-chip of your device
  
-:!: **''​NOTE:''​** If case you have a revision > v1.10, you need to flash an elder OEM firmware release first, and only then flash OpenWrt; tested and works [[http://​forum.lowyat.net/​topic/​2481658/​all|credits go to sayboon]] for his tutorial+:!: **''​NOTE:''​** If case you have a revision > v1.10 (but not v2.x), you need to flash an elder OEM firmware release first, and only then flash OpenWrt; tested and works [[http://​forum.lowyat.net/​topic/​2481658/​all|credits go to sayboon]] for his tutorial
  
  
Line 112: Line 126:
  
   * Download **Factory** image if you want to install OpenWrt on router with OEM firmware.   * Download **Factory** image if you want to install OpenWrt on router with OEM firmware.
-  * Download **Update** image if you already have OpenWrt installed. +  * Download **Upgrade** image if you already have OpenWrt installed.
  
 ==== Downloads for TL-WR1043ND v1.x  ==== ==== Downloads for TL-WR1043ND v1.x  ====
  
 ^ Branch ^ Type ^ Download link ^ ^ Branch ^ Type ^ Download link ^
-|  **Stable** (Attitude Adjustment)  |  **Factory** ​ |  http://​downloads.openwrt.org/​attitude_adjustment/12.09/​ar71xx/​generic/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin ​ | +|  **Stable** (Barrier Breaker)  |  **Factory** ​ |  http://​downloads.openwrt.org/​barrier_breaker/14.07/​ar71xx/​generic/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin ​ | 
-|  :::  |  **Upgrade** ​ |  http://​downloads.openwrt.org/​attitude_adjustment/12.09/​ar71xx/​generic/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin ​ |+|  :::  |  **Upgrade** ​ |  http://​downloads.openwrt.org/​barrier_breaker/14.07/​ar71xx/​generic/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin ​ |
 |  **Trunk** (Barrier Breaker) ​ |  **Factory** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin ​ | |  **Trunk** (Barrier Breaker) ​ |  **Factory** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin ​ |
 |  :::  |  **Upgrade** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin ​ | |  :::  |  **Upgrade** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin ​ |
Line 126: Line 139:
  
 ^ Branch ^ Type ^ Download link ^ ^ Branch ^ Type ^ Download link ^
 +|  **Stable** (Barrier Breaker) ​ |  **Factory** ​ |  http://​downloads.openwrt.org/​barrier_breaker/​14.07/​ar71xx/​generic/​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin ​ |
 +|  :::  |  **Upgrade** ​ |  http://​downloads.openwrt.org/​barrier_breaker/​14.07/​ar71xx/​generic/​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin ​ |
 |  **Trunk** (Barrier Breaker) ​ |  **Factory** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin ​ | |  **Trunk** (Barrier Breaker) ​ |  **Factory** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin ​ |
 |  :::  |  **Upgrade** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin ​ | |  :::  |  **Upgrade** ​ |  http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin ​ |
 +
 +==== Downloads for TL-WR1043ND v3.x  ====
 +
 +^ Branch ^ Type ^ Download link ^
 +|  **Stable** (Barrier Breaker) ​ |  **Factory** ​ |  -  |
 +|  :::  |  **Upgrade** ​ |  -  |
 +|  **Trunk** (Barrier Breaker) ​ |  **Factory** ​ |  -  |
 +|  :::  |  **Upgrade** ​ |  -  |
  
 ==== Flash Layout ==== ==== Flash Layout ====
-Please read the article [[doc:​techref:​Flash Layout]] for a better understanding. It contains a couple of explanations. Then let's have a quick view at flash layout of this particular device:+Please read the article [[doc:​techref:​Flash.Layout]] for a better understanding. It contains a couple of explanations. Then let's have a quick view at flash layout of this particular device:
  
 ^   ​TP-Link WR1043ND ​ Flash Layout stock firmware ​          ​^^^^^^ ^   ​TP-Link WR1043ND ​ Flash Layout stock firmware ​          ​^^^^^^
Line 149: Line 172:
 ART = Atheros Radio Test - it contains mac addresses and calibration data for the wifi (EEPROM). If it is missing or corrupt, ath9k won't come up anymore. ART = Atheros Radio Test - it contains mac addresses and calibration data for the wifi (EEPROM). If it is missing or corrupt, ath9k won't come up anymore.
  
 +==== Firmware flashing ====
  
- +=== Automated ​flashing ​with a script ​===
-==== OEM mass flashing ​====+
  
 Flashing hundreds of devices using the web interface can be a real pain. You can use this shell script to automate it: Flashing hundreds of devices using the web interface can be a real pain. You can use this shell script to automate it:
Line 183: Line 206:
 </​code>​ </​code>​
  
-==== OEM installation ​using the TFTP and RS232 method ====+=== Flashing ​using the serial console (recovery) ​===
  
-If you want to upgrade ​using TFTP you follow these steps (as an alternative to the above install process).+If your device doesn'​t even boot (e.g. due to a bad flash), then you will need to attach to its serial console. You will have **two options to transport the firmware** into the device: 1) using tftp, or 2) using the serial connection itself for file transfer ​(using the Kermit protocol).
  
-Quick howto recover from bad flash. ([[.:tl-wr1043nd:​flashlog|full log]])+Requirements: 
 +  * terminal program set to **115200 8N1**, no flow control 
 +    * ''​minicom ​--baudrate 115200 --device /​dev/​ttyUSB0 --8bit''​ (I couldn'​t type the ''​tpl''​ command using this) 
 +    * ''​screen /​dev/​ttyUSB0 115200,​cs8,​-ixon''​ (this worked for me) 
 +  * the new //​firmware.bin//​ file.
  
-Requirements:​  +To **enter the boot prompt**: right after you see ''​Autobooting in 1 seconds'' ​in the console type ''​tpl''​. See this example for a ([[.:​tl-wr1043nd:​flashlog|full console log]]when using tftp.
-  ​terminal program (e.g. minicom) set to **115200 8N1**, no flow control +
-  * file named //​code.bin//​ containing openwrt firmware. +
-  * tftpd server with an address 192.168.0.5 (configurable with ''​setenv'' ​command, ​''​printenv'' ​first if unsure)+
  
-The simplest tftpd server to use is dnsmasq. Install and run with ''​dnsmasq --enable-tftp --tftp-root=/​code.bindirectory''​+== 1) Commands when using tftp (lan) for firmware transfer ==
  
-Commands:+The tftp server must be listening on 192.168.0.5:69 (configurable with ''​setenv''​ command; use ''​printenv''​ if not sure), and the router must be connected through one of the lan ports. The simplest tftp server to use is dnsmasq: ''<​nowiki>​dnsmasq --enable-tftp --tftp-root=/​directory-containing-firmware.bin</​nowiki>''​.
  
-After you see ''​Autobooting in 1 seconds''​ type ''​tpl''​ and hit enter to get into command prompt.+**For v1.x hardware:**
  
 <​code>​ <​code>​
-tftpboot 0x81000000 ​code.bin+tftpboot 0x81000000 ​firmware.bin
 erase 0xbf020000 +7c0000 # 7c0000: size of the firmware (be aware that you may have a different size thus bricking your router) erase 0xbf020000 +7c0000 # 7c0000: size of the firmware (be aware that you may have a different size thus bricking your router)
 cp.b 0x81000000 0xbf020000 0x7c0000 cp.b 0x81000000 0xbf020000 0x7c0000
Line 207: Line 231:
 </​code>​ </​code>​
  
-For version 2.1 you must use the following+**For v2.1 hardware:​** 
 <​code>​ <​code>​
-tftp 0x80060000 ​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin+tftp 0x80060000 ​firmware.bin
 erase 0x9f020000 +0x7c0000 erase 0x9f020000 +0x7c0000
 cp.b 0x80060000 0x9f020000 0x7c0000 cp.b 0x80060000 0x9f020000 0x7c0000
Line 215: Line 240:
 </​code>​ </​code>​
  
-==== OEM installation ​using the Kermit ​and RS232 method ​==== +== 2) Commands when using Kermit ​(serial console) for firmware transfer ​==
- +
-If you do not want to bother with running a tftpd server on your computer, especially considering the security concerns, you can also use a Kermit client to transfer the new image. It may take forever and a half (15-20min) to copy, but it's easier and more secure than running a tftpd server. These instructions assume you're using a Linux system, but they will give you all you need to do the same on a Windows box.+
  
-Requirements:​  +The tftp protocol is insecure and sometimes it doesn'​t work even if the console log suggests otherwiseIn such cases you can also use a Kermit client to transfer the new image on the serial connectionIt may take forever and a half (15-20min) to transfer the image, but it's easier and more secure than running a tftp server. These instructions assume you're using //**ckermit**// on a Linux system, but they will give you all you need to do the same on a Windows box.
-  * terminal program (e.gminicomset to **115200 8N1**, no flow control +
-  * file named //code.bin// containing openwrt firmware. +
-  * Kermit client (these instructions will involve using C-Kermit under Linux)+
  
-In your terminal program ​you type:+Enter the boot prompt on the serial console (see above), and in your terminal program type:
  
 <​code>​ <​code>​
Line 231: Line 251:
 </​code>​ </​code>​
  
 +Then start //ckermit// (without any arguments) and run the following commands in it (or configure your Kermit client to these parameters):​
  
-Hint: After you see Autobooting in 1 seconds type tpl and hit enter to get into command promt. 
- 
- 
-Fire up C-Kermit and run the following commands (or configure your Kermit client to these parameters):​ 
 <​code>​ <​code>​
 set line /​dev/​ttyUSB0 # Just make sure you got the right USB interface set line /​dev/​ttyUSB0 # Just make sure you got the right USB interface
Line 248: Line 265:
 set send pack 1000 set send pack 1000
 set window 5 set window 5
-send code.bin # Make sure you include a proper path to the file. That's why I just kept it in /home/$user+send firmware.bin # Make sure you include a proper path to the file. That's why I just kept it in /home/$user
 </​code>​ </​code>​
  
-After the 15-20min file transfer, the new firmware should be on your router and you can continue in terminal:+After the 15-20min file transfer, the new firmware should be on your router and you can continue in the terminal: 
 <​code>​ <​code>​
 cp.b 0x81000000 0xbf020000 0x7c0000 cp.b 0x81000000 0xbf020000 0x7c0000
 bootm 0xbf020000 bootm 0xbf020000
 </​code>​ </​code>​
- 
  
 ==== Upgrading OpenWrt ==== ==== Upgrading OpenWrt ====
 -> [[doc:​howto:​generic.sysupgrade]] -> [[doc:​howto:​generic.sysupgrade]]
- 
-:!: ** WARNING: Recent versions of trunk are reported to brick the 1043ND and other devices: ** 
- 
-https://​forum.openwrt.org/​viewtopic.php?​pid=176604 
- 
-Unless you know what you're doing, use the latest stable version. 
  
 ==== Back to original firmware ==== ==== Back to original firmware ====
Line 273: Line 284:
  
 With the WR1043ND router, there is a catch: the stock firmware is obtained from the OEM: http://​www.tplink.com/​en/​support/​download/?​model=TL-WR1043ND With the WR1043ND router, there is a catch: the stock firmware is obtained from the OEM: http://​www.tplink.com/​en/​support/​download/?​model=TL-WR1043ND
-OEM TP-Link firmware for the TL-WR1043nd**//​V1//​** with the boot part removed to revert to the original OEM firmware: http://​goo.gl/​cMdOdz 
- 
  
   * in case the file name of this firmware file does not contain the word **//"​boot"//​** in it, you can simply revert back to original firmware   * in case the file name of this firmware file does not contain the word **//"​boot"//​** in it, you can simply revert back to original firmware
   * in case the file name of this firmware file does contain the word **//"​boot"//​** in it, you need to cut off parts of the image file //before// flashing it:   * in case the file name of this firmware file does contain the word **//"​boot"//​** in it, you need to cut off parts of the image file //before// flashing it:
 +
 +
 +The following method applies both for the V1 and V2 since the bootloader is the same size.
 +
  
 An example of an image file with the word "​boot"​ in it is ''​wr1043nv1_en_3_9_17_up_boot(091118).bin''​. An example of an image file with the word "​boot"​ in it is ''​wr1043nv1_en_3_9_17_up_boot(091118).bin''​.
Line 286: Line 299:
 </​code>​ </​code>​
  
-You should transfer the firmeware image to the /tmp folder and revert back to original firmware:+You should transfer the firmeware image to the /tmp folder and revert back to original firmware ​(if availlable you can flash the firmware via the webinterface as well):
  
 +Via the safer method using sysupgrade:
 <​code>​ <​code>​
-mtd -r write tplink.bin ​linux+sysupgrade /tmp/tplink.bin
 </​code>​ </​code>​
  
-Or depending on your mtd you may have to +Or alternatively use the mtd method:
 <​code>​ <​code>​
 mtd -r write tplink.bin firmware mtd -r write tplink.bin firmware
 </​code>​ </​code>​
  
-This has been confirmed by [[https://​forum.openwrt.org/​viewtopic.php?​pid=110583#​p110583|supertom64]]+This has been confirmed by [[https://​forum.openwrt.org/​viewtopic.php?​pid=110583#​p110583|supertom64]] (for the V1) and by [[https://​forum.openwrt.org/​viewtopic.php?​pid=232448#​p232448|akirkby]] (for the V2, flashing using the webinterface) 
 + 
 +OEM TP-Link firmware for the TL-WR1043nd with the **//boot part removed//** to revert to the original OEM firmware: 
 +  * TL-WR1043nd **//V1//** [[http://​q.gs/​6gAN3|TL-WR1043ND-V1-stripped.zip]] 
 +  * TL-WR1043nd **//V2//** [[http://​q.gs/​6gAN7|TL-WR1043ND-V2-stripped.zip]]
  
  
Line 311: Line 328:
 ==== Interfaces ==== ==== Interfaces ====
  
-The default ​network ​configuration is:+The OpenWrt ​default configuration ​of the [[doc/​networking/​network.interfaces|network interfaces]] ​is as follows:
 ^ Interface Name ^ Description ^ Default configuration ^ ^ Interface Name ^ Description ^ Default configuration ^
-| br-lan | LAN & WiFi | 192.168.1.1/​24 |  +''​br-lan'' ​| LAN & WiFi | 192.168.1.1/​24 | 
-| eth0 | LAN ports (1 to 4) + WAN | None |  +''​eth0'' ​  | LAN ports (1 to 4) + WAN | //​none// ​
-| wlan0 | WiFi | Disabled ​ +''​wlan0''  ​| WiFi | //​disabled// ​|
- +
  
 ==== Switch Ports (for VLANs) ==== ==== Switch Ports (for VLANs) ====
Line 329: Line 344:
 | LAN 3 | 3 | 2 | | LAN 3 | 3 | 2 |
 | LAN 4 | 4 | 1 | | LAN 4 | 4 | 1 |
-| Gigabit Media Independent Interface | 5 (marked as CPU) | 0 (marked as CPU) Switch0 CPU Port| +[[wp>Gigabit Media Independent Interface|GMII]] ​| 5 (marked as CPU) | 0 (marked as CPU) Switch0 CPU Port| 
-Gigabit Media Independent Interface ​| - | 6 Switch0 CPU Port |+::: | - | 6 Switch0 CPU Port |
  
-FIXME There is a port 6 on v2.x I haven'​t found it's purpose yet! 
- 
-Theory (may be wrong):\\ 
 The v2.x get's the lan and wan interface not via eth0.1/​eth0.2 but via eth0 (wan) and eth1 (lan). The v2.x get's the lan and wan interface not via eth0.1/​eth0.2 but via eth0 (wan) and eth1 (lan).
 The eth0 in the same vlan as port 5 on the switch. The eth0 in the same vlan as port 5 on the switch.
-Because of that, I think that port 6 on the v2.x routers ​may be an aditional ​CPU port - used for wan traffic only.+Because of that port 6 on the v2.x routers ​is an additional ​CPU port - used for wan traffic only.
  
 Wan has VLAN 2, that shouldn'​t be touch,as you lose the WAN port. Start you VLANs from 3 , attaching them to the eth1.x sub-interfaces. Wan has VLAN 2, that shouldn'​t be touch,as you lose the WAN port. Start you VLANs from 3 , attaching them to the eth1.x sub-interfaces.
  
 +See Schematics:
  
 +{{:​media:​wr1043ndv2-schematics.png?​600|}}
  
-http://​www.realtek.com.tw/​products/​productsView.aspx?​Langid=1&​PNid=18&​PFid=15&​Level=5&​Conn=4&​ProdID=197 
  
 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. 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.
Line 375: Line 388:
  
 </​code>​ </​code>​
 +
 +The port numbers are shown here:
 +
 +{{:​media:​img_20140513_175452.jpg}}
  
 ==== Use the WAN-Port as a LAN-Port ​ ==== ==== Use the WAN-Port as a LAN-Port ​ ====
 **remove** to following lines, to remove the wan specific configuration (vlan and interface) **remove** to following lines, to remove the wan specific configuration (vlan and interface)
  
 +**V1.x**
 /​etc/​config/​network /​etc/​config/​network
-<​code>​ +<​code>​config interface '​wan'​
-config interface '​wan'​+
  option ifname '​eth0.2'​  option ifname '​eth0.2'​
- option proto '​dhcp'​ + option proto '​dhcp'</​code>​
-</​code>​+
 and and
-<​code>​ +<​code>​config switch_vlan
-config switch_vlan+
  option device '​switch0'​  option device '​switch0'​
  option vlan '​2'​  option vlan '​2'​
- option ports '0 5t' + option ports '0 5t'</​code>​
-</​code>​+
  
-and **add** the port 0 to the exsisting ​Vlan +and **add** the port 0 to the existing ​Vlan 
-<​code>​ +<​code>​config switch_vlan
-config switch_vlan+
  option device '​switch0'​  option device '​switch0'​
  option vlan '​1'​  option vlan '​1'​
 # add port 0 to the line below # add port 0 to the line below
- option ports '0 1 2 3 4 5t' + option ports '0 1 2 3 4 5t'</​code>​
-</​code>​+
  
 +**V2.x**
 +/​etc/​config/​network
 +<​code>​config interface '​wan'​
 + option ifname '​eth0'​
 + option proto '​dhcp'</​code>​
 +and
 +<​code>​config switch_vlan
 + option device '​switch0'​
 + option vlan '​2'​
 + option ports '5 6'</​code>​
 +
 +and **add** the port 5 to the existing Vlan
 +<​code>​config switch_vlan
 + option device '​switch0'​
 + option vlan '​1'​
 +# add port 5 to the line below
 + option ports '0 1 2 3 4'</​code>​
  
 ==== Add VLAN and Second Wan on v.2.x  ==== ==== Add VLAN and Second Wan on v.2.x  ====
Line 411: Line 440:
  
 Adapt to your needs Adapt to your needs
 +<​HTML>​
 +<p style="​padding:​ 10px;​border:​1px solid grey;​height:​600px;​font:​12px/​14px Georgia, Garamond, Serif;​overflow:​Auto;​background-color:#​FFFFFF">​
 <​code>​ <​code>​
 config interface '​loopback'​ config interface '​loopback'​
Line 495: Line 526:
         option vid '​5'​         option vid '​5'​
 </​code>​ </​code>​
 +</p>
 +</​HTML>​
  
 ==== Failsafe mode ==== ==== Failsafe mode ====
Line 531: Line 564:
 ===== Hardware ===== ===== Hardware =====
 ==== Info ==== ==== Info ====
 +TP-Link naming scheme is, that numbers behind the comma, refer to changes in the firmware only, the hardware is identical.
 +
 ^ Type ^ HW ver. 1.x ^ HW ver. 2.x ^ ^ Type ^ HW ver. 1.x ^ HW ver. 2.x ^
-| **[[wp>​Instruction set]]:​** ​              ​| ​ [[wp>MIPS architecture|MIPS32]] ​ ||+| **[[wp>​Instruction set]]:​** ​              ​| ​ [[wp>MIPS_instruction_set#​MIPS32|MIPS32]] ​ ||
 | **Vendor:​** ​                              ​| ​ [[wp>​Qualcomm Atheros]] ​ || | **Vendor:​** ​                              ​| ​ [[wp>​Qualcomm Atheros]] ​ ||
 | **[[doc:​techref:​Bootloader]]:​** ​          ​| ​ [[doc:​techref:​bootloader:​uboot|U-Boot]] 1.1.4  || | **[[doc:​techref:​Bootloader]]:​** ​          ​| ​ [[doc:​techref:​bootloader:​uboot|U-Boot]] 1.1.4  ||
-| **[[doc:​hardware:​soc|System-On-Chip]]:​** ​ |  AR9132 rev 2 (MIPS 24Kc V7.4)  ​| ​ QCA9558 ​(MIPS 74Kc V5.0)  |+| **[[doc:​hardware:​soc|System-On-Chip]]:​** ​ |  AR9132 rev 2  |  QCA9558 ​ |
 | **[[doc:​hardware:​cpu|CPU]]/​Frq** ​         |  24Kc V7.4 400 MHz  |  74Kc V5.0 720 MHz  | | **[[doc:​hardware:​cpu|CPU]]/​Frq** ​         |  24Kc V7.4 400 MHz  |  74Kc V5.0 720 MHz  |
 | **Target name** ​                          ​| ​ [[http://​wiki.openwrt.org/​tag/​ar71xx?​do=showtag&​tag=ar71xx|ar71xx]] ​ || | **Target name** ​                          ​| ​ [[http://​wiki.openwrt.org/​tag/​ar71xx?​do=showtag&​tag=ar71xx|ar71xx]] ​ ||
-| **Initial flash image** ​                  ​| ​ ''​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin'' ​ |  ''​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin'' ​ | 
-| **Upgrade image** ​                        ​| ​ ''​openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin'' ​ |  ''​openwrt-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin'' ​ | 
 | **Flash-Chip:​** ​                          ​| ​ [[http://​www.spansion.com/​Support/​Datasheets/​S25FL064P_00.pdf|ST 25P64V6P]] ​ |  [[http://​www.nexflash.com/​hq/​enu/​ProductAndSales/​ProductLines/​FlashMemory/​SerialFlash/​W25Q64FV.htm|Winbond 25Q64FV]] ​ | | **Flash-Chip:​** ​                          ​| ​ [[http://​www.spansion.com/​Support/​Datasheets/​S25FL064P_00.pdf|ST 25P64V6P]] ​ |  [[http://​www.nexflash.com/​hq/​enu/​ProductAndSales/​ProductLines/​FlashMemory/​SerialFlash/​W25Q64FV.htm|Winbond 25Q64FV]] ​ |
 | **Flash size:​** ​                          ​| ​ 8192 KiB  || | **Flash size:​** ​                          ​| ​ 8192 KiB  ||
Line 546: Line 579:
 | **Wireless Power:​** ​                      ​| ​ Maximal power output is 24 dBm (251 mW)  || | **Wireless Power:​** ​                      ​| ​ Maximal power output is 24 dBm (251 mW)  ||
 | **802.11n:​** ​                             |  3 x 3 : 2  |  3 x 3 : 3  | | **802.11n:​** ​                             |  3 x 3 : 2  |  3 x 3 : 3  |
-| **[[doc:​hardware:​Switch]]:​** ​             |  [[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]]  |  [[http://​wikidevi.com/​files/​Atheros/​specsheets/​AR8327_AR8327N.pdf|Atheros AR8327N-BL1A]] ​ | +| **[[doc:​hardware:​Switch]]:​** ​             |  [[http://​realtek.info/pdf/rtl8366_8369_datasheet_1-1.pdf|RealTek RTL8366RB]] ​ |  [[http://​wikidevi.com/​files/​Atheros/​specsheets/​AR8327_AR8327N.pdf|Atheros AR8327N-BL1A]]  | 
-| **USB:​** ​                                 |  Yes 1 x 2.0 (OHCI platform; device name ''​1-1''​) ​ ||+| **[[doc/​techref/​swconfig]]:​** ​            ​| ​ [[https://​dev.openwrt.org/​browser/​trunk/​target/​linux/​generic/​files/​drivers/​net/​phy/​rtl8366rb.c|yes,​ rtl8366rb]] ​ |  [[https://​dev.openwrt.org/​browser/​trunk/​target/​linux/​generic/​files/​drivers/​net/​phy/​ar8216.c|yes,​ ar8216]]  | 
 +| **USB:​** ​                                 |  Yes 1 x 2.0 ([[wp>​Open Host Controller Interface|OHCI]] platform; device name ''​1-1''​) ​ ||
 | **Power:​** ​                               |  12V DC 1.5A  || | **Power:​** ​                               |  12V DC 1.5A  ||
 | **[[doc:​hardware:​port.serial|Serial]]:​** ​ |  [[#​Serial|Yes]] ​ || | **[[doc:​hardware:​port.serial|Serial]]:​** ​ |  [[#​Serial|Yes]] ​ ||
Line 733: Line 767:
 </​code>​ </​code>​
  
-<HTML> +<WRAP center round important 83%>At the moment it is **NOT** possible to **UNBRICK** the router by **JTAG** (no write access to flashrom). ​So be very careful not to overwrite the u-boot.</​WRAP>​
-<span style="​color:​red;​font-size:​150%;">​W A R N I N G</​span>​ +
-<p style="​border:​2px dashed red;"> +
-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 careful not to overwrite the u-boot.+
  
  
Line 805: Line 834:
  
 //:!: Note2: From versions 1.8 up to 2.x holding the reset button for more than 30' resets to OpenWRT initial settings.// //:!: Note2: From versions 1.8 up to 2.x holding the reset button for more than 30' resets to OpenWRT initial settings.//
 +
 +//:!: Note3: If you use current trunk version of OpenwRT then the reset button is controlled through /​etc/​rc.button/​reset file. If you hold the button for longer than 5 seconds, then OpenWRT resets to initial settings. You can change the behaviour in this file: /​etc/​rc.button/​reset//​
  
 ===== Debricking ===== ===== Debricking =====
Line 922: Line 953:
 Total: 62104 17472 44632 Total: 62104 17472 44632
 </​code>​ </​code>​
 +
 +This chip from Digikey should work too, if you aren't able to obtain a DDR-module: {{http://​www.digikey.de/​product-detail/​de/​AS4C32M16D1-5TCN/​1450-1006-ND/​4234565|Alliance Memory, Inc. AS4C32M16D1-5TCN}}
  
 ==== I²C GPIO Mod ==== ==== I²C GPIO Mod ====
Line 945: Line 978:
  
  
-===== Custom ​IPv6 image for wr1043nd ​=====+===== Custom ​OpenWrt ​image with LuCi integrated ​=====
  
-a custom image with ipv6 support: radvd, wide-dhcpv6,​ 3g stick support, made for RCS-RDS Fiberlink dual stack PPPoE service, +http://​www.superwrt.eu/en/​firmware/​tp-link-wr1043nd
-but should be okay for static wan settings on other ISPs: +http://​superwrt.ro/​descarca/
-http://​www.superwrt.eu/​firmware/​tp-link-wr1043nd/​+
  
 +Note - official stable releases from openwrt.org also have Luci integrated.
 ===== Other models with the same hardware ===== ===== Other models with the same hardware =====
  
toh/tp-link/tl-wr1043nd.1393657844.txt.bz2 · Last modified: 2014/03/01 08:10 by mexus