-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ar71xx: add support for TP-Link Archer A7 v5 #1462
Conversation
this is identital to Archer C7 v5, but with a different flash layout TP-Link Archer C7 v5 is a dual-band AC1750 router, based on Qualcomm/Atheros QCA9563+QCA9880. Specification: 750/400/250 MHz (CPU/DDR/AHB 128 MB of RAM (DDR2) 16 MB of FLASH (SPI NOR) 3T3R 2.4 GHz 3T3R 5 GHz 5x 10/100/1000 Mbps Ethernet 10x LED, 2x button UART header on PCB Flash instruction: Upload lede-ar71xx-generic-archer-c7-v5-squashfs-factory.bin via Web interface Flash instruction using TFTP recovery: Set PC to fixed ip address 192.168.0.66 Download lede-ar71xx-generic-archer-c7-v5-squashfs-factory.bin and rename it to ArcherC7v5_tp_recovery.bin Start a tftp server with the file tp_recovery.bin in its root directory Turn off the router Press and hold Reset button Turn on router with the reset button pressed and wait ~15 seconds Release the reset button and after a short time the firmware should be transferred from the tftp server Wait ~30 second to complete recovery. With help from: Michael Hilgenstock Signed-off-by: Arvid E. Picciani <aep@exys.org>
{"fs-uboot", 0x20000, 0x20000}, | ||
|
||
{"os-image", 0x40000, 0x180000}, /* Stock: base 0x40000 size 0x120000 */ | ||
{"file-system", 0x1c0000, 0xd80000}, /* Stock: base 0x160000 size 0xde0000 */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could dynamic partitioning be used here by deleting the os-image and file-system partitions and replacing them with {"firmware", 0x40000, 0xf00000},
? It looks like build_image() can create the two partitions on the fly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you could, but i'd rather copy paste from the other devices. It's already difficult enough to get something upstream. Probably easier when there's nothing new.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for adding dynamic partitioning.
I'm currently in the process of adapting all ar71xx targets to use this, as the os-image partition size of 0x180000 is too small and causes build errors using kernel 4.14
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xback very nice. it usually takes around 6 months for a PR to get merged, so no rush. Let me know when the existing targets changed and i'll adapt the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pushed the changes for the other ar71xx targets, switching most of them to dynamic partitioning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. I also bought an Archer A7 mistakenly thinking it would be supported by openwrt.
OVERLY WORDY INFO FOLLOWS FOR NOOBS LIKE MYSELF:
I created a ubuntu VirtualBox and tried to build using the pull request via:
git clone https://github.com/openwrt/openwrt.git
cd openwrt
git fetch origin +refs/pull/1462/merge
git checkout FETCH_HEAD
make menuconfig
make -j8
But this ran into problems for the above and no openwrt-ar71xx-generic-archer-a7-v5-squashfs-factory.bin was created.
However, with this patch on just master openwrt, I was able to create the bin file.
git checkout master
git apply [patch_name.patch]
rm .config
make defconfig
make menuconfig
One gotcha here is that I needed to change to "ath79" before "TP-LINK Archer A7 v5" would show under "Default Profile".
Then I just ran "make -j8" again and the bin file was created. I logged into the factory router GUI, and uploaded this bin. Everything came back and I had SSH access to 192.168.1.1.
There is no LuCI GUI in this build by default and opkg is not yet supporting this ath79 so in order to get this I had to rebuild with luci:
./scripts/feeds update
./scripts/feeds install -a -p luci
make menuconfig
make -j8
SCP (now the sysupgrade bin) into the router's /tmp dir and use sysupgrade from the router to get it updated. Done. Have LuCI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your comment! I've been putzing about, unable to create the *factory.bin.
I have just one quick question. To which patch are you trying to link? Chrome shows "this patch" in bold and elinks displays it as just grey text.
Also, thank you to aep!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be honest, I had a good bit of help from the IRC channel. They pointed me at this patch. In fact, I believe they crated a patch link for me. I think I recall them saying it was from the mailing list as opposed to the pull request.
Using the patch linked here, I was able to follow my recipe pasted above. Good luck!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I want to be able to opkg install
stuff, will this version work?
I assume ath79
device tree hasn't been released, so we won't have opkg repository for it, is that right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been installing downloaded .ipk files.
Hey @aep thanks for your comments and help. However, I get the message 'invalid file type'. Also I have tried to flash via TFTP.
After the given TFTP Instructions the Router only reboots with it's given tp-link Firmware Am I using the wrong release, since you are saying download I appreciate your help. |
Hi @8grad . ignore the commit message, this is just copy paste required for upstreaming in openwrt. You need to build this pull request and select archer A7 in menuconfig, then use lede-ar71xx-generic-archer-a7-v5-squashfs-factory.bin from bin. note the a, not c. see https://help.github.com/articles/checking-out-pull-requests-locally/ for how to get a pull request into your local clone |
Hey @aep, |
Thank you @aep. So far this is working great for me. |
Hey @aep, |
@xhbl A7 US version may be yet another board. would you be able to take a picture of the board? |
Hey @xhbl
|
oh... thats actually my fault, i forgot to rename the leds in bringup. will fix it when i get time to do that. thanks for the find |
Great! works like a charm! |
+1; patched 18.06.1, built and installed using factory firmware upgrade, and the installation went perfectly |
It's supposed to be working install instructions man, put some effort in it. |
this device was added to the ath79 target now: 1e4ee63 |
Indeed, I don't see any valid reason to keep it open. Thanks! |
Does the 5G work with this patch? I only see radio0 is enabled. |
@jslee7897 yes, 5ghz radio works fine. Please note that this PR is abandoned in favor of upstream change 1e4ee63 |
Hello @aep, I am trying to flash my AC1750 A7. I'm super new to open source firmware for routers. I have flashed a Buffalo router with DDWRT firmware years ago. There was not a compatibility issue with the Buffalo router, so flashing via Web Interface was easy. I am looking at this page -- https://openwrt.org/toh/hwdata/tp-link/tp-link_archer_a7_v5 Is the stable build of OpenDDWRT only available for: Can you send me in the right direction so I don't cause my AC1750 A7 to boot loop or brick? |
Personally i recommend flashing via tftp, because it always works, even after you flashed a broken firmware. It's rather difficult to brick modern tplink devices, so don't worry too much. This PR was never merged. Ignore it and go with whatever the wiki says. |
A word of caution here. Snapshot images are the development firmware images and have no web interface by default (you need to connect through SSH remote terminal and install it). They are also updated frequently so you won't be able to install some packages after a week or so.
According to the commit adding support for this device, you can use both web interface and tftp recovery. I updated the wiki, now both "GUI OEM" and "u-boot recovery" are listed as available.
It was added after OpenWrt 18.06 release and new devices aren't backported to older releases. It will be in the next OpenWrt release, the 19.something that is going to happen in a few months.
lol, OpenWrt and DDWrt are two different projects. |
Thanks for the quick replies @aep @bobafetthotmail I’m returning my TP-Link AC1750 A7 due to lack of support for open source firmware and no VPN client option with stock firmware. The replacement router will be an Asus AC3200. According to my research, Asus routers have Merlin firmware that allows for OpenVPN client options and most are compatible with stable OpenWRT and DDWRT. |
this is identital to Archer C7, but with a different flash layout
TP-Link Archer C7 v5 is a dual-band AC1750 router, based on Qualcomm/Atheros
QCA9563+QCA9880.
Specification:
750/400/250 MHz (CPU/DDR/AHB
128 MB of RAM (DDR2)
16 MB of FLASH (SPI NOR)
3T3R 2.4 GHz
3T3R 5 GHz
5x 10/100/1000 Mbps Ethernet
10x LED, 2x button
UART header on PCB
Flash instruction:
Upload lede-ar71xx-generic-archer-c7-v5-squashfs-factory.bin via Web interface
Flash instruction using TFTP recovery:
Set PC to fixed ip address 192.168.0.66
Download lede-ar71xx-generic-archer-c7-v5-squashfs-factory.bin
and rename it to ArcherC7v5_tp_recovery.bin
Start a tftp server with the file tp_recovery.bin in its root directory
Turn off the router
Press and hold Reset button
Turn on router with the reset button pressed and wait ~15 seconds
Release the reset button and after a short time
the firmware should be transferred from the tftp server
Wait ~30 second to complete recovery.
With help from: Michael Hilgenstock
Signed-off-by: Arvid E. Picciani aep@exys.org