TP-Link archer c6 v4 openwrt

that was clearly a mistake, since it's not supported and if it only got 8mb flash, it never will be.

1 Like

Ouch, this one is totally different architecture from previous revisions, and for worse. 3.5mb oem firmware kind of fits A/B layout in that teardown repo.

it doesn't work no

Archer C6 v4 uses an ARM CPU designed by TP-Link which is an closed source model and not supported by Linux kernel.

In my opinion, the TP1900BN likely never supported (or will take a LOT time to get support, due to need reverse engineering to get support)

Well then it will not have any version of openwrt

1 Like

That you were told yesterday already.

V3 compatible version of OpenWrt with V4? The product appears identical to the V3 but there is no information available about its processor

It is totally different from v3

  • arm in place of mips
  • less (too little) flash
  • does not run linux

Stop flogging the dead horse, you've been told multiple times, it's a dead end.

1 Like

I already bought it for that reason and it turns out that it doesn't work

I can't change it anymore, I already have it paid for in 3 months

I know that arm64 does not use that much resource

well thanks for everything

1 Like

No way.

Archer C6 v1/v2 uses an mips qca9563 (ath79) - supported
Archer C6 v3 uses MT7621AT (ramips) - supported
Archer C6 v4 uses an proprietary arm-based cpu from tp-link - not supported.

arm processors have variants which may not compatible each other.

Anyway, Archer C6 v4 flash size (4MB) is very small for normal and secure OpenWRT operation, and developers dropped official support after 19.07 release for all 4MB devices, so, all of efforts are useless and should not be expected.

Opinion: You should give back that router (if possible) and buy an filogic variant of ax3000t from Xiaomi, the cost/benefit is very cool.

At this point -even with considerable effort and a resulting image that wouldn't be fit for official images (no webinterface, opkg and many other basic features)- it is impossible to fit OpenWrt into 4 MB flash (see e.g. Can't connect to router page - #17 by slh), as such, this is a hard game over for merging new (4 MB flash-) device support.

1 Like

It is 8M flash partitioned in two slots by OEM, but the main deal crasher is totally new closed system architecture.

1 Like
148           0x94            uImage header, header size: 64 bytes, header CRC: 0xB2DA8F2, created: 2022-03-31 02:39:24, image size: 66344 bytes, Data Address: 0x41C00000, Entry Point: 0x41C00000, data CRC: 0x9B9B94BB, OS: Firmware, CPU: ARM, image type: Standalone Program, compression type: lzma, image name: "U-Boot 2014.04-rc1 for leopard_e"
4133463       0x3F1257        eCos RTOS string reference: "eCost(sysCount) %u"
4133604       0x3F12E4        eCos RTOS string reference: "eCost(sysCount)"

Leopard_e leads to other evil twin

uses Qualcomm CPU, nothing else

Unlikely, also small flash explains why OEM code has so little function.

tp link has responded

I just don't use the flash

what he wears

The router has a Qualcomm CPU processor and 128 MB of RAM.


Less more than they haven't closed my post

Now I need you to tell me tp link the flash

You have been told that the custom CPU makes this effectively a non-starter. You may want to look at other firmware options, but OpenWrt is not going to support this.

If you'd like to try to make OpenWrt support available for this device, you can start the actual development work by following this guide: