Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:tp-link:archer_c2_ac750 [2018/05/28 17:35] – ↷ Page name changed from toh:tp-link:ac750 to toh:tp-link:archer_c2_ac750 tmomas | toh:tp-link:archer_c2_ac750 [2022/06/29 14:20] – [Switch] Add more details about using VLAN IDs above 31 in the outer switch configuration znark | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== TP-Link Archer C2 AC750 ====== | ====== TP-Link Archer C2 AC750 ====== | ||
| - | ===== Info ===== | + | {{:media:tplink:archer-c2-v1:archer-c2-ac750-v1.png?300}} |
| - | | **[[wp> | + | |
| - | | **Vendor:** | [[wp> | + | |
| - | | **[[docs:techref: | + | |
| - | | **[[docs: | + | |
| - | | **[[docs: | + | |
| - | | **Flash-Chip: | + | |
| - | | **Flash size: | + | |
| - | | **RAM: | + | |
| - | | **Wireless No1: | + | |
| - | | **Wireless No2: | + | |
| - | | **[[docs: | + | |
| - | | **USB: | + | |
| - | | **[[docs: | + | |
| - | ===== Serial ====== | + | <WRAP 80%> |
| + | <tabbox Hardware Highlights> | ||
| + | ---- datatable ---- | ||
| + | cols : Model, Versions, CPU, CPU MHz, Flash MB_mbflashs, | ||
| + | header | ||
| + | align : c, | ||
| + | filter | ||
| + | filter | ||
| + | ---- | ||
| + | <tabbox OpenWrt support> | ||
| + | ---- datatable ---- | ||
| + | cols : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWRT Forum Topic URL_url, Device Techdata_pageid | ||
| + | headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data | ||
| + | align : c, | ||
| + | filter | ||
| + | filter | ||
| + | ---- | ||
| - | Serial port: | + | <tabbox Hardware details> |
| + | ^ [[wp> | ||
| + | ^ Vendor | ||
| + | ^ [[docs:techref: | ||
| + | ^ [[docs: | ||
| + | ^ [[docs: | ||
| + | ^ Flash-Chip | ||
| + | ^ Flash size | 8192 KiB | | ||
| + | ^ RAM | 64 MiB | | ||
| + | ^ Wireless No1 | SoC-integrated: | ||
| + | ^ Wireless No2 | On-board chip: MT7610EN 5GHz 802.11ac | | ||
| + | ^ [[docs: | ||
| + | ^ USB | Yes 1 x 2.0 | | ||
| + | ^ [[docs: | ||
| - | ethernet | + | <tabbox Firmware downloads> |
| + | ---- datatable ---- | ||
| + | cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | ||
| + | headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock | ||
| + | align : c,c,c | ||
| + | filter | ||
| + | filter | ||
| + | ---- | ||
| + | </ | ||
| + | </WRAP> | ||
| - | On some versions you need to solder 2 bridges to get serial port working. You need good soldering experiences for that! | + | ===== Installation ===== |
| + | -> [[docs: | ||
| + | <WRAP center round important 60%> | ||
| + | The following procedure is known to work only on the **<color # | ||
| + | </ | ||
| + | |||
| + | As per the instructions in the [[https:// | ||
| + | OpenWrt 19.07.1 can be flashed via TFTP using an unofficial recovery image provided [[https:// | ||
| + | |||
| + | ==== Creating an OpenWrt TFTP recovery image ==== | ||
| + | <WRAP center round important 60%> | ||
| + | The following instructions might break your router. | ||
| + | Use only the provided recovery image if you don't understand what is going on. | ||
| + | |||
| + | Avoid renaming any arbitrary image to ArcherC2V1_tp_recovery.bin. | ||
| + | Providing an image without proper bootloader to TFTP recovery bricks your router and needs flashing with a SPI programmer. | ||
| + | </ | ||
| + | |||
| + | If you feel uncomfortable doing this, grab the prepped 19.07.1 image linked to above and skip this section. | ||
| + | |||
| + | The C2v1 TFTP recovery overwrites the uboot partition, hence it must be included in a recovery.bin | ||
| + | An official stock TPLink firmware file has a 512 byte header, which needs to be stripped for TFTP. | ||
| + | You need access to a Linux box for this procedure (Windows Subsystem for Linux (' | ||
| + | Instructions below are taken from the git commit that added support into OpenWrt. | ||
| + | |||
| + | 1. Download a stock TP-Link Firmware file [[https:// | ||
| + | |||
| + | 2. Extract u-boot from the binary file: | ||
| + | |||
| + | < | ||
| + | |||
| + | 3. Now merge the OpenWrt **sysupgrade** image and the u-boot into one binary: | ||
| + | |||
| + | < | ||
| + | |||
| + | ==== Flashing OpenWRT ==== | ||
| + | |||
| + | * Set your computer' | ||
| + | * To flash the recovery image, start a TFTP server from IP address 192.168.0.66 and serve the recovery image named ' | ||
| + | * Connect your device to the LAN port, then press the WPS/Reset button and power it up. Keep pressing the WPS/Reset button for 10 seconds | ||
| + | * The device will try to download the recovery image and flash it. This might take up to 20-25 minutes to finish. When done, the router will reboot itself. | ||
| + | * After reboot, you can access OpenWrt at 192.168.1.1. From here on out, you can simply use sysupgrade with the **vanilla** OpenWrt images to upgrade. | ||
| + | |||
| + | <WRAP center round info 95%> | ||
| + | Remember to allow access to your TFTP server program in firewall settings. (In case of Windows Firewall, it prompts you in first run.) | ||
| + | |||
| + | If you encounter timeouts, you might want to put a switch between your router and client to facilitate the flashing process. The tips below might not be needed after that. | ||
| + | |||
| + | Also, you //might// have to lower your ethernet link to 10 Mbps Half Duplex in order to finish the process. | ||
| + | |||
| + | </ | ||
| + | |||
| + | |||
| + | <WRAP center round important 95%> | ||
| + | |||
| + | A few users reported that flashing via TFTP is not always possible on some devices. Apparently there was a slight hardware change in some produced devices that causes TFTP inside u-boot to expect [[https:// | ||
| + | There is a [[https:// | ||
| + | |||
| + | **TLDR:** | ||
| + | |||
| + | If you want to stick to flashing via TFTP: | ||
| + | * on Windows use [[https:// | ||
| + | * on every other platform you could use [[https:// | ||
| + | |||
| + | Otherwise your best option is to establish a serial connection to the device and then load the image via '' | ||
| + | |||
| + | Other variants and more information is provided in the aforementioned forum thread. | ||
| + | |||
| + | </ | ||
| + | |||
| + | Similar instructions can be found as posted by OpenWrt forum member **yoq** [[https:// | ||
| + | |||
| + | ==== Flash Layout ==== | ||
| + | |||
| + | ^ | ||
| + | ^ Layer0 | ||
| + | ^ Layer1 | ||
| + | ^ Layer2 | ||
| + | ^ <color magenta> | ||
| + | ^ filesystem | ||
| + | ^ Layer3 | ||
| + | ^ Size in KiB | 128 KiB | ||
| + | ^ Name | ||
| + | ^ <color magenta> | ||
| + | ^ filesystem | ||
| + | * These seemingly irregular values are the result of the dynamic mtd splitter resizing the OpenWrt kernel and rootfs ' | ||
| + | |||
| + | ===== Hardware ===== | ||
| + | See the [[/ | ||
| + | |||
| + | ==== Pictures of the board ==== | ||
| + | |||
| + | The case is a bit hard to open, start with the two screws. Then start prying the lid from the bottom of the case, starting at the side with the ethernet connectors, There are 11 notches all around keeping the lid in place. They come loose by pushing the bottom part of the case outward. | ||
| + | |||
| + | **v1** | ||
| + | |||
| + | {{media: | ||
| + | |||
| + | **v1.1** | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ==== Serial ===== | ||
| + | |||
| + | <WRAP center round alert 60%> | ||
| + | At least one user has reported 3.3 V logic levels, **//not//** TTL (5 V) levels | ||
| + | </ | ||
| + | |||
| + | ^ Serial connection parameters for Archer C2 AC750 v1 | 115200, 8N1 | | ||
| + | |||
| + | The Serial connector is labeled ' | ||
| + | |||
| + | Ethernet side of PCB | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | Led side of PCB | ||
| + | |||
| + | Where ' | ||
| + | |||
| + | **Soldering** | ||
| + | |||
| + | The GND pin may be a bit hard to solder, i needed to scratch away some paint from the PCB to make a large enough connection. On some versions you need to solder 2 bridges to get serial port working. You need good soldering experiences for that! | ||
| + | |||
| + | **Board picture (v1)** | ||
| + | |||
| + | UART isn't populated, it's indicated by a red rectangle on the picture below (click for bigger size). | ||
| + | |||
| + | {{: | ||
| ===== Switch ====== | ===== Switch ====== | ||
| + | |||
| The C2 uses a external GBit switch, connected by MDIO bus. Network traffic to the CPU is passed through the internal switch of the MT7620A SoC: | The C2 uses a external GBit switch, connected by MDIO bus. Network traffic to the CPU is passed through the internal switch of the MT7620A SoC: | ||
| + | |||
| < | < | ||
| | | ||
| Line 49: | Line 207: | ||
| + | |||
| + | <WRAP center round info 60%> | ||
| + | Earlier versions of this article suggested “the driver for OpenWrt” (for the RTL8367R(B) switch chip) would have limited the range of usable 802.1q VLAN IDs to 1 – 31. | ||
| + | |||
| + | While this may have been true for some earlier builds (could not confirm immediately), | ||
| + | |||
| + | < | ||
| + | config switch | ||
| + | option name ' | ||
| + | option reset ' | ||
| + | option enable_vlan ' | ||
| + | option enable_vlan4k ' | ||
| + | </ | ||
| + | |||
| + | If you edit the switch VLAN configuration in LuCI, it may add the '' | ||
| + | </ | ||
| + | |||
| + | <WRAP center round important 60%> | ||
| + | OpenWrt releases 21.02.0 — 21.02.3 (the latest official release as of this writing) appear to have a regression in their default network configuration which makes the inner (MT7620A) switch visible in LuCI as '' | ||
| + | |||
| + | The router works as it should but configuring VLANs through LuCI may not work as expected and only the outer switch ('' | ||
| + | |||
| + | Until fixed in later releases, you can work around the issue by removing the extraneous '' | ||
| + | |||
| + | < | ||
| + | uci delete network.@switch[0] | ||
| + | uci commit | ||
| + | reboot | ||
| + | </ | ||
| + | </ | ||
| ===== UBoot ====== | ===== UBoot ====== | ||
| Line 70: | Line 258: | ||
| ===== GPIO ====== | ===== GPIO ====== | ||
| - | ^ Color ^ Name ^ GPIO ^ Polarity ^ | + | ^ Color |
| - | | Green | LAN | 1 | Active low | | + | | Green |
| - | | Green | USB | 11 | Active low | | + | | Green |
| - | + | ||
| - | + | ||
| - | ===== Support Status ===== | + | |
| - | The C2 is not officially supported by OpenWrt yet. All the files provided here, are results of the amazing work our community have been doing together. Check the Forum Threads section for more information and direct contact. | + | |
| - | + | ||
| - | + | ||
| - | ===== Installation (V1 model only) ===== | + | |
| - | + | ||
| - | <WRAP center round important 60%> | + | |
| - | The following procedure works only on the **<color # | + | |
| - | </ | + | |
| - | + | ||
| - | OpenWrt can be flashed via TFTP using an unofficial recovery image provided by the OpenWrt' | + | |
| - | + | ||
| - | To flash the recovery image, start a TFTP server from IP address 192.168.0.66 and serve the recovery image named ArcherC2V1_tp_recovery.bin that you have extracted. Connect your device to the LAN port, then press the WPS/Reset button and power it up. Keep pressing the WPS/Reset button for 10 seconds. It will try to download the recovery image and flash it. You must set your machine' | + | |
| - | + | ||
| - | It can take up to 20-25 minutes to finish. When it reaches 100%, the router will reboot itself. | + | |
| - | + | ||
| - | OpenWrt can be accessed at 192.168.1.1. | + | |
| - | + | ||
| - | <WRAP center round alert 60%> | + | |
| - | A few users reported that flashing via TFTP server was only possible when the option "Use anticipation window of" with 1000 bytes was enabled in TFTPD32 for Windows. So, if your flashing process hang at some point, restart the process with this option enabled. | + | |
| - | + | ||
| - | Also, you //might// have to lower your ethernet link to 10 Mbps Half Duplex in order to finish the process. | + | |
| - | </ | + | |
| - | + | ||
| - | + | ||
| - | ===== Upgrade ===== | + | |
| - | + | ||
| - | After successfully flash OpenWrt firmware with the method above, you will be able to directly upgrade it via web interface to the latest release we have from, also forum member, **abnoeh**. You can download **LEDE.for.ArcherC2V1.complied.tar.xz** [[https:// | + | |
| - | + | ||
| - | if you didn't preserved setting when you upgrade it, you will need to enter http:// | + | |
| ===== Forum Threads ===== | ===== Forum Threads ===== | ||
| Line 113: | Line 269: | ||
| Thanks to everyone that contribute to make this possible. | Thanks to everyone that contribute to make this possible. | ||
| - | |||
| - | |||
| ===== Tags ===== | ===== Tags ===== | ||
| - | {{tag> | + | [[meta: |
| + | {{tag> | ||