| Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision |
| toh:tp-link:archer-c5-c7-wdr7500 [2018/02/17 19:06] – ↷ Links adapted because of a move operation | toh:tp-link:archer-c5-c7-wdr7500 [2024/06/08 20:15] – [Recovery using serial connection] jeixav |
|---|
| Dual Band (concurrent) and Gigabit Ethernet. Advertised as 1750 Mbps. It has simultaneous Triple-Stream (3x3) radios on both 2.4GHz and 5 GHz Bands. It supports 802.11n in 2.4GHz for 450Mbps throughput and [[#Tags|IEEE 802.11ac (draft)]] for 1300Mbps throughput in 5GHz. //Note: The editing history for this page is at [[toh:tp-link:tl-wdr7500|Previous Archer C5/C7/WDR7500 page]] // | Dual Band (concurrent) and Gigabit Ethernet. Advertised as 1750 Mbps. It has simultaneous Triple-Stream (3x3) radios on both 2.4GHz and 5 GHz Bands. It supports 802.11n in 2.4GHz for 450Mbps throughput and [[#Tags|IEEE 802.11ac (draft)]] for 1300Mbps throughput in 5GHz. //Note: The editing history for this page is at [[toh:tp-link:tl-wdr7500|Previous Archer C5/C7/WDR7500 page]] // |
| |
| **The Archer C5 v1.x**: available worldwide, has 3 internal (2.4GHz) and 3 external (5GHz) antennas. | <WRAP center round tip 60%> |
| | While the Archer C7 has been a very popular router over the years, it comes from a day long before high-speed home connections. |
| |
| **The Archer C5 v2.0**: available worldwide, has ?? internal (2.4GHz) and 2 external (5GHz) antennas. | MIPS-based devices in this class can't keep up with high-speed lines (> 300 mbps) and the features people now demand. |
| |
| **The Archer C7**: available worldwide, has 3 internal (2.4GHz) and 3 external (5GHz) antennas. | There are now multi-core, ARM-based devices in the same price class that far outperform the Archer C7 |
| |
| **The Archer C7R (also called the TL-WDR7500)**: currently available in PRC only, has 6 external antennas. | See [[toh/tp-link/archer-c5-c7-wdr7500#nat_performance|Archer C7 NAT performance]] |
| | </WRAP> |
| |
| {{media:tplink:tl-wdr7500:c7-1.png?300|TP-Link Archer C7 AC1750}} | |
| {{media:tplink:tl-wdr7500:c7-2.png?300|TP-Link TL-WDR7500 - PRC only}} | |
| |
| | **The Archer C5 v1.x**: available worldwide, has 3 internal (2.4GHz) and 3 external (5GHz) antennas. |
| |
| ===== Supported Versions ===== | **The Archer C5 v2.0**: available worldwide, has ?? internal (2.4GHz) and 2 external (5GHz) antennas. |
| ^ Version/Model ^ S/N ^ Release Date ^ last seen (Shop) ^ OpenWrt Version Supported ^ Technical Data ^ Model Specific Notes ^ | |
| | Archer C5 v1.20 | - | ? | | BB | [[toh:hwdata:tp-link:tp-link_archer_c5_ac1200_v1.20|Technical Data]] | QCA9880-BR4A (v2). Same as C7 v2.0. | | |
| | Archer C5 v2.x | - | ? | | no | [[toh:hwdata:tp-link:tp-link_archer_c5_ac1200_v2.0|Technical Data]] | 2.x is based on Broadcom chips rather than Atheros and not supported yet | | |
| | Archer C7 v1.0 | - | 2013-01-15 | | BB (2.4GHz only) | [[toh:hwdata:tp-link:tp-link_archer_c7_ac1750|Technical Data]] | 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.1 | - | 2013-??-?? | | BB (2.4GHz only) | [[toh:hwdata:tp-link:tp-link_archer_c7_ac1750|Technical Data]] | QCA9880-AR1A (v1) | | |
| | Archer C7 v2.0 | - | 2013-12-17 | 2017-1 | BB 14.07, CC 15.05 | [[toh:hwdata:tp-link:tp-link_archer_c7_ac1750_v2.0|Technical Data]] | 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 | | Trunk (r47588), builds of 15.05.1 (r49220) | [[toh:hwdata:tp-link:tp-link_archer_c7_ac1750_v2.0|Technical Data]] | 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 | - | ?? | | ?? | ?? | mentioned in tp-link's downloads 2017-1 | | |
| | Archer C7 v4.0 | - | ?? | | ?? | ?? | mentioned in tp-link's downloads 2017-1 | | |
| | 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 | [[toh:hwdata:tp-link:tp-link_archer_c7r_wdr7500_2_cn|Technical Data]] | 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 | | trunk since r47344 | [[toh:hwdata:tp-link:tp-link_archer_c7r_wdr7500_3_cn|Technical Data]] | QCA9880-BR4A (v2). Currently available only in PRC [[https://forum.openwrt.org/viewtopic.php?id=51150|photos]] | | |
| | WDR7500 (Archer C7R) v4.0 | - | ????-??-?? | | maybe experimental | [[toh/hwdata/tp-link/tp-link_archer_c7r_wdr7500_v5.0|Technical Data]] | 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-??-?? | | maybe experimental | [[toh/hwdata/tp-link/tp-link_archer_c7r_wdr7500_v5.0|Technical Data]] | QCA9880-BR4A (v2). Manual available at http://service.tp-link.com.cn/list_download_technology_1_0_299.html | | |
| |
| For the Archer C7 v1.x and WDR7500 v2.x, the 5GHz 802.11a/n/ac functionality is not supported, and likely will never be, since support for the AR1A (v1) variant of QCA9880 chip is not included in the open source ath10k driver. | **The Archer C7**: available worldwide, has 3 internal (2.4GHz) and 3 external (5GHz) antennas. |
| The Archer C7 v2.x uses the BR4A (v2) variant which is supported in ath10k [[http://wireless.kernel.org/en/users/Drivers/ath10k|ath10k Linux]] | |
| |
| **Notes:** The 802.11ac 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. | **The Archer C7R (also called the TL-WDR7500)**: currently available in PRC only, has 6 external antennas. |
| |
| 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. | |
| ===== Quick Start Guide ===== | |
| <WRAP right 50% round important > | |
| **Newer versions of Archer C7 v2.0:** | |
| The current stable release Chaos Calmer 15.05.1 provides full support for the //original// v2.0 version of the Archer C7 and has Luci (webUI) built-in. However, in late 2015, TP-Link changed the hardware configuration without bumping the hardware version number, v2.0 devices with serial numbers greater than 215C use a gd25q128 flash chip, which is supported in trunk as of r47588 and in custom compiles of 15.05.1 newer than r49220. Either of these options are confirmed to work, although the kmod-ath10k driver (for 5GHz Wi-Fi functionality) and LuCI (if desired) will need to be installed as packages after the firmware is flashed. | |
| |
| The current stable release Chaos Calmer 15.05.1 dated 15-Mar-2016 17:48 is r48532. | <WRAP center round alert 80%> |
| | **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> |
| |
| <WRAP right 50% round important > | |
| **If these instructions don't work:** Recent versions (late 2015 and newer) of TP-Link routers sold in the United States will not upgrade firmware through the OEM firmware web interface unless the header includes the US region code. | |
| |
| As of r49217 trunk now includes the necessary US region header in the v2 firmware file, currently other regions accept this firmware as only the US region firmware is locked. Once trunk is installed you can install any firmware. You can also flash any firmware image using the TFTP Recovery method to install OpenWrt. | {{media:tplink:tl-wdr7500:c7-1.png?300|TP-Link Archer C7 AC1750}} |
| </WRAP> | {{media:tplink:tl-wdr7500:c7-2.png?300|TP-Link TL-WDR7500 - PRC only}} |
| |
| **Note:** The Archer C7 V2.0's web interface does not accept the Chaos Calmer RC1 .bin file unless you rename it to something with less dots; like openwrtCC.bin. | |
| |
| * Download the 15.05.1 build of OpenWrt to your PC. | ===== Supported Versions ===== |
| * [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-archer-c5-squashfs-factory.bin|Archer C5 V1.X]] | <!-- ToH: { |
| * [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-archer-c7-v1-squashfs-factory.bin|Archer C7 V1.X]] | "source": "json", |
| * [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-archer-c7-v2-squashfs-factory.bin|Archer C7 V2]] | "dom": "t", |
| * If you want to install 15.05.1 with support for the new gd25q128 flash chip you can download this [[https://zioncluster.ca/openwrt/archer-c7/openwrt-ar71xx-generic-archer-c7-v2-squashfs-factory.bin|factory]] or [[https://zioncluster.ca/openwrt/archer-c7/openwrt-ar71xx-generic-archer-c7-v2-squashfs-sysupgrade.bin|sysupgrade]] image, then manually install the ath10k [[https://zioncluster.ca/openwrt/archer-c7/ath10k-firmware-qca988x_2014-11-13-77f72b5f7dd940386d9e619a17904987759b7186-1_ar71xx.ipk| firmware]] and [[https://zioncluster.ca/openwrt/archer-c7/kmod-ath10k_3.18.29+2016-01-10-1_ar71xx.ipk|kernel module]]. | "paging": false, |
| * [[https://github.com/zgmnkv/openwrt-dist|Alternative build]] of 15.05.1 firmware and packages for Archer C7 v2 with new gd25q128 flash chip | "rotate": true, |
| * Check the [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/md5sums|MD5-Hash]] of the file you downloaded. If it doesn't match, redownload the file. | "shownColumns": ["model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], |
| * connect your PC to a LAN port of the TP-link. If the configuration was not changed, the DHCP on the router will give you a 192.168.0.X address and the TP-link web administration page is http://192.168.0.1/. (User: admin, Password: admin) Under 'System Tools' select 'Firmware Upgrade'. Browse to the previously downloaded *.bin file. Click Upgrade. | "filterColumns": {"model": "^Archer C5 .*$"} |
| * If the Webinterface tells you 'You have no authority to access this router!' that's because your browser does not send the correct HTTP referer header. Disable addons or use a different browser. | } --> |
| * If the web interface tells you 'Please choose a file to upgrade', just rename the file to something shorter like ''openwrt.bin''. | |
| * Connect to http://192.168.1.1 with your web browser | |
| * Set your password and configure the router through the web UI. [[:doc:howto:basic.config|Basic Config]] | |
| * Congratulations! You just installed OpenWrt on your Router! | |
| |
| | <!-- ToH: { |
| | "source": "json", |
| | "dom": "t", |
| | "paging": false, |
| | "rotate": true, |
| | "shownColumns": ["model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], |
| | "filterColumns": {"model": "^Archer C7$"} |
| | } --> |
| |
| Forum discussion/support thread: [[https://forum.openwrt.org/viewtopic.php?id=44201]] | <!-- ToH: { |
| | "source": "json", |
| | "dom": "t", |
| | "paging": false, |
| | "rotate": true, |
| | "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 ^ |
| | | Archer C5 v1.20 | ? | | From 14.07 on | QCA9880-BR4A (v2). Same as C7 v2.0. | |
| | | 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.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 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 | 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 v3.0 | ?? | | Unsupported | QCA9563 + QCA9880, 16 MB flash | |
| | | Archer C7 v4.0 | ?? | | From 18.06 on | 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) | |
| | | 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) 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) 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) 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]]. | |
| |
| **Note**: Factory default IP address range is 192.168.0.1 while OpenWrt uses 192.168.1.1 by default. If you have trouble accessing your router after initial flash, check that you have a 192.168.1.x IP address on your PC. | |
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== |
| ^ SoC ^ Ram ^ Flash ^ Network ^ USB ^ Serial ^ JTag ^ | <!-- ToH: { |
| | Qualcomm QCA9558@720MHz | 128MiB | 8MiB/16MiB | 4 x 1 | Yes | Yes | Yes | | "source": "json", |
| | "dom": "t", |
| | "paging": false, |
| | "rotate": true, |
| | "shownColumns": ["model", "version", "cpu", "cpumhz", "flashmb", "rammb", "wlanhardware", "wlan24ghz", "wlan50ghz", "ethernet100mports", "ethernet1gports", "modem", "usbports"], |
| | "filterColumns": {"model": "^Archer C5 .*$"} |
| | } --> |
| |
| //Note: 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.// | ====NAT performance==== |
| | 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. |
| |
| Manufacturer's site: [[http://www.tp-link.com/en/products/details/?categoryid=2872&model=Archer+C7|Archer C7]] [[http://www.tp-link.com.cn/product_double_299.html|TL-WDR7500]] | <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. |
| |
| ---- datatable ---- | <hidden Measurement details>Firmware: latest native, "150428". Tool: ''iperf3 -l 1M'' in TCP mode, for WAN->LAN measurement ''-R''everse flag was used. |
| cols : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, Forum Topic URL_url, Device Techdata_pageid | |
| headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data | |
| align : l,l,l,c,c,c,c,c | |
| filter : Model~Archer C5 * | |
| filteror: Model~Archer C7* | |
| sort : Model | |
| ---- | |
| |
| Information about WDR-7500 Ver 6.0. | The thermal throttling could not be triggered even after covering the router with a blanket, case temperature: ~55-60°C.</hidden> |
| China | |
| |
| ^ Brand^ Model ^ Versions^ SoC^ USB ^ Serial ^ JTag ^ Aditional WIFI Chip ^ Ethernet ^ RAM ^ Flash^ | <tabbox Archer C7 2.0> |
| | TP-Link| WDR-7500|6.0 (CN)|QCA9563-AL3A| NO | Yes | ? |QCA9880-BR4A | RTL8367S Gigabit Switch 1WAN + 4 LAN| W9751G6KB-25|25Q64CSIG (BH1621)| | 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> |
| |
| PCB | [[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: |
| http://oi66.tinypic.com/2uzsegy.jpg | |
| |
| QCA9563-AL3A MIPS CPU | | Type | Average Bitrate per Second | |
| http://i66.tinypic.com/o70ft1.jpg | |------------------------------------------------------------------------|-------------------------------| |
| | | 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 | |
| |
| QCA9880-BR4A | |
| http://i65.tinypic.com/awt8hx.jpg | |
| |
| RTL8367S Gigabit Switch | Enabling wireless, running additional applications, or even imperfect ISP lines can significantly limit "real world" performance to well below these values. |
| http://i67.tinypic.com/21eb5w6.jpg | |
| |
| One memory chip WinBond | [[docs/guide-user/network/traffic-shaping/sqm|SQM]] is commonly known as "bufferbloat management" or "QoS" and is often very valuable on consumer lines. |
| W9751G6KB-25 RAM | |
| http://i63.tinypic.com/wvqszb.jpg | |
| |
| Flash Chip | ====USB Support ==== |
| 25Q64CSIG (BH1621) | 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. |
| http://i65.tinypic.com/9asmqh.jpg | |
| |
| UART J1 | |
| http://i67.tinypic.com/s1tjlk.jpg | |
| |
| Here is Forum topic about it - https://forum.openwrt.org/viewtopic.php?pid=336271#p336271 | ===== Installation ===== |
| ===== Experimental Versions ===== | |
| |
| /* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * | -> [[docs:guide-user:installation:generic.flashing|Install OpenWrt (generic explanation)]] |
| * The official Table of Hardware only lists current, stable versions of OpenWrt. * | |
| * Use this space to describe any on-going efforts to create a newer version * | |
| * of the firmware for this device. Provide links to firmware images, * | |
| * active threads on the forum, or other sources of information. * | |
| * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */ | |
| |
| **v3** | ==== Quick Start Guide ==== |
| |
| - This is a 15.05 for v3 by risk: [[https://drive.google.com/open?id=0B6rRnEPNTcLAMnRENU5Cc0NiYUE|Factory]] [[https://drive.google.com/open?id=0B6rRnEPNTcLANGw4aEN1ajJSZG8|Sysupgrade]] \\ | **Note:** The Archer C7 V2.0's web interface does not accept the image .bin file unless you rename it to something with less dots; like openwrt.bin. |
| - Factory firmware is flashable over the webui, tested for this [[http://www.aliexpress.com/item/TL-WDR7500-english-openwrt-firmware-AC1750-2-4G-5G-Wireless-wifi-router-27db-Antenna-2-USB/1824015531.html|device]] | |
| |
| | * Download the correct version for your router from the tables below. |
| | * Note that if your router says US, EU, or IL on the sticker on the bottom, you might need a different image than the image linked in the tables below. The images in the table below are for "rest of world" routers. If you browse to the parent directory of the linked images, you'll see the appropriate US, EU, or IL .bin file. |
| | * connect your PC to a LAN port of the TP-link. If the default configuration was not changed, the DHCP on the router will give you a 192.168.0.X address and the TP-link web administration page is http://192.168.0.1/. (User: admin, Password: admin) Under 'System Tools' select 'Firmware Upgrade'. Browse to the previously downloaded *.bin file. Click Upgrade. |
| | * If the Webinterface tells you 'You have no authority to access this router!' that's because your browser does not send the correct HTTP referer header. Disable addons or use a different browser. |
| | * If the web interface tells you 'Please choose a file to upgrade', just rename the file to something shorter like ''openwrt.bin''. |
| | * Connect to http://192.168.1.1 with your web browser |
| | * Set your password and configure the router through the web UI. [[docs:guide-quick-start:checks_and_troubleshooting|Basic Config]] |
| | * Congratulations! You just installed OpenWrt on your Router! |
| |
| - //!!! Warning !!! this is a clean 15.05 build, no special stuff, you'll have to opkg install kmod-ath10k by hand, like on c7 v2// | |
| - opkg needs release keys: | |
| wget -qO- http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/base/base-files_157-r46767_ar71xx.ipk | tar -xzO ./data.tar.gz | tar -C / -xz ./etc/opkg/keys/ | |
| |
| **v4** **v5** | **Note**: Factory default IP address range is 192.168.0.1 while OpenWrt uses 192.168.1.1 by default. If you have trouble accessing your router after initial flash, check that you have a 192.168.1.x IP address on your PC. |
| |
| Look for risk (irc://freenode.net/openwrt) if you have information on these devices or these devices, and can test. Versions v3, v4 and v5 should have identical hardware, and only difference should be different software versions. | |
| ===== Hardware Highlights ===== | |
| |
| ---- datatable ---- | ==== Archer C5 ==== |
| cols : Model, Versions, Platform, 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_ | <!-- ToH: { |
| header : Model, Version,SoC,CPU MHz,Flash MB,RAM MB,WLAN Hardware,WLAN2.4,WLAN5.0,100M ports,Gbit ports,Modem,USB | "source": "json", |
| align : l,l,c,c,c,c,c,c,c,c,c,c,c | "dom": "t", |
| filter : Model~Archer C5 * | "paging": false, |
| filteror: Model~Archer C7* | "rotate": true, |
| sort : Model | "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], |
| ---- | "filterColumns": {"model": "^Archer C5 .*$"} |
| | } --> |
| |
| | FIXME Please add the installation procedure here. |
| |
| ===== Installation ===== | ==== Archer C7 ==== |
| - → [[doc:howto:obtain.firmware]] | <!-- ToH: { |
| - → [[docs:user-guide:generic.flashing|Install OpenWrt]] | "source": "json", |
| - → [[about/latest|Latest OpenWrt release]] | "dom": "t", |
| *For the Archer C7 V2 please see "Installation of TP-Link Archer C7 V2" below. | "paging": false, |
| | "rotate": true, |
| | "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], |
| | "filterColumns": {"model": "^Archer C7$"} |
| | } --> |
| |
| ---- datatable ---- | === All C7 Versions === |
| cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | OpenWrt firmware images have a name that is too long for the TP-Link web interface to handle. They need to be renamed to something short like ''factory.bin'' |
| align : l,l,c | |
| filter : Model~Archer C5 * | |
| filteror: Model~Archer C7* | |
| sort : Model | |
| ---- | |
| |
| ==== Installation of TP-Link Archer C7 V2 ==== | === Installation of TP-Link Archer C7 V1.X === |
| | <WRAP round important > |
| | The following images are known not to work and lead to a boot loop: |
| | * LEDE 17.01.X as documented [[https://forum.openwrt.org/t/problem-installing-firmware-on-tp-link-archer-c7-v1-1-openwrt-working/2218|in the forum]] and [[https://bugs.openwrt.org/index.php?do=details&task_id=872|the bug tracker]] |
| | * OpenWrt 18.06.X as documented [[https://forum.openwrt.org/t/archer-c7-v1-0-crashes-on-boot/19784|in the forum]] and [[https://bugs.openwrt.org/index.php?do=details&task_id=1743|the bug tracker]] |
| | </WRAP> |
| | |
| | Last known good firmware images are Chaos Calmer 15.05.1. |
| | |
| | === Installation of TP-Link Archer C7 V2 === |
| (Updated and tested on March 2017 by orenr) | (Updated and tested on March 2017 by orenr) |
| |
| Error code: 18005 | Error code: 18005 |
| Upgrade unsuccessfully because the version of the upgraded file was incorrect. Please check the file name. | Upgrade unsuccessfully because the version of the upgraded file was incorrect. Please check the file name. |
| | |
| | For TP-Link Archer C7 v2.0, it is enough just to rename the factory image to something like ''factory.bin'', then just upload it via the OEM web interface like a firmware upgrade. Note that if your router says US, EU, or IL on the sticker on the bottom, you might need a different image than the image linked in the tables above. The images in the table above are for "rest of world" routers. If you browse to the parent directory of the linked images, you'll see the appropriate US, EU, or IL .bin file. (tested by tp-linked on May 2018) |
| |
| For TP-Link Archer C7 v2.1 it is enough just to rename the factory image to something like ''factory.bin'', then just upload it like a firmware upgrade. | For TP-Link Archer C7 v2.1 it is enough just to rename the factory image to something like ''factory.bin'', then just upload it like a firmware upgrade. |
| Use the following workaround (based on https://www.gargoyle-router.com/phpbb/viewtopic.php?f=8&t=8210) | Use the following workaround (based on https://www.gargoyle-router.com/phpbb/viewtopic.php?f=8&t=8210) |
| |
| **1.Download appropriate modified version of DDWRT that passes the TP-Link verification:** | == 1.Download appropriate modified version of DDWRT that passes the TP-Link verification: == |
| |
| (Based on http://www.dd-wrt.com/phpBB2/viewtopic.php?p=998919&sid=9bd1c67b9e96384f914718a843aa2ea4) | (Based on http://www.dd-wrt.com/phpBB2/viewtopic.php?p=998919&sid=9bd1c67b9e96384f914718a843aa2ea4) |
| Flash the DD-WRT firmware. Please note that TP-Link defaults to 192.168.0.1, but DD-WRT defaults to 192.168.1.1, so make sure to reconnect the Ethernet cable if your DHCP client cannot figure it out. | Flash the DD-WRT firmware. Please note that TP-Link defaults to 192.168.0.1, but DD-WRT defaults to 192.168.1.1, so make sure to reconnect the Ethernet cable if your DHCP client cannot figure it out. |
| |
| **2.Flash TP-Link reverted FW:** | == 2.Flash TP-Link reverted FW:== |
| |
| Now you need to flash an older version of the vendor firmware, which doesn't check the file signatures. | Now you need to flash an older version of the vendor firmware, which doesn't check the file signatures. |
| The router is back on 192.168.0.1 now. | The router is back on 192.168.0.1 now. |
| |
| **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'' |
| |
| * Trunk (for all serial numbers): https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/openwrt-ar71xx-generic-archer-c7-v2-squashfs-factory.bin | === Installation and upgrade of TP-Link Archer C7 V3 === |
| * Chaos Calmer 15.5.01 (for serial numbers prior to 215C) https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/openwrt-15.05.1-ar71xx-generic-archer-c7-v2-squashfs-factory.bin | (Updated and tested install on February 2020 by zenith828) |
| | |
| Before flashing, rename the downloaded file to make it shorter and remove all dots except one, e.g. ''firmware.bin'' | |
| |
| ==== 5G Wifi Problems / 5GHz network controller not identified ==== | I followed the instructions for installing Archer C7 V4 (see below) successfully. |
| |
| When OpenWrt Designated Driver 50104 was installed, for example, No 5GHz network controller has been identified. (/etc/config/wireless does not contain the 5GHz radio controller). | 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. |
| |
| Be sure you have installed the firmware package for ath10k . ath10k-firmware-qca988x_*.ipk | 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. |
| The files are in /lib/firmware | |
| |
| View with ''dmesg'' about kernel firmware loading. There should not be warnings like: cant load firmware-*.bin | === Installation and upgrade of TP-Link Archer C7 V4 === |
| | (Updated and tested install on June 2018 + upgrade 2019 by arberg) |
| |
| **To fix that (Archer C7 v2)** | * Download current release (see table above or [[toh/views/toh_fwdownload?dataflt%5BModel*~%5D=Archer+c7+ac1750&dataflt%5BVersions*~%5D=v4|firmware downloads here]]) |
| | * Rename to for instance firmware.bin |
| | * Install OpenWrt by choosing Upgrade via Router Stock WebUi |
| |
| ''opkg update | I used newest TP-Link firmware when I did the update, in other words I had let TP Link update its original firmware first. This is probably not necessary. The 8 MB Archer C7 v2 file will not install on the C7 v4. |
| opkg install kmod-ath10k | |
| opkg install ath10k-firmware-qca988x | |
| rm /etc/config/wireless && wifi detect > /etc/config/wireless | |
| cat /etc/config/wireless | |
| reboot'' | |
| |
| Reference - Archer C7 missing ath10 firmware - https://dev.openwrt.org/ticket/21527 | * **OpenWrt Upgrade** |
| | * Luci > System > Backup/flash firmware > Flash new firmware image |
| | * Choose sysupgrade image, and choose the `openwrt-<version>-ar71xx-generic-archer-c7-v4-squashfs-sysupgrade.bin` file |
| |
| ===== Hardware ===== | === Installation of TP-Link Archer C7 V5 via webUI === |
| ==== Info ==== | (Updated and tested on February 2019 by casta) |
| Table does not describe TL-WDR7500 v3.x or Archer C5 v2.x | |
| | **Version:** | **TL-WDR7500 v2.x (Archer C7R)** | **Archer C7 v1.x** | **Archer C7 v2.x / C5** | **TL-WDR7500 v4.x (Archer C7R)** | | |
| | **[[wp>Instruction set]]:** | [[wp>MIPS architecture|MIPS]] |||| | |
| | **Vendor:** | [[wp>Qualcomm Atheros]] |||| | |
| | **[[doc:techref:Bootloader]]:** | [[doc:techref:bootloader:uboot|U-Boot]] (press **tpl** to enter U-Boot console on OEM firmware) |||| | |
| | **[[doc:hardware:soc|System-On-Chip]]:** | QCA9558 (QCA9558-AT4A) 3x3 a/b/g/n (b/g/n, in this instance) |||| | |
| | **[[doc:hardware:cpu|CPU]]/Speed:** | MIPS74Kc@720 MHz |||| | |
| | **Flash Chip:** | cFeon Q64-104HIP || Winbond W25Q128FV | Winbond W25Q64FV | | |
| | **Flash Specs:** | 8 MiB SPI || 16 MiB SPI (14.3MHz) | 8MiB SPI | | |
| | **RAM Chip:** | Hynix H5PS5162GFR-Y5C x 2 | Winbond W9751G6KB-25 x 2 ||| | |
| | **RAM Specs:** | 128 MiB |||| | |
| | **Wireless No1:** | Integrated: QCA9558 3x3 b/g/n |||| | |
| | **Wireless No2:** | MiniPCIe: QCA9880-AR1A (v1) 3x3 a/n/ac PCIe radio || MiniPCIe: QCA9880-BR4A (v2) 3x3 a/n/ac PCIe radio | QCA9880-BR4A (v2) 3x3 a/n/ac | | |
| | **[[doc:hardware:Switch]]:** | GbE [[https://wikidevi.com/files/Atheros/specsheets/AR8327_AR8327N.pdf?|AR8327N-AL1A]] || GbE [[https://wikidevi.com/files/Atheros/specsheets/AR8327_AR8327N.pdf?|AR8327N-BL1A]] || | |
| | **USB:** | 2 x USB 2.0 |||| | |
| | **Power:** | External 12V 2.5A ||| External 12V 2.0A | | |
| | **Serial:** | [[#Serial|Yes]] |||| | |
| | **JTAG:** | Yes |||| | |
| |
| === Flash backup === | * Download current release (see table above) |
| | * Rename to for instance firmware.bin |
| | * Upgrade via Router webui |
| |
| I need to remove the Flashchip from the mainboard to connect it to a spi-programmer. I used flashrom ( https://flashrom.org ) to read out the flash chip. Dont forget to connect the /WP and /RESET Pin to VCC!\\ | I used an European original firmware (out of the box) when I did the update. WebUI install is working nicely. |
| **''flashrom -p ft2232_spi:type=openmoko,divisor=2 -r flash-chip-backup.img''**\\ | |
| Read it two times with different divisors. Then compare both files with ''diff''. The newest Version of flashrom supports both 16M flash chips. | |
| |
| Is some one have a solution to read it in place over jtag? The VCC connection seem to be direct to the power supply. The programmer need to powers all 3.3V components. But then the cpu could start working... | == User confirmations for webUI method == |
| ==== Power Consumption ==== | ^ Date ^ User ^ Tested OpenWRT version ^ HW Version ^ Stock firmware ^ |
| The included power supply is rated at 2.5A at 12V (30W), but the router does not draw anywhere near the 30 Watts deliverable by that supply. The extra capacity is useful for powering USB devices, however. The following are power measurements taken of an Archer C7 AC1750 V2.0 measuring current over the DC wires. The AC/DC adapter outputs 12.2V loaded. A Kill-A-Watt power meter was used to confirm the measurements and showed the AC/DC adapter was fairly efficient. | | 2019-02 | casta | | v5 | | |
| | | 2019-06-01 | nuv | 18.06.2 (openwrt-18.06.2-ar71xx-generic-archer-c7-v5-squashfs-factory.bin) | v5.0 (EU) | 1.0.4 Build 20180425 rel.72768(4555) | |
| | | 2019-07-19 | pkos98| 18.06.4 (openwrt-18.06.4-ar71xx-generic-archer-c7-v5-squashfs-factory.bin) | v5.0 (EU) | | |
| | | 2019-10-13 | scolytus| 18.06.4 (openwrt-18.06.4-ar71xx-generic-archer-c7-v5-squashfs-factory.bin) | v5.0 (EU) | 1.0.4 Build 20180425 rel.72768(4555) | |
| |
| | === Installation of TP-Link Archer C7 V5 via TFTP === |
| | (Updated and tested on November 2018 by mac_low) |
| |
| * Stock firmware measurements | * Download current release (see table above) |
| * booting draws between 2.4 and 3.5 W | * Rename to for instance ArcherC7v5_tp_recovery.bin |
| * idle power 2.4 W | * Set TFTP server under IP:192.168.0.66 with this ArcherC7v5_tp_recovery.bin on the root |
| * downloading file over 2.4 GHz 3.6 W | * Turn off the router |
| * downloading over both 2.4 and 5 GHz 4.1 W | * Press and hold Reset button |
| * flashing firmware 4.4 W | * Turn on router with the reset button pressed and wait 5-10 seconds |
| * OpenWrt firmware | * Release the reset button and after a short time the firmware should be transferred from the tftp server |
| * idle power 2.2 to 2.4 W | * Wait ~30 second to complete recovery |
| * downloading via wifi at 12 Mbps through router instance of OpenVPN w/compression 3.1 W | |
| * idle with all gigabit ports connected and both wlans enabled: 5.5 W | |
| |
| | 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. |
| |
| ===== Configuration ===== | ==== Archer C7R ==== |
| | <!-- ToH: { |
| | "source": "json", |
| | "dom": "t", |
| | "paging": false, |
| | "rotate": true, |
| | "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], |
| | "filterColumns": {"model": "^Archer C7R.*$"} |
| | } --> |
| |
| ==== Port Map ==== | === Installation of TP-Link WDR7500 V3 via TTL and TFTP === |
| * [[https://dev.openwrt.org/changeset/37507|switch port map]] | - 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 |
| |
| Switch Ports: | ==== 5G Wifi Problems / 5GHz network controller not identified ==== |
| | 0 | eth1 | | |
| | 1 | WAN | | |
| | 2 | LAN1 | | |
| | 3 | LAN2 | | |
| | 4 | LAN3 | | |
| | 5 | LAN4 | | |
| | 6 | eth0 | | |
| |
| {{:media:tplink:tl-wdr7500:archerc7v2-switch-diagram.png?600|}} | When OpenWrt Designated Driver 50104 was installed, for example, no 5GHz network controller was detected (''/etc/config/wireless'' did not contain the 5GHz radio controller). |
| ==== VLAN Tagging for WAN ==== | |
| Note that the WAN port is port #1 and connected to eth0.\\ | |
| To tag the WAN port create the VLAN ID under "Network => Switch" and assign it to "Port #1" and "Port #6". | |
| Under "Network => Interface" edit the "WAN" interface and for its "Physical Settings" use eth0.<VLAN ID>\\ | |
| Example: VLAN ID 7 for German Telekom VDSL would be eth0.7 | |
| |
| ==== Flash Layout ==== | To fix, install proper kernel module and firmware packages for your 5GHz WLAN hardware (see tech specs of your Archer model), e.g. for C5 v1 and some C7 versions you would use: |
| |
| ^ 8MB Flash Chip ^^ | ''opkg update |
| | ''0x000000000000-0x000000020000'' | "u-boot" | | opkg install kmod-ath10k |
| | ''0x000000020000-0x000000120000'' | "kernel" | | opkg install ath10k-firmware-qca988x |
| | ''0x000000120000-0x0000007e0000'' | "rootfs" | | rm /etc/config/wireless && wifi detect > /etc/config/wireless |
| | ''0x0000007e0000-0x0000007f0000'' | "config" | | cat /etc/config/wireless |
| | ''0x0000007f0000-0x000000800000'' | "ART" | | reboot'' |
| |
| ^ 16MB Flash Chip (Archer C7 V2) ^^ | On release 18.xx and later, ''wifi detect'' has been deprecated. Use ''wifi config'' instead - it will generate ''/etc/config/wireless'' for you. |
| | ''0x000000000000-0x000000020000'' | "u-boot" | | |
| | ''0x000000020000-0x000000120000'' | "kernel" | | Review //Kernel log// with ''dmesg''. There can still be warnings like //Direct firmware load for ath10k....bin failed//, just make sure the device is properly detected in the end. Some firmwares reject to load unless you configure the wifi device country code to the value they suggest in the log (e.g. set ''option country 'US' '' in ''/etc/config/wireless''). |
| | ''0x000000120000-0x000000fa0000'' | "rootfs" | | |
| | ''0x000000fa0000-0x000000ff0000'' | "config" | | Reference - [[https://dev.openwrt.org/ticket/21527|Archer C7 missing ath10 firmware]] |
| | ''0x000000ff0000-0x000001000000'' | "ART" | | |
| ==== Entering Failsafe Mode on Archer C5 ==== | ==== Entering Failsafe Mode on Archer C5 or Archer C7 ==== |
| To enter Failsafe-Mode press the WPS/Reset Button rapidly after starting the router. Stop when the second LED (from left) starts flashing very rapidly. Continue [[doc:howto:generic.failsafe|here]] and [[doc:howto:generic.failsafe#In failsafe mode|here when already logged in in failsafe mode]]. | To enter Failsafe-Mode press the WPS/Reset Button rapidly after starting the router. Stop when the second LED (from left) starts flashing very rapidly. Continue [[docs:guide-user:troubleshooting:failsafe_and_factory_reset|here]] and [[docs:guide-user:troubleshooting:failsafe_and_factory_reset#In failsafe mode|here when already logged in in failsafe mode]]. |
| | |
| | If your timing is good, you can save your finger. On power-up, an Archer C7 v2 will do a "light test" and shortly thereafter the power ("sun") light will go off. It will then start flashing several times per second, for a period of a couple seconds. If you're running a recent build of OpenWrt (tested in March 2018), during that window indicated by fast-flashing, a single click of the WPS/Reset button will get you into failsafe mode. Success in entering failsafe mode is indicated by the power light flashing even faster. If the power light goes to a slower flashing rate or steady on, the window to enter failsafe mode has closed. |
| |
| ==== Return to Factory Firmware ==== | ==== Return to Factory Firmware ==== |
| **The following instruction also works on V2** | **The following instruction also works on V2** |
| |
| -> [[docs:user-guide:generic.uninstall]] | -> [[docs:guide-user:installation:generic.uninstall]] |
| |
| {{page>meta:infobox:dangerous&noheader&nofooter&noeditbtn}} | {{page>meta:infobox:dangerous&noheader&nofooter&noeditbtn}} |
| |
| Obtain the factory firmware from the OEM: | Obtain the factory firmware from the OEM: |
| http://www.tplink.com/en/support/download/?model=Archer+C7 | [[http://www.tplink.com/en/support/download/?model=Archer+C7]] |
| |
| * UNTESTED 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 | * (tested on archer c5 v2) 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: |
| |
| ==== 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''. |
| | |
| | Setup your computer to 192.168.0.66 or 192.168.1.66 as appropriate for your version (SubnetMask /24 = 255.255.255.0) and connect it to LAN1. Start TFTP server (e.g. [[https://www.cyberciti.biz/faq/install-configure-tftp-server-ubuntu-debian-howto/|tftpd-hpa on debian]]) and provide recovery file with it. An Archer C7 will repeatedly try at 5-second intervals to connect to the TFTP server if you have the "wrong" address. |
| |
| To activate TFTP Recovery press and hold WPS/Reset Button during powering on until WPS LED turns on. | To activate TFTP Recovery press and hold WPS/Reset Button during powering on until WPS LED turns on. |
| Setup your computer to 192.168.0.66 (SubnetMask /24 = 255.255.255.0) and connect it to LAN1. | |
| Start TFTP server and provide recovery file with it. | |
| |
| For de-bricking with an OpenWrt image use the factory.bin image. | For de-bricking with an OpenWrt image use the factory.bin image. |
| |
| <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 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.) 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. | 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.) |
| |
| The TX pullup is most likely needed in version 2 models of revision B (serial beginning with 215B...), 16MB flash memory. 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: | 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]]. 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): |
| |
| <code> | <code> |
| R (~800 Ohms) ------------- | R (~800 Ohms) ------------- |
| /---\/\/\/`--- 3.3V --| USB FTDI | | /---\/\/\/`------ VCC --RED--| USB FTDI | |
| ----------- | | 3.3V | | ----------- | | 3.3V | |
| |Archer V2|-- RX --+--------------- TX --| | --> to PC (minicom, screen, C-Kermit, ...) | |Archer V2|-- RX --+----------------- TX --ORA--| | --> to PC (minicom, screen, C-Kermit, ...) |
| |serial |-- TX ------------------ RX --| | | |serial |-- TX -------------------- RX --YLW--| | |
| | |-- GND ---------------- GND --| | | | |-- GND ------------------ GND --BLK--| | |
| ----------- ------------- | ----------- ------------- |
| </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: |
| reset | reset |
| </code> | </code> |
| | |
| | ===== Hardware ===== |
| | ==== Info ==== |
| | | **Version:** | **TL-WDR7500 v2.x (Archer C7R)** | **Archer C7 v1.x** | **Archer C7 v2.x / C5** | **TL-WDR7500 v4.x (Archer C7R)** | |
| | | **[[wp>Instruction set]]:** | [[wp>MIPS architecture|MIPS]] |||| |
| | | **Vendor:** | [[wp>Qualcomm Atheros]] |||| |
| | | **[[docs:techref:bootloader]]:** | [[docs:techref:bootloader:uboot|U-Boot]] (type **tpl** to enter U-Boot console on OEM firmware) |||| |
| | | **[[docs:techref:hardware:soc|System-On-Chip]]:** | QCA9558 (QCA9558-AT4A) 3x3 a/b/g/n (b/g/n, in this instance) |||| |
| | | **[[docs:techref:hardware:cpu|CPU]]/Speed:** | MIPS74Kc@720 MHz |||| |
| | | **Flash Chip:** | cFeon Q64-104HIP || Winbond W25Q128FV | Winbond W25Q64FV | |
| | | **Flash Specs:** | 8 MiB SPI || 16 MiB SPI (14.3MHz) | 8MiB SPI | |
| | | **RAM Chip:** | Hynix H5PS5162GFR-Y5C x 2 | Winbond W9751G6KB-25 x 2 ||| |
| | | **RAM Specs:** | 128 MiB |||| |
| | | **Wireless No1:** | Integrated: QCA9558 3x3 b/g/n |||| |
| | | **Wireless No2:** | MiniPCIe: QCA9880-AR1A (v1) 3x3 a/n/ac PCIe radio || MiniPCIe: QCA9880-BR4A (v2) 3x3 a/n/ac PCIe radio | QCA9880-BR4A (v2) 3x3 a/n/ac | |
| | | **[[docs:techref:hardware:switch]]:** | GbE [[https://wikidevi.com/files/Atheros/specsheets/AR8327_AR8327N.pdf?|AR8327N-AL1A]] || GbE [[https://wikidevi.com/files/Atheros/specsheets/AR8327_AR8327N.pdf?|AR8327N-BL1A]] || |
| | | **USB:** | 2 x USB 2.0 |||| |
| | | **Power:** | External 12V 2.5A ||| External 12V 2.0A | |
| | | **Serial:** | [[#Serial|Yes]] |||| |
| | | **JTAG:** | Yes |||| |
| | |
| | |
| | Information about WDR-7500 Ver 6.0. |
| | China |
| | |
| | ^ Brand^ Model ^ Versions^ SoC^ USB ^ Serial ^ JTag ^ Aditional WIFI Chip ^ Ethernet ^ RAM ^ Flash^ |
| | | TP-Link| WDR-7500|6.0 (CN)|QCA9563-AL3A| NO | Yes | ? |QCA9880-BR4A | RTL8367S Gigabit Switch 1WAN + 4 LAN| W9751G6KB-25|25Q64CSIG (BH1621)| |
| | |
| | PCB |
| | http://oi66.tinypic.com/2uzsegy.jpg |
| | |
| | QCA9563-AL3A MIPS CPU |
| | http://i66.tinypic.com/o70ft1.jpg |
| | |
| | QCA9880-BR4A |
| | http://i65.tinypic.com/awt8hx.jpg |
| | |
| | RTL8367S Gigabit Switch |
| | http://i67.tinypic.com/21eb5w6.jpg |
| | |
| | One memory chip WinBond |
| | W9751G6KB-25 RAM |
| | http://i63.tinypic.com/wvqszb.jpg |
| | |
| | Flash Chip |
| | 25Q64CSIG (BH1621) |
| | http://i65.tinypic.com/9asmqh.jpg |
| | |
| | UART J1 |
| | http://i67.tinypic.com/s1tjlk.jpg |
| | |
| | Here is Forum topic about it - [[https://forum.openwrt.org/viewtopic.php?pid=336271#p336271]] |
| | |
| | ==== Flash Layout ==== |
| | |
| | ^ 8MB Flash Chip ^^ |
| | | ''0x000000000000-0x000000020000'' | "u-boot" | |
| | | ''0x000000020000-0x000000120000'' | "kernel" | |
| | | ''0x000000120000-0x0000007e0000'' | "rootfs" | |
| | | ''0x0000007e0000-0x0000007f0000'' | "config" | |
| | | ''0x0000007f0000-0x000000800000'' | "ART" | |
| | |
| | ^ 16MB Flash Chip (Archer C7 V2) ^^ |
| | | ''0x000000000000-0x000000020000'' | "u-boot" | |
| | | ''0x000000020000-0x000000120000'' | "kernel" | |
| | | ''0x000000120000-0x000000fa0000'' | "rootfs" | |
| | | ''0x000000fa0000-0x000000ff0000'' | "config" | |
| | | ''0x000000ff0000-0x000001000000'' | "ART" | |
| | |
| | |
| | ==== Flash backup ==== |
| | |
| | I need to remove the Flashchip from the mainboard to connect it to a spi-programmer. I used flashrom ([[https://flashrom.org]]) to read out the flash chip. Dont forget to connect the /WP and /RESET Pin to VCC!\\ |
| | **''flashrom -p ft2232_spi:type=openmoko,divisor=2 -r flash-chip-backup.img''**\\ |
| | Read it two times with different divisors. Then compare both files with ''diff''. The newest Version of flashrom supports both 16M flash chips. |
| | |
| | Is some one have a solution to read it in place over jtag? The VCC connection seem to be direct to the power supply. The programmer need to powers all 3.3V components. But then the cpu could start working... |
| | |
| | ==== Power Consumption ==== |
| | The included power supply is rated at 2.5A at 12V (30W), but the router does not draw anywhere near the 30 Watts deliverable by that supply. The extra capacity is useful for powering USB devices, however. The following are power measurements taken of an Archer C7 AC1750 V2.0 measuring current over the DC wires. The AC/DC adapter outputs 12.2V loaded. A Kill-A-Watt power meter was used to confirm the measurements and showed the AC/DC adapter was fairly efficient. |
| | |
| | |
| | * Stock firmware measurements |
| | * booting draws between 2.4 and 3.5 W |
| | * idle power 2.4 W |
| | * downloading file over 2.4 GHz 3.6 W |
| | * downloading over both 2.4 and 5 GHz 4.1 W |
| | * flashing firmware 4.4 W |
| | * OpenWrt firmware |
| | * idle power 2.2 to 2.4 W |
| | * downloading via wifi at 12 Mbps through router instance of OpenVPN w/compression 3.1 W |
| | * idle with all gigabit ports connected and both wlans enabled: 5.5 W |
| | |
| ==== Benchmarks ==== | ==== Benchmarks ==== |
| |
| * EXT2 USB -> Router -> FTP (unencrypted) -> PC : 14.9-15.5MB/s | * EXT2 USB -> Router -> FTP (unencrypted) -> PC : 14.9-15.5MB/s |
| * Router /dev/zero -> EXT2 USB : 10-19,42MB/s (depending on BS parameter of dd) | * Router /dev/zero -> EXT2 USB : 10-19,42MB/s (depending on BS parameter of dd) |
| | |
| | ===== Configuration ===== |
| | |
| | ==== Port Map ==== |
| | * [[https://dev.openwrt.org/changeset/37507|switch port map]] |
| | |
| | Switch Ports: |
| | | 0 | eth1 | |
| | | 1 | WAN | |
| | | 2 | LAN1 | |
| | | 3 | LAN2 | |
| | | 4 | LAN3 | |
| | | 5 | LAN4 | |
| | | 6 | eth0 | |
| | |
| | {{: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 ==== |
| | |
| | At least on a v2 device, there are only 128 VLAN "slots" available. If configuration of VLAN tags above 127 is required, the `vid` option will be required. See [[docs:guide-user:base-system:basic-networking#switch_configuration]] for further details. |
| | |
| | === Tagging "WAN" Interface for ISP Connectivity === |
| | Note that the WAN port is port #1 and connected to eth0.\\ |
| | To tag the WAN port create the VLAN ID under "Network => Switch" and assign it to "Port #1" and "Port #6". |
| | Under "Network => Interface" edit the "WAN" interface and for its "Physical Settings" use eth0.<VLAN ID>\\ |
| | Example: VLAN ID 7 for German Telekom VDSL would be eth0.7 |
| | |
| |
| ===== Photos ===== | ===== Photos ===== |
| {{http://wikidevi.com/w/images/0/0c/TL-WDR7500_8.jpg?400|TP-Link TL-WDR7500 QCA9880-AR1A over MiniPCIe}} | {{http://wikidevi.com/w/images/0/0c/TL-WDR7500_8.jpg?400|TP-Link TL-WDR7500 QCA9880-AR1A over MiniPCIe}} |
| |
| | FIXME: Information on the pinout of JP4 would be helpful |
| ==== WDR7500 v3 ==== | ==== WDR7500 v3 ==== |
| {{media:tplink:tl-wdr7500:tl-wdr7500-v3_pcb_top2.jpg?400}} | {{media:tplink:tl-wdr7500:tl-wdr7500-v3_pcb_top2.jpg?400}} |
| {{media:tplink:tl-wdr7500:tl-wdr7500-v3_pcb_bottom2.jpg?400}} | {{media:tplink:tl-wdr7500:tl-wdr7500-v3_pcb_bottom2.jpg?400}} |
| |
| |
| ==== Serial ==== | ==== Serial ==== |
| | === Archer C5 v2 === |
| | {{:media:tplink:archerc5:pinout-serial-archer-c5-v2.jpg?direct&400|}} |
| | |
| | Configure your favorite terminal with the following settings: 115200 baud, 8 bit, no parity, 1 stop bit, no flow control. |
| | |
| === WDR7500 v2 / Archer C7 v2 === | === WDR7500 v2 / Archer C7 v2 === |
| {{media:tplink:tl-wdr7500:tl-wdr7500_serial_pinout.jpg?400|}} | {{media:tplink:tl-wdr7500:tl-wdr7500_serial_pinout.jpg?400|}} |
| <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 condensator, 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> |
| |
| I don't know what to really call this. I've been told on IRC that it is more like the WDR-7500. See the label pic and decide for yourself: | I don't know what to really call this. I've been told on IRC that it is more like the WDR-7500. See the label pic and decide for yourself: |
| |
| {{:media:tplink:tplink_archer_c7_v4.0_us.jpg?400|}} | {{media:tplink:archer_c7_v4_us.jpg?400|}} |
| |
| Here is a full board pic: | Here is a full board pic: |
| |
| {{:media:tplink:tplink_archer_c7_v4.0_us-full.jpg?400|}} | {{media:tplink:archer_c7_v4_us_full.jpg?400|}} |
| |
| And zoomed in on the chips so they're readable: | And zoomed in on the chips so they're readable: |
| |
| {{:media:tplink:tplink_archer_c7_v4.0_us-chips.jpg?400|}} | {{media:tplink:archer_c7_v4_us_chips.jpg?400|}} |
| |
| In the lower right is the serial header. The first through hole is TX, second RX and third GROUND. There were two missing resistors at R27 and R24. I placed a 10K on R27 and a 1K on R24 (total shot in the dark based on some reading I had done, but it works). The RX through hole didn't seem to be connected to the right side of the R24 pad so it's got a solder bridge. Use 115200, 8N1, no flow control. | In the lower right is the serial header. The first through hole is TX, second RX and third GROUND. There were two missing resistors at R27 and R24. I placed a 10K on R27 and a 1K on R24 (total shot in the dark based on some reading I had done, but it works). The RX through hole didn't seem to be connected to the right side of the R24 pad so it's got a solder bridge. Use 115200, 8N1, no flow control. |
| (FYI: from TP-Link engineering, R24 = 220R, R27 = 1K) | (FYI: from TP-Link engineering, R24 = 220R, R27 = 1K) |
| |
| {{:media:tplink:tplink_archer_c7_v4.0_us-serial.jpg?400|}} | {{media:tplink:archer_c7_v4_us_serial.jpg?400|}} |
| | |
| | === Archer C7 v5.0 (EU) === |
| | |
| | As I didn't have 0402 sized resistors at home, I've used just one 0603 of 180R value. |
| | |
| | {{:media:tplink:archerc7:archer-c7-v5-eu-uart.jpg?400|}} |
| |
| ==== JTAG ==== | ==== JTAG ==== |
| |
| ===== Tags ===== | ===== Tags ===== |
| {{tag>GigabitEthernet 2NIC 2WNIC 5Port 74Kc 128ram 8flash 16flash 2usb ap135 qca9558 qca9880 802.11ac ath10k 802.11n 802.11g 802.11b 802.11a simultan MiniPCIexpress QCA9563}} | {{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}} |