Atheros SoC and LED mappings

[Dirk van der Walt]

Hi all,

We've been successfully implementing OpenWRT on the EAP-3660.
Unfortunately according to our supplier the EAP-3660 is now at end of life, and the replacement is the M36.

They both contain Ateros SoC chips:
ath_ahb: wifi0: Atheros 2315 WiSoC: mem=0xb0000000, irq=3

It seems that although the M36 has extra features out of the box, the hardware is pretty much the same.
Although the hardware seems to be the same there is unfortunately quite a price difference between the two, but the EnGenius proved much more reliable that the Ubiquity hardware.

On both of the models, the LEDs does not work as desired after flushed with OpenWRT
The following happens to the LEDs:

EAP-3660:
1.) Power LED stays on ( Working as desired)
2.) LAN LED indicates traffic (Working as desired)
3.) WLAN LED is off (I'd like it to indicate traffic)

M36
1.) Power LED stays on when WiFi is disabled and indicates traffic when WiFi is enabled (Wrong LED shows WiFi traffic)
2.) LAN LED is off ( should indicate LAN traffic)
3.) WLAN LED is off ( should indicate Wifi traffic instead of the power LED which indicates WiFi traffic)

I've played around with gpioctl to test the LED's and only the M36 responded:
The WLAN LED on the M36 respond to gpioctl set 2
The following command moved the flickering power LED to the correct LED: (default was 7)
sysctl -w dev.wifi0.ledpin=2

On the E-3660 there was no way I could get the WLAN LED going.
On the M36 there was no way I could get the LAN LED going.

Any suggestions, or help to correct these issues will be greatly appreciated.

Kind regards