Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
toh:tp-link:archer-c5-c7-wdr7500 [2020/12/29 13:24] – [Supported Versions] Tidied up the supported versions table that's not sourced from the datatables. Replaced another stale SVN trunk / 15.05.1 reference. Corrected some Engrish. Replaced another stale Wikidevi link. borrominitoh:tp-link:archer-c5-c7-wdr7500 [2024/02/13 16:13] – [Archer C7] - rotate table jow
Line 1: Line 1:
-la====== TP-Link Archer C5 AC1200 / TP-Link Archer C7 AC1750 / TP-Link TL-WDR7500  ======+====== TP-Link Archer C5 AC1200 / TP-Link Archer C7 AC1750 / TP-Link TL-WDR7500  ======
 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]] //
  
Line 5: Line 5:
 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>
  
Line 25: Line 25:
 **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>
- 
- 
  
  
Line 34: Line 32:
  
 ===== Supported Versions ===== ===== Supported Versions =====
----- datatable ---- +<!-- ToH: { 
-cols    ModelVersionsSupported Current RelOEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid +  "source""json", 
-headers ModelVersion, 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    ModelVersionsSupported Current RelOEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid +  "source""json", 
-headers ModelVersion, 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    ModelVersionsSupported Current RelOEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid +  "source""json", 
-headers ModelVersion, 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     ^
Line 73: Line 74:
  
 ===== Hardware Highlights ===== ===== Hardware Highlights =====
----- datatable ---- +<!-- ToH: { 
-cols    ModelVersionsCPU, CPU MHz, Flash MB_mbflashs, RAM MB_mbram, WLAN Hardware, WLAN 2.4Ghz, WLAN 5.0Ghz, Ethernet 100M ports_, Ethernet Gbit ports_, ModemUSB ports_ +  "source""json", 
-header  : ModelVersion,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====
Line 98: Line 99:
 </tabbox> </tabbox>
  
-[[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 +[[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 runninglimited to about the following throughput: 
-  * 300 Mbps without SQM, 600 Mbps with software flow offload enabled (v19 and later+ 
-  * 150-200 Mbps with SQM+|   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                   | 
  
 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.
Line 131: Line 159:
  
 ==== Archer C5 ==== ==== Archer C5 ====
----- datatable ---- +<!-- ToH: { 
-cols    ModelVersionsSupported Current RelFirmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_urlFirmware 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    ModelVersionsSupported Current RelFirmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_urlFirmware 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 ===
Line 247: Line 279:
  
 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    ModelVersionsSupported Current RelFirmware 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 upTested by Mats, 2021-01-17
  
 ==== 5G Wifi Problems / 5GHz network controller not identified ==== ==== 5G Wifi Problems / 5GHz network controller not identified ====
Line 319: Line 364:
 ==== 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''.
Line 379: Line 424:
 </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:
Line 517: Line 562:
  
 {{: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 ====
Line 1890: Line 1937:
  
 ===== 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}}
  • Last modified: 2024/10/12 15:51
  • by noki