Looking for support of TP-Link EAP225 v4

For Developers
21

EAP225-Outdoor v3 support is now merged with 7e4de89e631a. This device won't be very different. Aside from the board name it's pretty much identical.

The watchdog on GPIO3/GPIO4 can always be added at a later point. The same hardware is at least also present on the EAP245v1, so perhaps this is also something all (single port) devices in this series have in common.

22

I did some tests using gpio-restart. They worked as expected for a regular reboot. This is a hack which covers not all cases.
This is the patch for rebooting.

diff --git a/target/linux/ath79/config-5.10 b/target/linux/ath79/config-5.10
index 75e282b..f8b9dc7 100644
--- a/target/linux/ath79/config-5.10
+++ b/target/linux/ath79/config-5.10
@@ -161,6 +159,8 @@ CONFIG_PHYLIB=y
 # CONFIG_PHY_AR7200_USB is not set
 # CONFIG_PHY_ATH79_USB is not set
 CONFIG_PINCTRL=y
+CONFIG_POWER_RESET=y
+CONFIG_POWER_RESET_GPIO_RESTART=y
 CONFIG_RATIONAL=y
 CONFIG_REALTEK_PHY=y
 CONFIG_REGMAP=y
diff --git a/target/linux/ath79/dts/qca9563_tplink_eap225-v4.dts b/target/linux/ath79/dts/qca9563_tplink_eap225-v4.dts
index 73de898..7e677a9 100644
--- a/target/linux/ath79/dts/qca9563_tplink_eap225-v4.dts
+++ b/target/linux/ath79/dts/qca9563_tplink_eap225-v4.dts
@@ -27,6 +27,15 @@
 			gpios = <&gpio 9 GPIO_ACTIVE_HIGH>;
 		};
 	};
+
+	gpio-restart {
+		compatible = "gpio-restart";
+		gpios = <&gpio 4 GPIO_ACTIVE_LOW>;
+		priority = <254>;
+		active-delay = <100>;
+		inactive-delay = <100>;
+		wait-delay = <1800>;
+	};
 };
 
 &eth0 {
diff --git a/target/linux/ath79/dts/qca9563_tplink_eap2x5-1port.dtsi b/target/linux/ath79/dts/qca9563_tplink_eap2x5-1port.dtsi
index 127741f..bbdfb01 100644
--- a/target/linux/ath79/dts/qca9563_tplink_eap2x5-1port.dtsi
+++ b/target/linux/ath79/dts/qca9563_tplink_eap2x5-1port.dtsi
@@ -108,7 +108,7 @@
 
 	phy6: ethernet-phy@6 {
 		reg = <6>;
-		reset-gpios = <&gpio 11 GPIO_ACTIVE_LOW>;
 	};
 };
23

I had a look at TPLink's gpl code:

TPLink is using linux kernel 3.38.

  • linux/kernels/linux-3.3.8/drivers/net/ethernet/atheros/ag71xx/ag71xx_phy.c
    • In function ag71xx_phy_connect(struct ag71xx *ag) there is an explicit mdio bus reset which is not visible in the openwrt source.
  • linux/kernels/linux-3.3.8/drivers/net/phy/rtl8211.c
    • In rtl8211_config_init(struct phy_device *pdev) there is an explicit software reset (Bit 15) on init.
    • The phy is described in the openwrt source in drivers/net/phy/realtek.c
    • In rtl8211f_config_init(struct phy_device *phydev) (openwrt source) there is no reset and instead the delay configuration.

Various interesting files:

linux/kernels/linux-3.3.8/Documentation/devicetree/bindings/net/qcom-ag71xx.txt
linux/kernel/linux-3.3.8/arch/mips/configs/board956x_eap225v<x>_defconfig
24

Thanks for investigating! In 5.15 this soft reset is also performed by the mainline driver (used by OpenWrt). 5.10 doesn't have this reset yet.

Now, this all occurs when initialising the phy on boot, not when shutting it down on shutdown or restart. If the ethernet port already works on both boot and reboot, I don't expect this soft reset to help make it work in u-boot after a reboot. Unless they've updated the bootloader, these devices don't have emergency TFTP loading support anyway, and you basically need to be next to the device to have serial access.

If you would like to add full reboot support using GPIO4, that's also fine for me. Just make sure you describe GPIO3, GPIO4, and the associated hardware in the commit message.

25

