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 [2020/04/12 14:09] – [Installation] Typo borromini | 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 ====== | ||
| + | |||
| + | {{: | ||
| <WRAP 80%> | <WRAP 80%> | ||
| Line 47: | Line 49: | ||
| ===== Installation ===== | ===== Installation ===== | ||
| -> [[docs: | -> [[docs: | ||
| - | |||
| <WRAP center round important 60%> | <WRAP center round important 60%> | ||
| - | The following procedure | + | The following procedure |
| </ | </ | ||
| As per the instructions in the [[https:// | As per the instructions in the [[https:// | ||
| OpenWrt 19.07.1 can be flashed via TFTP using an unofficial recovery image provided [[https:// | OpenWrt 19.07.1 can be flashed via TFTP using an unofficial recovery image provided [[https:// | ||
| - | |||
| ==== Creating an OpenWrt TFTP recovery image ==== | ==== 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. | If you feel uncomfortable doing this, grab the prepped 19.07.1 image linked to above and skip this section. | ||
| Line 69: | Line 77: | ||
| 2. Extract u-boot from the binary file: | 2. Extract u-boot from the binary file: | ||
| - | '' | + | < |
| 3. Now merge the OpenWrt **sysupgrade** image and the u-boot into one binary: | 3. Now merge the OpenWrt **sysupgrade** image and the u-boot into one binary: | ||
| - | '' | + | < |
| ==== Flashing OpenWRT ==== | ==== Flashing OpenWRT ==== | ||
| Line 84: | Line 91: | ||
| * 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. | * 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.) | ||
| - | <WRAP center round info 60%> | + | If you encounter timeouts, you might want to put a switch between your router and client to facilitate the flashing process. |
| - | If you encounter timeouts, you might want to put a switch between your router and client to facilitate the flashing process. | + | |
| - | + | ||
| - | A few users reported | + | |
| Also, you //might// have to lower your ethernet link to 10 Mbps Half Duplex in order to finish the process. | Also, you //might// have to lower your ethernet link to 10 Mbps Half Duplex in order to finish the process. | ||
| Line 95: | Line 101: | ||
| - | Similar instructions can be found as posted by OpenWrt forum member **yoq** [[https:// | + | <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 ===== | ===== Hardware ===== | ||
| See the [[/ | See the [[/ | ||
| - | ==== Pictures of the Ver. 1.0 board ==== | + | ==== 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. | 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** | ||
| - | ==== Serial ===== | + | {{media: |
| - | Serial port: TTL voltage, 115200 bps, 8N1. | + | **v1.1** |
| + | |||
| + | {{:media: | ||
| + | |||
| + | ==== Serial ===== | ||
| <WRAP center round alert 60%> | <WRAP center round alert 60%> | ||
| Line 117: | Line 156: | ||
| </ | </ | ||
| - | The Serial connector is labeled ' | + | ^ Serial connection parameters for Archer C2 AC750 v1 | 115200, 8N1 | |
| + | |||
| + | The Serial connector is labeled ' | ||
| Ethernet side of PCB | Ethernet side of PCB | ||
| Line 128: | Line 169: | ||
| Led side of PCB | Led side of PCB | ||
| + | Where ' | ||
| - | Where ' | + | **Soldering** |
| - | You can verify this, by using a volt meter to check that ' | + | |
| - | 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. | + | 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)** |
| - | The bootloader of the stock firmware can be interrupted | + | UART isn't populated, it's indicated |
| - | + | ||
| - | From the serial console, you can login to the running linux of a stock firmware with: username ' | + | |
| + | {{: | ||
| ===== 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 165: | 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 189: | Line 261: | ||
| | Green | LAN | 1 | Active low | | | Green | LAN | 1 | Active low | | ||
| | Green | USB | 11 | Active low | | | Green | USB | 11 | Active low | | ||
| - | |||
| ===== Forum Threads ===== | ===== Forum Threads ===== | ||
| Line 198: | Line 269: | ||
| Thanks to everyone that contribute to make this possible. | Thanks to everyone that contribute to make this possible. | ||
| - | |||
| ===== Tags ===== | ===== Tags ===== | ||
| [[meta: | [[meta: | ||
| {{tag> | {{tag> | ||