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/10/08 23:21] – [Info] s3sebastian | 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 ====== | ||
| - | ===== Supported Versions ===== | + | {{:media:tplink:archer-c2-v1:archer-c2-ac750-v1.png? |
| - | ---- datatable ---- | + | |
| - | cols | + | |
| - | headers | + | |
| - | align : c, | + | |
| - | filter | + | |
| - | filter | + | |
| - | ---- | + | |
| + | <WRAP 80%> | ||
| + | <tabbox Hardware Highlights> | ||
| ---- datatable ---- | ---- datatable ---- | ||
| - | cols : Unsupported Functions_unsupporteds | + | cols : Model, Versions, CPU, CPU MHz, Flash MB_mbflashs, |
| + | header | ||
| + | align : c, | ||
| filter | filter | ||
| filter | filter | ||
| ---- | ---- | ||
| - | + | <tabbox OpenWrt support> | |
| - | + | ||
| - | ===== Hardware Highlights ===== | + | |
| ---- datatable ---- | ---- datatable ---- | ||
| - | cols : Model, Versions, | + | cols : Brand, |
| - | header | + | headers |
| - | align : | + | align : c, |
| filter | filter | ||
| filter | filter | ||
| ---- | ---- | ||
| + | <tabbox Hardware details> | ||
| + | ^ [[wp> | ||
| + | ^ Vendor | ||
| + | ^ [[docs: | ||
| + | ^ [[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: | ||
| - | ===== Installation ===== | + | <tabbox Firmware downloads> |
| ---- datatable ---- | ---- datatable ---- | ||
| - | cols : Model, Versions, Supported Current Rel, Firmware OpenWrt | + | 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 | + | headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock |
| align : c,c,c | align : c,c,c | ||
| filter | filter | ||
| filter | filter | ||
| ---- | ---- | ||
| + | </ | ||
| + | </ | ||
| + | ===== Installation ===== | ||
| -> [[docs: | -> [[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%> | <WRAP center round important 60%> | ||
| - | The following | + | The following |
| + | Use only the provided recovery image if you don' | ||
| + | |||
| + | Avoid renaming | ||
| + | Providing an image without proper bootloader to TFTP recovery bricks | ||
| </ | </ | ||
| - | OpenWrt can be flashed via TFTP using an unofficial recovery image provided by the OpenWrt' | + | If you feel uncomfortable doing this, grab the prepped 19.07.1 image linked to above and skip this section. |
| - | To flash the recovery | + | The C2v1 TFTP recovery |
| + | An official stock TPLink firmware file has a 512 byte header, which needs to be stripped | ||
| + | You need access | ||
| + | Instructions below are taken from the git commit that added support into OpenWrt. | ||
| - | It can take up to 20-25 minutes to finish. When it reaches 100%, the router will reboot itself. | + | 1. Download a stock TP-Link Firmware file [[https:// |
| - | OpenWrt can be accessed at 192.168.1.1. | + | 2. Extract u-boot from the binary file: |
| - | <WRAP center round info 60%> | + | < |
| - | A few users reported that flashing via TFTP server | + | |
| + | 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 | ||
| + | |||
| + | If you encounter timeouts, you might want to put a switch between | ||
| 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. | ||
| + | |||
| </ | </ | ||
| - | ===== Upgrade ===== | + | <WRAP center round important 95%> |
| - | After successfully flash OpenWrt firmware with the method above, you will be able to directly upgrade it via web interface | + | A few users reported that flashing |
| + | There is a [[https://forum.openwrt.org/t/tftp-download-from-tp-link-archer-c2-does-not-work-properly/ | ||
| - | If you didn't preserved setting when you upgrade it, you will need to enter '' | + | **TLDR:** |
| + | If you want to stick to flashing via TFTP: | ||
| + | * on Windows use [[https:// | ||
| + | * on every other platform you could use [[https:// | ||
| - | ===== creating TFTP recovery | + | Otherwise your best option is to establish a serial connection to the device and then load the image via '' |
| - | The C2v1 TFTP recovery overwrites the uboot partition, hence it must be included | + | Other variants and more information is provided |
| - | An official stock TPLink firmware file has a 512 byte header, which needs to be stripped for TFTP: | + | |
| - | dd if=c2v1_stock_firmware.bin of=ArcherC2V1_tp_recovery.bin bs=1 skip=512 | + | </ |
| - | To create a recovery | + | |
| - | dd if=c2v1_stock_firmware.bin of=c2v1_uboot.bin bs=1 skip=512 count=131072 | + | Similar instructions can be found as posted by OpenWrt forum member **yoq** [[https://forum.openwrt.org/ |
| - | cat c2v1_uboot.bin openwrt-squashfs-sysupgrade.bin | + | |
| + | ==== Flash Layout ==== | ||
| + | |||
| + | ^ | ||
| + | ^ Layer0 | ||
| + | ^ Layer1 | ||
| + | ^ Layer2 | ||
| + | ^ <color magenta> | ||
| + | ^ filesystem | ||
| + | ^ Layer3 | ||
| + | ^ Size in KiB | 128 KiB | ||
| + | ^ Name | ||
| + | ^ <color magenta>mountpoint</ | ||
| + | ^ filesystem | ||
| + | * These seemingly irregular values are the result of the dynamic mtd splitter resizing the OpenWrt kernel and rootfs ' | ||
| ===== Hardware ===== | ===== Hardware ===== | ||
| - | ==== Info ==== | + | See the [[/ |
| - | ^ [[wp> | + | |
| - | ^ Vendor | + | ==== Pictures of the board ==== |
| - | ^ [[docs:techref:bootloader]] | + | |
| - | ^ [[docs: | + | 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. |
| - | ^ [[docs:techref:hardware:cpu|CPU]]/ | + | |
| - | ^ Flash-Chip | Winbond 25Q64BVSIG [[http:// | + | **v1** |
| - | ^ Flash size | 8192 KiB | | + | |
| - | ^ RAM | 64 MiB | | + | {{media:tplink:archer_c2_ac750_t.jpg? |
| - | ^ Wireless No1 | SoC-integrated: MT7620A 2.4GHz 802.11bgn | | + | |
| - | ^ Wireless No2 | On-board chip: MT7610EN 5GHz 802.11ac | | + | **v1.1** |
| - | ^ [[docs:techref:hardware:switch]] | + | |
| - | ^ USB | Yes 1 x 2.0 | | + | {{:media:tplink:archer-c2-v1:archer_c2_v1.1_front.jpg?400|}} {{:media:tplink:archer-c2-v1:archer_c2_v1.1_back.jpg?400|}} |
| - | ^ [[docs: | + | |
| - | ==== Pictures of the Ver. 1.0 board ==== | ||
| - | {{: | ||
| ==== Serial ===== | ==== Serial ===== | ||
| - | Serial port: | + | <WRAP center round alert 60%> |
| + | At least one user has reported 3.3 V logic levels, **// | ||
| + | </ | ||
| - | ethernet <- VCC GND TxD RxD -> Leds | + | ^ Serial connection parameters for Archer C2 AC750 v1 | 115200, 8N1 | |
| - | On some versions you need to solder 2 bridges to get serial port working. You need good soldering experiences | + | 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 125: | 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 149: | 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 158: | 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> | ||