Hi,
I still have problem with the latest Snapshot image (Aug 10) in terms of EAP 225 v3 Outdoor (same as EAP225 v4).

  • Successfully flashed with 'cliclientd stopcs` workaroung from stock GUI
  • First boot is ok...I am able to connect via SSH, but when I set the root passwd and soft reboot from command line after that I am unable to reach the device
  • Only cold restart (remove the POE power chord) helps!
    Do you already have a fix to resolve this issue? Does anyone have a compiled working image for EAP 222 v3 outdoor (should be the same as EAP225 v4)?
1 Like
26

Does this device use dsa to 100%?
Swconfig is included in the build but it doesn’t seem to use it in the network config and it still works?

27

Hi Guys! Any update on this? Can we expect some fix in next releases?

28

Hello, is EAP 225 v4 supported in 22.03? If not, does anyone know why and when it will be added? Thanks!

29

Due to the need of a lot of backporting, EAP225v4 and EAP225 Outdoor v3 will be supported with the 23.xx release. You can currently use the snapshots.
See the EAP225 Outdoor v3 - thread for a more detailed explanation.

30

Do any of you experience something similar to a memory leak for the 5GHz or something?
It has happened two times now after I installed OpenWrt on the 225v4. It runs at full speed at 5GHz about a week and then boom it gets very unstable speed if any speed at all with full connection. And after a power cycle it works again with full speed?
I have tried disabled the ACK setting that where supposed to make iOS work better so I thought I had found the problem last week but it’s back.

https://forum.openwrt.org/t/eap225v4-missing-all-ath10-drivers
But I don’t know if it is something with the Ath10-ct driver because it wasn’t included when I build the firmware?

31

You might try this

although TP-link EAP225 V4 has 128Mb ....

32

To be hounest I for this time got tired of Linux and wifi drivers and bought a wifi6 AP instead I simply run it on original firmware.

33

5GHz works for me

iwinfo phy0-ap1 ass | grep TX

	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1     78609 Pkts.
	TX: 360.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 2      4237 Pkts.
	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1    174349 Pkts.
	TX: 360.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 2      5602 Pkts.
	TX: 360.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 2    277530 Pkts.
	TX: 360.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 2    339514 Pkts.
	TX: 90.0 MBit/s, VHT-MCS 2, 40MHz, VHT-NSS 2     15353 Pkts.
	TX: 324.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 2     10960 Pkts.
	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1     11618 Pkts.
	TX: 240.0 MBit/s, VHT-MCS 5, 40MHz, VHT-NSS 2    325863 Pkts.
	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1     17648 Pkts.
	TX: 360.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 2      1631 Pkts.
	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1      1290 Pkts.
	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1      2938 Pkts.
	TX: 360.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 2       319 Pkts.
	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1       405 Pkts.
	TX: 180.0 MBit/s, VHT-MCS 8, 40MHz, VHT-NSS 1     23435 Pkts.
	TX: 300.0 MBit/s, VHT-MCS 7, 40MHz, VHT-NSS 2         6 Pkts.
	TX: 90.0 MBit/s, VHT-MCS 2, 40MHz, VHT-NSS 2       383 Pkts.
	TX: 240.0 MBit/s, VHT-MCS 5, 40MHz, VHT-NSS 2        95 Pkts.

MIPS: machine is TP-Link EAP225 v4
SoC: Qualcomm Atheros QCA956X ver 1 rev 0
DISTRIB_DESCRIPTION='OpenWrt 23.05.0-rc3 r23389-5deed175a5'

ath10k-board-qca9888 - 20230804-1
ath10k-firmware-qca9888-ct-full-htt - 2020-11-08-1

34

Posting here because this thread seems to be the authoritative one referred to by OpenWRT's device wiki page.

I have successfully flashed v4 (Wall) hardware with release 23.05.4 today. Everything appears to be working. I'm going to kick the VLAN and throughput tyres a bit tomorrow.

I followed the instructions for v3+ hardware here https://openwrt.org/toh/tp-link/eap225 - each step of which was necessary, but which all worked as advertised.

If all goes well I would like to see the v4 hardware recognised as working with 23.05.4.

35

While looking for an outdoor AP, I noticed TP-Link is now selling a V4 version of the 225 Outdoor. I can't find any info on it in the FCC database, so unsure what could have changed. Has anyone gotten their hands on a 225 Outdoor V4 yet?