Support for EAP225-Wall

[elcovv1]

Hi,

I'm thinking about buying the EAP225-Wall. The model has been mentioned in a thread about the EAP225-v3, but it looks like it would be a separate effort:

Anyone working on TP-Link EAP225?

Looking at the GPL sources, the EAP225-Wall is supposedly based on the AP151 reference design. For now, I've focussed on the devices that were based on the AP152 reference board. The FCC photos seem to confirm this, as the board has a QCA9561. The picture of the 5GHz radio is proper potato-quality, but if I had to guess I would say it's also a QCA9886. It does appear that the mach-eap225-wallv2.c file is of similar complexity as the EAP245v3. This would mean that the device has a bootloader tha…

What are the chances that openwrt support will be available for this router?

[svanheule]

Luck has it @Borromini sent me one two weeks ago, so the port is basically done.

I need to clean up the commits, but if you want you can build it already.

svanheule/openwrt

[Borromini]

How's your MT7621 chops eh? For a crack at that TP-Link EAP235-Wall once they start to sell that for real

[svanheule]

Challenge accepted!

Hopefully it doesn't need any difficult patches like the original EAP AC devices, then it shouldn't be too hard

[Borromini]

Hehe Cool!

[svanheule]

And by using KEY_LIGHTS_TOGGLE for the LED button, there is a trigger to use for toggling the LED. An example script can be found in the other topic linked below, and should probably go on the wiki if this device gets merged.

Toggle LED with push button

The hardware.button wiki page lists KEY_LIGHTS_TOGGLE as one of the supported keys, for which I can add a script in /etc/rc.button/lights_toggle. To disable the LED(s), I could probably just loop over all buttons and set trigger to 'none' and default to '0'. That would mean I lost all user config though, so I'll have a look at how to avoid that. Edit: Found a similar use case for KEY_LIGHTS_TOGGLE Edit: DTS entry: led { label = "LED button"; linux,code = <KEY_LIGHTS_TOGGLE>; gpios = <&…

[m4rv1n]

They did at least release the EAP230-WALL recently, so are we lucky and will this one be on the list of supported devices as well? I might even help paying the hardware so you guys could get your hands on one.

[Borromini]

The EAP-235 is popping up on Amazon for Europe as well now, so here's hoping they might actually be shipping somewhere in December.

[Sanduur]

Hey guys,

I have one of EAP225-WALL v2, while official web page https://openwrt.org/toh/tp-link/eap225 tells me, Qualcomm Atheros QCA9561, Qualcomm Atheros QCA9886.

The 2.4GHZ works fine, but it seems to have QCA9888 for 5GHZ, not QCA9886 like in the description:

$ dmesg | grep -i qca
[ 0.000000] SoC: Qualcomm Atheros QCA956X ver 1 rev 0
[ 44.385556] ath10k_pci 0000:00:00.0: qca9888 hw2.0 target 0x01000000 chip_id 0x00000000 sub 0000:0000
[ 44.767294] ath10k_pci 0000:00:00.0: failed to fetch board data for bus=pci,bmi-chip-id=0,bmi-board-id=20 from ath10k/QCA9888/hw2.0/board-2.bin
[ 45.385639] ath10k_pci 0000:00:00.0: failed to fetch board-2.bin or board.bin from ath10k/QCA9888/hw2.0

As you see in dmesg, the 5GHZ is not working and it is also not in the config now (of course):

$ cat /etc/config/wireless

config wifi-device 'radio0'
option type 'mac80211'
option path 'platform/ahb/18100000.wmac'
option channel '1'
option band '2g'
option htmode 'HT20'
option disabled '1'

config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'

Can I fix this? Any ideas? If I run stock firmware, the 5GHZ band works really well.