| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| toh:tp-link:archer-c5-c7-wdr7500 [2020/01/15 20:02] – [TFTP Recovery (De-Bricking)] kaenguruh | toh:tp-link:archer-c5-c7-wdr7500 [2024/02/13 16:13] – [Archer C7] - rotate table jow |
|---|
| While the Archer C7 has been a very popular router over the years, it comes from a day long before high-speed home connections. | While the Archer C7 has been a very popular router over the years, it comes from a day long before high-speed home connections. |
| |
| MIPS-based devices in this class can't keep up with high-speed lines and the features people now demand. | MIPS-based devices in this class can't keep up with high-speed lines (> 300 mbps) and the features people now demand. |
| |
| There are now multi-core, ARM-based devices in the same price class that far outperform the Archer C7 | There are now multi-core, ARM-based devices in the same price class that far outperform the Archer C7 |
| |
| See https://openwrt.org/toh/tp-link/archer-c5-c7-wdr7500#nat_performance | See [[toh/tp-link/archer-c5-c7-wdr7500#nat_performance|Archer C7 NAT performance]] |
| </WRAP> | </WRAP> |
| |
| **WARNING: DO NOT install OpenWrt 17.03 or 18.06 on Archer C7 v1.x (and WDR7500 v2.x)**, the AR1A (v1) variant of QCA9880 wifi card causes a bootloop as the ath10k driver crashes hard when trying to initialize wifi hardware. Also, in older OpenWrt releases the 5GHz 802.11a/n/ac wifi does not work (due to issues with the same wifi card). | **WARNING: DO NOT install OpenWrt 17.03 or 18.06 on Archer C7 v1.x (and WDR7500 v2.x)**, the AR1A (v1) variant of QCA9880 wifi card causes a bootloop as the ath10k driver crashes hard when trying to initialize wifi hardware. Also, in older OpenWrt releases the 5GHz 802.11a/n/ac wifi does not work (due to issues with the same wifi card). |
| </WRAP> | </WRAP> |
| |
| |
| |
| |
| |
| ===== Supported Versions ===== | ===== Supported Versions ===== |
| ---- datatable ---- | <!-- ToH: { |
| cols : Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid | "source": "json", |
| headers : Model, Version, Current Release, OEM Info, Forum Topic, Technical Data | "dom": "t", |
| align : c,c,c,c,c,c,c | "paging": false, |
| filter : Model~Archer C5 * | "rotate": true, |
| sort : Version | "shownColumns": ["model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], |
| ---- | "filterColumns": {"model": "^Archer C5 .*$"} |
| | } --> |
| |
| ---- datatable ---- | <!-- ToH: { |
| cols : Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid | "source": "json", |
| headers : Model, Version, Current Release, OEM Info, Forum Topic, Technical Data | "dom": "t", |
| align : c,c,c,c,c,c,c | "paging": false, |
| filter : Model~Archer C7 * | "rotate": true, |
| sort : Version | "shownColumns": ["model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], |
| ---- | "filterColumns": {"model": "^Archer C7$"} |
| | } --> |
| |
| ---- datatable ---- | <!-- ToH: { |
| cols : Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid | "source": "json", |
| headers : Model, Version, Current Release, OEM Info, Forum Topic, Technical Data | "dom": "t", |
| align : c,c,c,c,c,c,c | "paging": false, |
| filter : Model~Archer C7R* | "rotate": true, |
| sort : Version | "shownColumns": ["model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], |
| ---- | "filterColumns": {"model": "^Archer C7R.*$"} |
| | } --> |
| |
| ^ Version/Model ^ Release Date ^ last seen (Shop) ^ OpenWrt Version Supported ^ Model Specific Notes ^ | ^ Version/Model ^ Release Date ^ last seen (Shop) ^ OpenWrt Version Supported ^ Model Specific Notes ^ |
| | Archer C5 v1.20 | ? | | BB | QCA9880-BR4A (v2). Same as C7 v2.0. | | | Archer C5 v1.20 | ? | | From 14.07 on | QCA9880-BR4A (v2). Same as C7 v2.0. | |
| | Archer C5 v2.x | ? | | no | 2.x is based on Broadcom chips rather than Atheros and not supported yet (definitely no 802.11ac/5GHz )| | | Archer C5 v2.x | ? | | Unsupported | 2.x is based on Broadcom chips rather than Atheros and not supported yet (definitely no 802.11ac / 5 GHz) | |
| | Archer C7 v1.0 | 2013-01-15 | | BB (2.4GHz only) | QCA9880-AR1A (v1). [[http://wikidevi.com/wiki/TP-LINK_Archer_C7|wikidevi]] [[http://www.tp-link.com/en/products/details/?categoryid=2872&model=Archer+C7|product page]] | | | Archer C7 v1.x | 2013-01-15 | | From 14.07 on (2.4 GHz radio only) | QCA9880-AR1A (v1.x). [[https://wikidevi.wi-cat.ru/TP-LINK_Archer_C7_v1.x|Wikidevi]]. [[http://www.tp-link.com/en/products/details/?categoryid=2872&model=Archer+C7|TP-Link product page]]. | |
| | Archer C7 v1.1 | 2013-??-?? | | BB (2.4GHz only) | QCA9880-AR1A (v1) | | | Archer C7 v2.0 | 2013-12-17 | 2017-01 | From 14.07 on | QCA9880-BR4A (v2). v2.0 printed on serial label on packaging. TP-Link support say "V2 has improved and DFS certified chipset. Flash capacity is 16 MB (v1: 8 MB). V2 also fixed some bugs on v1". [[https://forum.openwrt.org/viewtopic.php?pid=226595#p226595|Forum]]. [[http://blog.naver.com/ckdalsdk12/40208033303|Photos]]. [[http://www.tp-link.com/en/support/download/?model=Archer+C7&version=V2|TP-Link stock firmware]]. [[https://wikidevi.wi-cat.ru/TP-LINK_Archer_C7_v2.x|Wikidevi]]. | |
| | Archer C7 v2.0 | 2013-12-17 | 2017-1 | BB 14.07, CC 15.05 | QCA9880-BR4A (v2). v2.0 printed on serial label on packaging. TP-Link support say "V2 has improved chipset which is DFS certificated. The flash capacity is 16MB compared to 8MB of V1. V2 also fixed a few bugs on V1". [[https://forum.openwrt.org/viewtopic.php?pid=226595#p226595|forum]] [[http://blog.naver.com/ckdalsdk12/40208033303|photos]] [[http://www.tp-link.com/en/support/download/?model=Archer+C7&version=V2|stock firmware]] [[https://wikidevi.com/wiki/TP-Link_Archer_C7_v2|wikidevi]] | | | Archer C7 v2.0 | December 2015 | | From 15.05.1 on | In late 2015 the v2 changed to flash chip GD25Q128, affected serial numbers start with 215C or higher. | |
| | Archer C7 v2.0 | December 2015 | | Trunk (r47588), builds of 15.05.1 (r49220) | In late 2015 the V2 changed to flash chip gd25q128, affected serial numbers start with 215C or higher. The chip is supported in trunk as of r47588 and 15.05.1 as of r49220 | | | Archer C7 v3.0 | ?? | | Unsupported | QCA9563 + QCA9880, 16 MB flash | |
| | Archer C7 v3.0 | ?? | | ?? | QCA9563 + QCA9880, 128 Mbit flash | | | Archer C7 v4.0 | ?? | | From 18.06 on | mentioned in tp-link's downloads 2017-1 | |
| | Archer C7 v4.0 | ?? | | Trunk [[https://openwrt.org/toh/views/toh_fwdownload?dataflt%5BModel*~%5D=Archer+c7+ac1750&dataflt%5BVersions*~%5D=v4|Snapshot]], not in the builds of 17.0x | mentioned in tp-link's downloads 2017-1 | | | Archer C7 v5.0 | ?? | | From 18.06 on | mentioned in tp-link's diff from V4 is 1 USB port (instead of 2) | |
| | Archer C7 v5.0 | ?? | | Trunk [[https://openwrt.org/toh/views/toh_fwdownload?dataflt%5BModel*~%5D=Archer+c7+ac1750&dataflt%5BVersions*~%5D=v5|OpenWrt]], in the builds of 18.x | mentioned in tp-link's diff from V4 is 1 USB port (instead of 2) | | | WDR7500 (Archer C7R) v2.0 | 2013-01-15 | | [[https://forum.openwrt.org/viewtopic.php?pid=213547#p213547|Custom build with target support patch]] 2.4GHz only | QCA9880-AR1A (v1). Seems PRC only. [[https://forum.openwrt.org/viewtopic.php?id=44201|WiP]]. [[http://www.tp-link.com.cn/product_double_299.html|TP-Link product page]]. [[https://wikidevi.wi-cat.ru/TP-LINK_TL-WDR7500_v2.x|Wikidevi]]. [[http://www.aliexpress.com/wholesale?SearchText=TL-WDR7500|AliExpress]]. | |
| | WDR7500 (Archer C7R) v2.0 | 2013-01-15 | | [[https://forum.openwrt.org/viewtopic.php?pid=213547#p213547|custom build with target support patch]] 2.4GHz only | QCA9880-AR1A (v1). Available only in PRC. [[https://forum.openwrt.org/viewtopic.php?id=44201|WiP]] [[http://www.tp-link.com.cn/product_double_299.html|product page]] [[http://wikidevi.com/wiki/TP-LINK_TL-WDR7500_v2.x|wikidevi]] [[http://www.aliexpress.com/wholesale?SearchText=TL-WDR7500|aliexpress]] | | | WDR7500 (Archer C7R) v3.0 | 2015-11-02 | | From 17.01 on | QCA9880-BR4A (v2). Seems PRC only. [[https://forum.openwrt.org/viewtopic.php?id=51150|Photos]]. | |
| | WDR7500 (Archer C7R) v3.0 | 2015-11-02 | | trunk since r47344 | QCA9880-BR4A (v2). Currently available only in PRC [[https://forum.openwrt.org/viewtopic.php?id=51150|photos]] | | | WDR7500 (Archer C7R) v4.0 | ????-??-?? | | Unsupported | QCA9880-BR4A (v2). Manual available from [[http://service.tp-link.com.cn/list_download_technology_1_0_299.html|TP-Link]]. | |
| | WDR7500 (Archer C7R) v4.0 | ????-??-?? | | maybe experimental | QCA9880-BR4A (v2). Manual available at http://service.tp-link.com.cn/list_download_technology_1_0_299.html | | | WDR7500 (Archer C7R) v5.0 | 2015-??-?? | | Unsupported | QCA9880-BR4A (v2). Manual available from [[http://service.tp-link.com.cn/list_download_technology_1_0_299.html|TP-Link]]. | |
| | WDR7500 (Archer C7R) v5.0 | 2015-??-?? | | maybe experimental | QCA9880-BR4A (v2). Manual available at http://service.tp-link.com.cn/list_download_technology_1_0_299.html | | |
| |
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== |
| ---- datatable ---- | <!-- ToH: { |
| cols : Model, Versions, CPU, CPU MHz, Flash MB_mbflashs, RAM MB_mbram, WLAN Hardware, WLAN 2.4Ghz, WLAN 5.0Ghz, Ethernet 100M ports_, Ethernet Gbit ports_, Modem, USB ports_ | "source": "json", |
| header : Model, Version,SoC,CPU MHz,Flash MB,RAM MB,WLAN Hardware,WLAN2.4,WLAN5.0,100M ports,Gbit ports,Modem,USB | "dom": "t", |
| align : l,l,c,c,c,c,c,c,c,c,c,c,c | "paging": false, |
| filter : Model~Archer C5 * | "rotate": true, |
| filteror: Model~Archer C7* | "shownColumns": ["model", "version", "cpu", "cpumhz", "flashmb", "rammb", "wlanhardware", "wlan24ghz", "wlan50ghz", "ethernet100mports", "ethernet1gports", "modem", "usbports"], |
| sort : Model | "filterColumns": {"model": "^Archer C5 .*$"} |
| ---- | } --> |
| |
| ====NAT performance==== | ====NAT performance==== |
| The WLAN<->LAN throughput of Archer C7 2.0 with OpenWrt Chaos Calmer RC3 was measured to be substantially lower than that of the native firmware. (450 to 500Mbps with OpenWrt vs. 750 to 800Mbps with native firmware, both measured under conditions close to ideal). See [[https://forum.openwrt.org/viewtopic.php?id=53703|this thread]] for details. | Please be aware that //OpenWrt firmware does not support the hardware NAT capability// of these routers. Hence, the throughput between WAN<->LAN will be slower than with stock firmware. This is only important for users with highspeed internet connections, e.g. a 1G fibre connection. If your internet connection is <=200-300 Mbps you don't need to worry about this. But if you need faster NAT throughput, consider buying faster hardware. |
| |
| Furthermore, please be aware that //OpenWrt firmware does not support the hardware NAT capability// of these routers. Hence, the throughput between WAN<->LAN will be slower than with stock firmware. This is only important for users with highspeed internet connections, like e.g. a 1G fibre connection. If your internet connection is <=200Mbps you don't need to worry about this (maybe even up to 300Mbps). But if you need faster NAT throughput, consider buying faster hardware. | <tabbox Archer C5 1.20> |
| | The WAN->LAN throughput with native firmware: 485-490Mbps and drops to 305-310Mbps with hardware NAT disabled. After an hour of stress testing there were no signs of thermal throttling. |
| | |
| | The WAN<-LAN or LAN<->LAN performance is not affected at 950Mbps. |
| | |
| | <hidden Measurement details>Firmware: latest native, "150428". Tool: ''iperf3 -l 1M'' in TCP mode, for WAN->LAN measurement ''-R''everse flag was used. |
| | |
| | The thermal throttling could not be triggered even after covering the router with a blanket, case temperature: ~55-60°C.</hidden> |
| | |
| | <tabbox Archer C7 2.0> |
| | The WAN<->LAN throughput with OpenWrt Chaos Calmer RC3 was measured to be substantially lower than that of the native firmware. (450 to 500Mbps with OpenWrt vs. 750 to 800Mbps with native firmware, both measured under conditions close to ideal). See [[https://forum.openwrt.org/viewtopic.php?id=53703|this thread]] for details. |
| | </tabbox> |
| | |
| | [[https://www.reddit.com/r/openwrt/comments/oe43kb/tplink_archer_c7_v2_openwrt_nat_sqm_offloading/|More recent testing on OpenWrt 19.07.7]] suggests that the venerable Archer C7 (and other single-core, MIPS-based routers with ~720 MHz clock rates) are, under ideal conditions with no wireless or "unnecessary" services running, limited to about the following throughput: |
| | |
| | | Type | Average Bitrate per Second | |
| | |------------------------------------------------------------------------|-------------------------------| |
| | | Default routing (download) | 325 Mbits | |
| | | Default routing (upload) | 310 Mbits | |
| | | Software flow offloading (download) | 843 Mbits | |
| | | Software flow offloading (upload) | 831 Mbits | |
| | | | | |
| | | Default routing + SQM [fq_codel + simple] (download) | 245 Mbits | |
| | | Default routing + SQM [fq_codel + simple] (upload) | 150 Mbits | |
| | | Software flow offloading + SQM [fq_codel + simple] (download) | 268 Mbits | |
| | | Software flow offloading + SQM [fq_codel + simple] (upload) | 284 Mbits | |
| | | | | |
| | | Default routing + SQM [fq_codel + simplest_tbf] (download) | 271 Mbits | |
| | | Default routing + SQM [fq_codel + simplest_tbf] (upload) | 188 Mbits | |
| | | Software flow offloading + SQM [fq_codel + simplest_tbf] (download) | 288 Mbits | |
| | | Software flow offloading + SQM [fq_codel + simplest_tbf] (upload) | 495 Mbits | |
| | | | | |
| | | Default routing + SQM [cake + piece_of_cake] (download) | 244 Mbits | |
| | | Default routing + SQM [cake + piece_of_cake] (upload) | 167 Mbits | |
| | | Software flow offloading + SQM [cake + piece_of_cake] (download) | 266 Mbits | |
| | | Software flow offloading + SQM [cake + piece_of_cake] (upload) | 337 Mbits | |
| | | | | |
| | | Default routing + SQM [cake + layer_cake] (download) | 246 Mbits | |
| | | Default routing + SQM [cake + layer_cake] (upload) | 146 Mbits | |
| | | Software flow offloading + SQM [cake + layer_cake] (download) | 266 Mbits | |
| | | Software flow offloading + SQM [cake + layer_cake] (upload) | 315 Mbits | |
| |
| [[https://forum.openwrt.org/t/comparative-throughput-testing-including-nat-sqm-wireguard-and-openvpn/44724?u=jeff|More recent testing]] suggests that the venerable Archer C7 (and other single-core, MIPS-based routers with ~720 MHz clock rates) are, under ideal conditions with no wireless or "unnecessary" services running limited to below about | |
| * 300 Mbps without SQM, 600 Mbps with software flow offload enabled (v19 and later) | |
| * 150-200 Mbps with SQM | |
| |
| Enabling wireless, running additional applications, or even imperfect ISP lines can significantly limit "real world" performance to well below these values. | Enabling wireless, running additional applications, or even imperfect ISP lines can significantly limit "real world" performance to well below these values. |
| |
| [[https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm|SQM]] is commonly known as "bufferbloat management" or "QoS" and is often very valuable on consumer lines. | [[docs/guide-user/network/traffic-shaping/sqm|SQM]] is commonly known as "bufferbloat management" or "QoS" and is often very valuable on consumer lines. |
| ====USB Support ==== | ====USB Support ==== |
| The SoC hardware used here and in other devices appears to //only //support USB 2.0 devices; the OHCI driver (USB 1.0/1.1) does not detect any applicable hardware. Use of older/slower USB devices such as keyboards, mice, and UPS may require a USB 2.0 hub as an intermediary. See [[https://dev.openwrt.org/ticket/15194|OpenWrt Ticket #15194]] and [[https://dev.openwrt.org/ticket/16505|#16505]] for further details. | The SoC hardware used here and in other devices appears to //only //support USB 2.0 devices; the OHCI driver (USB 1.0/1.1) does not detect any applicable hardware. Use of older/slower USB devices such as keyboards, mice, and UPS may require a USB 2.0 hub as an intermediary. See [[https://dev.openwrt.org/ticket/15194|OpenWrt Ticket #15194]] and [[https://dev.openwrt.org/ticket/16505|#16505]] for further details. |
| |
| ==== Archer C5 ==== | ==== Archer C5 ==== |
| ---- datatable ---- | <!-- ToH: { |
| cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | "source": "json", |
| align : l,l,c | "dom": "t", |
| filter : Model~Archer C5 * | "paging": false, |
| sort : Version | "rotate": true, |
| ---- | "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], |
| | "filterColumns": {"model": "^Archer C5 .*$"} |
| | } --> |
| |
| FIXME Please add the installation procedure here. | FIXME Please add the installation procedure here. |
| |
| ==== Archer C7 ==== | ==== Archer C7 ==== |
| ---- datatable ---- | <!-- ToH: { |
| cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | "source": "json", |
| align : l,l,c | "dom": "t", |
| filter : Model~Archer C7 * | "paging": false, |
| sort : Version | "rotate": true, |
| ---- | "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], |
| | "filterColumns": {"model": "^Archer C7$"} |
| | } --> |
| |
| === All C7 Versions === | === All C7 Versions === |
| ==3.Flash OpenWrt FW:== | ==3.Flash OpenWrt FW:== |
| Download the firmware from the links in the tables above. Before flashing, rename the downloaded file to make it shorter and remove all dots except one, e.g. ''firmware.bin'' | Download the firmware from the links in the tables above. Before flashing, rename the downloaded file to make it shorter and remove all dots except one, e.g. ''firmware.bin'' |
| | |
| | === Installation and upgrade of TP-Link Archer C7 V3 === |
| | (Updated and tested install on February 2020 by zenith828) |
| | |
| | I followed the instructions for installing Archer C7 V4 (see below) successfully. |
| | |
| | I started with the most recent FW on the Archer C7 V3 SW version 3.14.3 (release date 2015-05-08) |
| | I upgraded to OpenWrt v19.07.1, but I used the binary named the Archer C7 v2, because that's what listed as the binary for the v3. This causes the Model to be listed as "TP-Link Archer C7 v2" on the status page. Hopefully this is the only issue. |
| | |
| | I have not done extensive testing on it to ensure that all the functionality is working properly, but I have tested the wireless and everything seems to be in order. |
| |
| === Installation and upgrade of TP-Link Archer C7 V4 === | === Installation and upgrade of TP-Link Archer C7 V4 === |
| |
| I used European TP-Link original firmware when I did the update. | I used European TP-Link original firmware when I did the update. |
| | Also look [[:toh:tp-link:archer_c7#if_tftp_flashing_fails|at this link]] for Archer c7 v5 (EU) if you have trouble TFTP-ing. |
| |
| ==== Archer C7R ==== | ==== Archer C7R ==== |
| ---- datatable ---- | <!-- ToH: { |
| cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | "source": "json", |
| align : l,l,c | "dom": "t", |
| filter : Model~Archer C7R* | "paging": false, |
| sort : Version | "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], |
| ---- | "filterColumns": {"model": "^Archer C7R.*$"} |
| | } --> |
| |
| FIXME Please add the installation procedure here. | === Installation of TP-Link WDR7500 V3 via TTL and TFTP === |
| | - Download the corresponding OpenWrt Install (factory, not sysupgrade) image for your router, and rename it to something short like "firmware.bin" |
| | - Set your computer to the static IP address: 192.168.1.100 |
| | - Start a TFTP server on your computer, and place firmware.bin in the root folder |
| | - Connect over TTL (speed=115200), and when you see the text "Autobooting in 1 seconds", quickly type "tpl" to halt the boot process |
| | * You will now be greeted with a command prompt. Firstly we download the firmware over TFTP by issuing the following command: |
| | **tftpboot 0x80020000 firmware.bin** |
| | * If everything goes well, you will see a message saying "Bytes transferred = 8126464 (7c0000 hex)". Next we erase the flash. Please take care so that the power will not go out etc. You have been warned! |
| | **erase 0x9f020000 +0x7c0000** |
| | * If everything goes well, you will see a message saying "Erased 124 sectors". Finally we write the firmware to flash, by issuing the following command |
| | **cp.b 0x80020000 0x9f020000 0x7c0000** |
| | * Wait a few minutes after the writing has finished, and power cycle the router. OpenWRT should now start up. Tested by Mats, 2021-01-17 |
| |
| ==== 5G Wifi Problems / 5GHz network controller not identified ==== | ==== 5G Wifi Problems / 5GHz network controller not identified ==== |
| ==== TFTP Recovery (De-Bricking) ==== | ==== TFTP Recovery (De-Bricking) ==== |
| |
| The serial-less TFTP recovery method for the [[toh:tp-link:tl-wdr4300#de-brick_or_oem_installation_using_the_tftp_recovery|TP-Link TL-WDR4300]] also works for the Archer C7 (confirmed on v1.1 and v2) and the Archer C5 (v1.20). | The serial-less TFTP recovery method for the [[toh:tp-link:tl-wdr4300_v1#de-brick_or_oem_installation_using_the_tftp_recovery|TP-Link TL-WDR4300]] also works for the Archer C7 (confirmed on v1.1 and v2) and the Archer C5 (v1.20). |
| |
| For firmware revisions before 3.14.1 (140929), the router looks for an IP address of 192.168.1.66 and a file named ''ArcherC7v2_tp_recovery.bin''. Firmware 3.14.1 updates the bootloader to look for an IP address of 192.168.0.66 and a file named ''ArcherC7v3_tp_recovery.bin'' even on hardware v2 units, but may also load ''ArcherC7v2_tp_recovery.bin''. Some v1.1 units may also look for ''ArcherC7v1_tp_recovery.bin''. The model Archer C5 looks for the file ''ArcherC5v1_tp_recovery.bin''. | For firmware revisions before 3.14.1 (140929), the router looks for an IP address of 192.168.1.66 and a file named ''ArcherC7v2_tp_recovery.bin''. Firmware 3.14.1 updates the bootloader to look for an IP address of 192.168.0.66 and a file named ''ArcherC7v3_tp_recovery.bin'' even on hardware v2 units, but may also load ''ArcherC7v2_tp_recovery.bin''. Some v1.1 units may also look for ''ArcherC7v1_tp_recovery.bin''. The model Archer C5 looks for the file ''ArcherC5v1_tp_recovery.bin''. |
| |
| <code> | <code> |
| original_product_id = ffffffff | original_product_id = ffffffff |
| original_product_ver = ffffffff | original_product_ver = ffffffff |
| recovery_product_id = c7000002 | recovery_product_id = c7000002 |
| </code> | </code> |
| |
| While this would be a fine safety feature in another context, it means the recovery process can reject a valid new image if the image in flash is corrupted. Unfortunately, such corruption can easily occur if the flashing process is interrupted: when an image is accepted, the flashing process first erases the whole space, which takes a while, and then writes the new image. If this process is interrupted during the erasure phase, the in flash header will appear as all 0xFF, and further recovery attempts will therefore fail because the header hardware id and version values will no longer match. If this happens, you'll need to try either a serial connection, or building an image with the header values overridden (in **tp-link.mk** set **TPLINK_HWREV** and **TPLINK_HWID** to **0xffffffff**). | or |
| | <code> |
| | Bytes transferred = 16384512 (fa0200 hex) |
| | original_product_id = 00000000 |
| | original_product_ver = 00 |
| | original_resvered_id = 00 |
| | original_special_id = 55530000 |
| | recovery_product_id = c7000002 |
| | recovery_product_ver = 01 |
| | recovery_resvered_id = 01 |
| | recovery_support_list = 00000000;55530000; |
| | compare special,ret:0 |
| | auto update firmware: product id verify fail! |
| | </code> |
| | |
| | While this would be a fine safety feature in another context, it means the recovery process can reject a valid new image if the image in flash is corrupted. Unfortunately, such corruption can easily occur if the flashing process is interrupted: when an image is accepted, the flashing process first erases the whole space, which takes a while, and then writes the new image. If this process is interrupted during the erasure phase, the in flash header will appear as all 0xFF, and further recovery attempts will therefore fail because the header hardware id and version values will no longer match. If this happens, you'll need to try either a serial connection, or building an image with the header values overridden (in **tp-link.mk** set **TPLINK_HWREV** and **TPLINK_HWID** to **0xffffffff**), or override the values corresponding to original_product_id,original_product_ver,original_resvered_id in the firmware image, which start at offset 0x40 in the firmware and stored as 4 byte int each (i.e. set 3*4=12 bytes to 0xFF starting at offset 0x40, if that does not work try setting to 0x00). |
| |
| |
| **Update for debricking without serial on OpenWrt 19.07:** After building your own image with the modified TPLINK_HWREV and TPLINK_HWID (you can also download mine here: [[https://github.com/danielschmalhofer/Important-Openwrt-Things/blob/master/archer_c7_ac1750_debricking.zip]]) you can flash with tftp the right image. You will see, if you hit the right one, when the blinking takes longer than normal. After that you will be able to access the router via terminal on root@192.168.1.1 - but take care, because for me the image was gone after a reboot. You will habe to make a sysupgrade. But the sysupgrade via terminal will fail, because of the corrupting header-infos, and even -F will not help you. So go install luci (opkg update && opkg install luci), login via http://192.168.1.1 and upgrade the system via the web interface - there the Force option works. | **Update for debricking without serial on OpenWrt 19.07:** After building your own image with the modified TPLINK_HWREV and TPLINK_HWID (you can also download mine here: [[https://github.com/danielschmalhofer/Important-Openwrt-Things/blob/master/archer_c7_ac1750_debricking.zip]]) you can flash with tftp the right image. You will see, if you hit the right one, when the blinking takes longer than normal. After that you will be able to access the router via terminal on root@192.168.1.1 - but take care, because for me the image was gone after a reboot. You will have to make a sysupgrade. But the sysupgrade via terminal will fail, because of the corrupting header-infos, and even -F will not help you. So install luci (opkg update && opkg install luci), login via http://192.168.1.1 and upgrade the system via the web interface - there the Force option works. |
| |
| ==== Recovery using serial connection ==== | ==== Recovery using serial connection ==== |
| Connect to your router via serial (TX, RX and GND .. VCC not needed), power it up, then type "tpl" until the boot process is halted and you should be at the console. (Each "tpl" you type must be followed by carriage-return/linefeed. If you're running C-Kermit in an Emacs shell buffer under Linux, the carriage-return character is a control-M.) | Connect to your router via serial (TX, RX and GND .. VCC not needed), power it up, then type "tpl" until the boot process is halted and you should be at the console. (Each "tpl" you type must be followed by carriage-return/linefeed. If you're running C-Kermit in an Emacs shell buffer under Linux, the carriage-return character is a control-M.) |
| |
| If you're having problems getting 'tpl' to work, you may need a pull-up resistor inline on the TX side of the connection, see [[https://goo.gl/7KFvfb]] for details. The TX pullup is most likely needed in version 2 models of revision B (serial beginning with 215B...), 16MB flash memory. A pull-up resistor also resolved "bleed through" of binary data into the console on an Archer C7 with a serial number beginning with 2154. | If you're having problems getting 'tpl' to work, you may need a pull-up resistor inline on the TX side of the connection, see [[https://lists.infradead.org/pipermail/lede-dev/2016-November/003774.html|link (broken)]]. The TX pullup is most likely needed in version 2 models of revision B (serial beginning with 215B...), 16MB flash memory. A pull-up resistor also resolved "bleed through" of binary data into the console on an Archer C7 with a serial number beginning with 2154. |
| |
| If you find three 220 Ohms resistors and one 150 Ohms resistor in your drawer they will do the trick when put in series. Additionally, if you are puzzled after reading the linked forum post above, this circuit may help (Vcc of the sketched FTDI was set to 3.3V): | If you find three 220 Ohms resistors and one 150 Ohms resistor in your drawer they will do the trick when put in series. Additionally, if you are puzzled after reading the linked forum post above, this circuit may help (Vcc of the sketched FTDI was set to 3.3V): |
| </code> | </code> |
| |
| | NOTE: If you are using a 3 pin cable containing an FTDI chip (such as the 3.5mm audio jack version), it is not possible to connect the resistor to VCC on the FTDI side. Instead, use the VCC on the Archer side, this is the normally unused pin next to GND on the 4 pin connection. |
| |
| Set up a TFTP server with your firmware at 192.168.1.100, then run the following commands: | Set up a TFTP server with your firmware at 192.168.1.100, then run the following commands: |
| |
| {{:media:tplink:tl-wdr7500:archerc7v2-switch-diagram.png?600|}} | {{:media:tplink:tl-wdr7500:archerc7v2-switch-diagram.png?600|}} |
| | |
| | Note: It seems that Archer C5 has a slightly different structure. Switch has 6 ports and the only interface ''eth0'' connects to it carrying both VLAN1 and VLAN2. See page [[toh:tp-link:archer_c5_v4#switch|TP-Link Archer C5 v4]]. v2 is similar. So the overall full duplex WAN throughput cannot exceed 1 Gbps. |
| |
| ==== VLAN Tagging ==== | ==== VLAN Tagging ==== |
| <WRAP center dangerous 70%> | <WRAP center dangerous 70%> |
| Warning!\\ | Warning!\\ |
| The labels in the image look wrong (did not actually confirm with real hardware). It should be either VCC, GND, TX, RX or VCC, GND, RX, TX. The second pin has four connections to the surrounding mass, so is GND. The first pin has a capacitor, which points to the fact that it is VCC. | The labels in the image look wrong (confirmed with real hardware). It should be VCC, GND, RX, TX. The second pin has four connections to the surrounding mass, so is GND. The first pin has a capacitor, which points to the fact that it is VCC. |
| </WRAP> | </WRAP> |
| |
| |
| ===== Tags ===== | ===== Tags ===== |
| {{tag>GigabitEthernet 2NIC 2WNIC 5Port 74Kc 128ram 8flash 16flash 2usb ap135 QCA9558 QCA9563 QCA9880 ath10k 802.11n 802.11g 802.11b 802.11a 802.11ac simultan MiniPCIexpress}} | {{tag>MIPS MIPS32 74Kc QCA9558 QCA9563 QCA9880 8flash 16flash 128ram 5Port GigabitEthernet vlan 802.11bgn 802.11ac simultan internalantenna detachableantenna 2ant 3ant 6ant 2NIC 2WNIC ath10k ap135 1usb 2usb usb2.0 MiniPCIexpress serial jtag u-boot 12v_powered}} |